Results for “create_update_delivery_detail”

50+ results




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

Overview

WSH_INTERFACE_EXT_GRP is an Oracle EBS public API group package in the APPS schema that supports the Shipping Execution (WSH) product family. Its classification as a GRP package indicates that it bundles related business logic for the extended shipping interface, providing a single entry point for creating and updating shipping entities such as deliveries, delivery details, trips, stops, delivery legs, and freight costs. It also manages delivery and exception actions — including pre-ship confirmation activities for Oracle Transportation Management (OTM) integrations. The package is central to activities that occur when shipping data must be propagated through the interface tables. It depends on the FND_API error-handling framework, FND_FLEX_EXT for key flexfield validation, and WSH_UTIL_CORE for internal shipping utility routines. It is referenced by sixteen dependent packages, underscoring its role as a foundational integration component.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. Each represents a distinct action or data transformation in the shipping interface lifecycle:

  • HANDLE_MISSING_INFO — Processes records or attributes with incomplete information, applying default logic or raising errors as required.
  • DELIVERY_ACTION — Executes an action against a delivery record, such as confirming, closing, or otherwise transitioning its status.
  • CREATE_UPDATE_DELIVERY — Creates a new delivery or updates an existing delivery header.
  • DELIVERY_DETAIL_ACTION — Performs an action on a delivery detail, typically the line-level shipment contents.
  • CREATE_UPDATE_DELIVERY_DETAIL — Creates or updates delivery detail records.
  • TRIP_ACTION — Executes an action against a trip, such as consolidation, dispatch, or status change.
  • CREATE_UPDATE_TRIP — Creates or updates a trip record.
  • STOP_ACTION — Performs an action against a trip stop.
  • CREATE_UPDATE_STOP — Creates or updates a trip stop.
  • CREATE_UPDATE_FREIGHT_COSTS — Creates or updates freight cost entries associated with shipping transactions.
  • GET_EXCEPTIONS — Retrieves exception records relevant to shipping operations.
  • EXCEPTION_ACTION — Applies an action to an exception record, such as acknowledging or resolving it.
  • DELIVERY_LEG_ACTION — Performs an action on a delivery leg, the segment of movement between stops.
  • OTM_PRE_SHIP_CONFIRM — Facilitates pre-ship confirmation processing for Oracle Transportation Management integration.

Tables Accessed

Two tables are documented as referenced through APPS synonyms:

  • WSH_EXCEPTIONS — Stores shipping exception records. The package reads and writes this table through GET_EXCEPTIONS and EXCEPTION_ACTION to surface and resolve exceptions encountered during shipping interface processing.
  • PLITBLM — A PL/SQL index-by table type defined in the database, used for passing collections of records between package procedures and their callers without a physical database table. It is a standard mechanism for handling multi-row data in PL/SQL APIs.

Usage Notes

WSH_INTERFACE_EXT_GRP is invoked mainly as a server-side API group by other packages rather than directly by end users. Its referenced-by list includes major shipping and warehouse management packages: INV_LPN_TRX_PUB, INV_PICK_RELEASE_PUB, INV_RCV_RESERVATION_UTIL, INV_SHIPPING_TRANSACTION_PUB, WMS_CATCH_WEIGHT_PVT, WMS_CONTAINER_PVT, WMS_DIRECT_SHIP_PVT, WMS_PACKING_WORKBENCH_PVT, WMS_REPLENISHMENT_PVT, WMS_SHIPPING_INTERFACE_GRP, WMS_SHIPPING_TRANSACTION_PUB, WMS_TASK_DISPATCH_GEN, WMS_XDOCK_PEGGING_PUB, WMS_XDOCK_UTILS_PVT, WSH_NEW_DELIVERY_ACTIONS, and WSH_WMS_LPN_GRP. These relationships confirm that the package serves as a shared interface layer between Inventory (INV), Warehouse Management (WMS), and Shipping Execution (WSH) modules. Custom concurrent programs, interface loaders, or customer-specific extensions that need to programmatically manage deliveries, trips, stops, freight costs, or shipping exceptions should call these procedures through the standard FND_API error-handling protocol. Direct DML against WSH_EXCEPTIONS should be avoided in favor of EXCEPTION_ACTION to preserve data integrity and business rule enforcement.