| Name | Type | Cardinality | Label | Required | Help |
|---|
| assemblyItem |
RecordRef |
0..1 |
Assembly |
T |
Select the assembly you need to build. Click the Open icon to open a list of assembly items.
When the item is selected, the components of that assembly show on the items subtab.
Once an assembly build is associated with this work order, this field cannot be changed. |
| autoCalculateLag |
boolean |
0..1 |
Auto-calculate Lag |
F |
Check the Auto-calculate Lag box if you want NetSuite to calculate lag times for operation tasks. For more information, click help and read Operations Overlap. |
| buildable |
double |
0..1 |
Buildable |
F |
|
| built |
double |
0..1 |
Built |
F |
The Built field displays the total number of assemblies that have been completed on associated assembly builds. |
| class |
RecordRef |
0..1 |
|
|
Select a class to associate the assemblies on this work order with a particular class. Your selection here carries over to the assembly build.
Click New to set up a new class.
Go to <_TABNAME=LIST_CLASS_> > <_TASKCATEGORY=LIST_CLASS_> > Classes for details about existing classes. |
| createdDate |
dateTime |
0..1 |
|
|
|
| createdFrom |
RecordRef |
0..1 |
Created From |
F |
The Created From field displays the number of the sales order associated with this work order, if any.
Note: The Created From field is not available if you are creating a stand-alone work order on the Enter Work Orders page. The Created From field appears only on existing work orders created from sales orders using one of these methods:
* By clicking on the Work Ord. link on the line item in the sales order
* By automatic work order creation from a sales order when the Create WO field is marked upon saving the sales order |
| customFieldList |
CustomFieldList |
0..1 |
|
|
|
| customForm |
RecordRef |
0..1 |
Custom Form |
T |
Select the form to use with this work order.
If you customized a sales order form, select it here, or click New to customize a new sales order form. |
| department |
RecordRef |
0..1 |
|
|
Select a department to associate the assemblies on this work order with a particular department. Your selection here carries over to the assembly build.
Click New to enter a new department.
Go to <_TABNAME=LIST_DEPARTMENT_> > <_TASKCATEGORY=LIST_DEPARTMENT_> > Departments for details about existing departments. |
| endDate |
dateTime |
0..1 |
|
|
In the Production End Date field, enter the date you expect to complete assembly production. This field defaults to show the transaction date plus lead time.
Note: When you use Demand Planning, the assembly supply is based on the production end date.
Using the Manufacturing Routing feature:
When you use the Routing and Demand Planning features to generate supply work orders, the function of the Production Start Date field and Production End Date field depend on the selected scheduling method NetSuite uses to calculate production requirements.
* Forward Scheduling
When you use forward scheduling, you set a production start date and NetSuite calculates the time, materials, and resources required to complete all necessary operations to finish the task. The production end date is determined based on these calculations.
When using the Forward Scheduling method, on work orders, the Production Start Date field is required and defaults to the current date. The Production End Date field is grayed out because it will be calculated.
* Backward Scheduling
When you use backward scheduling, you set the production end date, which is the date you need to have the completed items. Then, based on data from the associated routing, as well as the related work center calendar, NetSuite calculates the time, materials, and resources required to complete all necessary operations. The production start date is determined based on these calculations.
When using the Backward Scheduling method, on work orders, the Production End Date field is required. The Production Start Date field is grayed out because it will be calculated.
Note: This calculated start date may be a date in the past, prior to the current date.
For more details, click Help and read Production Scheduling Methods Overview. |
| entity |
RecordRef |
0..1 |
|
|
Select a customer if you want to associate this work order with a particular customer. |
| expandAssembly |
boolean |
0..1 |
Build Sub-Assemblies |
F |
If you check the Build Sub-Assemblies box, member items that are assemblies themselves are also built to complete the work order. Then, sub-assembly components are displayed hierarchically on the Items subtab.
Clear the box if you do not want to build member assemblies.
Once an assembly build is associated with this work order, this field cannot be changed. |
| firmed |
boolean |
0..1 |
Firmed |
F |
Planned work orders can be either Open or Firmed.
* Open – Open planned work orders will be deleted before supply planning runs.
Clear this box to keep the order Open.
* Firmed – Firmed planned work orders will NOT be deleted before supply planning runs.
Check this box to firm this order. |
| isWip |
boolean |
0..1 |
|
|
Check the WIP box to designate the work order to use WIP instead of a standard assembly build.
The setting can be applied when the Status field is set either to Planned or Released.
It cannot be changed once a posting assembly transaction has been attributed to the work order. |
| itemList |
WorkOrderItemList |
0..1 |
|
|
|
| job |
RecordRef |
0..1 |
|
|
Select a job if the assemblies on this work order are for a particular job. Click the Open icon to open a list of jobs. |
| lastModifiedDate |
dateTime |
0..1 |
|
|
|
| location |
RecordRef |
0..1 |
|
|
Select a location if you track them. The location you select here carries over to the assembly build.
If you use the Multi-Location Inventory feature, the location selected is the one that component inventory items are committed from.
Note: All items on one work order must be committed from the same location. Items can commit only from the location specified, even if there are no available items at the specified location, and there are items available at another location.
Select New to enter a new location record.
Go to <_TABNAME=LIST_LOCATION_> > <_TASKCATEGORY=LIST_LOCATION_> > Locations for details about existing location records. |
| manufacturingRouting |
RecordRef |
0..1 |
Manufacturing Routing |
F |
Select the appropriate manufacturing routing. |
| memo |
string |
0..1 |
|
|
Optionally enter a memo for this work order. Later, you can search for the memo text to find this work order. |
| options |
CustomFieldList |
0..1 |
|
|
|
| orderStatus |
WorkOrderOrderStatus |
0..1 |
Order Status |
F |
Select the current status of this order. |
| partnersList |
PartnersList |
0..1 |
|
|
|
| quantity |
double |
0..1 |
Quantity |
T |
Enter the quantity you want to create of the assembly item. This can be a fractional number, if necessary. |
| revision |
RecordRef |
0..1 |
Revision |
F |
For work orders, NetSuite automatically populates the effective revision based on the effective date. If you change the revision selected on the work order, then NetSuite changes the components on the top level assembly based on the revision selected.
If you change the revision selected on the work order and the Build Subassembly box is checked, then top-level components will change based on the revision selected and the lower level components are determined based on the effective date. |
| salesTeamList |
SalesTeamList |
0..1 |
|
|
|
| schedulingMethod |
WorkOrderSchedulingMethod |
0..1 |
Scheduling Method |
T |
When you use the Routing and Demand Planning features to generate supply work orders, you can choose the method NetSuite uses to calculate production requirements. These calculations assess the time, materials, and resources required to complete an order and set a start or end date for the production run accordingly.
The two methods available are as follows:
* Forward Scheduling
When you use forward scheduling, you set a production start date and NetSuite calculates the time, materials, and resources required to complete all necessary operations to finish the task. The production end date is determined based on these calculations.
When using the Forward Scheduling method, on work orders, the Production Start Date field is required and defaults to the current date. The Production End Date field is grayed out because it will be calculated.
* Backward Scheduling
When you use backward scheduling, you set the production end date, which is the date you need to have the completed items. Then, based on data from the associated routing, as well as the related work center calendar, NetSuite calculates the time, materials, and resources required to complete all necessary operations. The production start date is determined based on these calculations.
When using the Backward Scheduling method, on work orders, the Production End Date field is required. The Production Start Date field is grayed out because it will be calculated.
Note: This calculated start date may be a date in the past, prior to the current date.
For more details, click Help and read Production Scheduling Methods Overview. |
| sourceTransactionId |
string |
0..1 |
|
|
|
| sourceTransactionLine |
long |
0..1 |
|
|
|
| specialOrder |
boolean |
0..1 |
|
|
|
| startDate |
dateTime |
0..1 |
|
|
In the Production Start Date field, enter the date you expect to begin assembly production. This field defaults to show the transaction date.
Note: When you use Demand Planning, the component demand is based on the production start date.
Using the Manufacturing Routing feature:
When you use the Routing and Demand Planning features to generate supply work orders, the function of the Production Start Date field and Production End Date field depend on the selected scheduling method NetSuite uses to calculate production requirements.
* Forward Scheduling
When you use forward scheduling, you set a production start date and NetSuite calculates the time, materials, and resources required to complete all necessary operations to finish the task. The production end date is determined based on these calculations.
When using the Forward Scheduling method, on work orders, the Production Start Date field is required and defaults to the current date. The Production End Date field is grayed out because it will be calculated.
* Backward Scheduling
When you use backward scheduling, you set the production end date, which is the date you need to have the completed items. Then, based on data from the associated routing, as well as the related work center calendar, NetSuite calculates the time, materials, and resources required to complete all necessary operations. The production start date is determined based on these calculations.
When using the Backward Scheduling method, on work orders, the Production End Date field is required. The Production Start Date field is grayed out because it will be calculated.
Note: This calculated start date may be a date in the past, prior to the current date.
For more details, click Help and read Production Scheduling Methods Overview. |
| status |
string |
0..1 |
Status |
F |
|
| subsidiary |
RecordRef |
0..1 |
|
|
If you use OneWorld, select a subsidiary. |
| tranDate |
dateTime |
0..1 |
|
|
NetSuite inserts today's date for the date of this work order. You can enter or select another date. |
| tranId |
string |
0..1 |
|
|
NetSuite increases the largest work order number by one. If you wish, you can enter another number. The next order number will revert to the standard pattern. |
| units |
RecordRef |
0..1 |
Unit of Measure |
F |
If the assembly you select uses Units of Measure, the units are displayed in this field.
* New work orders you enter on this form can use only stock units.
* Work orders you view that were previously generated by NetSuite display the units for reference only and cannot be changed. |