Results for “mrp_wip_components_u1”

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

Overview

MRP.MRP_WIP_COMPONENTS is a planning snapshot table in the Oracle E-Business Suite discrete manufacturing and materials planning schema. It stores information on component requirements for discrete jobs, repetitive schedules, and nonstandard jobs, and it is populated by the Snapshot process and consumed by the Planner. Its principal source is WIP_REQUIREMENT_OPERATIONS, which it mirrors into a form suitable for netting by the MRP, MPS, and DRP planning engines. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, has 26 documented columns in the ETRM 12.2.2 physical schema, and reports a VALID status in the MRP schema.

From a heuristic Data Vault modeling perspective, the mined foreign key structure classifies MRP_WIP_COMPONENTS as a link. It resolves the many-to-many association between work-in-process entities and inventory items across a planning compilation, rather than serving as a standalone hub of items or a purely descriptive satellite.

Key Information Stored

The most significant columns capture the planning context, the work order identity, and the quantity semantics that differ by job type.

• INVENTORY_ITEM_ID — identifier of the component item; also a foreign key to MRP.MRP_SYSTEM_ITEMS.
• ORGANIZATION_ID — the inventory organization that owns the requirement.
• COMPILE_DESIGNATOR — the plan being compiled: MPS, MRP, or DRP.
• WIP_ENTITY_ID — the discrete job or repetitive schedule that carries the component.
• OPERATION_SEQ_NUM — the routing operation sequence on which the component is required.
• JOB_REFERENCE_ITEM_ID — for discrete jobs, the item for which the job is defined; a foreign key to MRP.MRP_SYSTEM_ITEMS.
• ALLOCATED_QUANTITY — the requirement quantity for discrete job components, and the demand quantity for nonstandard job components flagged as demand.
• NET_QUANTITY — the total quantity already issued to a repetitive schedule (at most one row per component), the supply quantity for nonstandard job supply components, and the netted quantity for nonstandard job header records.
• SUPPLY_DEMAND_TYPE — determines whether a nonstandard job component is treated as supply or demand.
• WIP_ENTITY_TYPE — distinguishes the underlying WIP entity class.
• QUANTITY_REQUIRED and QUANTITY_ISSUED — the planned requirement and the issued quantities used in variance and shortage reporting.
• OPERATION_START_DATE and OPERATION_OFFSET_DAYS — scheduling dates and offsets used to place demand in time.
• PROJECT_ID and TASK_ID — project and task attribution for project manufacturing.
• PLANNING_GROUP — grouping attribute used by the planning engine.

The surrogate primary key is MRP_WIP_COMPONENTS_PK, defined over INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR, WIP_ENTITY_ID, OPERATION_SEQ_NUM, and JOB_REFERENCE_ITEM_ID. The unique index MRP_WIP_COMPONENTS_U1, the object most commonly referenced by identifier MRP_WIP_COMPONENTS_U1, enforces uniqueness over the same six columns in the APPS_TS_TX_IDX tablespace. A nonunique index, MRP_WIP_COMPONENTS_N1, covers WIP_ENTITY_ID for work-order-oriented access paths.

Common Use Cases and Queries

Typical reporting confirms component demand generated for a specific plan and organization, or reconciles issued quantities against requirements.

• Listing component requirements for a plan: SELECT wip_entity_id, inventory_item_id, operation_seq_num, allocated_quantity FROM mrp.mrp_wip_components WHERE organization_id = :org AND compile_designator = 'MRP';
• Identifying all components feeding a discrete job by joining on WIP_ENTITY_ID, which benefits from MRP_WIP_COMPONENTS_N1.
• Supply/demand analysis for nonstandard jobs by filtering on SUPPLY_DEMAND_TYPE and examining NET_QUANTITY versus ALLOCATED_QUANTITY.
• Comparing issued versus required quantities using QUANTITY_ISSUED and QUANTITY_REQUIRED for schedule adherence reporting.
• Project manufacturing reporting filtered by PROJECT_ID and TASK_ID.

Related Objects

• MRP.MRP_SYSTEM_ITEMS — referenced through INVENTORY_ITEM_ID and JOB_REFERENCE_ITEM_ID.
• WIP_REQUIREMENT_OPERATIONS — the principal source table from which this snapshot is derived.
• MRP.MRP_WIP_COMPONENTS_PK — the primary key constraint over the six business columns.
• MRP_WIP_COMPONENTS_U1 — the unique index enforcing the same business key.
• MRP_WIP_COMPONENTS_N1 — the nonunique index on WIP_ENTITY_ID.
• MRP.MRP_WIP_COMPONENTS snapshot data flows into planning engine processing alongside the compile designator plans defined in the MRP schema.