Search Results reconciliate_moves

Overview

FTE_TP_GRP is a public PL/SQL package in the APPS schema (source file FTETPGPS.pls) that provides the core integration layer between Oracle Shipping execution (WSH) and the Freight and Transportation Execution (FTE) module. It is classified as a GRP-level API, meaning it is intended to expose higher-level, transaction-oriented entry points — including callback procedures and concurrent-level processing logic — rather than primitive single-record CRUD operations.

The package's principal business purpose is to synchronize trip, stop, and continuous-move information between the shipping UI/transactional engine and the FTE data model. It handles several distinct integration responsibilities: it looks up continuous move information for display on shipping screens; it responds to trip and stop lifecycle events issued by WSH by maintaining the corresponding FTE move records; it maps and reconciles moves; it firms planned moves; and it purges staging tables used during interface processing.

Key Procedures and Functions

The package exposes seven documented program units, each targeting a specific stage of the shipping-to-freight integration flow.

• LOOKUP_CM_INFO — Retrieves continuous move information (a segment plus its associated move attributes) for a given trip identifier, so that shipping user interfaces can display continuous move details.
• TRIP_CALLBACK — A callback entry point invoked by WSH when actions are performed on trips. It accepts an action parameter record identifying the triggering event (e.g., confirm, cancel) plus a table of trip records, and applies the corresponding changes to the continuous move / move records maintained by FTE.
• STOP_CALLBACK — The analogous callback for stop-level events, processing a table of stop records in response to actions performed on trip stops.
• MAP_MOVES — Establishes or maintains the correspondence between source move structures and their FTE move representations.
• RECONCILIATE_MOVES — Reconciles moves, aligning existing FTE move data with the move data derived from the shipping source (trips, trip moves, and interface rows). This addresses the user's search term "reconciliate_moves" and is the unit responsible for resolving discrepancies between the two representations.
• TP_FIRM_MOVES — Firms planned moves, converting tentative/planned move records into firm, committed transportation moves.
• PURGE_INTERFACE_TABLES — Cleans up the FTE interface/staging tables after processing, removing successfully consumed rows to prevent re-processing.

Because the package is AUTHID CURRENT_USER, it executes with the privileges of the calling user, requiring appropriate object grants on the referenced tables.

Tables Accessed

Through APPS synonyms, the package reads and writes the following:

• FTE_MOVES and FTE_TRIP_MOVES — the primary FTE move entities; written/updated by MAP_MOVES, RECONCILIATE_MOVES, TP_FIRM_MOVES, and the callbacks.
• FTE_MOVES_INTERFACE and FTE_TRIP_MOVES_INTERFACE — staging tables used for inbound movement data and purged by PURGE_INTERFACE_TABLES.
• WSH_TRIPS_INTERFACE — shipping-side interface data referencing trips.
• PLITBLM — the standard PL/SQL index-by table used to carry message data back to callers.

Usage Notes

The callback procedures (TRIP_CALLBACK, STOP_CALLBACK) are invoked by the WSH shipping transaction engine, not by direct user action, when trip and stop actions occur. LOOKUP_CM_INFO supports shipping UI display. The remaining units — MAP_MOVES, RECONCILIATE_MOVES, TP_FIRM_MOVES, and PURGE_INTERFACE_TABLES — are typically driven by FTE processing and concurrent programs (including reconciliation and move-firming batches) or by custom code during integration. The package is referenced by one other package, and its header ($Header: FTETPGPS.pls 115.2) reflects a 2003 vintage, so behavior is stable across 12.1.1 and 12.2.2.