Data Map

Data Map

This section describes how each field is set on the Child MO.

BOM Type/Name: as specified in the Picklist for the Parent MO. By default it will attempt to use the MFG BOM.

Draw From Site: Draw From Site has several potential sources. It is retrieved from the following sources, in the order shown below. Use as an example a top-level MO for 100XLG.

The first source is the Issue From site from the BA100G subassembly line on the 100XLG BOM.

The second source is the Default Issue From site on the BOM Header of the subassembly BOM.

Lastly, it will use the Draw From Site on the Scheduling Preference. See Scheduling Preference below.

Due Date: set to Parent MO Start Date, then adjusted for Lead Time Offset (if Use Component Lead Time Offset is marked) and Down Days.

MO Description: set to Parent MO Number.

MO Number: the top level Parent MO Number is used as a prefix for all MOs below the top. If the top level MO is MO00123, the first subassembly below the top is MO00123-0001, the next subassembly at that level will be MO00123-0002, and so on.

Note that the Create Child MOs utility runs automatically when it detects that the Manufacturing module is scheduling a Manufacturing Order. This results in MOs being created for first-level subassemblies, and when those are scheduled it triggers creating MOs for second-level subassemblies, and so on. The result is the subassembly MOs numbers will tend to be numbered across a level, then down to the next level and across that level, rather than from top-to-bottom within an assembly and then top-to-bottom within another assembly.

Post To Site: set to the Parent MO Draw From Site. If this is empty, it uses the Scheduling Preference Draw From Site. See Scheduling Preference below.

Quantity: set to the Component Quantity from the Parent MO Picklist, converted to a quantity in the base Unit of Measure. The quantity to make of the subassembly item can be altered. See the Custom Business Logic chapter for more information on changing the quantity.

Routing Name: by default, the subassembly Primary Routing will be used. An alternative Routing Name can be provided. See the Custom Business Logic chapter for more information on how to provide a Routing Name.

Scheduling Method: always Backward Infinite because the subassembly MO needs to finish on a specific date to be ready for the MO above it.

Scheduling Preference: set to the Parent MO Scheduling Preference. If this is blank, it uses the Default Scheduling Preference.