Search Results p_outermost_lpn_id

Overview

APPS.WMS_SHIPPING_TRANSACTION_PUB is a public PL/SQL integration package that bridges Oracle Shipping Execution and Oracle Warehouse Management (WMS) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its declared purpose, drawn directly from the package header, is to act as the integration point between Shipping and WMS for direct ship, LPN ship, trip and delivery management, and truck closing operations. The package is registered with a public API classification and an active lifecycle, and its repository metadata identifies the business entity as WMS_SHIPPING_TRANSACTION. The header revision (120.3.12010000.1) confirms the shipped object is aligned with the 12.1 code line and is carried forward into 12.2.2.

Key Procedures and Functions

The package exposes a broad set of documented procedures and functions (fifty in total). The primary functional groupings are as follows:

• IS_LOADED — determines whether a load or dock context is already occupied, given organization, dock door, dock appointment, and direct ship indicators.
• GET_DOCK_DOORS, GET_STAGING_LANE, GET_LPN_LOV, GET_DELIVERIES, GET_DELIVERY_INFO, GET_DELIVERY_DETAIL_ID — LOV and inquiry routines that return reference cursors used by Shipping/WMS forms to populate dock door, staging lane, LPN, delivery, and delivery detail selections.
• GET_DELIVERY_NAME — returns the delivery name for a supplied delivery identifier.
• POPULATE_WSTT — populates the WMS shipping staging/temporary structure for a given organization, LPN, trip, dock door, and direct ship flag.
• NESTED_SERIAL_CHECK, LPN_DISCREPANCY_CHECK, CHECK_LPN_IN_SAME_TRIP, CHECK_LPN_DELIVERIES, MISSING_ITEM_CHECK, NONTRANSACTABLE_ITEM_CHECK — validation routines that enforce serial number integrity, LPN discrepancies, trip/delivery consistency, and item eligibility before shipping transactions proceed.
• LPN_SUBMIT, CREATE_DELIVERY, GET_LPN_DELIVERY, UPDATE_TRIP, UPDATE_DELIVERY — transacting routines that submit LPN shipments and create or maintain trip and delivery records.

The header additionally defines a t_genref REF CURSOR type and package constants such as G_PKG_NAME and G_ALLOW_SHIP_SET_BREAK, used to control set break behavior during shipping.

Tables Accessed

Through APPS synonyms, the package reads and writes core Shipping, Inventory, and WMS tables. Inventory and transaction tables include MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_TEMP, MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_TRANSACTION_TYPES, and MTL_TXN_REQUEST_LINES — supporting item validation, serial control, and transaction staging. Order and customer data are drawn from OE_ORDER_LINES_ALL, OE_SETS, OE_TRANSACTION_TYPES_TL, HZ_CUST_ACCOUNTS, HZ_PARTIES, and GL_DAILY_CONVERSION_TYPES. The WMS-specific working table WMS_DIRECT_SHIP_TEMP supports direct ship processing. Together these tables supply the validation, reference, and staging data required for LPN, trip, delivery, and direct ship operations.

Usage Notes

WMS_SHIPPING_TRANSACTION_PUB is invoked primarily from Oracle Shipping Execution and WMS forms during dock, load, trip, and delivery processing, and is referenced by six other packages in the EBS schema. It is a typical candidate for concurrent program invocation where bulk LPN submission, trip update, or delivery creation is required. Custom extensions should call only the documented public procedures and respect the package constants, particularly G_ALLOW_SHIP_SET_BREAK, which governs set break enforcement. Because the routines perform committed inventory and shipping transactions, callers should invoke them within the standard EBS transaction and error-handling framework, check the returned status and message code outputs (for example, from POPULATE_WSTT), and avoid direct DML against the underlying tables. The package should be treated as an integration contract between Shipping and WMS rather than a general-purpose utility.