Search Results check_req_po_cancelled

Overview

OE_DS_PVT is a private PL/SQL package in the APPS schema that supports Oracle Order Management's drop-ship fulfillment functionality. Drop shipping allows a sales order to be fulfilled directly by a supplier rather than from internal inventory, bypassing the standard pick, pack, and ship cycle. The suffix "_PVT" designates this as an internal, private API: it is not intended for direct invocation by external or customer-facing code, and its procedures may change between releases without notice. OE_DS_PVT provides the low-level plumbing that links Order Management sales orders to their corresponding purchasing documents and records the resulting inventory transactions when goods are received against a drop-ship purchase order.

The package is registered as VALID in the ETRM metadata for 12.1.1 and 12.2.2 and exposes six documented procedures and functions. It depends on the SYS.STANDARD package and is referenced by four other packages, including INV_LOGICAL_TRANSACTIONS_PUB, OE_LINE_UTIL, and PO_GML_DB_COMMON, as well as by itself, indicating internal recursion or layered calls.

Key Procedures and Functions

• DROPSHIPRECEIVE — The principal routine, responsible for processing a drop-ship receipt. It records the receipt of goods supplied directly by the vendor against the originating sales order and drives the associated inventory and order-management updates.
• GET_MTL_SALES_ORDER_ID — A lookup function that retrieves the MTL_SALES_ORDERS identifier associated with a drop-ship context, allowing downstream logic to map order information into the inventory sales-order framework.
• INSERT_OE_DROP_SHIP_SOURCE — Inserts a record into the OE_DROP_SHIP_SOURCES entity, establishing or maintaining the link between a sales order line and its drop-ship sourcing information.
• CHECK_PO_APPROVED — Validates whether the relevant purchase order has been approved before drop-ship processing proceeds, enforcing the purchasing approval gate.
• CHECK_REQ_PO_CANCELLED — Determines whether the associated requisition or purchase order has been cancelled, allowing callers to halt drop-ship activity when the supply document is no longer valid.
• OM_PO_DISCREPANCY_EXISTS — Checks for discrepancies between Order Management and Purchasing data, flagging conditions where the sales order and purchase order no longer align.

Tables Accessed

OE_DS_PVT reads and writes a broad set of supply-chain tables. Order and sourcing data is held in OE_DROP_SHIP_SOURCES and OE_DROP_SHIP_SOURCE_S, with MTL_SALES_ORDERS linking to the inventory sales-order model. Transaction processing touches MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_S, MTL_TRANSACTIONS_INTERFACE, and MTL_TRANSACTION_LOTS_INTERFACE. Serial-controlled items are handled through MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_INTERFACE, and OE_MTL_SN_INTERFACE_S. Item, subinventory, and organization context come from MTL_SYSTEM_ITEMS, MTL_SECONDARY_INVENTORIES, HR_ORGANIZATION_INFORMATION, and GL_CODE_COMBINATIONS, with FND_LANGUAGES providing language support for any user-facing validation messages.

Usage Notes

This is a private API and should not be called directly from custom code. It is invoked internally by Order Management forms, workflows, and concurrent processes that manage drop-ship orders, and it is consumed by packages such as OE_LINE_UTIL and INV_LOGICAL_TRANSACTIONS_PUB. Because the metadata documents no parameter lists, integrators should treat the procedure signatures as unsupported. Any customization requiring drop-ship receipt logic should use the supported public APIs and preserve the OE_DROP_SHIP_SOURCES linkage so that order-to-purchase reconciliation remains intact.