Netsuite Manufacturing
Netsuite Manufacturing
2023.1
This software and related documentation are provided under a license agreement containing restrictions
on use and disclosure and are protected by intellectual property laws. Except as expressly permitted
in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or
related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the
U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed, or activated on delivered hardware, and modifications of such
programs) and Oracle computer documentation or other Oracle data delivered to or accessed by
U.S. Government end users are "commercial computer software," "commercial computer software
documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display,
disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs
(including any operating system, integrated software, any programs embedded, installed, or activated
on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/
or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the
applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined
by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle®, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a
registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use
of third-party content, products, or services, except as set forth in an applicable agreement between you
and Oracle.
This documentation is in pre-General Availability status and is intended for demonstration and preliminary
use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to
this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of
this documentation.
If this document is in private pre-General Availability status:
The information contained in this document is for informational sharing purposes only and should be
considered in your capacity as a customer advisory board member or pursuant to your pre-General
Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, timing, and pricing
of any features or functionality described in this document may change and remains at the sole discretion
of Oracle.
This document in any form, software or printed matter, contains proprietary information that is the
exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms
and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle
PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has
been executed by you and Oracle and with which you agree to comply. This document and information
contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle
without prior written consent of Oracle. This document is not part of your license agreement nor can it be
incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website
at https://www.oracle.com/corporate/accessibility.
Oracle customers that have purchased support have access to electronic support through My Oracle
Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Sample Code
Oracle may provide sample code in SuiteAnswers, the Help Center, User Guides, or elsewhere through
help links. All such sample code is provided "as is” and “as available”, for use only with an authorized
NetSuite Service account, and is made available as a SuiteCloud Technology subject to the SuiteCloud
Terms of Service at www.netsuite.com/tos.
Oracle may modify or remove sample code at any time without notice.
As the Service is a multi-tenant service offering on shared databases, Customer may not use the Service
in excess of limits or thresholds that Oracle considers commercially reasonable for the Service. If Oracle
reasonably concludes that a Customer’s use is excessive and/or will cause immediate or ongoing
performance issues for one or more of Oracle’s other customers, Oracle may slow down or throttle
Customer’s excess use until such time that Customer’s use stays within reasonable limits. If Customer’s
particular usage pattern requires a higher limit or threshold, then the Customer should procure a
subscription to the Service that accommodates a higher limit and/or threshold that more effectively aligns
with the Customer’s actual usage pattern.
Beta Features
This software and related documentation are provided under a license agreement containing restrictions
on use and disclosure and are protected by intellectual property laws. Except as expressly permitted
in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed or activated on delivered hardware, and modifications of such
programs) and Oracle computer documentation or other Oracle data delivered to or accessed by
U.S. Government end users are "commercial computer software" or “commercial computer software
documentation” pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure,
modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any
operating system, integrated software, any programs embedded, installed or activated on delivered
hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other
Oracle data, is subject to the rights and limitations specified in the license contained in the applicable
contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the
applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks
of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a
registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use
of third-party content, products, or services, except as set forth in an applicable agreement between you
and Oracle.
This documentation is in pre-General Availability status and is intended for demonstration and preliminary
use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to
this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of
this documentation.
The information contained in this document is for informational sharing purposes only and should be
considered in your capacity as a customer advisory board member or pursuant to your pre-General
Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, and timing of any
features or functionality described in this document remains at the sole discretion of Oracle.
This document in any form, software or printed matter, contains proprietary information that is the
exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms
and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle
PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has
been executed by you and Oracle and with which you agree to comply. This document and information
contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle
without prior written consent of Oracle. This document is not part of your license agreement nor can it be
incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
Send Us Your Feedback
We'd like to hear your feedback on this document.
Answering the following questions will help us improve our help content:
■ Did you find the information you needed? If not, what was missing?
■ Did you find any errors?
■ Is the information clear?
■ Are the examples correct?
■ Do you need more examples?
■ What did you like most about this document?
Click here to send us your comments. If possible, please provide a page number or section title to identify
the content you're describing.
Manufacturing
■ Manufacturing Overview
■ Assembly Items
■ Assembly Work Orders
■ Advanced Bill of Materials
■ Bill of Materials Member Control for Assembly Items
■ Manufacturing Work In Process (WIP)
■ Manufacturing Routing
■ Outsourced Manufacturing
■ Manufacturing Preferences Overview
■ SuiteAnalytics Manufacturing Workbook
■ Advanced Manufacturing
■ Manufacturing Mobile
■ Engineering Change Order
Manufacturing
Manufacturing Overview 2
Manufacturing Overview
Manufacturing processes help organizations create finished goods from raw or semi-finished materials
using some combination of labor and machinery. Finished goods are then sold, at a profit, to other
manufacturers, wholesalers, or retailers who then sell them to consumers.
NetSuite integrates your manufacturing workflow from the sales order and process planning to building
goods, tracking work orders, and releasing finished goods for shipping.
For information about how to work with NetSuite Manufacturing, see the following help topics:
Important: The Advanced BOM record became available in NetSuite 2017.2. After your
administrator enables the Advanced Bill of Materials feature, the Advanced BOM replaces the
Assembly/Bill of Materials record.
Manufacturing
Manufacturing Overview 3
The NetSuite Manufacturing Mobile SuiteApp enables operators with little ERP knowledge to use
mobile scanners to report manufacturing shop floor data. This mobile solution compliments the
existing Advanced Manufacturing scanner to provide improved performance, scalability, customization
support, and streamlined production activities.
■ Engineering Change Order:
Generate Engineering Change Order (ECO) records to document changes to your Bills of Materials
(BOMs) and authorize the implementation of those changes.
Manufacturing
Assembly Items 4
Assembly Items
An assembly item is an inventory item made up of several components, but identified as a single item.
Assemblies are manufactured by combining raw materials that you stock.
Note: For details about distinctions between Groups, Kits, and Assemblies, see the help topic
Groups, Assemblies, and Kit/Packages.
After you create assembly item records that define the members of an assembly, you can track the raw
materials and the assembled items separately.
For example, Wolfe Manufacturing sells the LogLeaper mountain bike that they assemble in-house. The
LogLeaper is assembled from the following inventory components:
NetSuite tracks the stock of the LogLeaper and each component item separately. This enables Wolfe
to track the stock levels of LogLeaper mountain bikes in inventory and available to ship to customers.
Wolfe can also track the quantity of materials available to assemble more bicycles.
1. Enable the Assembly Items feature. For more information, see Enabling Assembly Items.
2. To create assembly item records that define the assembly components, select the parts that make
up the assembly. For more information, see Assembly Item Records.
■ To create an assembly item record, go to Lists > Accounting > Items > New
■ On the New Item page, click Assembly. For more information, see the help topic Creating
Item Records.
3. Record an assembly build:
■ After you create an assembly item record, enter an assembly build to record assembly
production. Physically manufacturing assemblies in a production run increases your stock of
assembled items.
■ To record inventory level changes, go to Transactions > Inventory > Build Assemblies to enter
an assembly build for each production run. For more information, see Building Assembly
Items.
■ After you create your assembly item, build the assembly in NetSuite to replenish stock. To
record an assembly build, go to Transactions > Inventory > Build Assemblies.
NetSuite tracks assembly item and member component records separately. It also tracks the
assembly and member item stock status individually. For each assembly build you record:
■ the assembly item stock level increases
■ the member items' individual stock levels decrease
Manufacturing
Enabling Assembly Items 5
Important: With the release of NetSuite 2023.1 Bills of Materials, where components are
embedded to an Assembly Item, will no longer be supported. Only business critical issues will
be fixed. To continue working with this functionality you should transition to the Advanced Bill of
Materials feature, which is free of charge. After you enable this feature, NetSuite will automatically
migrate all of your Bill of Materials to the new structure.
Inventory Inventory
Service Non-Inventory
Regular Assemblies
Serialized Assemblies
Manufacturing
Assembly Item Records 6
By not setting an income account on an inventory item's record, the item does not appear in the sales
transaction’s items list. The item is sold as part of the finished goods assembly the item belongs to, which
has its own income account.
If you do not set an expense account on a non-inventory item for resale, the item does not appear in the
purchase transaction’s item list.
Serialized or lot numbered inventory items can be members of an assembly only if the assembly is
serialized or lot numbered.
Purchase Transactions
To make assemblies available to purchase transactions, go to Setup > Accounting > Preferences
> Accounting Preferences. Check the Allow the Purchase of Assembly Items box on the Order
Management subtab, and then save. For information about preferences, see the help topic Items/
Transactions Accounting Preferences.
Web Sites
You can offer an assembly in your web site using the Store and Specials subtabs. Edit the assembly item
record to add the item to your web site.
Work Orders
The Work Orders feature enables you to track the production of assembly items for stock or to fill orders.
Work orders track the quantities of assemblies to be built, and the required quantities of components, or
member items. Use Special Order Work Orders for a particular sale. Use Production Work Orders to
increase stock. For more information, see Assembly Work Orders.
Matrix Assemblies
To use Matrix Assemblies, an administrator must enable the Matrix Items feature.
With the Assembly Items and Matrix Items features, you can create assembly item records that contain
matrix options. These options help improve assembly item planning and production tracking. Matrix
Manufacturing
Matrix Assemblies 7
options make it possible to use Bills of Materials (BOM) and Manufacturing Routings to build items with
numerous product styles and variations.
During production, you can create matrix assemblies using work orders and assembly builds.
For example, Wolfe Manufacturing produces mountain bikes and sells them only on their web site, not
through retailers.
Matrix assembly records enable you to manage a BOM at the parent matrix assembly level and then
implement BOM changes to specific configurations. BOM options can also be maintained on an individual
item record basis.
■ You can track demand for matrix assemblies and then make them available in the web store. You can
also build them using work orders or assembly builds.
■ For web store matrix assembly items, web store administrators can display only a parent matrix
assembly item. Then make configuration options available in a list.
After matrix assembly sub-items are created, you may need to update the following matrix items:
■ The BOM and its attributes such as the Cost Of Goods Sold (COGS) account or Unit of Measure.
■ The parent assembly item and update some or all sub-items at one time.
Manufacturing
Matrix Assemblies 8
Note: After you create a matrix assembly, the Effective Date and Obsolete Date fields do not
appear on the item record Component subtab.
To use BOM Control or set effective and obsolete dates, set them on the parent matrix assembly
item record. Revision control must be set on the matrix assembly child item records. For more
information, see Revision Control BOM Management.
Note: Previous BOMs are not updated with the changes entered.
2. Click Save.
Manufacturing
Phantom Assemblies 9
Phantom Assemblies
A phantom assembly is typically a non-stocked assembly that groups the components needed to produce
a subassembly. For example, compare a phantom assembly to folders on a computer. The folder
represents the phantom and the individual files are the components. They are called phantoms because
they are not counted as inventory items, but are created to fulfill the requirements of a higher-level
assembly.
Phantom Assemblies
■ No need to create multiple work orders. The phantom assembly is added to the higher-level work
order.
■ They work as build-to-order instructions. Components do not have to be issued from stock
beforehand.
■ They simplify Bill of Materials (BOM) management. If a component is changed on the Phantom BOM, it
is automatically reflected in all BOMs that use the phantom as a sub-assembly.
■ You can use them as configuration options for manufactured products when it would not be cost
effective to keep the assembly in stock.
For example, Wolfe Manufacturing can use a phantom wheel assembly to build the wheels as part of
the build assembly. With this phantom wheel assembly, Wolfe does not keep certain wheel types in
stock. In this example, the phantom could include the following:
After you add a wheel assembly to the work order, you issue the components. Then, the system
issues the components that make up that assembly and then adds them to the work order. For more
information, see Marking Assemblies to Create Work Orders.
While phantom assemblies are typically used as components in a larger assembly build, they can also be
used to create stock items. For example, as part of a warranty claim, a batch of replacement wheels could
be manufactured using a phantom assembly.
Manufacturing
Phantom Assemblies 10
On assembly builds, NetSuite uses the item source values (stock or phantom) from the assembly and
BOM revision record. However, the column field item source does not appear. The system expands the
list of components on the assembly build when the list of components contains a sub-assembly with a
phantom item source. You can override these default values on either the BOM record or the work order
record.
The following diagram illustrates how NetSuite determines default item source values.
■ The Frame is an inventory item. When the Special Order Item box is clear, the Item Source is
marked as Stock.
■ The Wheel assembly item is marked Phantom. Because the mark Sub-Assemblies Phantom box was
clear, the wheel assembly work order is marked Phantom, but its sub components are taken from
stock. If the Special-Order Item box is checked, the item source is marked Work Order.
Manufacturing
Phantom Assemblies 11
■ The Handle bar is normally an inventory item. When the Special Order Item box is checked, the
Item Source is marked Purchase Order.
In the following screenshot, Assembly Build for 0810 AssyB has two components. Component 0810
AssyA is an assembly and the 0810 AssyB BOM has Item Source set to Phantom, which is why the text is
indented.
For example, Wolfe Manufacturing sells road bikes in multiple configurations and have created a
BOM for each configuration. The company does not stock carbon-fiber wheels, but has the wheel
components in inventory and only assembles them when ordered. The carbon-fiber wheel is a sub-
assembly of the road bike assembly and the Road Bike BOM. The item source for the carbon-fiber
wheel is phantom.
Assembly and Inventory Items can be assigned a serial or lot number when you produce or receive them.
After the item is consumed, in the Work Order Item subtab Inventory Detail field, select the serial or lot
number being used.
When these features are enabled, phantom assembly options appear on the assembly and work order
records.
Manufacturing
Phantom Assemblies 12
Phantom Assembly/Bill of Check this box to mark the Item Source for this item on any bill
Materials record of materials as Phantom by default. This also applies to the item
source value on any work order where the item is used.
Mark Sub-Assemblies Assembly/Bill of Check this box to mark all sub-assemblies on the work order as
Phantom Materials and Work Phantom. The sub-assemblies will be built as part of the higher-
Order records level work order rather than drawn from stock.
Clearing this box does not refresh the items in the Item subtab.
It enables in-line editing of individual components.
Item Source Components subtab Adds Phantom as an option on the Item Source list. Enables
Assembly/Bill of sub-assembly components to be treated as phantoms on one
Materials and Work BOM, and regular stock items on another.
Order records
Manufacturing
Phantom Assemblies 13
An assembly demand plan with a phantom sub-assembly in its bill of materials calculates dependent
demand for components of the phantom item. However, it does not calculate for the phantom itself. For
more information, see the help topic Demand Planning.
After you select a basic unit type on an assembly record you can define a default unit for the item on a
particular transaction. On item records, designate a unit to default as a purchase unit, stock unit, or sales
unit.
Note: You can set purchase and sale units when you create the item record. After you save the
record, these units cannot be changed. You can make a selection for the stock units when you
create the item record. You can change the stock units after you save the record.
On Assembly Builds, Assembly Unbuilds, and Work Orders for Assembly Items with Units of Measure, the
Units field defaults to base units. You cannot change the default.
Fulfill Orders Yes (in units that match the sales order)
Replenish Location
Unbuild Assemblies
Prepare Estimates
Create Invoices
Adjust Inventory
Transfer Inventory
Write Checks
Manufacturing
Assemblies and Units of Measure 14
Generated reports display units of measure based on the units used in transactions.
Serialized Assemblies
When working with serial-numbered assembly items:
■ The base unit must be the lowest unit of measure when selecting a Units Type.
■ Units cannot have a decimal unit of measure conversion with the base units when selecting Stock
Units, Purchase Units, and Sale Units.
■ The quantity of serial numbers entered must equal the quantity in base unit when a transaction is
entered in a non-base units.
For example, you sell a serialized assembly that uses a base unit of Each and sale unit of Dozen.
When you enter a sales order for 2 of the assembly, enter 24 serial numbers on the order to
represent 24 each of the item.
Work orders you view that were previously generated by NetSuite display the units for reference only and
cannot be changed.
If the work order was created from another source (such as a sales order), you can change the quantity by
changing the source transaction. For more information, see Assembly Work Orders.
Manufacturing
Building Assembly Items 15
Entering an assembly build for each production run updates your inventory levels.
Note: If you use work orders and have entered work orders for assemblies, see Building Work
Orders to complete builds for those assemblies.
Note: If you use Advanced BOM, the Bill of Materials and Bill of Materials
Revision lists appear.
Manufacturing
Building Assembly Items 16
Note: You can change the quantity of members on a serialized or lot numbered assembly.
Use the assembly serial or lot numbers to track assembly items created with special
member quantities. You cannot track non-serial or non-lot assemblies that could have
special quantities of member items. Therefore, you may want to build non-serial or non-
lot assemblies with special quantities. You can build when your available quantity of that
assembly is zero and you are building assemblies with special quantities for a customer
order.
Manufacturing
Building Assembly Items 17
After an assembly item is built, it is treated like an inventory item for inventory costing purposes. The built
assembly item asset/costing value is the total value of the assembly's member items. These values act like
the assembly item's purchase price for inventory costing calculations.
Note: If you use NetSuite OneWorld, you can select the purchase currency on non-inventory
items for purchase and resale.
Inventory costing is tracked for the assembly item based on the inventory costing method chosen at
Setup > Accounting > Preferences > Accounting Preferences. For information about inventory costing, see
the help topic Using Item Records.
Unbuilding an assembly updates inventory levels on records for the finished assembly item and for each
member component individually. For each assembly you unbuild:
Manufacturing
Unbuild Assembly Items 18
Note: If you use Multi-Location Inventory, when you select an assembly item and
location, the maximum number you can unbuild appears in Quantity Built. If you do
not select a location, the maximum number that you can unbuild does not appear in
this field.
c. If you use serialized inventory, enter the Serial Numbers for the assemblies you plan to
unbuild.
d. If you use bin management, select the Assembly Item Record Bin Number from Bin
Numbers list. By default, all assemblies are removed from the preferred bin. To remove
some items from other associated bins, click the Bins icon or Inventory Detail icon.
When you unbuild this assembly, the bin quantity on hand decreases, and the bin quantity
on hand for each member item increases.
e. If you enabled Advanced Bill of Materials, select a Bill of Materials.
f. If you enabled Advanced Bill of Materials, select a Bill of Materials Revision.
g. In the Quantity to Unbuild field, enter the number of assembly items you want to unbuild.
You cannot enter a quantity that exceeds the number in the Quantity Built field.
h. The projected value of your disassembled items appears in the Projected Value field.
Projected Value is the sum of the value of the member items times the quantity entered.
i. In the Date field, enter the transaction date.
j. If you use accounting periods, select a transaction Posting Period. You cannot post to a
closed period.
k. Enter a Memo. You can search for this text later to find this entry.
3. In the Classification section, complete the following fields:
a. If you use NetSuite OneWorld, select a Subsidiary.
b. If you track departments, select a Department for this transaction.
c. If you track classes, select a Class for this transaction.
d. If you track locations, select a Location for this transaction.
4. The Components subtab provides the inventory detail for each component.
5. Click the Communication subtab.
a. Enter events on the Events subtab. For example, maintenance, repair, or setup.
i. Enter the event name or Title. For example, Assembly Work Center Setup.
ii. Enter the event Location. For example, West Coast Assembly.
Manufacturing
Unbuild Assembly Items 19
iii. Accept today’s Date or use the calendar to enter a different date.
iv. If this is an all day event, check the All Day box.
v. Enter event Start and End Times.
vi. Click Add.
To add more events, repeat this procedure.
For example, Setup could start at 7:00 am and end at 7:30 am. Then, Assembly could
start at 7:30 am and end at 3:30 pm. Finally, Breakdown could start at 3:30 pm and
end at 4:30 pm.
b. On the Tasks subtab, view or enter CRM tasks records. For information about tasks, see the
help topic Working with CRM Tasks.
c. The Phone Calls subtab enables you to view or enter phone calls.
d. The Files subtab enables you to attach files from the NetSuite File Cabinet, your computer,
or the internet.
■ To add a file from the File Cabinet, select one from the Attach File list.
After the file loads, NetSuite fills the Folder, Size, Last Modifed, and File Type fields.
■ To add a new file, in the Attach File list, select New.
Complete the List window.
e. On the User Notes subtab, add and track notations.
6. Click Save.
After you save the transaction, your inventory count of the assembly item decreases and the inventory
count of the member items increases accordingly.
For example, when you unbuild an assembly, each component is restocked and the item cost for each
component is calculated. Any variance between the assembly cost and the unbuild cost posts to the
selected Unbuild Variance account on the item record for that assembly.
If no variance account is selected for an assembly item, variance amounts for that item post to the Cost of
Goods Sold (COGS) account.
1. To open the assembly item record, go to Lists > Accounting > Item.
2. In the Unbuild Variance Account field, select the account where you want to post variance
amounts.
3. Click Save.
Manufacturing
Unbuild Assembly Items 20
When unbuilding an assembly item, NetSuite uses historical costing to determine member item values.
For example, a member item's historical transactions display a cost of $25. NetSuite uses this amount to
calculate cost for the member item after the assembly unbuild.
If the assembly being unbuilt was purchased from a vendor, a member item has no previous transactions.
The historical cost to be considered is $0 and member items in this case would have a value of $0.
If you want to adjust your inventory prior to an unbuild or rather than unbuilding an assembly, refer to
the following procedures:
The following example describes the transaction sequence for assembly item ABC.
Manufacturing
Unbuild Assembly Items 21
The assembly is removed from inventory and the appropriate number of member items is added to
inventory.
When you mark an order as built, the required items are marked built and added to inventory.
Note: Associated variances are not created when you mark an order built.
When you mark an order as closed, the required items are marked closed and added to inventory.
Note: Associated variances are created when you mark an order built. For information about
variances, see the help topic Using Item Records.
Manufacturing
Marking Work Orders Built 22
If one of the components of your assembly item is an assembly item, each item subcomponent appears.
Each subcomponent displays the quantity needed for each subcomponent to complete the assembly.
For example, your assembly item contains four components—Item A, Item B, Item C, Item D. Item B is
an assembly item made up of Widget 1 and Widget 2. Two of each widget are necessary for assembly of
Item B. And two of Item B are needed to complete the parent assembly. The quantity needed to complete
assembly Item B must be doubled to complete the parent assembly.
Manufacturing
Printing an Item Bill of Materials 23
Parent Assembly
Item A 1 1
Item B 2 2
Widget 1 2 4
Widget 2 2 4
Item C 5 5
Item D 1 1
To learn another way to view BOM details, see Bill of Materials Inquiry.
To learn how to print a bill of materials for work orders that you enter, see Printing a Work Order Bill of
Materials.
For example, you can run BOM Inquiry to identify the materials needed to assemble a Mountain Bike. The
inquiry shows that you need two wheels, one frame, one seat, and one handle bar. The inquiry also shows
the sub-assembly (phantom assembly) components for each wheel: one rim, one hub, one, tube, one tire,
and spokes.
Note: Custom roles must specify access to view this inquiry. For more information, see the help
topic Customizing or Creating NetSuite Roles.
Manufacturing
Bill of Materials Inquiry 24
Note: This field is available only when an assembly item uses Revision Control for its
Effective BOM Control value.
When assembly items use Effective Date as Effective BOM Control value, the Date field determines
the date when querying components of the assembly item.
Components are displayed based on the following criteria:
■ Selected date is greater than or equal to the effective date.
■ Selected date is less than or equal to the obsolete date.
If an assembly item uses Revision Control, you can query the components either By Date or By
Revision.
■ If you select By Date, then follow the process described in step 5 above.
■ If you select By Revision, in the Revision field, select a revision.
The active components for the revision are displayed and the date field displays the revision
effective date.
The inquiry displays all components used in a multi-level bill of materials structure, using a nested tree
view.
Component Name The name of the Component as defined in the Item Name field
Component Yield Shows how much of this component is available for final assembly, after
accounting for loss/scrap in the production process
A yield factor of 0.9 means that 90% of the usage quantity of the component on
a bill becomes part of the finished assembly.
BOM Quantity per Assembly The quantity required for this assembly according to the BOM
Quantity per Assembly The quantity required when component yield is taken into consideration
Quantity per Top Level Assembly The total quantity of this component required to make the top-level assembly
Top level items are typically finished products. For example, a Barbecue grill set.
Back Ordered The quantity of any unfulfilled order or existing commitment for this
component
Manufacturing
Bill of Materials Inquiry 25
On Order The total quantity ordered of this component across all current work orders
To display information stored in custom item fields for each component, click Customize.
Click the printer icon at the top of the inquiry page to print or export (Excel or CSV) the inquiry results.
Note: The data in the inquiry header (such as location and date) is not exported. Only the table
data resulting from the inquiry is exported. Only the columns shown on the query export page can
be exported or printed.
For more information, see Printing an Item Bill of Materials for an alternate way to view BOM details.
For example, the Costed BOM Inquiry helps a cost accountant in a manufacturing environment see the
different cost components associated with building an assembly. It can also show how each component is
calculated and rolled up to the finished goods.
This provides visibility into variances between inventory values at a certain time (displayed on the
Inventory Valuation reports). It also provides visibility in the desegregated component costs of the
assembly.
Note: To use the Costed BOM Inquiry, enable the Standard Costing and Assemblies features.
This inquiry can be run only for a standard cost assembly item.
After you select the subsidiary, location, and assembly, the inquiry displays the cost breakdown of the
assembly and its member components. This assembly cost is calculated based on the standard cost of
components.
For assemblies that have a conversion cost, the assembly cost is calculated as follows:
■ Component cost is based on the component cost displayed in the inventory revaluation transaction.
■ Conversion cost is based on the assembly inventory revaluation transaction.
For assemblies that do not use routing, the assembly cost is based on the component cost displayed in
the inventory revaluation transaction.
Manufacturing
Bill of Materials Inquiry 26
4. If you use the multi-location inventory feature, select the Location you want to view data for.
5. To show only the top level member items details check the Top Level Only box. Sub-assembly
information is not shown.
Clear the Top Level Only box to show all member items.
6. To decide what to include in an assembly, select a BOM Display Control option:
■ By Date – determines the date for querying assembly item components.
Components are displayed based on the following criteria:
□ Selected date is greater than or equal to the effective date.
□ Selected date is less than or equal to the obsolete date.
■ By Revision
This field is available only when an assembly item uses Revision Control for its Effective BOM
Control value.
When assembly items use Effective Date as the Effective BOM Control value, the date field
determines the date querying components of the assembly item.
If an assembly item uses Revision Control, you can query the components either by Date or by
Revision.
■ If you select By Date, then follow the process described in step 5 above.
■ If you select By Revision, then in the Revision field, select a revision.
The active components for the revision are shown and the Date field displays the revision
Effective Date.
Note: If you have enabled the Advanced BOM feature, the Bill of Materials and Bill of
Materials Revision lists will be displayed.
Note: To display a value, sub-assemblies must be a standard cost type. If a sub assembly
contains a component, the unit cost value is taken as a sum of all components costs.
Manufacturing
Bill of Materials Inquiry 27
Click the printer icon at the top of the inquiry page to print or export (Excel or CSV) the inquiry results.
The data in the inquiry header (location and date) does not get exported. Only the tabular data resulting
from the inquiry is exported. Only the columns shown on the query export page can be exported or
printed.
For more information, see Printing an Item Bill of Materials for an alternate way to view BOM details.
■ View the comprehensive cost breakdown of an assembly item, including bills of materials, operations,
and cost types based on selected bill of materials revision.
■ View and analyze costs of individual components required for an assembly. This calculation also
involves the material cost, labor cost, and additional costs associated with the component.
■ Estimate the potential costs of manufacturing items for bill of materials based on costing method,
purchase price, and item default price.
■ Access cost breakdowns for bills of materials as part of your product engineering and costing
processes.
You can access the SuiteApp by navigating to Reports > Cost Accounting > Costed Bill of Materials.
Only users with Administrator role can install the SuiteApp. For more information about installing a
SuiteApp, see the help topics Installing from the SuiteApp Marketplace and SuiteApp Marketplace in
NetSuite.
Assembly Items
Standard Costing
Server SuiteScript
Client SuiteScript
Manufacturing
Costed Bill of Materials 28
■ The Costed Bill of Materials SuiteApp will work if the cost currency has a default currency of the
customer’s subsidiary currency.
■ The subassemblies must have default bill of materials, and default routing for location to
retrieve data.
A custom role Costed_BOM_Role is created during the SuiteApp installation which will be used as a
default value for Execute As Role field in the Script Deployment page. It is updated in the Costed Bill of
Materials and Costed BOM DataService script.
Refer to the following table for minimum access levels of permissions required for SuiteApp deployments.
These minimum permissions must be updated to the existing role or while creating a new role.
Refer to the following table for the minimum permissions required for logged-in user role.
Manufacturing
Costed Bill of Materials 29
Manufacturing
Costed Bill of Materials 30
Note: In the Item field of the Costed Bill of Materials page, type three characters and click on the
field for the items to be populated in the list, based on the search. This is applicable only for Safari
browser.
Manufacturing
Costed Bill of Materials 31
5. From the Bill of Materials list, select the bill of materials to automatically populate the Bill of
Materials Revision and Effective Date fields.
6. From the Display Control list, select either By Date or By Revision to decide what to include
in an assembly. This field is available only when an assembly item uses revision control for its
effective display control value.
7. The Date/Effective Date field displays the date used to decide when a component should be
included in an assembly. This field is available only when an assembly item uses revision control
for its effective display control value.
The field is editable only if the display control value is set to By Date. The Date field controls
which date is used when querying the components of the assembly item. Then, components are
shown based on the following criteria:
■ The selected date is greater than or equal to the effective start date.
■ The selected date is less than or equal to the effective end date.
8. From the Bill of Materials Revision field, choose the bill of materials revision from the list.
9. Check the By Manufacturing Routing box only if the assembly item has an associated routing.
The box will be disabled if the item has no associated routing.
10. From the Manufacturing Routing list, select a manufacturing routing. This field is enabled when
you check the By Manufacturing Routing box.
11. In the Build Quantity field, enter the build quantity of the item you want to see for the costed
bill of materials. The default value is 1. However, if Manufacturing Routing And Work Center
feature is enabled in Enable Features page, the default value will be the costing lot size
mentioned in selected assembly item record.
12. Check the Top Level Only box to limit the details to the selected assembly item, its components,
and operation only. Information about sub-assemblies is not displayed. Clear this box to display
details at all levels of the fully exploded Bill of Materials. This field cannot be checked if the By
Manufacturing Routing box is selected.
13. From the Material Cost list, you can select the cost type to be used for all components.
■ Per Costing Method – Cost is calculated based on the costing method assigned to the item.
For example: LIFO, FIFO, Standard, Average, and so on.
■ Per Purchase Price – Cost is calculated as per the last purchase price of the item in the
location. If the last purchase price is not available, the report uses the default item purchase
price.
■ Per Item Default – Cost is calculated as per the standard cost of the item in the location.
14. Click Submit.
You can view the three subtabs (Material Costs, Assembled Costs, Fully Exploded Costs) after the
process is complete.
The following table provides details about the fields in the Material Costs subtab.
Field Description
Total Material Cost Total material cost calculates based on the build quantity and cost of the end assembly
item.
Manufacturing
Costed Bill of Materials 32
Field Description
Material Cost per Unit Material cost of a single unit of the end assembly item.
The following table provides details about the columns in the Material Costs subtab.
Level Level represents the level in the hierarchy of the exploded bill of materials.
Quantity Quantity of the component item as per the bill of materials required to produce
one unit of the assembly at this level.
Component Yield Component yield is retrieved from the selected bill of materials revision of the
assembly item.
Quantity Per Assembly Quantity of the component item required to produce one unit of the assembly at
this level based on component yield.
Quantity Per Top Level Quantity of the component item required to produce one unit of the end assembly.
Assembly
Unit Cost Unit cost of the component as per the selected material cost source.
The following table provides details about the fields in the Assembled Costs subtab.
Field Description
Total Assembled Cost Total assembled cost calculates based on the sum of material cost and conversion cost
of the end assembly item.
Assembled Cost per Unit Assembled cost of a single unit of the end assembly item.
The following table provides details about the columns in the Assembled Costs subtab.
Material Costs Cost of materials as per the selected material cost source to produce the final
assembly.
Manufacturing
Costed Bill of Materials 33
Labor Run Overhead Cost of labor overhead to produce the final assembly.
Labor Setup Overhead Cost of labor setup overhead to produce the final assembly.
Machine Run Overhead Cost of machine run overhead to produce the final assembly.
Machine Setup Overhead Cost of machine setup overhead to produce the final assembly.
The following table provides details about the fields in the Fully Exploded Costs subtab.
Field Description
Total Exploded Cost Total exploded cost is calculated based on the sum of material cost and conversion cost of
all subassemblies of the end assembly item.
Exploded Cost per Unit Exploded cost of a single unit of the end assembly item.
Material Cost % Percentage of the material cost from the total exploded cost percentage.
Conversion Cost % Percentage of the conversion cost from the total exploded cost percentage.
The following table provides details about the columns in the Fully Exploded Costs subtab.
Level Level represents the level in the hierarchy of the exploded bill of materials.
Material Costs Cost of materials as per the selected material cost source to produce the final
assembly.
Conversion Costs Cost types associated with each assembly to produce the final assembly.
Labor Run Overhead Cost of labor overhead to produce the final assembly.
Labor Setup Overhead Cost of labor setup overhead to produce the final assembly.
Manufacturing
Costed Bill of Materials 34
Machine Run Overhead Cost of machine run overhead to produce the final assembly.
Machine Setup Overhead Cost of machine setup overhead to produce the final assembly.
Note: If you have enabled Advanced Bills of Materials, this feature is not available.
Note: You must enter a display name on the member item records for an item name to appear.
Your administrator can customize the layout of your printed forms using Advanced PDF/HTML templates.
For more information, see the help topic Advanced PDF/HTML Templates.
To print labels for each member item and the assembly item:
Manufacturing
Printing Assembly Labels 35
For example, item#24567 (a table leg) is a component in items that you assemble. Run the Component
Where Used Inquiry to learn where that component is used:
■ item#77888, 3-piece table set, includes one small square table, one medium console table, and one
large rectangle table.
■ To produce one of item #77888 requires 13 table legs per assembly.
Note: If a parent assembly item is not active for the specified date, then child item
does not appear in the list.
3. Based on the criteria selected, you could see the following fields:
■ Assembly – The name of the assembly item that uses the component selected in the header.
■ Level – The level in the Bill of Materials (BOM) structure where the component resides.
For example, a level 1 item is a sub-member of the parent (selected) component item. A level 2
item is a sub-member of the level 1 item.
■ Quantity per Assembly – The amount of the component required to build the assembly.
Manufacturing
Running the Component Where Used Inquiry 36
■ On Hand / Available / Back Ordered / On Order – Quantities are displayed for the selected
location.
■ Units – The units for the component.
■ Effective Date – The date the assembly becomes effective.
■ Obsolete Date – The date the assembly is no longer effective.
The inquiry in the following example is run to determine where the Table Leg item is used as a
component.
Item Level Qty Required per Assembly Qty Required per Top-Level Assembly
Table: European 1 4 4
Table: American 1 6 6
The following is the same inquiry, with Single-Level only set to Yes.
Item Level Qty Required per Assembly Qty Required per Top-Level Assembly
Table: European 1 4 4
Table: American 1 6 6
Manufacturing
Assembly Work Orders 37
■ If you close a line on a sales order that links to an assembly, the link to the work order remains. The
work order remains open and the finished assembly from the build is added to general inventory.
■ If you change the quantity on a work order line, note the following. If the quantity exceeds the
amount on the corresponding sales order line, the link to the sales order remains. When the build is
completed, the excess assemblies are added to general inventory.
■ Sales orders that are cancelled are no longer linked to work orders.
Note: For transaction customization purposes, assembly work order forms are classified as sales
forms. If you create a custom transaction field and apply it to sales transactions, it shows on work
order forms.
Manufacturing
Assembly Work Orders Workflow Chart 38
Manufacturing
Two Types of Assembly Work Orders 39
Special order work orders track assemblies to be built for a particular sale. The work order can be
linked to the originating sale.
Sold assembly items where member items are in stock but not finished goods, NetSuite adds a work
order to the work order creation queue. Based on the amount of finished product needed for the
order, member items are committed to the work order to build the finished assemblies.
■ Production Work Orders
Production work orders track assemblies that need to be built to increase stock and are not intended
for a particular sale. Production work orders are not linked to a sales order and have no customer
assignment.
Production work orders are generated when the back ordered quantity of an assembly reaches its
assigned build point. After the build point is reached, NetSuite adds a work order in the Mass Create
Work Orders queue.
For each work order, a bill of materials (BOM) is generated to facilitate picking member items for the
build. When this work order completes, the regular stock level of the assembly increases and the
finished goods are committed to open sales orders.
Both production and special order work orders use the same Work Order transaction record in NetSuite.
A work order can be entered individually, or be automatically added to the work order creation queue
based on inventory settings, as described below:
Warning: Automatically creating seven hundred plus special work orders can impact system
processing.
The following is true for both types of work order forms. If you check the Mark Sub-Assemblies Phantom
box, member items that are assemblies themselves are also built to complete the work order.
If you use the Work Orders and Demand Planning features, see Work Orders and Sub-Assemblies.
You can also create a work order for an assembly item when you add it to a sales order. When you select
an assembly on a sales order, check the Create WO box. When the order is saved or approved, NetSuite
adds a work order to the Mass Create Work Order queue. For more information, see Marking Assemblies
to Create Work Orders. After work orders are entered, completing an assembly build for the work order
closes the order.
Manufacturing
Enabling the Work Orders Feature 40
4. Click Save.
After the feature is enabled, you can set the Build Based On Commitment accounting preference. For
more information, see the help topic Order Management Accounting Preferences.
For information about work order statuses, see Work Order Statuses
Note: When the Run Rate of previous operation is set to 0, the lag of current operation is also
set to 0. This results in no production from the previous operation.
Manufacturing
Entering an Individual Work Order 41
Note: After you associate an assembly build with this work order, you cannot change this
field.
9. Check the Mark Sub-Assemblies Phantom box to build member assembly items to complete the
work order.
Clearing this box does not refresh or remove sub-assembly components on the Items subtab.
To reload the BOM for a top level assembly, select a different assembly in the Assembly field.
To reload a BOM for a phantom sub-assembly, change the item source for the sub-assembly to
Phantom.
Note: After you associate an assembly build with this work order, you cannot change this
field.
For information about using the work order and demand planning, see Work Orders and Sub-
Assemblies.
10. Optionally, check the WIP box to designate the work order to use WIP instead of a standard
assembly build.
You can select this setting only when the order status is Released. You cannot change this setting
after a posting assembly transaction is logged against this work order. For information about using
WIP, see Manufacturing Work In Process (WIP).
11. Select the related Manufacturing Routing.
This list is available only when the WIP box is checked.
12. Check the Auto-Calculate Lag box to calculate lag times for operation tasks. For more information,
see Operations Overlap
13. Enter the Quantity of assembly items you want to create. This can be a fractional number.
If you enter a quantity higher than the available quantity, a warning message appears.
The item's available quantity is calculated based on availability across all locations. Changing the
header location does not affect the item availability used on the line.
Tip: You can customize the form to display item availability for each item across all
locations. For more information, see the help topic Creating Custom Entry and Transaction
Forms.
Important: After an assembly build is associated with this work order, note the
following. The quantity can be changed only by closing the work order and then making a
copy or creating a new work order. Closing the work order sets the Back Order amount to
zero for the component items. However, it has no financial impact on the created assembly
Item.
To create a new work order to enter a new quantity:
Manufacturing
Entering an Individual Work Order 42
Note: If you use Multi-Location Inventory, the selected location is the one that component
inventory items are committed from.
Important: All items on one work order must be committed from the same location.
Items can commit only from the location specified. This is true even if there are no available
items at the specified location, and there are items available at another location.
15. Routing and Demand Planning generate supply work orders that enable you to select a
Scheduling Method.
NetSuite automatically populates the Production Start Date field when a work order transaction is
initiated.
When the final assembly is built and recorded in the work order transaction, NetSuite automatically
populates the Production End Date field. For more information, see Production Start and End
Dates.
Note: If you use Advanced Bills of Materials, the Revision field is replaced by Bill of
Materials and Bill of Materials Revision.
6. Check the Mark Sub-Assemblies Phantom box to build member assembly items to complete the
work order.
Clearing this box does not refresh or remove sub-assembly components on the Items subtab.
To reload the BOM for a top level assembly, select a different assembly in the Assembly field.
To reload a BOM for a phantom sub-assembly, change the item source for the sub-assembly to
Phantom.
Manufacturing
Entering an Individual Work Order 43
Note: After you associate an assembly build with this work order, you cannot change this
field.
For information about using the work order and demand planning, see Work Orders and Sub-
Assemblies.
7. Select the related Manufacturing Routing.
This list is only available when the WIP box is checked.
8. Check the Auto-Calculate Lag box to calculate lag times for operation tasks. For information, see
Operations Overlap
9. Enter the Quantity of assembly items you want to create. This can be a fractional number.
If you enter a quantity higher than the available quantity, a warning message appears.
The item's available quantity is calculated based on availability across all locations. Changing the
header location does not affect the item availability used on the line
Tip: You can customize the form to display item availability for each item across all
locations. For more information, see the help topic Creating Custom Entry and Transaction
Forms.
Important: After an assembly build is associated with this work order, note the
following. The quantity can be changed only by closing the work order and then making a
copy or creating a new work order. Closing the work order sets the Back Order amount to
zero for the component items. However, it has no financial impact on the created assembly
Item.
To create a new work order to enter a new quantity:
Manufacturing
Entering an Individual Work Order 44
Note: All items on one work order must be committed from the same location. Items can
commit only from the location specified. This is true even if there are no available items at
the specified location, and there are items available at another location.
The Built field displays the total number of assemblies that have been completed on associated
assembly builds.
This field appears only after the form is saved.
15. On the Items subtab, complete the following steps:
a. Select an Item from the list.
When you select an assembly, the assembly components appear on the Items subtab.
If the assembly includes members that are assemblies and you checked the Mark Sub-
Assemblies Phantom box, note the following. The sub-assemblies and sub-assembly
components are indented based on their level in the assembly hierarchy.
■ The Quantity field shows the amount of the item required for this work order.
You can edit component quantities until a build is associated with the work order.
If you use Multiple Units of Measure, the quantity for members of an assembly item is
always defined in base units on work orders.
■ The Units field displays the base units of the component used in the parent assembly.
■ The Description field displays the item description as recorded on the item record.
b. Select the serial or lot numbers of items to commit those items to be used to complete this
work order.
■ The Commit field displays whether the available quantity is committed on this order.
Commitment occurs only when the full quantity is available. Otherwise, commitment is
indefinitely deferred.
■ The Options field displays any custom options associated with the item.
c. Select the Purchase Order option in the Item Source list to create a special order purchase
order for a component or sub-assembly.
Note: You must identify a preferred vendor and a purchase price on an item record
for that item to be selected as a special order. For more information, see the help
topic Identifying Special Orders.
d. Select the Work Order option in the Item Source list to create a special order work order
for a component or sub-assembly.
e. Click the arrows below to view steps for each subtab.
16. If you use the Outsourced Manufacturing feature, click the Outsourcing subtab and then complete
the fields, as required. For more information, see Outsourced Manufacturing.
17. Click the Relationships subtab, and then follow the steps below, as required.
a. Check the Update Customer box to update the sales team on the customer's record with
changes made.
b. Select a Partner and partner role, if necessary.
c. Check the box in the Primary column if this partner is the lead.
d. In the Contribution % column, enter the contribution percentage for each team member.
e. Click Add.
18. If you use Team Selling, click the Sales Team subtab, and then complete the following steps, as
required.
Manufacturing
Entering an Individual Work Order 45
After the work order is recorded, you can enter an assembly build against the order to close it.
Manufacturing
Entering an Individual Work Order 46
5. Click Save.
The custom field appears on your work order form.
NetSuite starts calculating production when the first build transaction is initiated or, if WIP is enabled, the
date components have been issued. The system end date is recorded when the work order is closed. The
end date must occur on the same day or some time after the start date. You cannot record an end date if
you have not entered a start date.
For example, you start to build mountain bikes for an assembly build. The work order displays both
the production start and end dates as January 16. The work order instructions require that 10 bicycles
be built. On January 15, two bicycles were built in your facility, so the system records the Start Date
as January 15. However the other eight bicycles are assembled earlier, on January 10. NetSuite
automatically adjusts the work order Start Date as January 10 and the End Date to January 15.
Automation logic always uses transaction dates. In the preceding example, the system used the dates
from the assembly builds for these non-WIP work orders. However, NetSuite lets you manually change
start and end dates.
1. On the work order, below the Production Start or End Date, click Enter Manually.
2. Select a new date from the calendar.
For example, you can change the date from Dec. 2 to Dec. 3.
3. Click Save.
Manufacturing
Entering an Individual Work Order 47
When you enter an Production Start Date, the Production End Date is editable.
Some work orders in the queue are not intended for a particular sale. Production work orders are
generated when the back ordered quantity of an assembly reaches its assigned build point. After the
build point is reached, a work order is added in the Mass Create Work Orders queue.
For each work order, a bill of materials (BOM) is generated to facilitate picking member items for the
build. When this work order completes, the regular stock level of the assembly is increased and the
finished goods are committed to open sales orders.
Special Order work orders track assemblies for a particular sale. Production work orders track assemblies
to increase stock. Both use the same work order form, but production work orders do not link to a sale
transaction.
After work orders are entered, completing an assembly build for the work order closes the order.
For information about entering individual work orders, see Entering an Individual Work Order.
Note: All items on one work order must be committed from the same location. Items can
commit only from the location specified. This is true even if there are no available items at
the specified location, and there are items available at another location.
3. Select a Department or Class if you track them. The selected department or class appears on the
assembly build.
4. Select a Parent Item to show only child items for that parent.
5. Enter a Minimum Quantity to filter the list by the minimum set on the item record.
6. Complete the fields on the Time Phased Items subtab.
The Time Phased Items subtab displays a list of items that need to be ordered based on time-
phased replenishment.
Note: To use these enhancements for time-phased planned items, the Demand Planning
feature must be enabled.
a. Check the box in the Order column next to each item you want to create a work order for.
b. Select an Order Date.
c. Select a Production End Date.
d. Check the box next to each item to order.
Manufacturing
Mass Creating Work Orders 48
Click the Mark All button to check all boxes or click the Unmark All button to clear all
boxes.
e. Accept the suggested Quantity or enter a new amount.
Note: When you use Demand Planning, see the help topic Demand Planning on
Item Records for information about suggested quantities.
When you use Multiple Units of Measure, the quantity for members of an assembly item is
always defined in base units on work orders.
f. Check the Mark Sub-Assemblies Phantom box to treat the sub-assemblies within the
selected assembly as phantoms. The sub-assembly components are included in the
assembly work order that is generated.
For information about work orders and demand planning, see, Work Orders and Sub-
Assemblies.
7. Click the Reorder Point Items subtab.
The Reorder Point Items subtab displays a list of items that need to be ordered based on
designated reorder point. These items have a quantity available that is less than the reorder point
indicated on the item record.
Note: To use these enhancements for time-phased planned items, the Demand Planning
feature must be enabled.
a. Check the box in the Order column next to items you want to order.
Click the Mark All button to check all boxes or click the Unmark All button to clear all
boxes.
b. Accept the suggested amount to order in the Quantity column, or enter a new quantity.
The suggested NetSuite order calculation is: (preferred stock level + quantity needed) less
(quantity available + quantity on order).
c. If you use Make Departments required and Allow Per-Line Departments, select a
Department. Departments are used for the corresponding line items on generated
purchase orders. For more information, see the help topic Using Per-Line Classifications.
d. Check the Mark Sub-Assemblies Phantom box to mark an individual sub-assembly as a
phantom assembly. A phantom assembly is typically a non-stocked assembly that groups
together material needed to produce a subassembly. The Phantom BOM option lets you
define the item source for the subassembly on a line-by-line basis.
If you use the Work Orders and Demand Planning features, see Work Orders and Sub-
Assemblies.
8. Click Submit.
Work Orders are generated for the items you have indicated. Work orders generated for assembly items
that use the Reorder Point replenishment method use Forward Scheduling. This is true regardless of
the default scheduling method set in the account preferences. For more information, see Production
Scheduling Methods Overview.
Manufacturing
Marking Assemblies to Create Work Orders 49
order, or you can tag the item record. For more information, see Creating Work Orders From a Sales
Orders and Creating Work Orders From Item Records.
Manufacturing
Planned Work Orders 50
■ Open – Open planned work orders are deleted before supply planning runs.
■ Firmed – Firmed planned work orders are not deleted before supply planning runs. For more
information, see Marking Work Orders Firmed.
You can manually create planned work orders, or you can have the NetSuite supply planning process
generated the planned work orders. For more information, see Manually Entering Planned Work Orders
and Automatically Generating Planned Work Orders.
To set up preferences:
Note: If you generate orders and also use the Manufacturing Routing and Demand
Planning features, you can define production scheduling methods on work orders. For
more information, see Production Scheduling Methods Overview and Supply Planning and
Routing.
3. In the Default Work Order Status field, choose one of the following:
■ Firm Planned
■ Open Planned
Manufacturing
Planned Work Orders 51
■ Released
Your selection defines the default status of new work orders you manually create.
4. Click Save.
■ Use Component Yield – Account for material component yield loss during the ordering and planning
process
■ Round Up Quantity as Component – Round the component quantity up in the units used on work
order
Manufacturing
Component Yield Preferences 52
Accounting for material variances lets you adjust your planned usable quantity by ordering more units
than the target build quantity. Work orders can reflect item order quantities based on accurate expected
component yield assumptions, not the quantities listed on the bill of materials.
For example, you sell a coffee cup assembly that is made up of 3 components: 1 cup, 1 lid and 1 sleeve.
Every 100 assemblies produces 5 defective cups. Therefore, when ordering the cup assembly you must
order 105 units to produce 100 cups.
To prevent NetSuite from calculating the necessary quantity to build/order, clear the Use
Component Yield box.
3. If you check the Use Component Yield box, you can set the following on the item record:
■ The Quantity field on the Components subtab is disabled because this quantity is calculated
by NetSuite.
This field displays the amount required for the assembly when one unit of the assembly is being
built. This value is automatically calculated from the entries in the Component Yield and BOM
Quantity fields.
■ The BOM Quantity column displays the quantity of the component used to build an item
assuming no loss.
■ The Component Yield column displays the anticipated yield due to loss during the
manufacturing process.
For example, a Sleeve is a component of the Coffee Cup assembly. Each Coffee Cup assembly
requires a sleeve. The sleeve has an anticipated loss amount of 50%. Enter the following on the
Coffee Cup assembly item record:
Manufacturing
Component Yield Preferences 53
For example, a mountain bike assembly requires 2 units of the brake component. The component yield
is 99%. To build 5 of these assemblies requires 10.1 units of the brake component. Because you can
consume components only in whole numbers, you cannot consume 10.1 units. You need to round up to
the next highest unit. For example, 11 brake component units.
On a work order for an assembly that uses component yield, NetSuite indicates the Component Quantity,
BOM Quantity and Component yield for rounded-up components.
1. Create or edit an item record for an Inventory item or an Assembly item that is used as a sub-
assembly component.
2. In the Purchasing/Inventory subtab Inventory Management section, do one of the following:
■ To enable NetSuite to round up the quantity consumed for this item, check the Round Up
Quantity as Component box.
■ To prevent NetSuite from rounding up the quantity consumed for this item, clear this box.
When you check this option, the Quantity field on the Components subtab is disabled because this
quantity is calculated by NetSuite.
Table (1)
Filler (1)
Manufacturing
Component Yield Preferences 54
Ten percent of the leg subassemblies are processed incorrectly and are waste. When a work order is
created for 100 table assemblies, NetSuite calculates that the order requires 110 rods and 110 fillers.
Example 3a:
The item Table Assembly and the item record Use Component Yield box is not checked.
After a work order is created for 100 Table Assemblies, NetSuite follows the component yield option for
the top level assembly and sub-level components.
Because component yield is not used for the top level, NetSuite does not use component yield for the
subassembly. The work order displays a requirement of 100 rods and 100 fillers.
Example 3b:
After the Build Subassembly box is checked, NetSuite performs a yield calculation for all subassembly
components.
Item A
Item B
■ is a component of A
Item C
■ is a component of B
Item D
■ is a component of B
A work order for Item A is created and the Build Subassembly box is checked. NetSuite uses component
yield for all subassemblies (C and D) because it respects the setting of the top level assembly.
Manufacturing
Editing a Work Order 55
remove the item from the work order. The quantity of components cannot be changed to a number less
than the quantity used in a build.
4. Click Save.
Note: If you use Advanced Manufacturing, you can track updates to your work order. For more
information, see the help topic Editing Work Orders for Scheduling.
Manufacturing
Printing a Work Order Bill of Materials 56
Note: The work order tracks whether a bill of materials has been printed. It resets this flag
whenever components are committed so that new top-level assemblies may be built.
8. Click the Select Order Number field to enter or scan in transaction bar codes.
9. Check the box in the Print column next to each order you want to print a bill of materials for.
10. Click Print.
Manufacturing
Printing a Work Order Bill of Materials 57
This section shows how many of each component are needed for each unit.
An alternative way to view and print the BOM is by using the Bill of Materials Inquiry.
Manufacturing
Appending a PDF File to Print with the Bill of Materials 58
2. In the Type field, select Assembly to filter your item list to show assembly items.
3. Click Edit next to the assembly item.
4. Click the Communication subtab of the item record.
5. In the Attach File field, attach the PDF file that contains the diagram, instructions, or other
information you want to print with the BOM.
6. Check the Print with BOM box.
The printed file is in PDF format and the contents of the PDF file are appended to printed BOMs for
this assembly item.
7. Click Add.
8. Click Save.
Manufacturing
Work Orders and Demand Planning 59
In the Work Order Lead Time field, enter the lead time (in days) to build one assembly in the base unit.
Then, NetSuite calculates the lead time for a work order using the following:
Work Order Lead Time on Item Record * Quantity in base unit of measure
■ When an End Date is entered but the Start Date is blank, the start date is calculated as follows:
Start Date = End Date - (Work Order Lead Time from the item record * Quantity in base unit of
measure)
■ When a Start Date is entered but the End Date is blank, the end date is calculated as follows:
End Date = Start Date + (Work Order Lead Time from the Item Record * Quantity in base unit of
measure)
Note: The natural rounding method is used to determine the start and end date of work orders.
Manufacturing
Work Orders and Demand Planning 60
The Mark Sub-assemblies Phantom box is checked on the item record for Item A: Coffee Gift Set. When
a planned work order is generated for a Coffee Gift Set, the component assembly requirements are for
items E, F, C and D. And, the purchase order created shows these items. Notice that Item B: Coffee Bean
Pair is not a requirement itself, only its member components are required.
Also, the Mass Create Work Order page displays the lines from the supply plan with the Mark Sub-
assemblies Phantom box disabled.
By contrast, the Mark Sub-assemblies Phantom box is clear on the item record for Item A: Coffee Gift
Set. The work order is created only for items B, C, and D. If B is not available, NetSuite does not create a
work order.
Manufacturing
Advanced Bill of Materials 61
Note: After your administrator enables the Advanced Bill of Materials feature, the Advanced
BOM record replaces the Assembly/Bill of Materials record. When you use Advanced BOM, any
existing BOM is automatically converted to a read-only legacy BOM record.
Important: Bill of Materials impacts many areas within NetSuite. Before making Advanced BOM
available to your organization, test it in your sandbox or release preview account. Any company
customizations and third party integrations could also be affected.
Multiple BOM revisions are created for assemblies that were using BOM revision control. For more
information, see the help topic Revision Control BOM Management. These revisions appear on the BOM
record revisions subtab.
Manufacturing
Enabling Advanced BOM 62
Important: If you disable Advanced BOM after using it, NetSuite deletes any BOM and BOM
revision records you created when Advanced BOM was enabled. NetSuite saves only legacy BOMs.
Advanced BOM also links existing routings to corresponding legacy BOMs. NetSuite saves a copy of the
link between the routing and the assembly in the event Advanced BOM is disabled. If Advanced BOM is
disabled, the routing is linked to the assembly record.
After Advanced BOM is enabled, the Assembly/Bill of Materials label changes to Assembly on the
New Item, Assembly Item, and Saved Search forms. In addition, the Derived from Member Items Cost
Estimate Type is no longer available for Assembly Items.
Legacy BOM records should be used as back up records only. To modify a legacy BOM record, create a
copy of the legacy BOM. For more information, see Copying a BOM Record.
Create a BOM
Creating Advanced Bills of Materials and BOM Revisions
Manufacturing
Create a BOM 63
Note: Selecting an assembly from the Restrict to Assemblies field does not create a link
between the BOM and the assembly.
6. To permit all locations to use this BOM, check the Available for All Locations box.
Clear this box to limit BOM use to the locations selected in the Restrict to Locations field.
7. Check the Inactive box if you do not want this BOM to appear in search lists on records and forms.
Clear this box if you want this BOM to appear in lists.
8. If you use NetSuite OneWorld, select the Subsidiary this BOM is available for. Subsidiary is
inherited by BOM revisions.
Press and hold CTRL to select multiple subsidiaries.
9. To make the BOM available for all subsidiaries of the selected parent, check the Include Children
box.
If checked, the read-only Used on Assembly box indicates that the BOM is associated to an
assembly.
10. Click Save.
1. To create a new assembly or use an existing assembly, go to Lists > Accounting > Items.
Manufacturing
Create a BOM 64
2. Beside the assembly you want to create a BOM for, click Edit.
3. Click the Manufacturing subtab.
4. In the Bill of Materials list, click New.
■ Create a new BOM to use the same current and future revisions
■ Create alternate BOMs with minor component changes for the same product
■ Update a product version with component updates
To copy a BOM:
For example, you can set one BOM as the master default for the assembly. Then, set a second BOM as the
East Coast location default. A BOM cannot be both a master and location default. They must be assigned
to separate BOMs within an assembly.
The following diagram displays the workflow an assembly follows to select the appropriate BOM:
Manufacturing
Create a BOM 65
For example, a mountain bike work order assembly is fulfilled at Wolfe Manufacturing’s Canadian facility.
Canadian models of the mountain bike use a different wheel assembly than those manufactured in the
United States. To complete the order, the system searches the BOM settings for a location default BOM. If
a Canadian default location BOM exists, it is selected.
If a Canadian location default is not defined, the assembly then searches for a master default BOM. If a
master BOM is assigned, it is selected. If a default BOM is not assigned, no BOM is selected.
When an assembly has no BOM defined, the Items sublist on the Work Order is empty. You must
manually add components.
This default BOM workflow logic also applies to the following NetSuite records and transactions:
■ Work orders
■ Assembly builds and unbuilds
■ Supply plans
■ Standard cost roll-ups
■ Phantom items
■ BOM inquiries
For example, revision Engineering RV2 saves Wolfe Manufacturing $27,000 dollars a year because it
uses a simplified spoke insertion method on its wheel assembly. This results in faster machine run times
compared to the previous Engineering BOM.
Manufacturing
Creating BOM Revisions 66
Note: Only one revision can be active at a time. BOM revision start and end dates cannot
overlap. Gaps between revision dates are permitted.
For more information, see the help topic Updating BOM Revision Record Dates.
7. Check the Inactive box if you do not want this BOM to appear in search lists on records and forms.
Clear this box if you want this BOM to appear in lists.
8. Click Save.
9. On the Revisions subtab, click Edit beside the revision you created.
10. On the Components subtab, select an Item to include with this revision.
All associated revision components appear in this subtab.
11. Accept or edit the BOM Quantity.
You can enter partial quantities up to 5 decimals.
12. Select or enter the Units.
Use the unit of measure that is defined on the BOM and consumed in production. The unit
improves flexibility, makes BOMs easier to read, and enables you to specify quantity units of
measure.
Select an Item Source.
The work order item source determines where item quantities are taken from. For example, from
stock, work order, or purchase order.
For more information, see the Item Source field on the Phantom Assemblies window.
13. To add more items, click Add and then repeat steps 9 through 12.
After you select your components, use the Move buttons to change component order.
14. Click Save.
Manufacturing
Creating BOM Revisions 67
Note: You can update the current revision Effective End Date on a new revision. If you try to
save the new BOM revision without an effective end date, NetSuite prompts you to set the date
minus one day. After you click OK, the system automatically sets the date and saves your revision.
For example, BOM Revision 1 was created without an effective end date. You create BOM Revision
2 and enter an Effective Start Date of February 25, 2020. Attempting a save displays the following
prompt. "Effective End Date of the previous revision is not set. Do you want it to be set to current
revision Effective Start Date minus one day?” Click Go Back in the message box. Set the Effective
End Date for BOM Revision 1 to February 24, 2020 and then save BOM Revision 2.
To customize a sublist, go to Customization > List, Records, & Fields > Other Sublist Fields. After you
create a custom field, it appears on the BOM Revision Components subtab.
Manufacturing
Creating BOM Revisions 68
Note: The BOM Revision component sublist is not automatically added to the work order.
1. Go to Customization > Lists, Records, & Fields > Transaction Line Fields > New.
2. Complete the Transaction Line Field form:
a. Enter a descriptive Label name.
b. ID value is used when scripting to instances of the transaction type.
Enter a name that begins with custcol and then an underscore. If you do not enter a value,
the system generates one. For example, custolcoliqity_vendor_control_no.
c. Select an Owner. Only owners can edit this field.
d. Enter a Description of this field. For example, capture the vendor’s lot/serial number during
item receipt.
e. Select the Type of field you want to create.
f. The Store Value box is checked by default so that the entered information is stored in the
custom field. This enables you to look at data that is stored elsewhere.
Clear this box to not store changes in the custom field. If you do not store the value,
changes are discarded. You can make the field read-only.
g. Optionally, check the Use Encrypted Format box to encrypt stored values for this field in
the database (values still appear in the UI).
After you save this field, you cannot change this option.
h. Optionally, check the Inactive box. Inactive custom fields do not appear on any forms or in
global searches.
3. On the Applies To subtab, check the Work Order box.
4. On the Sourcing & Filtering subtab, in the Source List, select BOM Revision Component.
5. In the Source From list, select the Bill of Materials Revision custom field.
6. Click Save.
After a BOM revision is selected on a work order, NetSuite automatically retrieves a list of
components related to the BOM revision. This ensures that custom field information is included in
the work order. For more information, see the help topic Creating Custom Transaction Line Fields.
Manufacturing
Linking Assemblies and BOMs 69
For example, The Wolfe Company manufactures mountain bikes its U.S. location. To do this, the U.S.
location uses BOM U.S. prompting NetSuite to automatically select the BOM U.S. Routing. Due to
increased mountain bike sales, Wolfe starts to manufacture mountain bikes in Canada. To manufacture
mountain bikes in Canada, BOM CA is selected and the system automatically uses BOM CA Routing.
Important: You cannot update Bills of Materials for routings that were used before Advanced
BOM was enabled.
The Manufacturing Routing page at Lists > Supply Chain > Manufacturing Routing displays the following
updates:
Manufacturing
Creating a Manufacturing Routing 70
For example, Wolfe Manufacturing builds bicycles in their Denver location using the BOM U.S. Routing.
The company then starts manufacturing bicycles at their Ontario location. By copying the BOM U.S.
Routing and renaming it to BOM ON Routing, the Ontario location can follow the U.S. manufacturing
process.
Manufacturing
Creating a Manufacturing Routing 71
Note: Standard costing and assemblies must be enabled to use the Costed BOM Inquiry. You
can run this inquiry for a standard cost assembly item only.
Manufacturing
Running a BOM Inquiry 72
Matrix Items
Matrix items consist of multiple combinations of product styles and variations with their respective bill
of materials and routings. During production, matrix assemblies can be created using work orders and
assembly builds.
If you use the Advanced BOM feature, the Bill of Materials subtab appears on the Manufacturing subtab:
■ The Bill of Materials subtab moves from the matrix assistant to the Manufacturing subtab.
■ Both parent and child items display a bill of materials sublist.
■ BOMs can be copied from parent to child item records.
■ The BOM sublist can be updated on child items.
■ You can assign a BOM or multiple BOMs to an assembly matrix.
■ The Components subtab no longer appears on the Matrix Assistant.
Note: You can add BOMs only from the assembly matrix parent or subitem.
Manufacturing
Matrix Items 73
Note: A BOM cannot be both a master and a location default. Only one default
designation is allowed for a BOM.
8. To apply the BOM subtab settings to child matrix items, click Update Matrix.
9. In the Update Matrix Item window, check the child items to Include in this update.
10. To copy the parent BOM to all child BOMs (mass update), check the Update BOMs of Matrix Sub-
items box.
11. Click Submit.
Manufacturing
Bill of Materials Member Control for Assembly Items 74
When you use the Assembly Items feature, the components needed for assemblies are identified in the
Bill of Materials (BOM). Components required for an assembly can change due to engineering changes,
vendor supply, availability, or seasonal requirements.
BOM member control helps you ensure that the right components are included in assembly builds at
the right time. You can use BOM controls to plan for the utilization and purchase of components that are
effective or obsolete within specific time frames.
To use BOM component member control, define effective and obsolete dates for member items on
assembly records. NetSuite determines whether a component is valid for an assembly based on these
date.
■ Effective Date/Revision – Defines the first date an item can be used for an assembly. Before the
effective date, the item is not included in the BOM.
■ Obsolete Date/Revision – Defines the last date an item can be used for an assembly. After the
obsolete date, the item is not included in the BOM.
After a work order is created, NetSuite determines which components are required based on the
transaction date. If you use the Demand Planning feature, NetSuite considers the production start date
and determines which components are required on that date.
On assembly item records, choose a BOM control method and set up effective and obsolete dates.
NetSuite uses them to determine which member items are needed to create an assembly based on the
date the item is produced.
For example, Wolfe Manufacturing assembles bicycles for distribution throughout the year. The
mountain bike component item includes the following:
Wolfe creates a work order dated 3/31/2020 that includes a Mountain Bike assembly. NetSuite
examines the effective and obsolete dates for the components on the assembly record and determines
the following:
Wolfe enters a work order dated 4/1/2020 that includes a Mountain Bike assembly, and NetSuite
determines the following:
Manufacturing
Setting Up BOM Control on Assembly Item Records 75
The appropriate assembly BOM items are shown on work orders at the appropriate dates without having
to manually change each work order.
For BOM management to track which components are needed at specific times, identify effective and
obsolete dates for member items. To do this, select a BOM control method on assembly item records.
Select to set dates individually for components or to create revision records to assign to items. When a
new work order is created, NetSuite can determine the member items required based on the work order
production date. For more information, see Setting Up BOM Control on Assembly Item Records.
You can choose to set an assembly to use revision control. For more information, see Setting an Assembly
to Use Revision Control.
If you choose to manage assembly BOMs with revision records, set up revision records. For more
information, see Creating Revision Records for BOM Control.
To use Bill of Materials (BOM) component member control, define effective and obsolete dates for
assembly record member items. You can enter the effective and obsolete dates individually on assembly
records. You can also create revision records that update many assembly records at one time. The
following methods enable you to manage which items are used in assemblies based on production dates.
Select one of the following methods:
■ Using Effective Date BOM Management – Control the BOM based on dates entered on the assembly
record’s Components subtab.
■ Revision Control BOM Management – Control the BOM by selecting a version with preset dates that
determine components.
Manufacturing
Setting Up BOM Control on Assembly Item Records 76
Note: A blank effective date indicates the item has always been included.
7. In the Obsolete Date field, enter the date when an item can be included as a member for an
assembly.
■ After the Obsolete Date, the item is not included in the BOM.
■ Before the Obsolete Date, the member is included in the BOM.
Note: A blank obsolete date indicates that the item will always be included.
NetSuite can source this item record to determine the correct BOM based on the assembly production
date.
The Revision Control method enables you to set the effective or obsolete date for many items at one time
by updating one revision record. When several items use a revision record, date changes can be made on
the revision record rather than individually for many member items. Rather than changing the dates on
every line item, you change only the effective or obsolete date in the revision record.
For assembly items that use Revision Control, create revision records to define effective and obsolete
dates. The assembly effective and obsolete dates are determined by the assigned revision record.
■ As individual records. For more information, see Creating Revision Records for BOM Control.
■ From assembly record Members subtab. For more information, see Setting an Assembly to Use
Revision Control.
After a revision is assigned to an assembly member, you can enter a new work order and select the
assembly. The correct revision defaults to based on the work order production date. The work order item
list displays the correct set of member components based on the revision used.
■ If you select a new revision, the item list updates to show the correct member items.
■ If you change the date, NetSuite updates the revision to the one which is effective for that date.
To use only the assembly default revision, on the work order form, click Customize and then make the
field not selectable
■ Edited revision record effective or obsolete dates are not retroactive. Previously entered transaction
data using that revision remain unchanged.
■ BOMs created for individual assembly builds compare the transaction date to the effective and
obsolete dates.
■ On an assembly unbuild, select a revision to determine the BOM. The default revision for an unbuild is
based on the current date.
Manufacturing
Setting Up BOM Control on Assembly Item Records 77
■ BOM costs using Standard Costing are based on the effective date shown on the planned standard
cost rollup record.
Note: If you use the Matrix Items feature, you cannot set the Effective BOM Control to Revision
Control on a matrix parent item. However, you can set the Effective BOM Control to Revision
Control on a matrix subitem.
On Work Orders
NetSuite automatically populates the work order effective revision based on the effective date. If you
change the work order, NetSuite changes the components on the top level assembly based on the
revision selected.
If you change the work order revision and the Build Subassembly box is checked, top-level components
change based on the selected revision. The lower level components are determined based on the
effective date.
Demand Planning
When demand increases for member items from a parent assembly, NetSuite reviews the work order
start date to determine demand for those member items. For example, the Mountain Bike component
items include the following:
Demand for the item requires a work order to be created on 3/20 and one on 4/20. Therefore, the first
work order uses the Member Item 2, and the second one will use Member Item 1. This is relevant if the
member items are assemblies that need to have work orders created for them.
To use revision records to manage effective and obsolete dates, set the assembly record to use revision
control.
Note: If you select Revision Control, you must use revision control for this item.
4. The Default Revision field displays the default revision for this item.
Manufacturing
Setting an Assembly to Use Revision Control 78
5. If you are creating a new item record, click Save and then click Edit to re-open the item.
If you are editing an item already set to revision control, go to the next step.
6. Click the Components subtab.
7. Select an existing member Item or add a new one.
8. In the Effective Revision field, enter a revision or create a new one. The revision record effective
date determines the start time when this item is included as a member for an assembly.
For each member, the default selection is Default. The item will then be included in builds by
default.
a. To define a non-default date revision record, in the Effective Revision field, select New
b. In the New Item Revision popup window, define the following for the assembly item:
■ Name (for example, Version 2)
■ Effective Date (for example, 4/1/2020)
■ Memo – Optionally enter a memo.
■ Inactive – Check this box to not display this revision in lists.
Alternatively, enter new revision records at Lists > Accounting > Item Revisions. For more
information about revision records, see Creating Revision Records for BOM Control.
For more information about using effective fields, see Setting Up BOM Control on Assembly Item
Records.
9. Select an Obsolete Revision. The obsolete revision record date determines the end time that an
item is to be used for an assembly.
When you select an obsolete revision, the correct obsolete date displays in that field.
10. Click Done or Add.
11. Repeat the steps 1 to 4 for each member item you want to assign a revision to.
12. Click Save.
The BOM for this assembly is determined by referencing the production date of each work order against
the revision record dates for member items.
When using the Revision Control method for Bill of Materials (BOM) management, create revision records
to assign to assembly items. These revision records define effective and obsolete dates and can be
assigned to many items.
Update effective and obsolete dates on the revision record one time to change the dates for many items.
Manufacturing
Creating Revision Records for BOM Control 79
Obsolete Dates
Obsolete dates on a revision record cannot be edited. You can set the effective date and then save the
revision. NetSuite then determines the obsolete date to avoid gaps or overlaps in dates covered by
revisions.
The obsolete date field does display a value if you try to insert a revision record between two others.
For example, you have a default revision and one with an obsolete date of 1/1/2017. The default revision
has an obsolete date of 12/31/2017. Next, you create a revision with an effective date of 1/1/2017. In this
case, the obsolete date is set to 12/31/2017. After you save, NetSuite changes the obsolete date of the
Default revision to 12/31/2016. If you create another revision with an effective date of 1/1/2018, it has no
obsolete date. This is because it is the one with the latest effective date. When you save it, it still has no
obsolete date and the 2017 revision has its obsolete date set to 12/31/2017.
Note: You can use the Import Assistant to add or update item revision records based on CSV file
data. For more information, see the help topic Item Revision Import.
Manufacturing
Manufacturing Work In Process (WIP) 80
1. Issue Work Order: Move raw materials to an assembly area (work center)
2. Complete Work Order: Assemble raw materials and stock finished goods
3. Close Work Order: Reconcile variances
This separation lets you enter work order transactions that define the completion of each step, from
material consumption to assembly and completion.
To know where materials are in the manufacturing process, use WIP to track your materials and record
the number of:
Use WIP to track assembly component to identify the materials not used in the process.
Tracking goods and materials enables you to control your inventory and raw materials. Controlling stock
can help you avoid the following:
NetSuite supports production processes with a long lead time and can track item assemblies as a work in
process.
To learn when materials are issued or removed from inventory, see Entering Work Order Issues.
To use WIP, enable the feature and set up item records, see Enabling the WIP Feature.
Note: On transactions using WIP, you must identify a WIP location for line items. The WIP
line location must match on all work order issue, work order completion, and work order close
transactions.
Manufacturing
Enabling the WIP Feature 81
After the feature is enabled, you can set up items for WIP processing. For more information, see Setting
Up Items as WIP Assemblies.
Manufacturing
Setting Up Items as WIP Assemblies 82
account because the amount has been shipped. This account is required when WIP is
checked for any location.
b. Scrap Account – The expense account for scrap that occurs during work order completion.
This account is required if WIP is checked for any location.
c. WIP Account – The asset account used when a work order component issue is entered. This
account is required if WIP is checked for any location.
Note: If you change the selected WIP account, the new WIP account affects only future
transactions. Existing transactions continue to show the WIP account when the transaction
was created.
4. To create a new assembly, complete assembly item form fields. For more information, see the help
topic Creating Item Records.
5. Click Save.
When the assembly is added to a work order, you can use WIP to process the assembly.
Work orders that are only partially completed do not account for unused WIP components. They are
moved into the cost of the finish goods account, even if they have not been used.
Note: You cannot clear the WIP box after a posting assembly transaction has been
attributed to this work order.
4. Select a Location.
This field is required for WIP work orders.
5. Complete the necessary form fields. For more information, see Entering an Individual Work Order.
6. Click Save.
After you designate a work order as WIP, complete the build process using the following:
■ Work Order Issue – Issue components to track material consumption or log service against a work
order.
For more information, see Entering Work Order Issues.
■ Work Order Completion – Identify the quantity completed and stocked.
For more information, see Entering Work Order Completions.
■ Work Order Close – Generate reconciliation entries to post variances that may occur during the
manufacturing process.
For more information, see Entering Work Order Closes.
The following table shows an example of the general ledger impact for WIP transactions:
Manufacturing
Using WIP on Work Orders 83
Consumption
Completion
Close
The work order issue indicates the material is consumed against the work. Issue assembly member
components to track material consumption or log service against a work order.
After components are issued, the material value is recorded in the assigned WIP account. You can issue
components for many work orders at one time.
If you use the Multiple Units of Measure feature, the issued component quantity is recorded in base units.
Manufacturing
Using WIP on Work Orders 84
After you issue components for an order, you can enter a work order completion against it to log the
finished assemblies. For more information, see Entering Work Order Completions.
Entering a completion does not record the consumption of materials. It only records the work done on
the assembly process and journals the value of the assembly out of the assigned WIP account.
You can enter a work order completion with backflush to issue components and complete the assembly
at one time.
Manufacturing
Using WIP on Work Orders 85
Note: The work order completion Projected Value field displays the cost of the assembly. It
does not display individual components (unless you use backflush). A Work Order Close for the
work order shows the difference between the cost of the assembly and the components.
Manufacturing
Using WIP on Work Orders 86
Manufacturing
Using WIP on Work Orders 87
Associating components with specific operations can benefit operations that take a long time to
complete. Some components may not be required when the work order starts. Therefore, it is not ideal
to issue all assembly components during the first operation. If you associate components with specific
operations for a routing, components are issued on the day the corresponding operation begins. For
example, a work order is set up as follows:
■ If the special component is linked to Operation 1, the component issue date is July 1, 2020.
■ If the special component is linked to Operation 4, the component issue date is July 21, 2020.
Note: To display the Components Per Operation subtab, create a new or edit an existing
Manufacturing Routing.
Manufacturing
Associating Components with Operations 88
Associations can also be defined for existing routings on assembly item records. Based on the specified
routing, NetSuite updates the associations to components on work orders.
Warning: Changing or deleting an operation number breaks all associations to the original
operation number. For example, any component associated with the previous operation number
will not be associated with the new operation number.
Important: If you use Manufacturing Routing and Work Centers, when you enter
a completion with backflush, you must complete additional steps. See Entering a
Completion With Backflush.
Manufacturing
Entering a Completion for an Individual Work Order 89
Note: If the Allow Overage on Work Order Transactions preference is enabled, then you
can complete/issue a quantity larger than planned.
6. If the ending operation is the last operation, you can enter a scrap quantity.
Manufacturing
Entering a Completion for an Individual Work Order 90
The quantity of assemblies scrapped, posts a value to the scrap account indicated on the item
record.
7. Verify the Quantity to Build:
When the ending operation is the last operation, the Quantity to Build field is populated with the
completed quantity. The quantity is marked completed and moved to inventory.
You cannot modify the quantity in this field. It updates dynamically based on the starting and
ending operation.
8. If this is a lot numbered or serial numbered assembly, click Inventory Detail to enter lot or serial
numbers.
If you use Multiple Units of Measure, the Units field on the Inventory Detail record defaults to base
units and cannot be changed.
9. Click Save.
Standard cost assemblies have costs calculated based on the WIP account indicated for the order, not by
date.
For example:
■ A bicycle wheel is made of the following component parts: rims, tires, and spokes.
□ Rims cost $5.
□ Tires cost $6.
□ Spokes cost $7.
□ The total bicycle wheel cost is $18.
■ When a work order is still in process, the standard cost of components changes to the following:
□ Rims cost $4.
□ Tires cost $5.
□ Spokes cost $6.
□ The total bicycle wheel cost is $15.
■ The change in the bicycle wheel cost from $18 to $15 requires the following WIP cost adjustment:
□ (-1) for each component issued
□ (-3) for each assembly taken out of the WIP location
When the standard cost for an inventory or assembly item in a location changes, note the following.
NetSuite creates a separate standard cost revaluation transaction for each partially built work order.
NetSuite creates standard cost revaluation transactions for each work order that does not have a status
of Released or Built.
Manufacturing
WIP and Inventory Costing 91
Cost of a Component
■ For an actual cost item or average cost item, the average or actual cost from the warehouse location is
posted.
■ For a standard cost item, the standard cost for component is posted.
Note: If you use WIP, an average cost assembly item generates a variance based on the
assembly cost and the component cost. If an adjustment needs to be made on the average cost
based on the variance, you should use an inventory adjustment worksheet.
Manufacturing
Manufacturing Routing 92
Manufacturing Routing
Manufacturing Routing and Work Center lets you schedule and record manufacturing operational
activities against a work order that requires multiple employees, or work centers. For example, you may
have a set of operations for the following: a preparation team, an assembly run team, and a quality
assurance team.
You can use the Manufacturing Routing and Work Center feature to record quantity assembly
completions and team resource costs. You can also use it to process overhead costs against individual
work order operations.
The following roles represent members of your organization who can benefit from using Manufacturing
Routing.
■ Set up a routing record that defines multiple steps for building a complex assembly.
■ Assign default scheduling parameters against each step.
■ Use backward scheduling to establish a supply plan based on manufacturing scheduling
requirements.
Production Manager
Your Production Manager can refine the shop floor tracking activities using the following:
Cost Accountant
Your Cost Accountant can identify opportunity areas:
■ Manufacturing Routing can be used only with assembly items using standard costing or
average costing.
■ Manufacturing Routing can be used only with work orders that are marked as Work In Process
(WIP).
■ Manufacturing Routing creates variances based on per-service item and cost categories.
To use the Manufacturing Routing and Work Center feature, a user with sufficient permission must do the
following:
Manufacturing
Cost Accountant 93
Completion records show the time machines and labor used. When time is entered against an operation
task, the scheduling for all tasks related to the work order automatically update. This update accurately
portrays progress against each operation. For more information, see Manufacturing Routing Completions
and Time Entry.
Values for assets and expenses associated with a routing work order post to the designated Work In
Process (WIP) account during the assembly process.
Manufacturing
Setting Up Manufacturing Routing 94
Values are added to the WIP account based on time logged against operation tasks or quantity produced
in a run. After the assembly process completes, the values are removed from the WIP account and added
to the Asset for Assembly account. For more information, see Manufacturing Routing Costing.
The following features must be enabled to use the Manufacturing Routing and Work Center feature:
Manufacturing
Setting Up Manufacturing Routing 95
Setting this preference enables NetSuite to automatically create planned time entries when processing
manufacturing work orders. When you use this preference, work orders display a new Planned Time
subtab. NetSuite generates planned time entries showing the amount of time being allocated to each
work center per day. The Planned Time subtab displays the duration of each operation and the associated
work center. When you examine this planned time data, you can determine if the resource capacity is
enough to meet needs, providing efficient manufacturing planning.
When you use this preference, NetSuite automatically recalculates planned time after each completion.
For example, your process requires Operation 10, which produces a completed quantity of 30. Next, you
report the completion of Operation 10 with a quantity of 15 and NetSuite recalculates the planned time
for the remaining quantity.
Note: If you use the Manufacturing Routing and Demand Planning features, note
the following. A selection to generate orders provides the option to define production
scheduling methods on work orders. For more information, see Supply Planning and
Routing.
5. Click Save.
Note: You can activate the Planned Time subtab on work orders that were entered prior to using
the Show Planned Capacity on Work Orders preference. To do so, open the work order in edit
mode, and then save. The Planned Time subtab and planned time entries appear on that work
order.
Manufacturing
Setting Up Manufacturing Routing 96
and employ workers to assemble widgets that you sell. You need to track costs associated with employee
labor, warehouse machines, and overhead associated with each work order.
You can create one of the following eight cost categories to help track costs:
■ Direct Cost – These costs are calculated when you record time for these items.
□ Labor Setup – Cost of time for labor to set up a run
For example, this is the cost of paying an employee to set up the machine that will be used to paint
the widget.
□ Labor Run – Cost of time for labor to run an assembly
For example, this is the cost of paying an employee to use the machine that paints the widget
during the assembly run.
□ Machine Setup – Cost of time spent to set up a machine to be used in a run
For example, each time you set up the machine that paints the widget, wear and tear costs you .02
cents.
□ Machine Run – Cost of time spent to run a machine during assembly
For example, each time you use the machine that paints the widget for an assembly run, wear and
tear costs you .04 cents.
■ Overheads
□ Labor Setup Overhead – Cost of overhead associated with labor to set up a run
For example, this is the safety training expense incurred for an employee who sets up the machine
used to paint the widget.
□ Labor Run Overhead – Cost of overhead associated with labor to run an assembly
For example, this is the safety training expense incurred for an employee completes an assembly
run.
□ Machine Setup Overhead – Cost of overhead associated with setting up a machine used in a run
For example, this is the water expense incurred by running a machine during the machine set up.
□ Machine Run Overhead – cost of overhead associated with running a machine during assembly
For example, this is the water expense incurred by running a machine during an assembly run.
1. To add choices to this list, go to Setup > Accounting > Setup Tasks > Accounting Lists..
2. Click New.
3. Click Cost Category.
4. Enter a name for the cost category. For example, US Labor Run Standard.
5. Select a cost type for this category. Choose from the following:
■ Labor Run
■ Labor Run Overhead
■ Labor Setup
■ Labor Setup Overhead
■ Machine Run
■ Machine Run Overhead
■ Machine Setup
■ Machine Setup Overhead
Manufacturing
Setting Up Manufacturing Routing 97
6. Check the Inactive box if you do not want this category to show in lists.
For information about creating a new cost category, see the help topic Creating Cost Categories.
A manufacturing charge item cannot be associated with a unit type even if you use the Multiple Units of
Measure feature. For information, see the help topic Creating Item Records.
Manufacturing
Setting Up Manufacturing Routing 98
For example, an employee works 10 hours on an assembly activity. A manufacturing operator needs to
record the hours worked as a completion for this step. The cost template defines costs associated with
the step completed: the rate for each activity, and what accounts these amounts should post to.
A manufacturing cost template streamlines tracking assembly process costs. It provides which rates and
accounts are commonly used for each step in an assembly process.
Important: Including too many cost types on a manufacturing cost template may degrade
NetSuite performance. Performance is compounded when multiple cost items are not related to
production.
1. Go to Lists > Supply Chain > Manufacturing Cost Template > New.
2. Enter a name for the template.
3. Optionally enter a memo. You can search for text you enter here to find this template later.
4. Check the Inactive box if you do not want this template to show in lists on forms and records.
Clear this box if you do want this template to show in lists.
5. Select a cost category.
For information about creating a cost category, see Defining Cost Categories for Manufacturing
Routing and Work Center.
6. Select an item.
Only items that have been marked as Manufacturing Charge Items show on this list.
For more information, see Defining a Manufacturing Charge Item.
7. Enter rates up to 7 decimal places for this line item.
■ If this is a Setup category, enter a fixed rate. This is a one-time charge for a setup activity.
■ If this is a Run category, enter a run rate. This is an amount charged for each run completed.
Note: Template creation performance is negatively affected when the number of lines on
the cost templates is not kept to a minimum.
8. Click Add.
9. Repeat steps 5 through 8 for each category. Enter one category for each activity associated with
this operational step.
You can add only one of each of the following cost category types: Labor Run, Machine Setup, or
Machine Run. However, you can add multiple categories for Overhead cost category types.
10. When all necessary categories have been added, click Save.
Manufacturing Labor Setup Service Warm up molding Fixed $10 per run Labor Setup
machine
Manufacturing
Setting Up Manufacturing Routing 99
Manufacturing Labor Setup Facility rental Fixed $16 per run Labor Setup
Overhead Overhead 1
Manufacturing Labor Run Service Costs to complete Run $14 per hour Labor Run
one run
Manufacturing Labor Run Electric utility cost per Run $13 per hour Labor Run Overhead
Overhead Service run 1
You create work centers by creating a static group, and then identifying it as a manufacturing work
center.
Note: You are selected by default. Only the owner of a group can add or remove
members or delete the group.
7. Check the Manufacturing Work Center box. This enables this group to be used as a work center
with routing records.
8. Click the Manufacturing Work Center Settings subtab.
9. Select one or more locations to associate with this work center.
If you use NetSuite OneWorld, you can select multiple locations within a subsidiary.
10. Enter the number of machine resources for this work center.
If this machine is used in multiple work centers, enter a decimal amount. For example, if this
machine is used by another work center for half the day, enter .05.
11. Enter number of labor resources for this work center.
If labor is used by multiple work centers, enter a decimal amount. For example, if a welder spends
only two hours in this work center in a day, enter .025.
12. Complete any additional fields necessary for this group record.
13. Click Save.
Manufacturing
Setting Up Manufacturing Routing 100
NetSuite uses the associated work calendar to schedule the operation tasks associated with each work
center.
For more information about creating a static group record, read the help topic Creating a Static Group.
Your production manager can set up a work calendar for each work center that specifies the hours
available for each. Based on this work center calendar information, you have real-time visibility into total
scheduling capacity. You also have intelligent manufacturing routing that calculates the processing time.
After you create the work calendar, specify that calendar on the work center record. Then, NetSuite
can use the designated work calendar to determine the time when resources should be scheduled for
associated manufacturing operation tasks.
Based on the requirement date, the supply planning engine determines the start date of a planned order.
The supply planning engine uses backward scheduling, based on the work calendar assigned. The supply
planning engine also considers work center calendars for forward scheduling when creating work orders.
Manufacturing
Work Center Calendars 101
After you create a routing record, that routing can be selected on a work order to direct the completion
of the assembly. The routing determines the work center, cost template, labor resources, and machine
resources that will be used during the assembly.
Routings are unique for each assembly item. However, routings can be shared across multiple locations.
Manufacturing
Creating a Manufacturing Routing 102
Tip: You can create a new routing by clicking the New Manufacturing Routing button on the
Manufacturing subtab of an assembly item record.
1. Cost Version
Verify that you have created a cost version.
For more information, see Defining Cost Versions Defining Cost Versions.
2. Planned Standard Cost Rollup
Run a cost rollup to calculate assembly cost. When you run a cost rollup, NetSuite checks for
a default routing to calculate costs for the assembly. If you have no defined default routings,
NetSuite uses the first routing created as the default routing to calculate the assembly cost.
Manufacturing
Creating a Manufacturing Routing 103
Planned Standard cost is a consolidation of cost based on the component and cost category.
For subassemblies, each of the cost categories are rolled up to the next level in the Bill of
Materials (BOM) hierarchy. The difference between the cost categories of this level and lower
levels in the roll up depend on the items associated with the rollup.
Note the following when you review the cost of an assembly item based on the cost rollup. The
lower level routing cost of building the subassembly is denoted with the subassembly item as
a component on the planned standard cost record. The routing cost of building this level final
assembly is denoted as follows. The Service and Other charge items appear as a component on
the planned standard cost record.
For more information, see the help topic Standard Cost Rollup.
3. Inventory Revaluation
When you use Standard Costing features, run update production cost to establish a standard cost
in production.
For more information, see the help topic Revalue Standard Cost Inventory.
■ Part 2: Rate
Based on the manufacturing charge item, the quantity is the total hours required.
The total unit cost is derived at a component level per cost category and per operation sequence.
■ Number of resources (from the work center) x Setup Time (from the routing record) x Manufacturing
Charge Item Unit Cost (from the item record)
■ Number of resources (from the work center) x Run Rate (from the routing record) x Manufacturing
Charge Item Unit Cost (from the item record)
The routing you use on a work order is a template that describes the required steps to build an assembly
item. The routing determines the work center, cost template, labor resources, and machine resources to
use during assembly.
Manufacturing
Manufacturing Routing and Work Orders 104
■ If you do not use NetSuite OneWorld, the schedule time zone is based on the time zone selected for
the company.
For more information, see the help topic Configuring Company Information.
■ If you do use NetSuite OneWorld, the schedule time zone is based on the time zone of the subsidiary
selected on the work order.
Manufacturing
Manufacturing Operation Tasks 105
Each of these tasks is a step that must be done in order for the assembly process to finish. After work for
the task has been done, manufacturing operators can log progress against each task on a work order
completion form.
■ Operation Sequence
■ Operation Name
■ Predecessor
■ Start Date
■ End Date
■ Input Quantity
■ Completed Quantity
■ Setup Time (Min)
■ Run Rate (Min/Unit)
Note: You can also modify tasks from the work order. Go to Transactions > Manufacturing >
Enter Work Orders > List. Click Edit next to the work order to be edited. Then click the Operations
subtab to view a list of operation tasks.
After task records are created, you can open and modify them individually. For more information, see
Editing a Manufacturing Operation Task.
Manufacturing
Manufacturing Operation Tasks 106
Operations Overlap
When you use the Manufacturing Routing feature, manufacturing planners can use the operations
overlap function to schedule overlapping manufacturing operations. Overlapping of manufacturing
operations can reduce work order lead times and allow more efficient utilization of manufacturing
resources. When you set up operations to overlap, work order operations can be processed in a
staggered method through the production cycle.
For example, a manufacturing routing requires two steps to complete a work order. However, work on
Step 2 requires that only half of Step 1 is completed. Therefore, it is more efficient to start Step 2 when
Step 1 is half-complete rather than waiting until it is 100% complete. This can be accomplished by defining
overlap for operations on the routing record.
First, a planning operator defines how a subsequent operation can overlap an earlier operation. The lag
amount can be based on time, quantity, or percentage on the manufacturing routing. After the defined
portion of the first operation completes, the second operation automatically begins.
For each sequence of the routing, you can define a lag type using the following types:
Autocalculate Lag
If you choose to autocalculate the routing, NetSuite can automatically calculate the optimal lag amount.
The Optimal (Minimal) Lag Amount is the shortest possible lead time for each work order. Optimizing lag
means that operations on a work order are scheduled strategically. This minimizes the lead time of the
order and maximize the utilization of work centers within the work order.
To autocalculate lag amount, check the Auto-Calculate Lag box on the routing record. When you check
this box, NetSuite disables the following fields in the grid:
■ Lag Type
■ Lag Amount
■ Lag Unit of Measure
If you want to define the fields noted above, do not check the Auto-Calculate Lag box. If you choose to
define these values, they default on work orders.
Manufacturing
Manufacturing Operation Tasks 107
If lag settings are changed on the operation record, NetSuite reschedules the operation when the task is
saved. The task reflects the new settings and reschedules all affected subsequent tasks.
When a work order is scheduled, NetSuite calculates the Optimal (Minimal) Lag Amount and Maximal Lag
Amount for each operation. This is true if the operation has a preceding operation and defined lag type.
Then, NetSuite does not allow the lag amount to be defined outside of this range.
The autocalculation setting can be changed only when the status of a work order is Planned or Released.
After creation, click the Operations subtab on work orders to view the Start Date/Time and End Date/Time
of each operation.
On the operation task record under the Predecessor section, the Lag Type and Lag Amount can be
edited. After save, NetSuite validates that each lag amount entered falls between the Optimal (Minimal)
Lag Amount and Maximal Lag Amount. If the lag amount entered is outside this range, an error displays
the valid range.
■ If the lag amount defined on the routing is less than the Optimal (Minimal) Lag Amount, it is adjusted
to the optimal lag amount.
■ If the lag amount defined on the routing is greater than the Maximal Lag Amount, it is adjusted to
equal the maximal lag amount.
After work is logged against the order and the status is In Process, you can no longer edit the operation
tasks.
■ Manufacturing charge items – Charge items are derived from the routing template, but can be
modified as necessary for individual orders.
■ Estimated time required for completion
When you enter a setup time or run time on the task record, these times are planned estimates and
are used for scheduling. It is only after completion time is entered against a task is the actual time
updated in the Actual Hours field.
Task dependencies are assigned based on the numeric order of the operation sequence and are not
editable.
Manufacturing
Manufacturing Operation Tasks 108
Note: When you modify task settings, labor and machine scheduling reflects calculations
based on the new entries after you save the task changes.
4. Click Save.
You can also modify tasks from the work order. Go to Transactions > Manufacturing > Enter Work
Orders > List. Click Edit next to the work order to be edited. Click the Operations subtab to view a list of
operation tasks.
You can view the operation tasks list and filter the list to show only tasks associated with Work Center 2.
Customize the view to show the Predecessor and Predecessor Completed Quantity. These fields let you
see which tasks Work Center 2 is due to work on next. (Create a custom view for the task list to display
specific columns and information by clicking Edit View.)
For example, the task list shows that two work orders have tasks for which the predecessors are
completed. You know that Work Center 2 needs to work on those tasks. When Work Center 2 finishes
their requirement for the tasks, click View next to those tasks in the task list to enter completions. The
completions entered then update associated work orders with new predecessor data. The work center
task lists display the updated task statuses.
After completions are entered for tasks, scheduling is updated for labor and machines to reflect
calculations based on the new entries.
For example, you complete work earlier than anticipated. Therefore, subsequent tasks move up and
start and end dates reschedule to be earlier. However, if a completion reflects that work is falling behind,
subsequent tasks move out and start and end dates reschedule to be later.
Manufacturing
Manufacturing Operation Tasks 109
Availability
The Manufacturing Task Scheduler is available in the shared Supply Chain Management SuiteApp. For
more information about this SuiteApp, see the Availability section of Supply Chain Management Reports.
You may also contact your NetSuite account manager.
For information about installing the Supply Chain Management SuiteApp, see the help topic Installing
Supply Chain Management.
For information on enabling features and preferences, see the help topic Enabling Features.
For instructions, see the help topic Installing Supply Chain Management. For information about installing
bundles, see the help topic Installing a Bundle.
Supply Chain Management is a managed SuiteApp and is automatically updated whenever there are
changes. Issue fixes and enhancements are available after the SuiteApp is updated in your account.
Manufacturing
Manufacturing Operation Tasks 110
By default, the following standard roles are granted full permissions to the two custom records that are
listed in the table:
■ CEO
■ CFO
■ Sales Vice President
■ Accountant
■ Accountant (Reviewer)
■ Bookkeeper
■ Warehouse Manager
In addition to the two custom records, ensure you assign the other permissions to standard or custom
roles. To edit or customize a role, go to Setup > Users/Roles > Manage Roles. On the Manage Roles page,
click the Role name to open the record and verify that the permissions are set to the required level. For
more information about editing or customizing roles, see the help topic Customizing or Creating NetSuite
Roles.
Based on your role, you can access the Manufacturing Task Scheduler by following the appropriate path:
■ Warehouse Manager
Inventory >Manufacturing> Manufacturing Task Scheduler
■ Administrator
Transaction>Manufacturing> Manufacturing Task Scheduler
■ Executive or Accounting
Financial > Manufacturing> Manufacturing Task Scheduler
View the following topics for the correct usage of the Manufacturing Task Scheduler:
■ Task Views
■ Time Period Bar
Manufacturing
Manufacturing Operation Tasks 111
See the following figure and table to learn the sections and tools of the Manufacturing Task Scheduler.
Work View options Switches the work view: Work Center or Work Order
2 Expand All/Collapse All Displays all or hides all tasks within a work center or work order
Time Period Changes the time period displayed on the chart: Daily, Weekly, Monthly
Date Range Displays the start and end date of a time period
Date Range icons Moves the start date from the previous or next date
Chart Header Displays the specific day, week, or month within the current date range
4 Manufacturing Operation Displays the list of tasks within a work center or work order
5 Summary Bar Represents all tasks on the chart assigned to a work center or work order
Manufacturing
Manufacturing Operation Tasks 112
7 Legend Provides a short description of each color on the summary and task bar
Task Views
The default Task View displays all your work orders, excluding work orders on Planned, Built, and Closed
Status, and those from the subsidiary. Use the default view or create a custom view if you need to closely
monitor a specific set of tasks. When creating a custom view, set your preferences for any of the following
filters:
Note: The Manufacturing Task Scheduler can display only a maximum of 2000 operation tasks
per page. Creating a custom view can be helpful in limiting the number of tasks to display on the
chart.
On the Task View Filter bar, the Add View button appears only on the default view. The Edit View and
Copy View buttons appear only on a custom view. The following instructions describe how to use any of
these task view controls.
■ To add a view
To create a custom view, click Add View. Assign a name to the view and select your preference for any
of the filters.
■ To edit a view
To make changes to a custom view, select the name of the view and then click Edit View. The current
preferences for the selected view are displayed on the form, which you can change or update.
■ To copy a view
To make a slight variation of an existing view, use the Copy View option.
For custom views with a specified date range for the production start date, the start and end of the range
appear with vertical bars. All production start dates that fall within the range appear inside the bars.
On the sample screenshot, the vertical bars on the chart are placed on the week of July 27 and August 31.
The production start date of all tasks fall within the vertical bars, and the date range.
Manufacturing
Manufacturing Operation Tasks 113
■ Daily: shows the day, month, and date on the date header. A total of 14 days appear at a time.
On the Daily chart, task bars cover the entire day, regardless of the number of work hours.
■ Weekly: shows the month and date of the first day of the week, on the date header. A total of 12
weeks appear at a time.
■ Monthly: shows the month and year on the date header. A total of 6 months appear at a time.
Based on your selected time period, the date range automatically adjusts. The date range displays the
start and end date of the current period covered, for the daily and weekly time period. When you select
the monthly option, it displays the start and end month with the year.
The previous or next icon (beside the date range) moves the start and end date or month before or after
the current selection, respectively. This automatically adjusts the date header and chart view.
In Work Order view, you can also see the assembly item of each work order and the work center where
the task is assigned. The pagination at the right side of the time period bar represents the number of
work orders on the current page. To go to a specific work order, select from the range of work order
numbers. On the chart, the summary bar across each work order represents all tasks under it.
Note: You cannot reassign and reschedule tasks through drag and drop of the task bars. You
must switch back to Work Center view to update the tasks directly on the chart.
To return to the initial list of work centers, remove any criteria on the search tool, and then click the
search icon.
Click the Expand All or Collapse All links to display or hide the work orders of all work centers at the same
time. This expands or collapses work centers across all pages, and persists when you move from one
page to another.
When work centers or work orders are collapsed, the chart displays only the summary bars. Summary
bars are useful in the following ways:
■ You can compare the summary bars across all work centers or work orders.
Manufacturing
Manufacturing Operation Tasks 114
■ In the Work Center view, displaying only the summary bars highlights any overloaded or underloaded
resource.
You can also use the pagination controls at the right side of the time period bar to help in searching for a
work center. It displays the current number of work centers displayed on the page. Click the down arrow
to view and select another page. Use the previous and next arrows to move from one page to the next.
The Manufacturing Task Scheduler can display a maximum of 20 work centers or work orders per page.
All work orders are represented on the summary bar across each work center, in green. You can check for
conflicting tasks with overlapping schedules, which appear in red.
Check the color codes on the legend bar. Use the following table as a guide to the definition or
description of colors used in the task bar, summary bar, and chart.
Color Definition
Green (Task Assigned) Summary bar color that indicates an assigned task
Red (Task Conflict) Summary bar color that indicates one or more tasks with overlapping schedules
Yellow (Not Started) Task bar color that indicates a task that has not started
Blue (Completed) Task bar color that indicates a task’s percentage of completion
Task Conflicts
On Work Center view, the summary bar displays all operation tasks assigned to a work center. The
summary bar can display a task conflict in red, if two or more overlapping tasks exceed the total working
hours per day.
The sample screenshot shows overlapping tasks in conflict for April 8 and 9, but not for April 10. This is
derived by comparing the duration of all tasks for a certain day against the total working hours allotted
for the work center.
Manufacturing
Manufacturing Operation Tasks 115
The following table shows the duration or working hours for each task and the total duration per day. You
can see how the overlapping tasks are shown as such in the summary bar. For April 8 and 9, the total task
duration exceeds the allotted 8 working hours for Work Center 3.
The duration is indicated in the planned time details of a work order. To view the duration of tasks in a
work order, go to Transactions > Manufacturing > Enter Work Orders > List. On a specific Work Order
page, view the duration on the Planned Time tab. For more information, see Manufacturing Routing and
Work Orders.
On the chart, you can adjust the schedule of a task, or reassign a task to another work center to resolve a
task conflict. For more information, see Update Tasks Using the Manufacturing Task Scheduler.
■ Reassign a Task
■ Forward Scheduling on the Manufacturing Task Scheduler
■ Backward Scheduling on the Manufacturing Task Scheduler
■ Update a Task Record
Note: You can update tasks directly on the chart only when you are on the Work Center view.
Use the task view filters to limit the view to specific work centers where the reassignment or
rescheduling are going to be performed.
Manufacturing
Manufacturing Operation Tasks 116
When you update the chart, appropriate icons appear to inform you which tasks can be reassigned and
updated. Refer to the list of icons used on the chart:
■ : This lock icon on the cursor indicates that the task is not open for reassignment or rescheduling.
■ : No lock on the cursor means that the task can be transferred to another chart location.
■ : This icon indicates that the task can be transferred to the new chart location.
■ : This icon indicates that the task cannot be transferred to the new chart location.
You can also check the work order status of the task to determine if the details can be updated or
changed. Only tasks with Planned or Released work order status can be updated.
To check the work order status, place the cursor on the task bar to display specific details from its
manufacturing operation task record.
Reassign a Task
To reassign a task, drag the task bar upward or downward within the same column, toward the new work
center.
Note: You cannot reassign a task to an inactive work center, or one that belongs to a different
subsidiary.
Manufacturing
Manufacturing Operation Tasks 117
As you drag the task bar, the check icon appears beside the start and end dates. This indicates that you
can drop the task onto the specific chart location on the new work center. The reassigned task retains all
its details, except for the new work center number.
Set your chart to the Work Center view to start forward scheduling. To locate the first task in the work
order, the sequence number located beside the work order number is first in the operation process. To
move the schedule to a different date, drag the task bar to the left or right of the original start date (same
row). You can drop the task to the new location when you see the new start date appear with a check
icon.
Note: Select the appropriate time period option to locate a new date on a different week or
month. Use the previous and next date range arrows to adjust the dates on the view.
After you move the date of the first operation task, NetSuite automatically adjusts the schedules of the
succeeding tasks. Switch to the Work Order view to review the new schedule of tasks within the work
order. NetSuite applies the changes made on the chart to the work order and operation task records.
To start backward scheduling, set your chart to the Work Center view by clicking its link located above the
chart header. On the left pane, look for the last operation task of the work order to be rescheduled. On
the chart, drag and drop the task bar of the last operation task to the new date.
■ Drag to the right of the current date to move the schedule to a later date.
■ Drag to the left of the current date to move the schedule to an earlier date.
When the last operation task bar has a new date, NetSuite automatically adjusts the preceding tasks to
accommodate the new schedule. You can review the new task schedules by switching to the Work Order
view.
Manufacturing
Manufacturing Operation Tasks 118
■ Setup Time
■ Run Time
■ Work Center
■ Machine Resources
■ Labor Resources
After you change a record, any adjustments to the time or date automatically appear on any dependent
fields. For more information about editing the task details, see Editing a Manufacturing Operation Task.
Limitations
Take note of the following limitations when using Manufacturing Task Scheduler:
■ The Manufacturing Task Scheduler does not support the following date formats for specific languages:
□ Chinese (Simplified)
▬ YYYY M D
▬ YYYY MM DD
□ Dutch
▬ D. MMM YYYY
▬ DD. MMM YYYY
□ Vietnamese
▬ D MONTH, YYYY
▬ DD MONTH, YYYY
Note: Procurement lead times do not affect these time requirement calculations.
The supply planning method used depends on whether a default routing is identified.
Manufacturing
Supply Planning and Routing 119
Note: Without a default routing, NetSuite makes calculations without reference to any
calendar or resource requirements.
■ Setup Time = Total cumulative setup time across all operation sequences in the default routing
■ Run Rate = Total cumulative run time across all operation sequences in the default routing
■ Total Hours per day = Total number of hours available on the associated work calendar
NetSuite calculates the order by backward scheduling from the due date. NetSuite does consider the
associated work calendar for days available, including holidays.
If changes are made to the associated work calendar or to the routing record, you should regenerate the
supply plan. These changes can include:
■ modifying the work calendar (such as to increase/decrease the working days or add/remove holidays)
■ editing the routing to increase/decrease a setup time or run rate
After regeneration, NetSuite modifies the order dates to reflect the new requirements and still meet the
due date deadline.
Do Not Generate — The supply plan uses backward scheduling to determine order date.
In this case, NetSuite creates only the supply plan line, not the Work
Order.
Manufacturing
Supply Planning and Routing 120
Not Do Not Forward The supply plan uses backward scheduling to determine the order
Generate date. Within the supply plan run, NetSuite automatically creates a work
order, and sets the production start date the same as the order date.
When the work order is created, NetSuite uses forward scheduling to
calculate the work order production end date and sets the production
start date.
Not Do Not Backward NetSuite creates a work order using the receipt date from the demand
Generate plan. The production end date is set at one day prior to the receipt
date. This allows time to complete production and be available on the
required date. The work order uses backward scheduling to calculate
the work order production start date.
For information about setting the Generate Work Order in Supply Plan preference, see Setting Routing
Preferences.
Forward Scheduling
Forward scheduling lets you set a production start date. Then, 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 dimmed 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. Based on data from the associated routing and related work center calendar,
NetSuite calculates the time, materials, and resources required to complete all operations. NetSuite
determines the production start date based on these calculations.
When you use Backward Scheduling on work orders, the Production End Date field is required. The
Production Start Date field is dimmed because it is automatically calculated.
Note: This calculated start date may be a date in the past, prior to the current date.
When Backward Scheduling is set as the default scheduling method, different factors determine the
production end date on generated work orders. For more information, see Backward Scheduling.
Manufacturing
Production Scheduling Methods Overview 121
These scheduling methods can be used when generating individual work orders and by generating work
orders using supply planning.
When a work order is saved, or generated, the supply planning engine calculates requirements and then
generates necessary work orders. On the work order Operations subtab, click an operation name to view
or edit details about the operation.
To choose a production scheduling method, you must first set these preferences:
This method you select automatically completes work orders. However, you can change the method on
individual orders with a status of Planned or Released.
Backward Scheduling
When you use the backward scheduling method for production planning, you set the production end
date. This is the date you need to have the completed items. Based on data from the associated routing
and related work center calendar, NetSuite calculates the time, materials, and resources required
to complete all operations. NetSuite determines the production start date and time based on these
calculations.
For example, you need to schedule an order of widgets that requires two operations to complete a
production run. Each operation requires 1 day of setup time and 10 days of production time. Operation 1
must be complete before Operation 2 can start. These production requirements appear in the following
illustration:
Manufacturing
Production Scheduling Methods Overview 122
When you enter the items completed date, NetSuite calculates the day work must begin to complete
production on time. When a work order is created by a supply plan, NetSuite schedules work so that
the last operation is completed before the due date. The due date time is 00:01 AM. Therefore, the last
operation on the work order is scheduled for completion by 11:59 PM on the day before the due date.
The time displayed for each operation is based on work hours set for each work center. For more
information, see Creating Manufacturing Work Centers or Groups.
Planners who use the Backward Scheduling method can reduce waste of manufacturing resources
because NetSuite calculates start dates automatically. Work order production is scheduled to start as late
as possible, giving planners flexibility to cancel or change an order.
Note: The NetSuite planning engine calculations may set a production start date in the past,
depending on the end date entered.
Production work is not automatically reallocated based on resource capacity. After work orders are
created, you may need to assess resource assignments.
When Backward Scheduling is used as the default scheduling method, the production end date on
generated work orders is determined using the following factors:
■ Sales Order - The box in the Create WO column on the Items subtab is checked. This is true for an
item that uses the WIP multi-step production process. A work order is generated for your assembly
item. The production end date on the work order is set to one day before the expected ship date on
the work order. If no expected ship date is entered, the production end date is set to the same day as
the sales order date.
■ Work Order - The box in the Create WO column on the Items subtab is checked. A work order is
generated for a sub-assembly. The sub-assembly’s production end date is set to the same date as the
parent item’s production start date.
■ Supply Plan - A work order is generated during a supply plan. The production end date for a sub-
assembly is set to the same date as the parent item’s production start date.
Important: The Generate Work Orders in Supply Planning preference must be set to any
option except Do not Generate.
■ Mass Creating Work Orders - Reorder point is the Replenishment Method. NetSuite uses Forward
Scheduling for the work orders regardless of the default scheduling method set in the account
preferences.
Manufacturing
Manufacturing Routing Completions and Time Entry 123
After you enter an operation task completion, on the record, click Actions > GL Impact to see completion
effects on the general ledger. The GL Impact page shows the overheads and labor expenses recorded
against the WIP account.
When you mark the final task work for an assembly completed, saving the completion records the items
as put into inventory. When you view the GL Impact page, the value is removed from the WIP account and
added to the inventory account.
You can set a preference for completion validation. For more information, see Completion Validation
Preference.
Note: When a completion and issue occurs and the status is not closed or built, the operation
status automatically changes to in-progress.
For detailed steps on entering a completion from a work order, see Entering a Completion for an
Individual Work Order.
Manufacturing
Manufacturing Routing Completions and Time Entry 124
Choose one of the following settings for the Check Completed Quantity in Prior Operations During
Operation Completion preference:
■ No Verification – Choose this setting if you do not want to receive verification warnings.
■ Require Confirmation before Saving – Choose this setting to receive verification warnings. NetSuite
permits the completed quantity to be greater than the predecessor completed quantity after the
warning is acknowledged.
■ Do Not Allow Saving – Choose this setting to require that the completed quantity is not greater than
the predecessor completed quantity.
Note: This field defaults to No Verification. If you do not change this default setting, unverified
completions can be entered. For more information about setting this preference, see the help
topic Order Management Accounting Preferences.
For example, completing Operation B requires a set amount of items that are generated during
Operation A. You can verify that the requirements of the predecessor have been met before saving the
completion for Operation B.
■ Creating 5 units during Operation A is a predecessor for creating 5 units during Operation B.
■ You choose the preference setting Do Not Allow Saving. The total completed quantity of Operation B
cannot be greater than the total completed quantity of Operation A.
■ Operation B requires 5 units that are created during Operation A. NetSuite verifies that 5 units are
completed during Operation A before Operation B can begin.
For orders completed across multiple days or shifts, partial quantities can be logged over time.
Operation A 50 30 15 5
Operation B 40 40 5 15
Operation C 35 45 0 20
Manufacturing
Manufacturing Routing Completions and Time Entry 125
Entering data on the completion form enables you to define the following information:
The Operations subtab shows which operations are being completed and the amount of labor and
machine time to record against each operation.
Note: Enter the completed quantity in the Operation Completion section of the form. The
Completed Quantity field on the Operations subtab is read–only.
For example, enter a completed quantity of 1, with the starting operation of 10, and ending operation of
30.
Operations 10, 20, and 30, the completed quantity is multiplied against the labor and machine time
requirements set on the operation task record. The labor and machine time fields on the Operations
subtab are populated.
The Operations subtab can be used as follows for each operation completed:
■ Completed Quantity displays the amount entered in the Completed Quantity field.
■ To record Setup Time:
□ If you have not recorded an operation setup time against an operation, the setup columns display
the full operation setup time. Time is based on the setup time defined on the operation task
record.
Check the Record Setup Time box.
For each operation, you have the following options:
▬ Modify the default setup time quantity.
Manufacturing
Manufacturing Routing Completions and Time Entry 126
Default run time = Qty completed x Run rate on the operation record
After the system enters labor and machine times for all completed operation tasks, NetSuite calculates
the progress and costs of the assembly.
Often machine and labor resources working concurrently are fully used against a certain operation task.
In such cases, both resource types are weighted equally to determine the true time recorded on the
operation task record.
Sometimes, one resource may have a higher value than the other resource for a certain task. For
example, on a task, the machine run time is less than labor run time. In such a case, the critical path is the
labor time because it is the greater of the two. NetSuite updates the production schedule based on the
larger requirement of the two. This applies to setup time and run time.
In another example, the recorded machine time is larger than the labor time because the machine can
run without constantly being overseen by labor. In this case, the machine time is the critical path, and
NetSuite uses it to update scheduling. NetSuite uses the labor time for costing purposes.
For an operation, if the labor run time is larger than the machine run time, NetSuite uses the labor run
time as the true hours.
Note: The default values that show for machine run and labor run times can be modified to
accommodate individual run times.
After the appropriate time values are determined, the amount appears in the Actual Hours field on the
operation task record. Based on the hours recorded, NetSuite adjusts the schedule of subsequent tasks
to provide a realistic view for completions.
■ Not Started
□ No time is recorded against the task.
□ No quantity completed is recorded on the task.
■ In Progress
□ Some time is recorded against the task.
□ Some quantity completed is recorded on the task and the completed quantity is less than the input
quantity required.
Manufacturing
Manufacturing Routing Completions and Time Entry 127
■ Completed
□ The completed quantity is equal to or greater than the input quantity required or the work order is
closed.
After you mark an order as built or closed, the operational task record associated with that order displays
a task status displays as Completed.
Manufacturing
Manufacturing Routing Costing 128
Values are added to the WIP account based on time logged against operation tasks or quantity produced
in a run. After the assembly process completes, the values are removed from the WIP account and added
to the Asset for Assembly account.
Account Formula
The result of these calculations posts to the WIP account for the assembly. Costs can be one of two types:
setup costs or run costs.
Setup Costs
Costs need to be logged for expenses related to setting up for an assembly run. These costs are defined
on the operation task record and are based on time logged against the task.
Note: Setup costs are only time dependent, not based on quantity produced.
For example, the operation task Staging defines costs on the Cost Detail subtab. One cost category
defined is Labor Setup. Using this category on a task defines the following:
■ The Labor Setup cost category record indicates the item Other Charge for Purchase - Labor Setup.
■ The task record defines the fixed rate for using the item Other Charge for Purchase - Labor Setup at
$30 .
■ The item record for Other Charge for Purchase - Labor Setup indicates the Assembly Staging
Expense expense account.
Therefore, when you log time against the Staging task, the appropriate amount posts to the
Assembly Staging Expense account. This amount is calculated as Expense amount = Setup time
logged x Labor setup fixed rate.
If 2 hours of time are logged against the Staging task, $60 is logged to the Assembly Staging
Expense account.
Similar calculations are made for other categories that may be defined on a task record. For example,
overheads (Overhead expense amount = Setup time logged x overhead rate).
Manufacturing
Manufacturing Routing Costing 129
Run Costs
Costs need to be logged for expenses related to processing an assembly run. These costs are defined on
the operation task record and are based on quantity completed during the assembly run.
For example, the operation task Staging defines costs on the Cost Detail subtab. One cost category
defined is Labor Run. Using this category on a task defines the following:
■ The Labor Setup cost category record indicates the item Other Charge for Purchase - Labor Run.
■ The task record defines the run rate for using the item Other Charge for Purchase - Labor Run at
$65 .
■ The item record for Other Charge for Purchase - Labor Setup indicates the Assembly Staging
Expense account.
Therefore, when you log time against the Staging task, the appropriate amount posts to the
Assembly Staging Expense account. This amount is calculated as Expense amount = Setup time
logged x Labor setup fixed rate.
If 10 units are completed for the Staging task, $650 is logged to the Assembly Staging Expense
expense account.
Similar calculations are made for other categories that may be defined on a task record. For example,
overheads (Overhead expense amount = Run quantity logged x overhead rate).
# of Resources x Setup Time x Manufacturing Charge Item # of Resources (work center) x Run Rate (routing
Unit Cost / Standard Cost Lot Size (assembly item - item record) x Manufacturing Charge Item Unit Cost (item
location map) record)
Manufacturing
Manufacturing Routing Costing 130
Manufacturing
Outsourced Manufacturing 131
Outsourced Manufacturing
Outsourced Manufacturing helps customers manage their subcontracted manufacturing processes by
purchasing outsourced assembly production from vendors. This feature enables NetSuite to automatically
consume production components, and then after production, transfer them to a specified location.
Automating Outsourced Manufacturing synchronizes NetSuite procurement and production transactions.
Now you can define an outsourcing location for the vendor who will outsource manufacturing for you.
Manufacturing
Setting up Outsourced Manufacturing 132
Important: You must have locations defined before you can configure your outsourced
manufacturing location. For more information, see the help topic Creating Locations.
2. On the Vendors page, click Edit next to the vender who will outsource manufacturing for you.
3. Click the Outsourced Manufacturing subtab.
4. Beside the Manufacturing Locations field, click the arrow icon.
5. In the Choose Manufacturing Location list, select the location or locations, for the outsourcing
vendor.
Note: Each location can be used by one vendor, but a vendor can use multiple locations.
6. Click Done.
7. Click Save.
Manufacturing
Setting up Outsourced Manufacturing 133
Note: When you select Outsourcing Charge, the Can Be Fulfilled/Received box on the
Preferences subtab is checked and cannot be cleared.
After you create the outsourcing charge item, you must perform the following tasks:
■ Create a Bill of Materials (BOM). For example, Outsourced BOM. For more information, see Create a
BOM.
■ Create a BOM Revision. For more information, see the help topic Creating BOM Revisions.
1. On the Bill of Materials Revision page, in the Item list, select the components you keep in
inventory and will provide to the vendor. For example, bike seats and bicycle wheels.
2. Select the Outsourcing Charge item.
3. Enter the BOM Quantity per assembly. For example, 1 seat, 2 wheels, and 1 charge item.
4. Click Save.
■ Create an Assembly Item. For more information, see the help topic Creating Item Records.
1. On the Manufacturing subtab, select the Bill of Materials.
2. Optionally, click the Master Default box to designate this as your default BOM for this
assembly.
3. Click Save.
Manufacturing
Outsourcing Production 134
Outsourcing Production
NetSuite enables customers to outsource their manufacturing efforts to vendors. Customers can
outsource from either a purchase order or from a work order.
Note: NetSuite automatically creates an Inventory Transfer and not a Transfer Order.
Manufacturing
Outsourcing Production 135
1. On the Purchase Order page, on the Items subtab, click the Items subtab.
2. Click the link in the Assembly Build Helper column.
The Assembly Build Helper page displays the assembly items with editable fields. You can change
the field values, as needed. For example, the vendor built 5 bicycle seats in production, therefore,
twenty–seats were consumed. The Quantity field shows that twenty seats were consumed in the
assembly build. You can change that number to twenty-five.
3. In the Quantity field, accept the default number, or enter a new number.
If you use serial lot numbers for consumed or produced final production, you can edit these field
values on the Assembly Build Helper page.
When you override a purchase order rate for a line, NetSuite automatically uses the new rate in the
final assembly charge.
4. Click Save.
Manufacturing
Outsourcing Production 136
Note: Before the Outsourced Manufacturing feature can be enabled, an administrator must
enable prerequisite features. To learn more, see Setting up Outsourced Manufacturing.
Manufacturing
SuiteAnalytics Manufacturing Workbook 137
■ Manufacturing Dataset
■ Manufacturing Workbook
■ Manufacturing Analytical Record Types
The SuiteAnalytics Workbook user interface enables customers with little record schema and query
language knowledge to create complex workbooks using drag-and-drop editing. New customization
options provide ways to display your data using rich formatting. For more information, see the help topic
SuiteAnalytics Workbook Overview.
Manufacturing Dataset
This Manufacturing dataset combines fields from the Manufacturing Transaction record type and one
custom formula. This dataset enables you to analyze the status of bills received during the last month. It
forms the source data for the Manufacturing Workbook.
Dataset Configuration
The Manufacturing dataset combines fields from one record type, one custom formula, and multiple
criteria filters. To edit the dataset, see the help topic Defining a Dataset.
Root Record Type Joined Custom Formula Field Data Grid Criteria Filers
Record Type
Manufacturing (none) The following custom formula is The following fields are The following criteria is
Transaction included in the dataset: included in the dataset. used to filer the dataset:
Manufacturing Workbook
NetSuite provides a Manufacturing Transaction data source, which introduces the analytics transactions
concept for manufacturing-specific transactions. The following transaction record types are available in
the Manufacturing Transaction data source:
Manufacturing
Manufacturing Workbook 138
For more information, see Manufacturing Transaction and Creating a Manufacturing Workbook.
Manufacturing Transaction
Manufacturing Transaction is a modified transaction record that improves manufacturing data searches
for the following manufacturing transactions:
■ Work Order
■ Assembly Build
■ Assembly Unbuild
■ Issue Components
■ Work Order Completion
■ Work Order Completion with Backflush
■ Work Order Close
These searches are filtered so that specified transaction types return results faster than generic
transaction searches. The data set is optimized for manufacturing by making the assembly field available
in the manufacturing transaction.
When you join a manufacturing component transaction line, the results return only components as
displayed on the form with positive quantities. Joining generic transaction lines can cause the main line to
behave as a component. Providing results with negative quantities (consumed during the production).
If you need a field from the larger generic transaction data set, you can join it to a Manufacturing
Transaction/Component. This join provides an expanded list of available fields.
Manufacturing
Manufacturing Workbook 139
You can use only those fields that you add to the Data Grid to generate a pivot table or
chart. By default, the Data Grid displays preselected fields, based on the root record selected
for the workbook.
3. To select source data, use one of the following options to add fields from the Manufacturing
Transaction record root to the data grid:
■ From the Manufacturing Transaction record, drag a field to the Data Grid
■ Double-click a field
■ In the Search field, enter the field name and then drag or double-click the field
a. To add fields to the data grid from the Manufacturing Transaction related record, click the
Join Record icon ( ).
Manufacturing
Manufacturing Workbook 140
h. In the Filter window, select the filter conditions to apply to the field.
Manufacturing
Manufacturing Workbook 141
a. Select the summary type and format options for any date or numerical fields.
1. Beside the next to the field you want to format, click the Field Menu icon ( ).
2. Select Summary Types.
b. Add totals and grand totals to the pivot table:
1. In the menu bar, click the totaling icon ( ).
2. In the Totaling window, for each field, select where you want the totals or grand
totals to appear.
3. Check the Set Individually box to select where the totals for each field will appear
on the pivot table.
4. Click OK.
c. Click Refresh ( ) to generate the pivot table.
Manufacturing
Manufacturing Workbook 142
b. Select the summary type and format options for any date or numerical fields.
1. Beside the next to the field you want to format, click the Field Menu icon ( ).
2. Select Summary Types.
c. In the Layout panel select a chart type.
d. Click Refresh ( ) to generate the chart.
e. In the Workbook Menu ( ), click Save As.
f. In the Save Workbook As window, enter a name and description for the workbook.
g. Click Apply.
Manufacturing
Manufacturing Analytical Record Types 143
This record type is the root record type on the Manufacturing Dataset. To access the record type or the
dataset, you must have the Assembly Items feature enabled. Some fields in the record type are also
feature dependent, or display values based on custom formula definitions.
For more information about the fields included in the manufacturing transaction analytical record type,
see the following table:
Bill of Materials Transaction Bill of Materials Displayed only with the Advanced BOM
feature enabled
Bill of Materials Transaction Bill of Materials Revision Displayed only with the Advanced BOM
Revision feature enabled
Buildable Transaction Line Buildable Displayed only with the Work Orders
feature enabled
TransactionLine.QUANTITY_SHIP_RECV
Class Transaction Line Class Displayed only with the Classes feature
enabled
End Date Transaction End Date Displayed only with the Manufacturing
Routing and Work Center, Demand
Planning, or MRP features enabled.
Location Transaction Line Location Displayed only with the Locations feature
enabled
Posting Period Transaction Posting Period Displayed only with the Accounting Periods
feature enabled
Manufacturing
Manufacturing Analytical Record Types 144
Start Date Transaction Start Date Displayed only with the Manufacturing
Routing and Work Center OR Demand
Planning or MRP features enabled.
Units Transaction Line Units Displayed only with the Multiple Units of
Measure feature enabled
The manufacturing component analytical record type is included in the field list on the Manufacturing
Dataset. To access the record type, you must have the Assembly Items feature enabled. Some fields in the
record type are also feature dependent, or display values based on custom formula definitions.
For more information about the fields included in the manufacturing component analytical record type,
see the following table:
Build Variance Transaction Line Build Variance Displayed only with Work Orders feature enabled
Manufacturing
Manufacturing Analytical Record Types 145
THEN get_item_avail(componentLine.” +
TransactionLineCommonFragment.FieldId.ITEM + “,
componentLine.” + LocationSelectFragment.FieldId.LOCATION
+ “) “ +
“THEN get_invtitem_onhand(componentLine.”
+ TransactionLineCommonFragment.
FieldId.ITEM + “, nvl(componentLine.” +
LocationSelectFragment.FieldId.LOCATION + “, —1)) “ +
“-sign(nvl(nullif(componentLine.” +
TransactionLineQuantityFragment.FieldId.QUANTITY + “, 0),
—1))” +
“ * “ +
“decode(“ +
“componentLine.” + TransactionLineCommonFragment.FieldId.
ITEM_TYPE + “, ‘Group’,NULL, “ +
“nvl2(“ +
“accountingLine.” + TransactionAccountingLineAccount
Fragment.FieldId.ACCOUNT + “, “ +
“decode(“ +“componentLine.” +
TransactionLineQuantityFragment.FieldId.QUANTITY + “, NULL
“, “ +
“componentLine.” + TransactionLine.FieldId.QUANTITY_SHIP_
RECV + “)” +
“, NULL)) “ +
Units Transaction Line Units Displayed only with Multiple Unit of Measure feature enabled
Manufacturing
Engineering Change Order 146
The Engineering Change Order feature lets you generate engineering change order (ECO) records. These
records document changes to your Bills of Materials (BOMs) and authorize the implementation of those
changes.
■ Using the ECO record, you can list item and bill of materials to be updated, and specify reasons for the
change.
■ Through the SuiteApprovals workflow, you create approval rules for your ECO records.
■ Each ECO record is evaluated and routed for approval through the applicable approval rule.
■ After approval, changes entered on the ECO record are automatically or manually implemented, and
affected records are modified.
■ You can keep track of revisions to items and BOMs using ECO lists and implementation logs.
■ Advanced Bill of Materials - List the quantities of raw materials, assemblies, sub-components, and
parts needed to manufacture a product at one or multiple facilities. After your administrator enables
the Advanced Bill of Materials feature, the Advanced BOM replaces the Assembly/Bill of Materials
record. For more information, see Advanced Bill of Materials.
■ Approval Routing - When you use approval routing, transactions that are entered are not processed
until they are approved. This gives provides oversight to persons of authority who can reject some
transactions if they do not wan them to continue being processed. For more information, see the help
topic Approval Routing.
Availability
The Engineering Change Order feature is available in the Supply Chain Management SuiteApp. For
information about this SuiteApp, see the Availability section of Supply Chain Management Reports. You
may also contact your NetSuite account manager.
Limitations
■ Engineering Change Order supports Inventory and Assembly Items only.
■ Use of the feature requires Advanced Bill of Materials.
■ Custom workflows for ECO approval are not currently supported.
■ A User Event (UE) script execution threshold is associated with successful loading of ECO records. ECO
records are successfully loaded when the account has no more than 80,000–90,000 active assembly
and inventory items per subsidiary.
■ Support for SOAP web services and CSV import is currently not available with the feature.
■ The feature does not support Legacy BOM. For more information, see Enabling Advanced BOM.
Manufacturing
Setup Requirements for Engineering Change Order 147
For instructions, see the help topic Installing Supply Chain Management.
For information on installing bundles, see the help topic Installing a Bundle.
You must perform this setup before Enabling Engineering Change Order.
Important: Custom workflows for ECO approvals are not currently supported.
Installation
For instructions, see the help topic Installing the SuiteApprovals SuiteApp.
Manufacturing
Setup Requirements for Engineering Change Order 148
Important: Access to the Supply Chain Preferences page is supported only for users with
Administrator roles.
After the feature is enabled, set up the role records of those who will use engineering change order. For
more information, see Roles and Permissions for Engineering Change Order.
■ Accountant (View)
■ CEO
■ CFO
■ Warehouse Manager
■ Administrator
Note: Administrator role is not available for selection in approval matrices. For more information,
see Setting Up SuiteApprovals Workflow for Engineering Change Order.
Other roles need additional permissions to use the feature. The table below outlines the permissions
required for using Engineering Change Order and SuiteApprovals. For information about customizing
roles, see the help topic Customizing or Creating NetSuite Roles.
Permission Level
Manufacturing
Setup Requirements for Engineering Change Order 149
Permission Level
After you customize a role to access SuiteApprovals and Engineering Change Order lists and records, an
administrator must add the role to script deployments.
Manufacturing
Setup Requirements for Engineering Change Order 150
To use SuiteApprovals, you must also set up the following requirements for users and approvers:
For more information about assigning roles, see the help topic Assigning Roles to an Employee.
To add access to Implement Engineering Change Order records for a custom role:
1. Go to Customization > Scripting > Script Deployments.
2. Click Edit next to ECO Implement SU.
3. On the Audience subtab, in the Roles field, select the roles you want to have access to Implement
Engineering Change Order record.
You can select multiple roles by holding down the Ctrl key when selecting each role.
4. When you finish, click Save.
Manufacturing
Setup Requirements for Engineering Change Order 151
You can select multiple roles by holding down the Ctrl key when selecting each role.
4. When you finish, click Save.
Note: If you do not want to use the preference, refer to the instructions in Implementing
Engineering Change Orders.
Before you set up engineering change order types, identify the departments and business processes that
would require control of change activities.
There is no limit to the number of change types you can create. The only requirement is that each type is
unique.
Important: Engineering Change Order supports the following actions in an ECO regardless of
ECO type: Add, Replace, and Remove.
1. Go to Lists > Engineering > Engineering Change Order Type > New (Administrator).
2. On the Engineering Change Order Type page:
a. In the Code field, optionally enter a unique code for the ECO type. If you enter a code, the
code will prefix the name of the ECO type.
b. In the ECO Type field, enter a unique name for the ECO type.
c. Optionally, enter additional information about the ECO Type in the Description field.
3. When you have finished, click Save.
Alternately, you can open the Engineering Change Order Type page by clicking New Engineering
Change Order Type. This button is located on the Engineering Change Order Type List page at Lists >
Engineering > Engineering Change Order Type.
Manufacturing
Setting Up Engineering Change Order Types 152
■ You define the criteria of a rule based on your change management process, the ECO Types you
created, and approval schedules.
■ You then create an approval list composed of employees required to act on ECO records defined by
the criteria.
The following procedures must be completed to set up the SuiteApprovals workflow for engineering
change order:
When you create an approval rule, you can require approval from an employee who is authorized to
approve ECOs for a department. To select an employee as department approver, you must first set up a
Manufacturing
Setting Up SuiteApprovals Workflow for Engineering Change Order 153
record for that employee. You can set up only one department approver per department, or combination
of department and subsidiary.
1. Go to Setup > Workflow Manager > Set Up Department Approver > New.
2. Select a department and a subsidiary. For NetSuite OneWorld, the combination of department and
subsidiary must be unique.
3. In the Approver field, select the employee you want to assign as department approver.
4. When you finish, click Save or Save & New to create another record.
Important: Setting up of department approver records through SOAP web services or CSV
import is not currently supported.
When you create an approval rule for ECOs, you can require approval from one or all members of a
specific group of employees. To add approvers of the types Group (Any) and Group (All) to an approval
list, you must first set up group records. For steps to create group records, see the help topic Working
with Groups.
Ensure that employee records of group members are active to avoid errors when adding these approver
types in approval lists.
Note: Inactive employees, employees from different subsidiaries, or those without login access
are considered invalid members. These employees will not be added as approvers when the group
they belong to is selected as group approver.
Note: You do not need to create groups based on roles. For more information, see Set Up Role
Approvers for Engineering Change Order.
Manufacturing
Setting Up SuiteApprovals Workflow for Engineering Change Order 154
Ensure that role records are active to avoid errors when adding these approver types in approval rules.
Note: Only active employees in the same subsidiary of the approval rule will be added as
approver for any of the Role approver types.
Note: You can only delegate approval to another employee within your subsidiary.
To delegate approval:
You can return to your record anytime to change your approval delegation details.
You can create approval rules using the Approval Rule page or the Approval Rule Assistant.
Manufacturing
Setting Up SuiteApprovals Workflow for Engineering Change Order 155
■ If you want to use a saved search in an approval rule, create saved searches of ECO records before
you create approval rules. For more information, see the help topic Saved Searches.
■ By default, an approval rule locks ECO records that are in Approved or Pending Approval status. An
ECO record may be edited and resubmitted for approval only if its status is set to Rejected. For more
information, see Resubmitting Engineering Change Orders for Approval.
Manufacturing
Setting Up SuiteApprovals Workflow for Engineering Change Order 156
Note: Engineering Change order does not use amount validation. The amount validation
fields are disabled on the approval rule record.
By default, approval routing is set to custom approval. Build your approval hierarchy using the
matrix. You can add approvers of the following types:
■ Employee Supervisor - The direct supervisor of the employee who submits the ECO record.
See Assign a Supervisor to an Employee.
■ Specific Approver - Any employee that belongs to the same subsidiary as the approval rule.
■ Department Approver - You can only select an employee as department approver if a record is
already set up for that employee. For more information, see Setting Up Department Approvers
for Engineering Change Order.
■ Group (Any) - Select a group to require that at least one of its members takes action on the
ECO record. See Set Up Group Approvers for Engineering Change Order.
■ Group (All) - Select a group to require that all its members take action on the ECO record.
■ Role (Any) - Select a role to require that at least one employee with the role takes action on the
ECO record. See Set Up Role Approvers for Engineering Change Order.
■ Role (All) - Select a role to require that all employees with the role take action on the ECO
record.
Important: When adding approvers, consider the sequence by which you add each one.
Make sure the hierarchy you build meets your approval process and requirements.
■ The employee’s supervisor is the first approver, by default. Click the Delete icon to remove the
supervisor from the approval chain, or to add back in another place in the sequence.
■ Click Add Approver, and select the Approver Type and Approver. Repeat these instructions to
add more approvers.
■ Ensure that you add all the required approvers, and that the sequence is correct.
Manufacturing
Setting Up SuiteApprovals Workflow for Engineering Change Order 157
Note: Engineering Change order does not use amount validation. The amount validation
fields are disabled on the approval rule record.
By default, approval routing is set to custom approval. Build your approval hierarchy using the
matrix.
You can add approvers of the following types:
■ Employee Supervisor - The direct supervisor of the employee who submits the ECO record.
See Assign a Supervisor to an Employee.
■ Specific Approver - Any employee that belongs to the same subsidiary as the approval rule.
■ Department Approver - You can only select an employee as department approver if a record is
already set up for that employee. For more information, see Setting Up Department Approvers
for Engineering Change Order.
■ Group (Any) - Select a group to require that at least one of its members takes action on the
ECO record. See Set Up Group Approvers for Engineering Change Order.
■ Group (All) - Select a group to require that all its members take action on the ECO record.
■ Role (Any) - Select a role to require that at least one employee with the role takes action on the
ECO record. See Set Up Role Approvers for Engineering Change Order.
■ Role (All) - Select a role to require that all employees with the role take action on the ECO
record.
Important: When adding approvers, consider the sequence by which you add each one.
Ensure the hierarchy you build meets your approval process and requirements.
■ The employee’s supervisor is the first approver, by default. Click the Delete icon to remove the
supervisor from the approval chain, or to add back in another place in the sequence.
■ Click Add Approver, and select the Approver Type and Approver. Repeat these instructions to
add more approvers.
■ Ensure that you add all the required approvers, and that the sequence is correct.
Manufacturing
Setting Up SuiteApprovals Workflow for Engineering Change Order 158
Important: You can make extensive changes to an approval rule only if it is not currently
running. If it is running, you can update only the rule’s end date. The system validates the updated
rule for uniqueness.
Important: You cannot delete an approval matrix if there is an ECO record in Pending Approval
that is using the approval matrix.
Manufacturing
Using Engineering Change Order 159
To review how approval rules work, see Approval Rules for Engineering Change Order.
■ Multiple Add actions for one or more items in one ECO record.
■ Multiple Remove actions for one or more items in one ECO record.
■ Multiple Replace actions for one or more items in one ECO record.
■ A mix of Add, Remove, and Replace actions for one or more items in one ECO record.
■ Add, Remove, and Replace actions for the same BOM and BOM revision are processed together.
NetSuite sends an email notification to coordinators of ECOs when bulk processes complete. The email
body contains a link to the ECO record and error details, if any occurred during implementation.
Note: During manual or automatic implementation, you can view the Implementation Status
of any ECO and track the status of each change action. For more information, see Viewing
Implementation Status.
1. Go to Lists > Engineering > Engineering Change Order > New (Administrator).
2. Use the following table to complete the Primary Information section.
Field Description
Date Creation date is set to today’s date by default. You may set this to a future
date.
Effective Start Date Use the calendar to set the date when the change order becomes effective.
Effective End Date Use the calendar to set the date when the change order becomes obsolete.
The effective end date is not mandatory.
Next Approver Displays a value after the ECO enters the approval workflow, depending on
the approval rule.
Inactive Leave this box clear to keep the ECO record active.
Manufacturing
Using Engineering Change Order 160
Note: Ensure you selected a subsidiary (NetSuite OneWorld) before entering product
change details. You can select only those items and assembly items associated with the
selected subsidiary.
Action Procedure
Add 1. In the Item field, enter the name of the item you want to add to a BOM.
4. Click Save.
5. Review the change details and click Save.
Remove 1. In the Item field, enter the name of the item you want to remove from a BOM.
Manufacturing
Using Engineering Change Order 161
Action Procedure
■ Enter the New Revision of the BOM after the change is implemented.
■ Repeat Steps 2 and 3 to enter more Remove change lines for the same item.
4. Click Save.
5. Review the change details and click Save.
Note: This change action removes the entire quantity of the item. The feature does
not allow removal of partial quantity.
Replace 1. In the Item field, enter the name of the item you want replaced in a BOM.
2. In the Item Replacement field, enter the replacement item.
Note: The Item and Item Replacement fields return search results as you
enter text.
5. Click Save.
6. Review the change details and click Save.
Important: You can update the product change details in the Add Change popup
window. However, the primary information values on the ECO record cannot be changed.
Note: Use the Process Changes, Notes, and Documentation / Files subtabs, as needed.
Instructions are available in the following steps.
Use the Process Changes subtab of the ECO record to enter process change information
for documentation and approval purposes.
Manufacturing
Using Engineering Change Order 162
If you edit the ECO record, the timestamp adjusts to the current date and time.
Note: ECO records for process changes go through approval. Ensure that you create
approval rules for these change types. For more information, see Approval Rules for
Engineering Change Order.
Important: The Make Copy function for ECO records does not support the duplication of
Product Changes entries onto the copy.
2. On the Engineering Change Order List page, locate the ECO record you want to copy.
3. Click the View link for the ECO record.
4. On the ECO record, select Make Copy under Actions.
5. Make changes in the Primary Information fields, as needed.
6. Click Save.
You use the email notifications generated by SuiteApprovals to view and take action on the ECO records
for your approval.
Manufacturing
Using Engineering Change Order 163
■ The ECO creator and users with access to the ECO, except the current approver, can update and
resubmit the record.
■ The user who originally submitted the ECO record cannot be an approver.
The resubmitted record is revalidated and either exits the workflow, or is routed for approval. Email
notifications are sent to specific recipients depending on the changes applied to the record and the
workflow state the record is in.
Manufacturing
Using Engineering Change Order 164
Note: Set the Implement Engineering Change Order Upon Final Approval preference to
automatically implement approved ECOs. See Setting Engineering Change Order Preference.
Note: You may need to click the collapse (-) icon for a change line to view its
implementation status.
Manufacturing