The quick answer
Open Transactions > Manufacturing > Issue Components in the Bulk Actions group, choose the Subsidiary and then the Location, mark the work orders and click Submit. Follow Process Status to Complete, open Processed Records to reach each Work Order Issue, and read its Components tab. A bulk issue takes the committed quantity of each component, so an order with a short component is only partly issued even though Process Status says Complete with 0 Errors. In the example the Zipper Set needed 40 and only 26 were issued, and WO3402 moved to In Process and left the list.
The screenshots show sample data. Person and operating-company names are fictional. Use your own records and values when following the steps.
Before you start
You need Work Orders and Manufacturing Work In Process enabled, Released WIP work orders that are not closed and have components committed at the location, an open posting period, and permission to create work order issues. The Date and Posting Period on the page are used for the issues it creates; the issues in the example carry the page's date and the October period, so check both before you submit. Lot-numbered or bin-managed components may need inventory detail, which a bulk issue may not be able to collect, so try those on a single order first. If a component is also backflushed on a completion, issuing it by hand as well can consume it twice. The Ignore Item Availability choice is described as using the remaining required quantity rather than the committed quantity, which could push inventory negative or fail on inventory detail. That was not tested here.
01. Check the short order first
Open WO3402, the 40 TR-210 Trail Daypack order. It is Released and nothing is used in build. On the Items subtab the Zipper Set needs a Quantity of 40 but only 26 are Committed, with 14 Back Ordered.
02. Open Issue Components and load the list
Click Transactions > Manufacturing and choose Issue Components in the Bulk Actions group. Subsidiary and Customer are required, and Customer reads - All -. Choose Harborview US and the list stays empty. Choose Austin Plant as the Location and the list loads: WO3401, WO3402 and WO3403 with Date, Order #, Item, Memo, the production dates and Order Quantity, an Issue checkbox and an Issue link on each row.
03. Compare the Filter by choices
Filter by decides which orders are listed. Some Items Committed, the default, lists orders where at least one component is committed. Change it to All Items Fully Committed and WO3402 drops out because its zipper is short, leaving WO3401 and WO3403.
Change it to Ignore Item Availability and all four orders appear, including WO3404, which has nothing committed. Then set it back to Some Items Committed. In the account observed the three choices listed about 95, 78 and 101 orders at one location, so expect Ignore Item Availability to list the most.
04. Mark two orders and submit
Check Issue on WO3401 and WO3402 and leave WO3403 for the next shift, then click Submit. NetSuite opens Process Status with submission 22541, Issue Work Orders, Not Started at 0.0%.
05. Follow the submission
Click Refresh. The submission is In Progress at 50.0%, which is one of the two orders done. Click Refresh again until Submission Status is Complete at 100.0% with 0 Errors.
Complete with 0 Errors means both orders were processed. It does not say every component was issued in full. Click Complete to open Processed Records. It lists Work Order #WO3401 with Work Order Issue #WOI3501 and Work Order #WO3402 with Work Order Issue #WOI3502, both Complete with Result Success.
06. Read the issue for the short order
Click Work Order Issue #WOI3502. The Components tab shows 40 TR-210 Shell Fabric Kits but only 26 TR-210 Zipper Sets: the committed quantity, not the 40 the order needs.
Open GL Impact. Each component credits component inventory and debits WIP for the same amount: 164.00 for the shell kits and 35.10 for the zippers. Labor and machine cost are not posted by the issue.
07. Read the work order afterwards
Click Work Order #WO3402 in Created From. Its Status is now In Process. The Zipper Set shows 26 Used in Build, 0 Committed and 14 still Back Ordered, and the Shell Fabric Kit shows 40 Used in Build.
08. Check the list again
Open Issue Components again, choose Harborview US and Austin Plant. Only WO3403 is listed, because WO3401 and WO3402 are now In Process and have left the page.
Check the result
- Process Status shows the submission as Complete at 100.0% with 0 Errors.
- Processed Records lists each marked order with Result Success and a Work Order Issue in Result Record.
- Each issue's Components tab shows the quantities that were really issued, and the work order shows Used in Build, Committed and Back Ordered to match.
- The marked orders are In Process and no longer listed on Issue Components.
Common questions
Why does Issue Components show no work orders?
Subsidiary and Customer are required, and in the account observed the list stays empty until a Location is chosen, even with a Subsidiary chosen. The page lists Released WIP work orders that still have components to issue, and Filter by decides how much has to be committed. An order that is not Released, is not WIP, is already In Process, or has no components committed under the default choice will not normally be listed.
What do Some Items Committed, All Items Fully Committed and Ignore Item Availability mean?
Some Items Committed lists orders where at least one component is committed. All Items Fully Committed lists only orders whose components are all committed, so an order with a short component drops out. Ignore Item Availability lists orders whatever is committed, including orders with nothing committed. The page does not warn you which one hides an order, so compare them when an order you expect is missing.
What happens when a component is short?
In the account observed, the bulk issue took the committed quantity of each component and left the rest outstanding as Back Ordered. WO3402 needed 40 Zipper Sets with 26 committed, and the issue contained 26. The order still moved to In Process. Check the issue's Components tab rather than assuming the order was issued in full.
Why does Process Status say Complete with 0 Errors when a component was only partly issued?
Complete means every marked order was processed. A short component is not treated as an error, so the Message stays at 0 Errors. The Processed Records line says Success for the order, and only the Work Order Issue and the work order's Items subtab show the quantity that was actually issued.
Why did the work order disappear from Issue Components?
The page lists Released orders. After a successful issue the order is In Process and no longer appears, even when a component is still outstanding. The order's own record still has its Issue Components button, so use that for the remainder once the stock arrives. How that form defaults the remaining quantity was not tested.
What is the accounting impact of a Work Order Issue?
Each issued component credits its inventory account and debits work in process, 164.00 and 35.10 in the example. The amounts follow the quantity issued and your costing setup, so read the GL Impact tab rather than working them out. The issue does not post routing labor or machine cost, which are normally recorded through completions, and it does not create finished goods.
What does the Issue link on each row do?
The Process column has an Issue link on each row. It is described as opening the individual Work Order Issue form for that order, which is the way to issue one order at a time or to change quantities. It was not tested here, and it does not submit the row for the bulk process.
What does Processed Records show for this page?
One line per marked order with its Line Status and Result, and the Work Order Issue it created in Result Record. Click the Record link to open the work order or the Result Record link to open the issue. If a line fails, its Error Message column should say why.