To create a physical breakdown from a Bill of Materials

You can use the Create Physical Breakdown Structure (tscfg2210m000) session to create the physical breakdown from a Bill of Material (BOM).

If you create a physical breakdown from a bill of material, this results in a direct copy of effective items present in the Bill of Material (tibom1110m000) session of LN Manufacturing to the Serialized Items (tscfg2100m000) session of LN Service. If no item service data is present, LN uses the item service defaults maintained for item type and item group to create items in Service.

To create a physical breakdown from a Bill of Materials
  1. Start the Create Physical Breakdown Structure (tscfg2210m000) session.
  2. In the Source field, select Bill of Material.
  3. Use the Deliveries option to create a physical breakdown from Sales (after sales). The end item of the sales order, the production BOM is copied to a physical breakdown. If you select this check box, you can use the fields in the Selection Range group box to create a physical breakdown from a range of installation group, items, or serialized items. For this selection range, a physical breakdown is created.
  4. If you select the Check Effectivity check box, the items' validity is checked before the items are copied to physical breakdown.
LN validates the following:

If the item is revision controlled and derived from sales deliveries, LN checks for revision from the sales order line. LN checks for the effective date from engineering items for the given item and revision.

If the item is not revision controlled and derived from sales deliveries, LN checks for the effective date from sales based on the Configuration Date in Sales field.

If the item is not from sales deliveries then, LN takes the effective date given as input.

  • Unit Effectivity: When LN creates the physical breakdown structure from a Bill of Material (BOM), LN considers unit effectivity as a validation. The items that belong to the unit effectivity are only created in service. Unit effectivity is checked from the serialized item. If unit effectivity is not present in the serialized item, LN checks the unit effectivity from a sales order line if the item originates from sales.
  • Fall back on Bill Of Material if source is not found: If you select this check box when you create the physical breakdown structure from an as-built structure or item breakdown and no source item is found, LN copies the bill of material of that item to the physical breakdown structure.
  • Consistency checks: If the physical breakdown is generated directly from a production BOM, LN performs a consistency check, both at LN Manufacturing and LN Service, to ensure the structure is defined without any mismatch. The items in such a structure must be defined in LN Service with appropriate service-item data with related configuration control, and checked for consistency.
LN performs the following consistency checks:

To distinguish between the items relevant and not relevant to service, LN copies the configuration-controlled items, namely serialized or anonymous items, into physical breakdown. If no service-item data is available for an item, based on service defaults, the item data will be created in items service and copied to physical breakdown.

Note

You must create service item data for all the items copied from a production bill of material to the physical breakdown structure.

LN checks for consistency with respect to the structure formation. A serialized item must always be situated above an anonymous item to ensure that the structure remains consistent with the item definition. LN begins to copy when inconsistency is detected in the structure formation and an error report is generated.

LN prints an error report if a serialized item is present under an anonymous item, as illustrated in the following example:

Example
LevelItemConf. ControlItem Service Data Present
0XSerializedYes
1YAnonymousYes
2ASerializedYes ------- Problem 1
2BNoneNo
1ZAnonymousYes
2ASerializedYes ------- Problem 2
3BNoneNo
4CAnonymousYes ------- Problem 3

 

All three problems are caused by serialized items present under anonymous items.

LN prints the following error report:

No PBD was generated for item X for the following reasons:

  • Parent item (Y-anonymous) has a lower configuration control setup than Child item (A-serialized).
  • Parent item (Z-anonymous) has a lower configuration control setup than Child item (A-serialized).
  • Parent item (B-none) has a lower configuration control setup than Child item (C-anonymous).

LN checks for consistency with respect to the loops in the bill of material (BOM). If two anonymous items occur in an opposite fashion, with respect to an existing structure definition, the anonymous items can subsequently end up in a loop.

LN detects a loop in a bill of material, LN prints an error report, as illustrated in the following example:

Example
LevelItemConf. ControlItem Service Data Present
0XSerializedYes
1YSerializedYes
2ASerializedYes
2BSerializedYes
1ZSerializedYes
2ASerializedYes
3BSerializedYes
4XSerializedYes ------- Problem 1

 

LN prints the following error report:

For item X, no PBD could be generated for the following reasons:

  • Cycle detected in BOM.