Results for “update_delivery_leg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.WSH_DELIVERY_LEGS_GRP is a Group-type PL/SQL package within the Oracle Shipping Execution (WSH) module of Oracle E-Business Suite. It serves as the public group API layer governing the delivery leg entity, which represents the movement of a delivery or trip from one location to another within the shipping and transportation lifecycle. Delivery legs are the granular transportation records that connect deliveries to trips, trip stops, and carrier manifest information.

The package exposes a stable public interface over the private business logic implemented in WSH_DELIVERY_LEGS_PVT. As a GRP-classified API, it is intended for external consumption by forms, concurrent programs, and custom extensions, insulating callers from internal implementation changes in the private layer. The package status is VALID across Oracle EBS 12.1.1 and 12.2.2, confirming it remains part of the supported shipping schema.

Functionally, the package supports the update and lifecycle actions applied to delivery legs, enabling transportation planning and execution workflows to modify leg details such as routing, scheduled dates, and carrier assignments without directly manipulating base tables.

Key Procedures and Functions

The documented interface consists of two public procedures:

• DELIVERY_LEG_ACTION — Executes a specified action against one or more delivery legs. This procedure encapsulates the transition logic that governs the state and behavior of a leg, allowing callers to trigger processing behavior defined by the shipping action model rather than issuing direct DML.
• UPDATE_DELIVERY_LEG — Updates the attributes of an existing delivery leg record. This procedure provides the supported path for modifying leg-level information while preserving the integrity of associated delivery, trip, and document instance data.

Both procedures are declared in the package specification and implemented in the package body. Because the ETRM metadata does not publish parameter signatures for these procedures, callers must obtain parameter lists from the corresponding specification source in the APPS schema rather than from this reference.

Tables Accessed

The package operates against the core shipping and transportation tables through APPS synonyms:

• WSH_DELIVERY_LEGS — The primary entity table, holding the delivery leg records that this package updates and acts upon.
• WSH_TRIPS and WSH_TRIP_STOPS — Trip and stop definitions that provide the transportation context for a leg and to which legs are linked.
• WSH_NEW_DELIVERIES — Delivery header information associated with the legs being processed.
• WSH_DOCUMENT_INSTANCES — Document instance records used to track shipping documentation generated or affected by leg activity.
• WSH_REPORT_SETS and WSH_REPORT_SET_LINES — Report set definitions and their lines, supporting document and report generation associated with delivery leg processing.
• PLITBLM — A standard Oracle EBS PL/SQL internal table type used for array or bulk processing within the package.

Reads and writes are concentrated on WSH_DELIVERY_LEGS, with the related tables supplying reference, validation, and documentation data required by the documented procedures.

Usage Notes

WSH_DELIVERY_LEGS_GRP is referenced by three other packages: WSH_DELIVERIES_GRP, WSH_INTERFACE_GRP, and FTE_TRACKING_WRAPPER, as well as being referenced by itself. The dependency on WSH_INTERFACE_GRP is particularly relevant for users searching on "wsh_interface_grp": the interface API layer calls into this package when processing inbound shipping interface data that requires delivery leg creation or update. This makes WSH_DELIVERY_LEGS_GRP part of the execution path for interface-driven shipping transactions.

The package also depends on WSH_DELIVERY_LEGS_PVT, WSH_UTIL_CORE, and WSH_DEBUG_SV, indicating that the public group API delegates business logic to the private layer while leveraging shared shipping utilities and debug instrumentation.

Typical invocation occurs from Oracle Shipping forms during transportation planning and execution, from concurrent programs that process delivery and trip changes, and from custom PL/SQL that must update legs using the supported API rather than direct DML. Because it is a documented GRP package, custom integrations should call these procedures in preference to updating WSH_DELIVERY_LEGS directly, ensuring that validation, document instance maintenance, and dependent record updates remain consistent.