Results for “mrp_assembly_operations”

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

Overview

The MRP_ASSEMBLY_OPERATIONS table resides in the MRP schema of Oracle E-Business Suite and belongs to the Master Scheduling/MRP product family. It is documented in ETRM as a physical table with 18 columns and a status of VALID in both release 12.1.1 and 12.2.2. Notably, the Oracle-published description for this object states that it is "Not currently used." This designation implies that the table is a legacy or reserved structure retained within the schema for backward compatibility, historical data retention, or internal use by unexposed code paths, rather than forming part of the actively supported functional data model.

Functionally, the object appears designed to associate an assembly item with the operations performed on a using assembly, storing operation sequencing and usage attributes. The presence of columns such as OPERATION_SEQ_NUM, OPERATION_USAGE_QUANTITY, OPERATION_OFFSET_PERCENT, and WIP_SUPPLY_TYPE suggests a historical role in modeling operation-level component consumption or supply relationships during planning or work-in-process processing. From a dimensional modeling perspective, the mined foreign key structure classifies this object heuristically as a link table, since it resolves relationships between item/organization/compile-designator combinations rather than storing descriptive attributes about a single entity. This classification is a modeling suggestion only and should not be treated as an authoritative Oracle designation.

Key Information Stored

The table is anchored by a composite primary key, MRP_ASSEMBLY_OPERATIONS_PK, defined over INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR, USING_ASSEMBLY_ITEM_ID, and OPERATION_SEQ_NUM. A separate unique index, MRP_ASSEMBLY_OPERATIONS_U1, spans the same columns in a different order (USING_ASSEMBLY_ITEM_ID, COMPILE_DESIGNATOR, ORGANIZATION_ID, INVENTORY_ITEM_ID, OPERATION_SEQ_NUM), reinforcing the composite nature of the business key. There is no single surrogate key column; uniqueness is derived entirely from these business columns.

• INVENTORY_ITEM_ID – identifies the assembly item whose operations are described; also part of the FK to MRP_SYSTEM_ITEMS.
• ORGANIZATION_ID – the inventory organization context, included in both foreign key relationships.
• COMPILE_DESIGNATOR – the plan or compile identifier that scopes the data set to a specific planning run.
• USING_ASSEMBLY_ITEM_ID – the assembly item that consumes or uses the operation; second FK column to MRP_SYSTEM_ITEMS.
• OPERATION_SEQ_NUM – sequence number ordering operations within the assembly.
• OPTIONAL_COMPONENT – flag indicating whether the component or operation is optional.
• OPERATION_USAGE_QUANTITY – quantity consumed per operation.
• OPERATION_OFFSET_PERCENT – offset percentage applied to the operation.
• WIP_SUPPLY_TYPE – the supply type associated with work-in-process.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE – concurrent program audit columns identifying the process that last populated the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard who-column auditing attributes.

Common Use Cases and Queries

Because the object is documented as not currently used, direct functional reporting is uncommon. Practitioners typically encounter it during data migration, schema comparison, or upgrade impact analysis between 12.1.1 and 12.2.2. A representative query joins to MRP_SYSTEM_ITEMS to resolve item descriptions:

• Row count and population checks – confirm whether any data exists at all: SELECT COUNT(*) FROM mrp.mrp_assembly_operations;
• Item resolution – join both item columns to MRP_SYSTEM_ITEMS on INVENTORY_ITEM_ID/ORGANIZATION_ID/COMPILE_DESIGNATOR and on USING_ASSEMBLY_ITEM_ID with the same key columns to retrieve descriptive attributes.
• Operation sequencing review – order by INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR, OPERATION_SEQ_NUM to inspect the stored operation chains.
• Audit lineage – filter by REQUEST_ID or PROGRAM_ID to trace the concurrent program that populated the rows.

Any use in custom code should be validated against Oracle Support guidance, given the "not currently used" designation.

Related Objects

The most significant dependencies derive from the two documented foreign keys, both targeting MRP_SYSTEM_ITEMS:

• MRP_SYSTEM_ITEMS – referenced twice, once via INVENTORY_ITEM_ID and once via USING_ASSEMBLY_ITEM_ID, each paired with ORGANIZATION_ID and COMPILE_DESIGNATOR.
• MRP_ASSEMBLY_OPERATIONS_PK – the primary key constraint enforcing row uniqueness.
• MRP_ASSEMBLY_OPERATIONS_U1 – the unique index providing an alternate business-key ordering.

Additional related structures commonly inspected alongside this table include MRP_SYSTEM_ITEMS_B, the bill and routing tables in the BOM module, and WIP operation tables that share similarly named columns. These are contextual associations rather than documented foreign keys and should be confirmed against the target environment before being relied upon.