Results for “updated_flag”

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

Overview

MRP_OE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a boundary interface between Oracle Order Management (OE) and the Material Requirements Planning and Advanced Supply Chain Planning engines. Its central purpose is to expose order-line demand information — quantity, date, and reservation status — to the planning processes in a normalized form, so that planning logic does not need to query order management tables directly or interpret their internal structures.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the invoking schema rather than the APPS owner. This allows planning code running in other schemas to call these functions while respecting the caller's security context. The package body is version-stamped 120.0, and despite its age it remains present in the 12.2.2 data model because the planning engines and their interface contracts were carried forward substantially unchanged from the 11i lineage.

Two constants define the demand source identifiers the package operates against: MTL_SALES_ORDER (value 2) for external sales orders and MTL_INT_SALES_ORDER (value 8) for internal sales orders, that is, inter-organization or internal requisition-driven demand. An IN_PROCESS constant (value 3) supports status evaluation. These constants align the package with the demand source taxonomy used by the MTL_DEMAND table.

Key Procedures and Functions

The package exposes six public functions, all taking a single demand identifier as input and returning a scalar value. Every function carries a pragma restrict_references declaration for WNDS (Write No Database State) and WNPS (Write No Package State), confirming that these routines are strictly read-only and therefore safe to call from SQL statements and parallel planning queries.

• mrp_quantity — Returns the demand quantity relevant to material requirements planning for the identified demand record.
• mrp_date — Returns the demand date used by the planning engine for MRP horizon and time-phasing calculations.
• available_to_mrp — Returns the quantity of the demand line that is available for MRP netting purposes.
• updated_flag — Returns a status indicator reflecting whether the demand record has been updated, allowing planning to detect changed order information.
• available_to_atp — Returns the quantity available to Available-to-Promise processing, supporting ATP and scheduling checks distinct from MRP netting.
• total_reserv_qty — Returns the total reserved quantity on the demand line, so planning can account for supply already committed to specific demand.

Tables Accessed

The package reads through APPS synonyms of three principal tables. MTL_DEMAND is the central demand repository populated from order management and other sources; the package derives quantities, dates, and demand source values from this table, which is why the demand source constants are defined at package level. MRP_SALES_ORDER_UPDATES is the staging table through which order management signals changed sales order information to the planning engine; the updated_flag function almost certainly interrogates this table. OE_ORDER_LINES_ALL holds the order line detail itself, providing authoritative line-level attributes such as ordered quantity and schedule dates that may not be fully replicated into MTL_DEMAND.

Usage Notes

MRP_OE is not an end-user API and has no user interface. It is an internal reference package invoked by the planning engine and by other PL/SQL packages — the metadata records nine dependent packages. Typical invocation occurs within the MRP, ASCP, and ATP concurrent program execution paths, and from Oracle Forms or custom code that needs a consistent, planning-oriented view of order demand without duplicating business logic. Because all functions are restricted to read-only state and accept only the demand identifier, customizations should call them rather than re-implementing equivalent queries, and should avoid modifying the package, as its contract is relied upon across the planning codebase.