Search Results bom_structures_b

Overview

The BOM_STRUCTURES_B table is the core master data table for storing bill of material (BOM) header information within Oracle E-Business Suite Bills of Material (BOM) module. It represents the definition of a specific bill, which is a structured list of components required to build an assembly or product. Each record in this table uniquely identifies a BOM for a given assembly item, organization, and alternate designation. The table serves as the primary parent entity for all component and routing details, forming the foundational structure for manufacturing, costing, and engineering processes in both discrete and flow manufacturing environments. Its integrity is critical for material planning, shop floor execution, and product lifecycle management.

Key Information Stored

The table's primary key is BILL_SEQUENCE_ID, a unique system-generated identifier for each BOM definition. Crucial business key columns, constrained by a unique key, form the natural identifier for a BOM: ASSEMBLY_ITEM_ID (from MTL_SYSTEM_ITEMS_B), ORGANIZATION_ID (from HR_ALL_ORGANIZATION_UNITS), and ALTERNATE_BOM_DESIGNATOR (from BOM_ALTERNATE_DESIGNATORS). Other significant columns include COMMON_BILL_SEQUENCE_ID, which enables the use of common bills across organizations by pointing to a master BOM definition, and PENDING_FROM_ECN, which links to the ENG_ENGINEERING_CHANGES table to manage engineering change order (ECO) implementations. Additional attributes track the BOM's effectivity dates, usage (e.g., manufacturing, engineering), and specific type.

Common Use Cases and Queries

Common operational and reporting scenarios involve querying this table to resolve BOM definitions and their relationships. A frequent requirement is to list all BOMs for a specific assembly item within an organization, including alternates. A typical SQL pattern joins BOM_STRUCTURES_B with MTL_SYSTEM_ITEMS_B for item details:

• SELECT msib.segment1 ASSEMBLY, bsb.alternate_bom_designator, bsb.effective_date FROM bom_structures_b bsb, mtl_system_items_b msib WHERE bsb.assembly_item_id = msib.inventory_item_id AND bsb.organization_id = msib.organization_id AND msib.segment1 = '<ITEM>' AND bsb.organization_id = <ORG_ID>;

Another critical use case is explosion and indented BOM reporting, where BOM_STRUCTURES_B provides the starting point (the top-level bill sequence ID) for recursive queries or joins to the BOM_COMPONENTS_B table. Integration with Work in Process (WIP) requires retrieving the specific BOM referenced by a discrete job. Furthermore, identifying bills pending implementation from an ECO is achieved by filtering on the PENDING_FROM_ECN column.

Related Objects

The table maintains extensive foreign key relationships, acting as a central hub. Key parent tables include MTL_SYSTEM_ITEMS_B (for the assembly item), HR_ALL_ORGANIZATION_UNITS (for the organization), BOM_ALTERNATE_DESIGNATORS, and ENG_ENGINEERING_CHANGES. Crucially, BILL_SEQUENCE_ID is referenced as a foreign key by numerous child tables that store detailed BOM data, including:

• BOM_COMPONENTS_B: Stores the component items of the BOM.
• BOM_COMPONENT_OPERATIONS: Links components to specific routing operations.
• BOM_STRUCTURES_B (self-reference via COMMON_BILL_SEQUENCE_ID): For common BOM structures.
• BOM_DEPENDENT_DESC_ELEMENTS: Holds descriptive element information for the BOM.
• ENG_REVISED_ITEMS: Tracks items revised by an ECO for this BOM.
• BOM_EXPLOSION_TEMP / BOM_SMALL_EXPL_TEMP: Temporary tables used during BOM explosion processes.

These relationships underscore the table's pivotal role in the BOM data model.