Results for “bom_components_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM_COMPONENTS_B is the foundational base table within the Oracle Bills of Material (BOM) application, owned by the BOM schema. It stores the component lines that make up a bill of material, effectively defining the parent-child relationships between assemblies and their constituent items. Each row represents a single component entry against a parent structure, capturing quantity, effectivity, operation assignment, and a wide range of planning and order-entry attributes. In Oracle EBS 12.1.1 and 12.2.2 the table is central to BOM explosion, implosion, cost rollup, work in process (WIP) supply, and order promising.

The ETRM metadata classifies this object heuristically as hub-leaning within a Data Vault modeling context. The component sequence acts as a durable surrogate identifier, with the structure acting as a hub-like anchor that many descriptive and transactional satellites attach to. This reflects the table's position as a central node referenced by numerous dependent objects.

Key Information Stored

The table contains 102 documented columns. The columns listed below represent the most operationally significant attributes.

• COMPONENT_SEQUENCE_ID — the surrogate primary key (BOM_COMPONENTS_B_PK), uniquely identifying each component line. It is also the business-key candidate carried by unique index BOM_COMPONENTS_B_U2.
• BILL_SEQUENCE_ID — foreign key to BOM_STRUCTURES_B, identifying the parent bill (assembly) to which the component belongs. Together with COMPONENT_ITEM_ID and EFFECTIVITY_DATE it forms the BOM_COMPONENTS_B_UK1 business unique constraint.
• COMPONENT_ITEM_ID — the inventory item used as the component on this bill line.
• COMPONENT_QUANTITY and COMPONENT_YIELD_FACTOR — the required quantity per assembly and its yield adjustment.
• EFFECTIVITY_DATE and DISABLE_DATE — the date range over which the component is valid on the structure.
• OPERATION_SEQ_NUM — the routing operation to which the component is assigned.
• WIP_SUPPLY_TYPE, SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID — supply characteristics used when the component is consumed in WIP.
• PLANNING_FACTOR and QUANTITY_RELATED — planning and yield behavior flags.
• COST_FACTOR and INCLUDE_IN_COST_ROLLUP — attributes governing costing contribution.
• REVISED_ITEM_SEQUENCE_ID — foreign key to ENG_REVISED_ITEMS, linking to the engineering revision of the component item.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield columns.
• OLD_COMPONENT_SEQUENCE_ID — self-referencing column used to track changes across engineering change orders.

Common Use Cases and Queries

Typical scenarios include retrieving all components for a given assembly, checking effectivity at a point in time, and driving BOM explosion reports. A representative query joining components to their parent structure is shown below.

• List active components for an assembly: SELECT c.COMPONENT_SEQUENCE_ID, c.COMPONENT_ITEM_ID, c.COMPONENT_QUANTITY FROM BOM.BOM_COMPONENTS_B c WHERE c.BILL_SEQUENCE_ID = :p_bill_seq AND TRUNC(SYSDATE) BETWEEN c.EFFECTIVITY_DATE AND NVL(c.DISABLE_DATE, TRUNC(SYSDATE)+1).
• Engineering change history: query rows where OLD_COMPONENT_SEQUENCE_ID is not null to trace superseded component lines.
• Cost rollup input: extract components flagged with INCLUDE_IN_COST_ROLLUP = 'Y' together with COST_FACTOR.
• WIP supply analysis: group by WIP_SUPPLY_TYPE to report push, pull, and operation-based supply.
• Routing alignment: join to BOM_COMPONENT_OPERATIONS on COMPONENT_SEQUENCE_ID and OPERATION_SEQ_NUM to reconcile components with their routing operations.
• Order and demand tracing: join MTL_DEMAND or OE_ORDER_LINES_ALL on COMPONENT_SEQUENCE_ID to link demand to the specific bill line that generated it.

Related Objects

BOM_COMPONENTS_B participates in a dense set of referential relationships.

• BOM_STRUCTURES_B — the parent-bill table; joined via BILL_SEQUENCE_ID.
• ENG_REVISED_ITEMS — engineering item revision; joined via REVISED_ITEM_SEQUENCE_ID.
• BOM_COMPONENTS_B (self-reference) — via OLD_COMPONENT_SEQUENCE_ID for change tracking.
• BOM_COMPONENT_OPERATIONS — the routing operations attached to a component; joined via COMPONENT_SEQUENCE_ID.
• BOM_SUBSTITUTE_COMPONENTS — substitute items defined for the component; joined via COMPONENT_SEQUENCE_ID.
• MTL_DEMAND — demand records derived from bill lines; joined via COMPONENT_SEQUENCE_ID.
• WIP_REQUIREMENT_OPERATIONS — WIP material requirements; joined via COMPONENT_SEQUENCE_ID.
• OE_ORDER_LINES_ALL — order lines that reference the component; joined via COMPONENT_SEQUENCE_ID.
• BOM_REFERENCE_DESIGNATORS — designator usages for components; joined via COMPONENT_SEQUENCE_ID.
• BOM_EXPLOSION_TEMP and BOM_IMPLOSION_TEMP — temporary working tables used by the BOM exploder and imploder; joined via COMPONENT_SEQUENCE_ID.