Search Results wsh_rlm_interface




Overview
Explore in AI Chat

Overview

The APPS.WSH_RLM_INTERFACE package body is a container that groups shared utilities and functions used in connection with Oracle E-Business Suite shipping and returns logistics functionality, specifically within the context of the RLM (Returns / Reverse Logistics Management) flow. In EBS 12.1.1 and 12.2.2, this package acts as an interface wrapper that bridges the shipping execution data model (deliveries, delivery details, delivery legs, trip stops) with reverse logistics processing routines exposed via RLM_CORE_SV. It encapsulates common queries and computations required to reconcile goods in transit, associates them with the appropriate delivery and trip structures, and returns the results to calling processes.

The package is a PL/SQL package body stored under the APPS schema and is currently reported with status VALID. Its dependency graph shows it consumes standard EBS API infrastructure (FND_API, FND_MESSAGE), debug and diagnostics services (WSH_DEBUG_INTERFACE, WSH_DEBUG_SV), the RLM core service package, utility routines (WSH_UTIL_CORE), and shipping execution tables. This pattern indicates the package is designed as a reusable service layer rather than a directly user-facing component.

Key Procedures and Functions

The ETRM documentation for the 12.2.2 release identifies a single documented callable:

  • GET_IN_TRANSIT_QTY — a function/procedure that returns the quantity of goods currently in transit, evaluated against the delivery and trip data available in the shipping execution tables. This routine is intended to supply reverse logistics or reconciliation logic with a consolidated view of in-transit inventory, so that downstream processes can decide on receipt, adjustment, or return actions.

The package body may contain additional private helpers, but the documented public interface centers on this quantity-retrieval routine. It relies on the RLM core services and debug utilities to record diagnostic information during execution.

Tables Accessed

The package references the following objects via APPS synonyms, all owned or accessed within the shipping execution schema:

  • WSH_NEW_DELIVERIES — the header record for a delivery, providing delivery-level context such as status, organization, and dates.
  • WSH_DELIVERY_DETAILS — line-level detail for the delivery, including shipped item, quantity, and inventory references.
  • WSH_DELIVERY_LEGS — the movement segments of a delivery, used to determine routing and leg-level status.
  • WSH_TRIP_STOPS — the stop sequence and location information for a trip, enabling location-aware in-transit quantities.
  • PLITBLM — a standard Oracle PL/SQL binary integer table type used for passing and manipulating numeric collections.

The combination of delivery, delivery details, delivery legs, and trip stops supports a positional (stop-aware) in-transit quantity calculation, consistent with the returns/reverse logistics use case.

Usage Notes

WSH_RLM_INTERFACE is not referenced by any database object in the ETRM inventory and does not appear to be invoked directly by Oracle Forms or a concurrent program in the standard shipping flows. Instead, it is referenced by three other packages, indicating it is consumed programmatically by other shipping or reverse-logistics modules. Typical invocation scenarios include:

  • Custom code or extensions that need to determine in-transit quantity for a delivery, trip, or stop as part of an RLM reconciliation process.
  • Server-side logic triggered by reverse logistics workflows that require delivery and trip data to compute available return quantities.
  • Diagnostic and troubleshooting scenarios, where the package's dependencies on WSH_DEBUG_INTERFACE and WSH_DEBUG_SV allow controlled debug output during execution.

Because the package calls FND_API and FND_MESSAGE, it conforms to the standard EBS API error-handling convention (message stacking and API return codes). Developers integrating with it should follow standard EBS API exception handling patterns and ensure the caller has appropriate privileges to read the underlying WSH tables.