Search Results old_order_quantity




Overview
Explore in AI Chat

Overview

MRP_RELIEF_INTERFACE is an interface table owned by the MRP schema within the Oracle E-Business Suite Master Scheduling/MRP product. Its documented purpose is to relieve the master schedule tables, meaning it acts as the transient staging area through which consumption, cancellation, and adjustment records are passed to reduce or eliminate existing planned orders, scheduled receipts, or demand entries in the planning engine. The table functions as the inbound conduit for relief transactions generated by execution systems such as Work in Process, Purchasing, Order Management, and Inventory, allowing the planning process to reconcile planned supply against actual activity.

From the perspective of the documented foreign key structure, the heuristic Data Vault classification for this object is a link. The table records the association between an item/organization context and a disposition or planned order reference, holding the transaction-level changes rather than serving as a standalone hub of business entities or a pure descriptive satellite.

Key Information Stored

The table contains 31 documented columns. The most significant are summarized below.

Common Use Cases and Queries

The primary use case is diagnosing relief processing failures. Rows with a PROCESS_STATUS indicating an error and a populated ERROR_MESSAGE reveal transactions that could not be applied to the master schedule.

  • Identifying unprocessed or failed relief rows: select TRANSACTION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, RELIEF_TYPE, PROCESS_STATUS, ERROR_MESSAGE from MRP_RELIEF_INTERFACE where PROCESS_STATUS is not null and ERROR_MESSAGE is not null.
  • Reconciling net quantity change for a planned order: compare NEW_ORDER_QUANTITY against OLD_ORDER_QUANTITY for a given PLANNED_ORDER_ID.
  • Tracing relief back to its source application using SOURCE_CODE and SOURCE_LINE_ID.
  • Auditing all relief activity generated by a specific concurrent request via REQUEST_ID.
  • Reporting on demand class changes using DEMAND_CLASS and OLD_DEMAND_CLASS.

Related Objects

The documented foreign key relationships define the principal dependent and referenced objects:

  • MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID to resolve item and organization descriptions.
  • WIP_ENTITIES — joined on DISPOSITION_ID to link relief to work in process entities.
  • MTL_DEMAND — joined on DISPOSITION_ID to link relief to demand records.
  • MRP_RECOMMENDATIONS — joined on PLANNED_ORDER_ID to associate relief with the planned order being modified or cancelled.

These relationships confirm the table's position at the boundary between execution-side transactions and the planning engine, where relief data is validated and applied to the master schedule.