Search Results wsh_tp_release_grp




Overview
Explore in AI Chat

Overview

The APPS.WSH_TP_RELEASE_GRP package body is a PL/SQL grouping package within the Oracle E-Business Suite Shipping (WSH) module. Its name follows the EBS naming convention in which the _GRP suffix denotes a grouping or dispatcher layer that centralizes the release-related operations used by the Transportation and Shipping execution flows. In the context of Oracle EBS 12.1.1 and 12.2.2, the package functions as an orchestration wrapper that consolidates calls to the underlying transportation release interfaces, principally WSH_TP_RELEASE_INT, and exposes them through a single, well-defined entry point.

The API classification recorded in the ETRM metadata is GRP, confirming that this package is not intended to perform low-level business logic itself. Rather, it delegates processing to the integration packages it references and provides a stable interface for concurrent programs, forms, and custom code that need to release transportation or delivery-related data to planning, execution, or third-party systems.

Key Procedures and Functions

The documented metadata identifies a single callable program unit:

  • ACTION — The sole documented procedure in the package. Consistent with the EBS grouping-package pattern, ACTION serves as a generic dispatcher: the caller passes an action code that selects which underlying release operation is performed, and the procedure routes execution to the appropriate routine in the referenced integration packages. The specific parameter list is not documented in the ETRM extract and should therefore not be assumed; callers should consult the package specification (WSH_TP_RELEASE_GRP) for the authoritative signature.

The dependency list shows that the package body depends on FND_API for standard API error and message handling conventions, WSH_TP_RELEASE_INT for the underlying release integration logic, WSH_UTIL_CORE for shared shipping utilities, and WSH_DEBUG_INTERFACE and WSH_DEBUG_SV for diagnostic logging and debug trace output. The presence of the debug packages indicates that the release process can be instrumented with debug logging during troubleshooting.

Tables Accessed

According to the documented table references, the package touches only one table through an APPS synonym:

  • PLITBLM — A standard Oracle PL/SQL-supplied table, typically used in conjunction with the DBMS_OUTPUT buffer for line or message output. Its presence reflects the package's debug and diagnostic messaging support rather than any application data persistence.

No WSH transactional tables are listed as direct references. This reinforces the grouping-package design: persistent insert, update, and delete activity against delivery, trip, or release records occurs inside the delegated integration package WSH_TP_RELEASE_INT, not within this body.

Usage Notes

The metadata records that APPS.WSH_TP_RELEASE_GRP is not referenced by any database object but is invoked by three other packages. This pattern is typical of a top-level entry point that is called from the application tier rather than from compiled database dependencies. Typical invocation paths include:

  • Shipping or transportation concurrent programs that release delivery or trip data to external planning systems.
  • Oracle Shipping Execution forms or Oracle Transportation Management integration flows that trigger a release on demand.
  • Custom concurrent programs and extensions that require a supported entry point for release processing without duplicating integration logic.

Because only the ACTION procedure is documented, custom code should call that entry point rather than the internal integration routines directly. Callers should pass the action code expected by the specification, and enable WSH debug via the standard debug profile options when tracing failures. Standard EBS considerations apply: the package executes under the APPS schema, and any distributed or concurrent invocation should be committed by the caller in accordance with the transaction boundaries enforced by WSH_TP_RELEASE_INT and FND_API.