Search Results mrp_planned_resource_reqs




Overview
Explore in AI Chat

Overview

The MRP_PLANNED_RESOURCE_REQS table is a core data structure within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the primary repository for planned resource requirements generated by a Material Requirements Planning (MRP) or Master Production Schedule (MPS) plan run. The table stores detailed information about the labor, machine, and other resource capacities needed to manufacture planned orders and repetitive schedules for assemblies, as dictated by the bill of material (BOM) and routing definitions. Its existence is critical for capacity planning, as it translates the master schedule into a time-phased projection of resource load, enabling planners to identify potential bottlenecks.

Key Information Stored

The table's structure links planned production to specific manufacturing resources. Its seven-column composite primary key precisely identifies each unique requirement. Key columns include COMPILE_DESIGNATOR, which identifies the specific MRP plan; USING_ASSEMBLY_ITEM_ID and ORGANIZATION_ID, which specify the item and plant for the planned order; and DEPARTMENT_ID, RESOURCE_ID, OPERATION_SEQ_NUM, and RESOURCE_SEQ_NUM, which pinpoint the exact resource and operation from the routing. Other significant columns typically include transaction dates, required resource units or hours, and associated supply identifiers (like PLANNED_ORDER_ID or REPETITIVE_SCHEDULE_ID), which link the requirement back to its generating supply record in tables like MRP_PLANNED_ORDERS.

Common Use Cases and Queries

This table is central to capacity analysis and resource load reporting. A common use case is generating a resource profile or load report for a specific plan. A typical query would join to BOM_DEPARTMENTS and BOM_RESOURCES for descriptive information, and filter by COMPILE_DESIGNATOR and a date range. For example:

  • Identifying Resource Bottlenecks: Summarizing total required hours by resource and period to compare against available capacity.
  • Drill-down from Capacity Plans: Querying detailed requirements for a specific overloaded resource to see which assemblies and planned orders are causing the load.
  • Plan Comparison: Analyzing how resource requirements differ between two plan scenarios (e.g., "What-if" vs. "Production").

Sample SQL often involves aggregating the RESOURCE_HOURS or similar quantity column grouped by resource, department, and time bucket.

Related Objects

As indicated by its foreign keys, MRP_PLANNED_RESOURCE_REQS has direct relationships with several fundamental manufacturing tables. It references MRP_SYSTEM_ITEMS (via USING_ASSEMBLY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR) for the planned item's master data. It links to BOM_RESOURCES for resource details (cost, available units) and to BOM_DEPARTMENTS for departmental information. It is a child table of the main planning supply table, MRP_PLANNED_ORDERS, though this relationship is often enforced via application logic rather than a direct foreign key. Data in this table is populated during the MRP plan launch and is consumed by the Capacity Planning engine and related reports.