Results for “mrp_bom_components”

50+ results




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

Overview

MRP.MRP_BOM_COMPONENTS is an Oracle EBS table within the Master Scheduling/MRP (MRP) product module that stores bill of materials (BOM) component information together with pending Engineering Change Order (ECO) data. It functions as the primary staging and reference table that the MRP planning engine consults when exploding assemblies into their component requirements. The table is owned by the MRP schema and holds 30 documented columns in the 12.1.1 and 12.2.2 releases.

The object exists to bridge engineering and manufacturing planning. It carries the current effective component structure alongside pending changes introduced through ECOs, allowing MRP to plan against both the as-built and the as-planned configuration. From a Data Vault modeling perspective, the metadata suggests a link classification, reflecting the fact that the table primarily represents relationships between an assembly and its components rather than standing alone as a hub or an attribute-only satellite. The composite primary key MRP_BOM_COMPONENTS_PK (COMPONENT_SEQUENCE_ID, INVENTORY_ITEM_ID, COMPILE_DESIGNATOR, ORGANIZATION_ID) reinforces this relationship-oriented role.

Key Information Stored

The table's identifying columns are central to understanding its content. COMPONENT_SEQUENCE_ID ties each row back to a specific BOM component line, while INVENTORY_ITEM_ID identifies the component item. ORGANIZATION_ID scopes the record to a specific inventory organization, and COMPILE_DESIGNATOR indicates the planning compilation instance to which the row belongs.

The USING_ASSEMBLY_ID column identifies the parent assembly that consumes the component, establishing the parent-child relationship that drives BOM explosion. ALTERNATE_BOM_DESIGNATOR distinguishes alternate bills of materials, and OPERATION_SEQ_NUM places the component at a specific routing operation. FROM_END_ITEM_UNIT_NUMBER and TO_END_ITEM_UNIT_NUMBER capture the end-item effective range that governs applicability.

Quantity and timing information resides in USAGE_QUANTITY, OPERATION_OFFSET_PERCENT, and EFFECTIVITY_DATE, with SUGGESTED_EFFECTIVITY_DATE and OLD_EFFECTIVITY_DATE supporting the pending ECO scenario. The CHANGE_NOTICE column names the engineering change, while USE_UP_CODE and DISABLE_DATE control phase-out behavior. OPTIONAL_COMPONENT and WIP_SUPPLY_TYPE further qualify the component's role. The unique index MRP_BOM_COMPONENTS_U1 spans COMPONENT_SEQUENCE_ID, USING_ASSEMBLY_ID, COMPILE_DESIGNATOR, ORGANIZATION_ID, ALTERNATE_BOM_DESIGNATOR, FROM_END_ITEM_UNIT_NUMBER, and OPERATION_SEQ_NUM, and represents the strongest business-key candidate. Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, and related concurrency fields) are also present.

Common Use Cases and Queries

Typical uses include multi-level BOM explosion reporting, ECO impact analysis, and validating the planning compilation used by MRP. A query joining components to their parent assembly is common:

  • SELECT b.USING_ASSEMBLY_ID, b.INVENTORY_ITEM_ID, b.USAGE_QUANTITY FROM MRP.MRP_BOM_COMPONENTS b WHERE b.ORGANIZATION_ID = :org_id AND b.COMPILE_DESIGNATOR = :des
  • Pending ECO reporting filtered on CHANGE_NOTICE and SUGGESTED_EFFECTIVITY_DATE to identify components not yet released to production.
  • Alternate BOM comparisons using ALTERNATE_BOM_DESIGNATOR to evaluate sourcing strategies.
  • Impact simulation before the next MRP plan run by contrasting EFFECTIVITY_DATE with DISABLE_DATE.

Related Objects

The foreign keys captured in the ETRM metadata define the table's principal dependencies:

  • BOM_INVENTORY_COMPONENTS — joined on COMPONENT_SEQUENCE_ID; supplies the master component definition.
  • MRP_SYSTEM_ITEMS — joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR to describe the component item.
  • MRP_SYSTEM_ITEMS (via USING_ASSEMBLY_ID) — describes the parent assembly.
  • MRP_SYSTEM_ITEMS — the dominant referenced table, reached through two distinct FK paths.

Collectively these relationships position MRP_BOM_COMPONENTS as a link between item master information and BOM definition data, consistent with its heuristic Data Vault classification.