Search Results hold_exists

Overview

APPS.OE_DROP_SHIP_PVT is a private PL/SQL package body in Oracle Order Management that supports drop shipment processing across the order-to-purchase order lifecycle. A drop ship occurs when a sales order line is fulfilled directly by a supplier rather than from internal inventory, creating a linked purchase order and a sourcing relationship recorded in SO_DROP_SHIP_SOURCES. This package provides the utility logic Oracle EBS uses to compare the state of a sales order line against its corresponding purchase order line, to evaluate holds and scheduling, and to translate internal PO status codes into readable values. Because it is classified as a PVT (private) package, it is not part of the public API surface and is intended to be called only by other Oracle-owned packages within the drop ship and order management flow, not by customer extensions.

Key Procedures and Functions

• GET_PO_STATUS — Returns the status of a purchase order header. The business purpose is to expose the PO header status to drop ship validation logic, and it is implemented by delegating to the PO header server-side API (PO_HEADERS_SV3), returning NULL when the underlying call raises an exception.
• GET_RELEASE_STATUS — Returns the status of a purchase order release, delegating to the PO releases server-side API (PO_RELEASES_SV2). It is used when drop shipment fulfillment is driven by a blanket agreement release rather than a standard PO.
• COMPARE_PO_SO — The central comparison routine. It reconciles sales order quantities (ordered less cancelled less shipped) against purchase order quantities aggregated from PO_LINE_LOCATIONS joined to SO_DROP_SHIP_SOURCES, excluding finally closed lines, and evaluates whether a hold exists on the PO. This function is the context in which the identifier hold_exists (with the companion variable po_hold_exists) appears; hold_exists is a local flag used within the comparison to determine whether hold conditions affect the drop ship relationship between the sales order line and the purchase order line.
• GET_HOLD_NAME — Resolves a hold identifier to its descriptive hold name, referencing SO_HOLDS and related hold tables so that drop ship discrepancies can be reported with meaningful hold descriptions.
• RECOVER_SCHEDULE — Reconstructs or restores schedule information for a drop ship line, supporting the scheduling alignment between the sales order demand and the supplier purchase order schedule dates.

Tables Accessed

• PO_HEADERS and PO_LINE_LOCATIONS — read to obtain purchase order status, quantities, cancelled and shipped amounts, and closed codes for comparison against sales order values.
• PO_REQUISITION_LINES — read where requisition-backed sourcing is relevant to the drop ship link.
• SO_DROP_SHIP_SOURCES — the primary linking table, joining sales order lines to purchase order lines and locations by header and line identifiers.
• SO_LINES_ALL and SO_LINE_DETAILS — read for sales order line attributes such as ordered, cancelled, and shipped quantities and units of measure.
• SO_HOLDS and SO_ORDER_HOLDS — read to identify active holds and resolve hold names, which is directly relevant to the hold_exists logic.

Usage Notes

OE_DROP_SHIP_PVT is invoked internally by other Oracle Order Management and Purchasing packages that manage drop shipment processing; the provided metadata indicates the package is referenced by one other package. It is typically triggered when order management must synchronize a sales order line with its sourcing purchase order, for example during order entry validation, scheduling, or hold evaluation. Because it is a private package, customizations should not call it directly; instead, developers should use supported public APIs and treat this body as an implementation detail subject to change between releases, including 12.1.1 and 12.2.2.