Search Results r_message_code

Overview

WMS_SHIPPING_INTERFACE_GRP is an Oracle Warehouse Management (WMS) API group package that provides a programmatic gateway between shipping-related inbound and outbound flows and the Warehouse Management execution tables. It is owned by APPS and classified under ETRM as an API group (GRP), meaning it exposes a set of callable procedures that other Oracle E-Business Suite modules and customer extensions use to stage, validate, and persist shipping data such as delivery details, trips, wave lines, and serial numbers. The package header carries a modest revision history (WMSGINTB.pls 120.4, dated 2007), indicating that the interface layer has been stable across the 11i and R12 code lines and remains present in 12.1.1 and 12.2.2.

The body declares conventional API framework constants, including g_ret_status_success, g_ret_status_error, and g_ret_status_unexp_error drawn from FND_API, together with g_pkg_name and g_pkg_version used for diagnostics. Release-level constants (G_WMS_RELEASE_LEVEL, G_J_RELEASE_LEVEL) allow the code to branch on the active WMS and INV release levels. A private print_debug procedure gated by the INV_DEBUG_TRACE profile writes trace messages through INV_LOG_UTIL.

Key Procedures and Functions

Six public program units are documented in the ETRM metadata:

• PROCESS_DELIVERIES — the top-level entry point that accepts a set of deliveries and drives the staging and validation of their associated delivery information into the WMS shipping temp structures.
• PROCESS_DELIVERY_DETAILS — processes the line-level detail of one or more deliveries, reconciling delivery detail records with WMS license plate and wave line data prior to inventory transactions.
• PROCESS_DELIVERY_TRIP — handles the trip and stop context associated with a delivery so that shipped goods are attributed to the correct trip and routing.
• PROCESS_SERIAL_NUMBER — validates and processes serial number information for serial-controlled items being shipped, ensuring inventory and delivery serial records align. This is the entry point most commonly sought by users searching for "process_serial_number."
• WAVE_LINE_EXISTS — a boolean-style lookup used to determine whether a wave line already exists for a given wave and item, supporting idempotent wave processing.
• SPLIT_WAVE_LINE — performs wave line splitting so that a single wave line can be broken into multiple lines to reflect partial picks or quantity reallocations.

The body also contains internal helpers, including the function get_lpn_context, which resolves LPN context, outermost LPN, and license plate number from WMS_LICENSE_PLATE_NUMBERS, and the debug utility print_debug. Parameter details are not reproduced here.

Tables Accessed

Documented APPS-synonym references include:

• WSH_DELIVERY_DETAILS — source delivery detail rows that define what is being shipped.
• WMS_SHIPPING_TRANSACTION_TEMP and WMS_WSH_WDD_GTEMP — staging tables used to buffer shipping transactions before they are committed to inventory.
• WMS_LICENSE_PLATE_NUMBERS — LPN context resolution and outermost LPN identification.
• WMS_WP_WAVE_LINES and WMS_WP_WAVE_LINES_S — wave line existence checks and wave line splitting.
• MTL_SERIAL_NUMBERS — serial number validation and serial assignment during shipping.
• MTL_MATERIAL_TRANSACTIONS_TEMP — temporary transaction staging for inventory updates.
• MTL_TXN_REQUEST_HEADERS, MTL_TXN_REQUEST_LINES, and DUAL — move order header/line interrogation and constant selection.
• PLITBLM — the standard Oracle PL/SQL character table type used for passing collections.

Usage Notes

WMS_SHIPPING_INTERFACE_GRP is not a concurrent program; it is invoked as a PL/SQL API from other server-side code. It is referenced by six other packages in the ETRM inventory, and is typically called from shipping execution, wave planning, or custom integration code when deliveries, delivery details, trips, or serial numbers must be pushed into WMS. Because it manipulates staging tables and relies on the current WMS and INV release levels, callers should invoke it within a transaction that respects FND_API return status values and should enable INV_DEBUG_TRACE only for diagnostics. Care is required with PROCESS_SERIAL_NUMBER, since serial number integrity affects both inventory balances and downstream delivery confirmation.