Search Results check_wms_install

Overview

POS_ASN_CREATE_PVT is an internal PL/SQL package in the APPS schema that supports the creation of Advance Shipment Notices (ASNs) within Oracle E-Business Suite Purchasing and Receiving. It is classified as a PVT (private) API, indicating that it is not exposed for direct customer invocation but instead serves as a supporting engine behind public APIs, Oracle Forms, and concurrent programs. The package encapsulates the validation, quantity derivation, and interface-insertion logic required to build ASN, shipment, and receipt records from inbound supplier data, including Advanced Shipment Notice (ASN) and Receiving (RCV) transactions. In Oracle EBS 12.1.1 and 12.2.2, this logic is central to supplier self-service, iSupplier Portal, and Excel-based ASN uploads, where shipment lines must be validated against purchase orders, lots, serial numbers, and license plate numbers (LPNs) before they are committed.

Key Procedures and Functions

The ETRM metadata documents sixteen callable units within this package. These can be grouped by function:

• Insertion routines — INSERT_MSNI, INSERT_MTLI, and INSERT_WLPNI create interface rows in the serial, lot, and LPN interface structures used during ASN staging.
• Validation routines — VALIDATESERIALRANGE, VALIDATELPN, VALIDATELOT, VALIDATE_SHIP_FROM, and CHECK_LPNLOTSERIAL_VALID confirm that serial numbers, LPNs, lots, and ship-from locations comply with defined inventory and shipping rules before records are accepted.
• Quantity derivation — GET_INVOICE_QTY, GETSHIPMENTQUANTITY, GET_PO_QUANTITY, GET_PO_PENDING_ASN_QUANTITY, and GET_TOTAL_SHIPPEDQUANTITY compute the quantities required to reconcile ordered, shipped, pending ASN, and invoiced amounts for a purchase order line or shipment.
• Utility and environment routines — FINDLLSCODE locates the applicable line location/shipment code, START_WIP_WORKFLOW initiates WIP workflow processing where applicable, and CHECK_WMS_INSTALL detects whether Warehouse Management System functionality is enabled, which affects validations.

Together these units provide the complete validation and staging capability required to construct a valid ASN transaction.

Tables Accessed

The package reads and writes data through APPS synonyms across the Purchasing, Inventory, and Receiving schemas. Purchasing tables PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, and PO_RELEASES_ALL supply the order, shipment, release, and distribution context against which ASN quantities are validated. Inventory tables MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE, MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, MTL_TRANSACTION_LOTS_INTERFACE, MTL_TRANSACTION_LOT_NUMBERS, MTL_SERIAL_NUMBERS_INTERFACE, and MTL_UNIT_TRANSACTIONS provide item, UOM, lot, and serial master data. Receiving tables RCV_LOTS_SUPPLY and RCV_SERIALS_SUPPLY are used to validate lot and serial supply. Collection types PO_TBL_DATE, PO_TBL_NUMBER, and PO_TBL_VARCHAR2000 are used to pass arrays of values between internal procedures, enabling bulk validation of shipment lines.

Usage Notes

POS_ASN_CREATE_PVT is not intended for direct customer calls. It is referenced by three other packages: itself (recursive reference), POS_EXCELASN_PVT, and POS_VIEW_RECEIPTS_GRP. POS_EXCELASN_PVT handles Excel-based ASN upload, and POS_VIEW_RECEIPTS_GRP supports receipt viewing. In practice, the package is invoked indirectly through the ASN creation flows exposed by Oracle iSupplier Portal and the Purchasing/Receiving forms, and through concurrent programs that process staged ASN interface records. Custom code should call the public ASN APIs rather than this private package. Because several procedures check WMS installation and serial/lot validity, behavior may vary depending on whether WMS and lot/serial control are enabled at the inventory organization level. As with all PVT packages, Oracle may change the internal signatures between releases, and any custom dependency on this package is unsupported.