In this task you will create a BOM parent record for each of your M items. The creation of the BOM parent record is often done at the same time that you assign your BOM Routing structure for each respective BOM.
Related Tasks Progression
•In subsequent tasks, you will create your Work Centers and Subcontractors that form the backbone of your shop schedule
•You will create your BOM Parent record and create the BOM Routing for that parent BOM
•You will then enter or import your BOM Components and assign them to the Work Center/Subcontractor routing sequence where those components will be issued to the job
Task Notes:
•Create a BOM parent for each of your M items in the Bill of Manufacturing screen using the + button and lookup.
•You can create all of your BOM Parents in advance. Or you can perform the header record creation step one item at a time as you assign your BOM Routing structure to each parent BOM in the BOM Routings Super Task to follow.
•Accept the default BOM type of 'BOM' unless you have specific need for the 'Batch' or 'Secondary' type. Avoid the 'Phantom' type for now until you assess its potential use during the Custom Manufacturing phase.
•If an item needs a Revision Name other than the default name, assign it an appropriate name.
Links:
Bill of Manufacturing Guide - Product Structures (Subassemblies)
Bill of Manufacturing Guide - BOM Types
Bill of Manufacturing Guide - Outputs
Screen Help - Bill of Manufacturing
NOTE: Confine your activities in this task to the List and Revision tabs.
BOM Parent Guidelines
Do not substitute phantom assemblies for subassemblies
Do not substitute phantom assemblies for subassemblies. The use of phantom assemblies should be limited to representing product options with custom manufacturing. A phantom assembly does not have a routing and can never be made on its own job or be stocked, which eliminates any possibility of using forecast and supply days planning, and they cannot be released to production in the correct order of multi-level assembly.
Never use revisions to represent different products or options
Revisions should only be used to represent versions of the same product. Never attempt to use revisions to represent different products or product options using a common BOM parent. This will not work and causes problems with costing, MRP, and inventory.
Use One-Off Items for custom manufactured Items
You can generate one off items from sales orders to create a custom item and BOM for custom manufacturing processing. There will be more information on the custom manufacturing workflow in Phase 8 of the Startup Wizard.
Common Questions
Can I use phantom assemblies to flatten my BOMs and reduce the number of jobs?
In light manufacturing systems, it is a common practice to “flatten” BOMs so that multiple levels can be represented within a single parent item. This creates “super jobs” where the entire component structure can be backflushed at job finish in a single transaction.
In general, avoid creating super jobs using phantom assemblies, which is counter-productive to the routing architecture that distinguishes DBA from light manufacturing systems. Routings enable each assembly in the product structure to be defined with its own processes and materials in its own BOM. Separate BOMs enable jobs to be released to production in the correct order of assembly and for job sequences to be listed in work centers in correct processing order.
Avoid substituting phantom assemblies for subassemblies. The use of phantom assemblies should be limited to representing product options with custom manufacturing. A phantom assembly does not have a routing and can never be made on its own job or be stocked, which eliminates any possibility of using forecast and supply days planning, and they cannot be released to production in the correct order of multi-level assembly.
The only instance where a super job achieved with phantom assemblies might make sense is when both of these conditions are met:
•The entire product structure is made in a single chain where subassemblies have no interdependent demand with other jobs.
•The entire product structure is essentially all made at once with no staggering of start dates among its subassemblies.
Very few products meet both of these conditions, so in most cases you will avoid super jobs and use subassemblies to take full advantage of the time-phased nature of MRP and shop control.
