Search Results get_order_number

Overview

The APPS.OE_ORDER_IMPORT_INTEROP_PUB package is a public PL/SQL API within the Oracle E-Business Suite Order Management (OM) and Purchasing (PO) integration layer. Its name reflects its primary design intent: to support the Order Import open interface while exposing reusable interoperation utility logic. Although it resides in the Order Management schema namespace, the documented dependency graph shows that the package is referenced heavily by Purchasing modules, including PO_INQ_SV, PO_RCO_VALIDATION_PVT, PO_REQS_INQ_SV, and PO_REQ_LINES_SV. This cross-module consumption indicates that the package serves a shared role in surfacing requisition, order, and drop-ship related attributes during requisition inquiry, validation, and processing flows.

In EBS 12.1.1 and 12.2.2, the package is classified as a PUB (public) API, meaning it is intended for supported external invocation rather than internal-only use. Its status is VALID and it is owned by the APPS schema, consistent with standard EBS API conventions.

Key Procedures and Functions

ETRM documents eight procedures and functions on this package. These provide quantity and identifier lookups that support order and requisition interoperation:

• GET_OPEN_QTY — Returns the open (unshipped, unfulfilled) quantity associated with an order, requisition, or line context, enabling callers to assess outstanding demand.
• GET_SHIPPED_QTY — Returns the quantity already shipped, supporting reconciliation between ordered and fulfilled amounts.
• GET_CANCELLED_QTY — Returns the cancelled quantity, allowing net requirement calculations.
• GET_ORDER_NUMBER — Retrieves the order number associated with a given order or requisition reference, used when displaying or validating order identifiers.
• GET_HEADER_ID — Returns the order header identifier, providing the surrogate key needed for downstream header-level operations.
• GET_REQ_HEADER_ID — Returns the requisition header identifier, bridging requisition processing to purchasing inquiries.
• GET_LINE_ID — Returns the order line identifier, supporting line-level lookups and updates.
• GET_REQUISITION_HEADER_IDS — Returns one or more requisition header identifiers, typically as a collection, for scenarios where multiple requisitions relate to a single order context.

Parameter signatures are not enumerated in the available metadata and should be confirmed against the deployed package specification before custom invocation.

Tables Accessed

The package references the following base tables through APPS synonyms:

• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — source order header and line data used for quantity and identifier retrieval.
• OE_DROP_SHIP_SOURCES and SO_DROP_SHIP_SOURCES — drop-ship sourcing records that link sales orders to requisitions and purchase orders.
• PO_REQUISITION_HEADERS and PO_REQUISITION_HEADERS_ALL — requisition header data used by the requisition header identifier functions.
• PO_REQUISITION_LINES_ALL — requisition line data supporting line-level quantity and reference lookups.

These tables explain the purchasing-side dependencies: requisition inquiry and validation services call this package to resolve order and drop-ship relationships without duplicating lookup logic.

Usage Notes

This package is typically invoked indirectly. Forms and concurrent programs in Order Management and Purchasing call the dependent service packages (PO_INQ_SV, PO_REQ_LINES_SV, and similar), which in turn invoke OE_ORDER_IMPORT_INTEROP_PUB. Custom code that needs order-to-requisition quantity reconciliation, drop-ship order resolution, or identifier lookups can call the public functions directly, provided commit and error-handling behavior is respected. Because it is a PUB API, direct calls are supported, but callers should verify the package specification in the target release (12.1.1 or 12.2.2) since internal implementations may differ while the public contract remains stable.