Search Results mrp_plan_schedules




Overview
Explore in AI Chat

Overview

The MRP_PLAN_SCHEDULES table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the central table for storing detailed supply and demand schedule data generated by planning engines. This includes the output from Master Production Scheduling (MPS), Material Requirements Planning (MRP), and Distribution Requirements Planning (DRP) runs. The table's primary role is to persist the time-phased plan recommendations—such as planned orders, scheduled receipts, and discrete demands—that are calculated during a plan compilation. These records form the basis for planner review, firming actions, and subsequent execution in manufacturing and procurement.

Key Information Stored

The table organizes schedule data using a combination of key identifier columns and detailed transaction attributes. The primary key, MRP_PLAN_SCHEDULES_PK, is based on ORGANIZATION_ID, COMPILE_DESIGNATOR, INPUT_ORGANIZATION_ID, INPUT_NAME, and PLAN_LEVEL, ensuring uniqueness for each schedule entry within a specific plan. Critical columns include the COMPILE_DESIGNATOR, which identifies the specific plan (e.g., 'MASTER_PLAN'), and the INPUT_NAME paired with INPUT_ORGANIZATION_ID, which link to the source schedule or designator used as plan input. The PLAN_LEVEL distinguishes between different planning hierarchies, such as item, supplier, or customer levels. Other significant columns typically store the transaction date, quantity, order type (supply or demand), associated item, and the recommended action details.

Common Use Cases and Queries

This table is fundamental for post-plan analysis and custom reporting. Planners and analysts query it to examine the net output of a planning run. A common use case is extracting all supply suggestions for a specific item to review planned order dates and quantities. Another is analyzing demand pegging by tracing a specific demand record back to its supply sources. Sample SQL often involves filtering by COMPILE_DESIGNATOR and ORGANIZATION_ID, and joining to inventory and item tables for descriptive information.

  • Sample Query Pattern: SELECT schedule_date, quantity, order_type FROM mrp_plan_schedules WHERE compile_designator = :plan_name AND organization_id = :org_id AND inventory_item_id = :item_id ORDER BY schedule_date;
  • Reporting Use Case: Generating a planner workbench report that lists all new planned orders suggested by the latest MRP run, highlighting items with critical shortages or excess supply.

Related Objects

The MRP_PLAN_SCHEDULES table has defined foreign key relationships with key setup and control tables in the MRP schema, as documented in the ETRM metadata. These relationships enforce data integrity and are critical for accurate joins in queries.

  • MRP_DESIGNATORS: Linked via INPUT_NAME and INPUT_ORGANIZATION_ID. This table stores definitions of planning designators, which are used to categorize and select planning data.
  • MRP_SCHEDULE_DESIGNATORS: Also linked via INPUT_NAME and INPUT_ORGANIZATION_ID. This table holds definitions for schedule designators, which identify specific sets of schedule data used as input to a plan.

These relationships indicate that the schedule data in MRP_PLAN_SCHEDULES is explicitly tied to the specific designator and organizational context defined in these reference tables, ensuring traceability from plan output back to its source parameters.