Search Results mrp_schedule_dates

Overview

The MRP_SCHEDULE_DATES table is a core transactional table within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the central repository for detailed master production schedule (MPS) and master demand schedule (MDS) entries. This table stores the disaggregated, time-phased supply and demand data generated by the planning engine, representing the fundamental output of a planning run. Its primary role is to record the specific dates and quantities for planned orders, scheduled receipts, and forecast consumption, forming the actionable schedule that drives manufacturing and procurement activities. The integrity of this data is critical for subsequent planning cycles, capacity planning, and execution systems.

Key Information Stored

The table's structure captures the essential dimensions of a scheduled entry. The primary key, MRP_SCHEDULE_DATES_PK, is a composite of MPS_TRANSACTION_ID, SCHEDULE_LEVEL, and SUPPLY_DEMAND_TYPE, ensuring uniqueness for each schedule line. Key columns include INVENTORY_ITEM_ID and ORGANIZATION_ID to identify the planned item, SCHEDULE_DESIGNATOR to specify the plan, and SCHEDULE_LEVEL to distinguish between MPS and MRP items. The SUPPLY_DEMAND_TYPE indicates whether the record is a planned order, scheduled receipt, or forecast demand. Critical date fields track the SCHEDULE_DATE, RELEASE_DATE for orders, and DUE_DATE for demands. Quantity and sourcing information is stored in columns such as QUANTITY, LINE_ID (for WIP lines), and SOURCE_ORGANIZATION_ID.

Common Use Cases and Queries

This table is central to post-planning analysis and custom reporting. Common use cases include extracting the planned order schedule for a specific item, analyzing forecast consumption against sales orders, and auditing the output of a planning run. A typical query pattern involves joining to MRP_SCHEDULE_ITEMS for item details and filtering by SCHEDULE_DESIGNATOR and ORGANIZATION_ID. For example, to retrieve all planned supply for a given plan and item, one might use:

• SELECT schedule_date, quantity, supply_demand_type
• FROM mrp_schedule_dates
• WHERE schedule_designator = 'MAIN_PLAN'
• AND inventory_item_id = 12345
• AND organization_id = 101
• AND supply_demand_type IN (1, 2) -- Planned Order types
• ORDER BY schedule_date;

Data from this table is also used to feed workbench interfaces and to generate planned order release reports for shop floor and purchasing.

Related Objects

MRP_SCHEDULE_DATES maintains extensive relationships with other planning and inventory entities, as indicated by its foreign keys. It is directly linked to MRP_SCHEDULE_ITEMS for item master data within a plan and to MRP_SCHEDULE_DESIGNATORS for plan definitions. For demand sourcing, it references MTL_SALES_ORDERS for sales order demands and MRP_FORECAST_DATES and MRP_FORECAST_DESIGNATORS for forecast data. On the supply side, it relates to WIP_LINES for production line details. Furthermore, it is connected to MRP_RECOMMENDATIONS via the REFERENCE_SCHEDULE_ID, which allows the planning engine to track the lineage of suggested actions back to the original schedule entries. These relationships underscore its position as a nexus between planning inputs and outputs.