Results for “original_schedule_quantity”

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

Overview

MRP_SCHEDULE_DATES is the core transaction table within the Oracle Master Scheduling/MRP (MRP) module that stores master production schedule (MPS) and master demand schedule (MDS) entries. Each row represents a dated schedule line — a supply entry, a demand entry, or a combined schedule record — associated with a specific inventory item, organization, and schedule designator. The table captures both the original planning intent and the running schedule state, including quantities, dates, repetitive daily rates, and the source origination of each entry.

Within the documented physical schema, the table is owned by the MRP schema and contains 55 columns. The heuristic Data Vault classification mined from the foreign-key structure is link, which suggests this object functions principally as a transactional junction that connects schedule items, forecast designators, sales orders, work-in-process lines, reservations, and recommendations. Practically, it behaves as the fact table for MPS/MDS planning activity rather than a descriptive reference table.

Key Information Stored

The primary key is composed of three columns: MPS_TRANSACTION_ID, SCHEDULE_LEVEL, and SUPPLY_DEMAND_TYPE. Together these form the unique index MRP_SCHEDULE_DATES_U1, which is the business-key candidate. The composite key distinguishes individual schedule transactions by their scheduling level and by whether the row represents supply or demand, which is directly relevant to the "supply_demand_type" search term that surfaced this object.

• MPS_TRANSACTION_ID — unique identifier for each MPS/MDS transaction; first component of the primary key.
• SCHEDULE_LEVEL — indicates the planning level (for example MPS versus MDS); second component of the primary key.
• SUPPLY_DEMAND_TYPE — classifies the row as a supply or demand entry; third component of the primary key.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — identify the planned item and the owning organization; used as a composite foreign key to MRP_SCHEDULE_ITEMS.
• SCHEDULE_DESIGNATOR — associates the row with a specific MPS/MDS schedule.
• SCHEDULE_DATE and SCHEDULE_WORKDATE — the effective calendar date and working date of the entry.
• SCHEDULE_QUANTITY and ORIGINAL_SCHEDULE_QUANTITY — current and as-originally-loaded quantities.
• RATE_END_DATE and REPETITIVE_DAILY_RATE — support repetitive manufacturing schedule rates.
• SCHEDULE_ORIGINATION_TYPE and SOURCE_CODE — describe how the entry was created or sourced.
• SOURCE_SCHEDULE_DESIGNATOR, SOURCE_ORGANIZATION_ID, and SOURCE_SALES_ORDER_ID — trace the originating schedule and sales order.
• REFERENCE_SCHEDULE_ID and FORECAST_ID — link to recommendations and forecast dates respectively.
• LINE_ID and RESERVATION_ID — connect to WIP lines and material reservations.

Common Use Cases and Queries

Because SUPPLY_DEMAND_TYPE is part of the primary key, it is the most frequently used filtering column in reporting. Typical scenarios include reviewing the net supply/demand position for an item, auditing MDS entries against sales orders, and reconciling MPS quantities with repetitive rates.

• List all demand entries for an organization and item within a date range.
• Sum supply versus demand quantities by schedule date to compute the projected available balance.
• Trace MDS records back to their originating sales order or forecast.
• Identify repetitive schedules by RATE_END_DATE and REPETITIVE_DAILY_RATE.

A representative query pattern filters on the composite key components and joins to the item master:

• SELECT SUPPLY_DEMAND_TYPE, SCHEDULE_DATE, SCHEDULE_QUANTITY FROM MRP.MRP_SCHEDULE_DATES WHERE ORGANIZATION_ID = :org AND INVENTORY_ITEM_ID = :item AND SCHEDULE_DESIGNATOR = :desig AND SUPPLY_DEMAND_TYPE = 'DEMAND';

Related Objects

The foreign-key metadata identifies the principal tables that MRP_SCHEDULE_DATES references. These relationships define the joins most commonly used in planning reports.

• MRP_SCHEDULE_ITEMS — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID; supplies item-level scheduling attributes.
• MRP_SCHEDULE_DESIGNATORS — joined on SOURCE_SCHEDULE_DESIGNATOR and SOURCE_ORGANIZATION_ID; defines schedule context.
• MRP_FORECAST_DESIGNATORS — joined on SOURCE_FORECAST_DESIGNATOR; links entries to forecast designations.
• MRP_FORECAST_DATES — joined on FORECAST_ID; provides forecast date detail.
• MRP_RECOMMENDATIONS — joined on REFERENCE_SCHEDULE_ID; connects schedules to planner recommendations.
• WIP_LINES — joined on LINE_ID; ties schedule rows to work-in-process lines.
• MTL_SALES_ORDERS — joined on SOURCE_SALES_ORDER_ID; links MDS entries to originating sales orders.
• MTL_RESERVATIONS — joined on RESERVATION_ID; associates the schedule with material reservations.

Together these relationships position MRP_SCHEDULE_DATES as the central link between master scheduling activity and its upstream demand and forecast sources, and its downstream execution and reservation records.