Search Results wsh_trips_grp




Overview

WSH_FTE_TP_INTEGRATION is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides the integration layer between Oracle Transportation Management (OTM) and the Warehouse Management (WSH) module within EBS 12.1.1 and 12.2.2. The package supports the Freight Transportation Execution (FTE) or Transportation Planning integration model, enabling shipment and trip data to be synchronized between the EBS Order Management and Shipping execution flows and the external transportation management engine. Its principal business role is the processing of inbound and outbound transportation events — trip creation, stop management, move reconciliation, and the purging of interface staging tables — so that carrier assignment, routing, and shipment lifecycle changes executed externally can be reflected back into EBS trips, trip stops, and delivery records. According to ETRM metadata (12.2.2), the package is classified as API classification OTHER and is documented as VALID in the APPS schema. It exposes seven documented procedures and is referenced by four other packages, confirming that it functions as a shared integration utility rather than a standalone entry point.

Key Procedures and Functions

  • LOOKUP_CM_INFO — Returns container management or carrier movement information used during integration processing, resolving the contextual data required to associate an external transportation event with EBS shipment structures.
  • TRIP_CALLBACK — Handles callback processing for trip-level events received from the external transportation system, updating the corresponding WSH trip records.
  • STOP_CALLBACK — Handles callback processing for trip stop-level events, applying stop additions, changes, or completions to the EBS trip stop entities.
  • MAP_MOVES — Maps external transportation move data into the equivalent EBS shipment and trip move structures, performing the translation between the two data models.
  • RECONCILIATE_MOVES — Reconciles moves between the external system and EBS, identifying and resolving discrepancies in move status, sequence, or assignment.
  • TP_FIRM_MOVES — Firms transportation moves in the integration process, committing tentative or planned moves into firm EBS trip and shipment records.
  • PURGE_INTERFACE_TABLES — Removes processed records from the integration staging/interface tables, controlling growth of the interface schema following successful processing.

Tables Accessed

The ETRM metadata does not enumerate specific base tables accessed via APPS synonyms. Based on object dependencies, WSH_FTE_TP_INTEGRATION operates against the WSH trip and trip stop entities through calls to WSH_TRIPS_PVT, WSH_TRIP_STOPS_PVT, WSH_TRIPS_GRP, WSH_TRIP_STOPS_GRP, and WSH_TP_RELEASE_GRP. These packages collectively read and write the trip header, trip stop, and release (delivery line) records that the integration procedures populate and maintain. The PURGE_INTERFACE_TABLES procedure operates against the FTE/transportation interface staging tables that hold inbound and outbound integration messages prior to reconciliation and purge.

Usage Notes

WSH_FTE_TP_INTEGRATION is typically invoked from the FTE_TP_GRP and WSH_TP_RELEASE_INT packages, and it is itself referenced by WSH_TRIPS_GRP and WSH_TRIP_STOPS_GRP, indicating that it is called both by scheduled integration programs and by trip lifecycle logic. In a standard deployment it is executed in the context of transportation integration concurrent programs, or through WSH_TP_RELEASE_INT when release data is transmitted to the external planning engine. Custom code should not call the callback procedures directly except in tightly controlled integration scenarios; the recommended invocation path is through the documented group packages. Because the package writes to trip and stop records, integration runs should be scheduled during defined transportation planning windows, and purging of interface tables should be coordinated with the reconciliation batch to avoid deleting unprocessed messages.