| # 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 Start the Create Physical Breakdown Structure (tscfg2210m000) session. In the Source field, select Bill of Material. Item Effectiveness If this check box is selected, 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, then LN checks for the effective date from sales based on Configuration Date in sales parameter. If the item is not from sales deliveries then, LN takes the effective date given as input. Fall back on Bill Of Material if source is not found: If this check box is selected when the physical breakdown structure is created 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. Check Consistency: If the physical breakdown is generated directly from a production BOM, LN performs a consistency check, both at LN Infor LN Manufacturing and LN Infor 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 items that are configuration controlled, 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 the Items - Service (tsmdm2100m000) session and copied to the Physical Breakdowns (tscfg2110m000) session. 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, so 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
Level | Item | Configuration Control | Item Service Data Present
0 | X | Serialized | Yes
1 | Y | Anonymous | Yes
2 | A | Serialized | Yes ------- Problem 1
2 | B | None | No
1 | Z | Anonymous | Yes
2 | A | Serialized | Yes ------- Problem 2
3 | B | None | No
4 | C | Anonymous | Yes ------- Problem 3
All three problems are caused by serialized items present under anonymous items. LN prints the following error report: For item X, no PBD could be generated, reason(s): 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 prints an error report if it detects a loop in a bill of material, as illustrated in the following example: Example
Level | Item | Configuration Control | Item Service Data Present
0 | X | Serialized | Yes
1 | Y | Serialized | Yes
2 | A | Serialized | Yes
2 | B | Serialized | Yes
1 | Z | Serialized | Yes
2 | A | Serialized | Yes
3 | B | Serialized | Yes
4 | X | Serialized | Yes ------- Problem 1
LN prints the following error report: For item X, no PBD could be generated for the following reason(s): Cycle detected in BOM. |