Create a physical breakdown from a Bill of Materials

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 the application Manufacturing to the Serialized Items (tscfg2100m000) session of the Application Service. If no item service data is present, the application uses the item service defaults maintained for item type and item group to create items in Service.

The application validates the following after creating a physical breakdown from a bill of materials:

If the item is revision controlled and derived from sales deliveries, the application validates for revision from the sales order line. The application 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, The application validates for the effective date from sales based on the Configuration Date in Sales field.

If the item is not from sales deliveries then, the application considers the effective date as the input.

• Unit Effectivity: When the application creates the physical breakdown structure from a Bill of Material (BOM), the application 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, the application 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, the application 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, the application performs a consistency check, both at the Manufacturing and Service package of the application, to ensure the structure is defined without any mismatch. The items in such a structure must be defined in Service package with appropriate service-item data with related configuration control, and checked for consistency.

The application performs the following consistency checks:

To distinguish between the items relevant and not relevant to service, The application 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.

The application validates 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. The application begins to copy when inconsistency is detected in the structure formation and an error report is generated.

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

The application validates 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.

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