Search Results mrp_oe




Overview
Explore in AI Chat

Overview

MRP_OE is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that provides the integration bridge between Oracle Order Management (OE) and the Oracle Material Requirements Planning (MRP) engine. Its central business function is to make sales order demand visible to MRP, MPS, and ATP processing by staging order line changes in an interface table and exposing helper logic that MRP can call. Because MRP planning runs in a batch, real-time changes to sales orders made in Order Management must be propagated to the planning engine so that dependent demand, supply, and available-to-promise calculations reflect the current committed order book. MRP_OE supports that propagation and supplies the small utility functions that the planning data collection process uses to qualify and format order demand.

Key Procedures and Functions

The documented package exposes six procedures and functions. Their purposes are as follows:

  • MRP_QUANTITY — Returns or normalises the order line demand quantity used by MRP for planning, ensuring the ordered quantity is expressed in the correct planning unit.
  • MRP_DATE — Returns or adjusts the date value (such as schedule or promise date) that MRP uses as the demand date for the order line.
  • AVAILABLE_TO_MRP — Determines whether a given order line qualifies as available demand to be passed to the MRP planning engine; used to filter ineligible lines.
  • UPDATED_FLAG — Manages or returns the processed/updated status flag on the sales order update staging record, marking whether a row has been consumed by the planning collection.
  • AVAILABLE_TO_ATP — Determines whether an order line is available to Available-to-Promise processing, distinguishing demand that participates in ATP checks.
  • TOTAL_RESERV_QTY — Computes or returns the total reserved quantity on the order line, relevant to netting reserved demand against supply.

No parameter lists are documented; the above reflects purpose only.

Tables Accessed

Through APPS synonyms the package references the following tables:

  • OE_ORDER_LINES_ALL — The base Order Management order line table, read to obtain ordered item, quantity, dates, and line attributes for the sales order.
  • MRP_SALES_ORDER_UPDATES — The staging/interface table into which sales order line changes are recorded so that the MRP data collection can pick them up; MRP_OE inserts or updates rows here to signal demand changes.
  • MTL_DEMAND — The demand table read (and, in the 12.1.1 excerpt, also accessed via MTL_DEMAND_OM_VIEW) to obtain the MRP-visible demand records and reserved quantities associated with order lines.

Usage Notes

MRP_OE is not a user-facing API; it is invoked internally. Typical invocation paths include the Order Management order entry and shipping forms, which trigger order line change events that must be communicated to MRP, and concurrent programs that populate the planning interface tables. The package is referenced by nine other database objects, indicating it is embedded within the broader planning and Order Management integration layer rather than called directly by customers. The ETRM metadata classifies the API as OTHER and reports it is not referenced by any database object itself, consistent with it being a mid-tier library package within the integration chain. Oracle's reordered planning flow expects MRP_OE to keep the MRP_SALES_ORDER_UPDATES interface synchronised so the next MRP/MPS run consumes accurate sales order demand. Customisations should avoid modifying the package directly; instead, extensions should rely on the documented procedures or on the underlying interface table.