Results for “wsh_interface_common_actions”

50+ results




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

Overview

WSH_INTERFACE_COMMON_ACTIONS is an Oracle EBS Shipping (WSH) package that centralizes the common processing logic used when delivery interface records are converted into actual Oracle Shipping delivery, delivery detail, trip, and freight cost entities. The package belongs to the Applications (APPS) schema and is classified under the generic "OTHER" API category rather than as a formal public API. Its header comment dates the source to 2007 (WSHINCAS.pls 120.0), which places it in the code line carried forward into both EBS 12.1.1 and 12.2.2.

The business purpose of the package is to abstract the shared actions that several interface processors (delivery, delivery detail, trip, and freight) must perform: assigning container and detail records to a parent, splitting or packing lines, cancelling interfaced records, creating or updating a trip for a delivery, and populating trip stop information. Because these actions are common to multiple calling programs, they are consolidated here rather than duplicated across the individual interface packages. ETRM documents twelve procedures in the package, and it is referenced by six other packages, confirming its role as a shared utility layer within the WSH interface stack.

Key Procedures and Functions

  • UPDATE_CONTNR_INT_ASSIGNMENTS — Updates container interface assignment records, associating child delivery details with a parent delivery detail and parent interface detail.
  • PROCESS_INTERFACED_DEL_DETAILS — Processes interfaced delivery detail rows for a given delivery interface, honoring a supplied action code and optionally a delivery or new delivery identifier.
  • PROCESS_INTERFACED_DELIVERIES — Processes interfaced delivery headers, returning the resulting delivery identifier and a return status.
  • PROCESS_SPLITS — Handles delivery detail rows that must be split across deliveries during interface processing.
  • PACK_LINES — Performs packing-related line processing for interface records.
  • PROCESS_NON_SPLITS — Processes interface rows that are not subject to splitting, complementing PROCESS_SPLITS.
  • PROCESS_CANCEL — Cancels interfaced delivery or detail records as directed by the action code.
  • DELIVERY_INTERFACE_WRAPPER — Wrapper routine that drives delivery interface processing end to end.
  • PROCESS_INT_FREIGHT_COSTS — Reads and applies interfaced freight cost records to deliveries.
  • CREATE_UPDATE_TRIP_FOR_DLVY — Creates a new trip or updates an existing trip for a delivery, the procedure most commonly associated with the search term create_update_trip_for_dlvy.
  • INT_TRIP_STOP_INFO — Populates interface trip stop information for trip and stop records.
  • LOCK_DELIVERY_AND_DETAILS — Acquires locks on delivery and delivery detail rows to ensure consistent concurrent processing.

The package also declares global variables, including G_Update_Attributes_Tab, G_Packing_Detail_Tab, and G_SERIAL_RANGE_TAB, plus the PL/SQL record and table types PackingDetailRecType and PackingDetailTabType used to pass packing detail identifiers between internal routines.

Tables Accessed

The documented tables fall into several functional groups. Shipping delivery structures are central: WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS, and WSH_DELIVERY_LEGS hold the resulting delivery, assignment, and leg records, while the corresponding interface tables WSH_DEL_ASSGN_INTERFACE, WSH_DEL_DETAILS_INTERFACE, WSH_DEL_LEGS_INTERFACE, and WSH_DEL_LEGS_INTERFACE_S hold the inbound staged data that the package consumes. Trip and carrier information is read from WSH_CARRIER_SERVICES. Freight costing uses WSH_FREIGHT_COSTS_INTERFACE and WSH_FREIGHT_COST_TYPES. Item master validation draws on MTL_SYSTEM_ITEMS. Order and requisition sourcing references OE_ORDER_LINES_ALL, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES_ALL. Organization context is resolved through HR_ORGANIZATION_INFORMATION.

Usage Notes

WSH_INTERFACE_COMMON_ACTIONS is invoked indirectly rather than as a standalone user-facing API. It is called by the delivery interface concurrent programs and by the other WSH interface packages that depend on it (six documented referencing packages). Because CREATE_UPDATE_TRIP_FOR_DLVY and the companion trip procedures are not documented as public APIs, custom code should generally not call them directly; instead, the supported integration path is to populate the WSH interface tables and let the standard delivery interface concurrent program perform the processing. When custom PL/SQL must reuse this logic, callers should follow the package's action-code conventions, respect the delivery interface identifiers, and check the returned status values (x_return_status, x_dlvy_id) before committing. The package's locking procedure, LOCK_DELIVERY_AND_DETAILS, indicates that concurrent execution against the same delivery rows should be serialized to avoid assignment and split inconsistencies.