Results for “released_quantity”

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

Overview

APPS.OE_QUERY is a public PL/SQL package in Oracle Order Management (OE) that provides query and derivation routines for order, line, and configuration data. It is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking session rather than the definer, which is consistent with its role as a read-oriented query helper rather than a privileged maintenance API. ETRM classifies the package as OTHER, indicating it is not a formal business-event or processing API. Its documented function list focuses on returning quantities, statuses, identifiers, and descriptive attributes that Order Management forms, reports, and dependent packages need but that are not conveniently exposed through base tables alone. Because these routines encapsulate release, reservation, scheduling, and configuration logic, callers rely on OE_QUERY to obtain consistent answers rather than re-deriving them.

Key Procedures and Functions

The package exposes 56 documented units. The following are representative of the functional groupings:

• LINE_TOTAL / SERVICE_TOTAL / CONFIGURATION_TOTAL — Compute monetary or quantity totals for an order line, a service line, or a configuration respectively.
• SCHEDULE_STATUS — Overloaded to return scheduling status either from a passed ORDER_LINE_ID or from a schedule status code; declared with PRAGMA RESTRICT_REFERENCES(..., WNDS).
• ATO_Indicator / Get_ATO_Indicator — Determine whether a line is an assemble-to-order item based on line and item type.
• RELEASED_QUANTITY / P_LINE_RELEASED_QUANTITY — Return the released quantity for a given order line.
• RESERVED_QUANTITY — Return reserved quantity at the line level.
• II_RESERVED_QUANTITY / II_RELEASED_QUANTITY / II_SCHEDULE_STATUS_CODE — Internal-item (component) level versions of reservation, release, and scheduling status queries.
• HOLD / SHIPMENT_NUMBER / LINE_NUMBER — Return hold information and descriptive identifiers.
• ITEM_CONC_SEG / ORDER_TYPE / SOURCE_ORDER_NUMBER / SOURCE_ORDER_TYPE / SUPPLY_RES_DETAILS — Return item concatenated segment values, order type, source order context, and supply reservation detail.

Tables Accessed

The package reads primarily from Order Management and shipping entities: SO_LINE_DETAILS, SO_ORDER_TYPES, SO_LOOKUPS, SO_ORDER_HOLDS_ALL, SO_PICKING_LINE_DETAILS, SO_PRICE_ADJUSTMENTS, and SO_RESULTS. It also references MTL_SYSTEM_ITEMS_KFV for item description, MTL_LOT_NUMBERS for lot context, and MTL_DEMAND_INTERFACE, MTL_SO_RMA_INTERFACE, and MTL_SO_RMA_RECEIPTS for supply and return material data. Financial and receivables context is drawn from AR_PAYMENT_SCHEDULES and RA_CUSTOMER_TRX_LINES. These accesses support quantity, scheduling, hold, shipment, and configuration derivations; the routines are largely read-only lookups against these APPS synonyms.

Usage Notes

OE_QUERY is typically invoked from Order Management forms, concurrent programs, and other OE packages rather than from end-user entry points. ETRM records twelve packages that reference it, so it functions as a shared query layer within the OE code family. Custom extensions should call it in the same manner as Oracle's own code — as a deterministic, session-privileged query helper — and should not expect it to perform DML. Because some functions carry WNDS declarations, they are safe for use in SQL and PL/SQL contexts where purity restrictions apply. The user search term atp_date_delivery reflects a common need to retrieve delivery and availability dates; such values are surfaced through the scheduling-related routines and their underlying SO and MTL sources rather than through a dedicated ATP API in this package.