Search Results wms_shipping_interface_grp




Overview
Explore in AI Chat

Overview

WMS_SHIPPING_INTERFACE_GRP is a public PL/SQL package in the APPS schema that acts as the integration bridge between Oracle Warehouse Management (WMS) and Oracle Shipping Execution (WSH) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented API classification is GRP, indicating a grouping or interface layer that orchestrates lower-level transactions rather than exposing a single business entity. The package's central purpose is to move and validate delivery detail, trip, serial number, and wave line information between the warehouse execution environment and the shipping tables so that outbound logistics operations remain consistent across both modules. Because warehouse picking, packing, staging, and shipping activities frequently cross module boundaries, this package provides the procedural contracts that shipping and inventory code paths depend on when they must create, validate, or update delivery and wave records. The package was documented with a VALID status in the ETRM repository and depends on the standard Oracle APIs FND_API and STANDARD, confirming that it follows the conventional EBS API error-handling and message-stack conventions.

Key Procedures and Functions

The package exposes six documented procedures and functions, which together cover the principal shipping-interface operations:

  • PROCESS_DELIVERY_DETAILS — Processes delivery detail records originating from warehouse activity so that shipping execution reflects the correct line-level contents of a delivery.
  • PROCESS_DELIVERY_TRIP — Handles trip-related processing for deliveries, synchronizing trip assignment information with the shipping data model.
  • PROCESS_SERIAL_NUMBER — Processes serial number information associated with shipped or staged material, ensuring serialized inventory is correctly recorded.
  • PROCESS_DELIVERIES — Performs processing at the delivery (header) level, coordinating multiple delivery detail and trip operations.
  • WAVE_LINE_EXISTS — A validation function that determines whether a wave line already exists, typically used to prevent duplicate wave line creation.
  • SPLIT_WAVE_LINE — Splits an existing wave line into multiple lines, supporting partial picks, quantity reallocations, or wave re-planning scenarios.

No parameter lists are asserted here; callers should reference the package specification in the target instance for exact signatures.

Tables Accessed

The package reads and writes the following documented tables, referenced through APPS synonyms:

Usage Notes

WMS_SHIPPING_INTERFACE_GRP is referenced by six documented packages, notably WSH_DELIVERY_DETAILS_INV, WSH_DELIVERY_DETAILS_PKG, WSH_DELIVERY_LEGS_ACTIONS, WSH_DETAILS_VALIDATIONS, WSH_TP_RELEASE, and WSH_TP_RELEASE_INT. This dependency pattern indicates the package is invoked from within standard shipping execution and transportation planning code paths, particularly during delivery detail maintenance, delivery leg actions, and transportation release processing. It is not typically called directly from Oracle Forms by an end user; rather it is invoked programmatically by the WSH and WMS module APIs. Customizations and extensions that create or modify delivery details, wave lines, or serial assignments in a warehouse context should honor these same calls to preserve integration integrity. Because the package depends on FND_API, callers should expect standard EBS API error codes and message-stack conventions, and should always check the return/exception status after invocation.