Search Results oe_mtl_sn_interface_s

Overview

APPS.OE_DS_PVT is a private PL/SQL package body within the Oracle E-Business Suite Order Management (OM) module, classified under the ETRM taxonomy as a PVT (private) API. It encapsulates the internal business logic supporting drop-ship order processing and the associated receiving, sourcing, and procurement validation operations. In Oracle EBS 12.1.1 and 12.2.2, the package acts as the execution layer that bridges Order Management drop-ship flows with Purchasing, Inventory, and Shipping execution data. Because it is a private package, it is not intended as a public integration surface; instead, it is invoked internally by Order Management processes such as order import, drop-ship receipt creation, and ship confirmation. The package status is VALID, indicating its dependencies resolve correctly within the documented environment.

Key Procedures and Functions

The documented package exposes six procedures and functions, each targeting a distinct aspect of drop-ship and procurement validation:

• DROPSHIPRECEIVE — Performs the drop-ship receipt transaction, creating the receiving records that reconcile the supplier shipment against the drop-ship sales order.
• GET_MTL_SALES_ORDER_ID — Retrieves the Inventory sales order identifier associated with a given transaction, linking the MTL_SALES_ORDERS record to Order Management data.
• INSERT_OE_DROP_SHIP_SOURCE — Inserts a new drop-ship sourcing record into OE_DROP_SHIP_SOURCES, establishing the supplier-to-order-line sourcing relationship.
• CHECK_PO_APPROVED — Validates whether the linked purchase order has been approved, which is a precondition for drop-ship receipt processing.
• CHECK_REQ_PO_CANCELLED — Determines whether the associated requisition or purchase order has been cancelled, preventing receipt against invalid procurement documents.
• OM_PO_DISCREPANCY_EXISTS — Detects discrepancies between Order Management expectations and Purchasing document data, supporting exception handling.

No parameter lists are documented in the ETRM metadata, so signatures are intentionally omitted.

Tables Accessed

The package references a broad set of APPS-synonym tables reflecting its cross-module role. Inventory and transaction tables include MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_S, MTL_TRANSACTIONS_INTERFACE, MTL_TRANSACTION_LOTS_INTERFACE, MTL_SYSTEM_ITEMS, MTL_SALES_ORDERS, and MTL_SECONDARY_INVENTORIES. Serial number handling draws on MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_INTERFACE, and notably OE_MTL_SN_INTERFACE_S, which is the object most directly associated with the user's search term and serves as the Order Management staging interface for serial number data. Sourcing data is maintained in OE_DROP_SHIP_SOURCES and OE_DROP_SHIP_SOURCE_S. Financial and organizational reference data come from GL_CODE_COMBINATIONS, GL_SETS_OF_BOOKS, HR_ORGANIZATION_INFORMATION, FND_LANGUAGES, and FND_PROFILE. The package also depends on several public package APIs, including FND_API, FND_MESSAGE, OE_ORDER_PUB, OE_MSG_PUB, and INV_RESERVATION_PUB, rather than accessing their underlying tables directly.

Usage Notes

OE_DS_PVT is typically invoked indirectly. Drop-ship receipt and sourcing logic is triggered from Order Management workflows, the Receive Drop Ship process, and ship confirmation flows that call public OM APIs such as OE_ORDER_PUB and OE_SHIP_CONFIRMATION_PUB, which in turn delegate to this private package. The serial number interface OE_MTL_SN_INTERFACE_S is populated during drop-ship receipt processing so that serialized items are staged for Inventory validation. Because the package is private and not referenced by any database object externally, it should not be called directly from custom code; developers seeking equivalent functionality should use the documented public APIs. The package is referenced by four other packages within the documented dependency set, confirming its role as an internal utility layer.