Results for “mrp_planned_resource_reqs”

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

Overview

MRP_PLANNED_RESOURCE_REQS is a table in the MRP schema of Oracle E-Business Suite (documented here for 12.1.1 and 12.2.2) that stores the resource requirements needed to build an assembly as determined by the Master Scheduling/MRP planning engine. During a planning run, the MRP engine explodes the bill of material (BOM) and routing for each planned order and records the resulting resource demand in this table. Each row represents a single resource requirement line tied to a planned assembly, department, and routing operation, and it feeds capacity planning, load reporting, and shop-floor scheduling.

From a heuristic perspective, the table is best described as a link object. It connects an assembly item (via USING_ASSEMBLY_ITEM_ID) to a resource (via RESOURCE_ID) and a department (via DEPARTMENT_ID), while also carrying its own descriptive attributes such as runtime quantity and offset percent. This link classification reflects the mined foreign-key structure rather than an official Oracle designation.

Key Information Stored

The table contains 27 documented columns. The most significant include:

• DEPARTMENT_ID – the department where the resource is used; part of the primary key and a foreign key to BOM_DEPARTMENTS.
• ORGANIZATION_ID – the inventory organization in which the requirement applies; part of the PK.
• COMPILE_DESIGNATOR – identifies the MRP plan or compilation set that produced the row; part of the PK.
• RESOURCE_ID – the resource required; part of the PK and a foreign key to BOM_RESOURCES.
• USING_ASSEMBLY_ITEM_ID – the assembly item being built; part of the PK and a foreign key to MRP_SYSTEM_ITEMS.
• OPERATION_SEQ_NUM and RESOURCE_SEQ_NUM – operation and resource sequence numbers; both are part of the composite PK.
• LINE_ID – links the requirement to its originating planning line.
• ALTERNATE_ROUTING_DESIGNATOR – the alternate routing used.
• RUNTIME_QUANTITY and RESOURCE_OFFSET_PERCENT – the calculated resource load and its offset.
• SETBACK_DAYS, BASIS, and RESOURCE_UNITS – planning attributes governing how the resource is scheduled and measured.
• EFFECTIVITY_DATE and DISABLE_DATE – the effective window for the requirement.
• REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE – audit columns identifying the concurrent request/program that generated the row.

The surrogate primary key is MRP_PLANNED_RESOURCE_REQS_PK, defined over DEPARTMENT_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR, RESOURCE_ID, USING_ASSEMBLY_ITEM_ID, OPERATION_SEQ_NUM, and RESOURCE_SEQ_NUM. These same columns constitute the business-key candidates that uniquely identify a resource requirement.

Common Use Cases and Queries

Typical uses include capacity and load reporting, verifying MRP-generated resource demand, and diagnosing discrepancies between planned and actual shop-floor load. A representative query for a specific plan is:

• SELECT * FROM MRP.MRP_PLANNED_RESOURCE_REQS WHERE COMPILE_DESIGNATOR = :plan AND ORGANIZATION_ID = :org;
• Joining to BOM_RESOURCES to report resource names and to BOM_DEPARTMENTS for department descriptions.
• Aggregating RUNTIME_QUANTITY by RESOURCE_ID and DEPARTMENT_ID to produce resource load summaries.

Related Objects

• BOM_RESOURCES – joined via RESOURCE_ID.
• BOM_DEPARTMENTS – joined via DEPARTMENT_ID.
• MRP_SYSTEM_ITEMS – joined on USING_ASSEMBLY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR.
• MRP_SYSTEM_ITEMS (again via SOURCE_ITEM_ID) – relates the requirement to its source item.
• MRP planning and capacity reports, which consume this table to display planned resource requirements.