Results for “fte_message”

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

Overview

FTE_TRACKING_WRAPPER is a server-side PL/SQL package body owned by APPS within the Oracle E-Business Suite transportation and logistics modules. It functions as a wrapper layer over the Oracle Freight and Tracking Engine (FTE) tracking infrastructure, coordinating the population of shipment tracking status records as carrier tracking messages flow into the E-Business Suite environment. The package is classified as OTHER in the ETRM repository, indicating that it is a supporting/integration wrapper rather than a primary public API, and it carries the internal header identifier FTETKWRB.pls (version 120.6, 2006).

The core business purpose of the package is to reconcile inbound carrier tracking information against delivery legs and to populate the FTE tracking tables — shipment status headers, shipment status details, and delivery proof records — so that in-transit visibility for outbound shipments is maintained. In the specific scenario documented, the wrapper processes a parent delivery leg and cascades tracking information down to child legs, ensuring that consolidated or multi-leg deliveries share consistent tracking status.

Key Procedures and Functions

The package exposes a bounded set of documented entry points (six procedures/functions in total), with the publicly referenced procedures listed as follows:

• POPULATE_CHILD_DELIVERY_LEGS — The primary documented procedure. It populates child delivery legs when tracking information is received for a parent delivery leg, writing records to FTE_SHIPMENT_STATUS_HEADERS, FTE_SHIPMENT_STATUS_DETAILS, and FTE_DELIVERY_PROOF. It accepts initialisation, delivery leg, transaction, and carrier identifiers, and returns standard EBS API status parameters (return status, message count, message data). It also declares a child-leg cursor against WSH_DELIVERY_LEGS and additional structures supporting functional workflow notification.
• GET_DELIVERY_OR_CONTAINER — Retrieves delivery or container context used to identify the tracking subject before status records are written.
• GET_DELIVERY_DETAILS — Resolves delivery detail attributes required for shipment status population.
• INSERT_ERROR_STATUS — Records error conditions encountered during tracking processing, including SQL error code and message text, so that failures are visible for reconciliation.
• CALL_LAST_DELIVERY_LEG — Invokes processing against the terminal delivery leg, ensuring final-leg tracking is captured.

The user search term "fte_message" aligns with the FTE_MESSAGE_* family of tables consumed by this package (address, contact, location, partner), which store normalised message-partner metadata accompanying inbound tracking transmissions.

Tables Accessed

The package reads and writes a defined set of APPS-synonym tables. Tracking output tables include FTE_SHIPMENT_STATUS_HEADERS, FTE_SHIPMENT_STATUS_DETAILS, FTE_SHIPMENT_STATUS_EXCEPTIONS, FTE_DELIVERY_PROOF, FTE_TRACKING_STATUS_S, and FTE_TRACKING_TRANSACTION_S, which collectively persist status, proof-of-delivery, and transaction-level tracking data. Message metadata is sourced from FTE_MESSAGE_ADDRESS, FTE_MESSAGE_CONTACT, FTE_MESSAGE_LOCATION, and FTE_MESSAGE_PARTNER, supporting resolution of the sender and recipient context of tracking messages.

Delivery structure is resolved from WSH_DELIVERY_ASSIGNMENTS and WSH_DELIVERY_DETAILS, with carrier identification via WSH_CARRIERS. Participating organisation and party data is obtained from HZ_PARTIES, and workflow parameter structures use WF_PARAMETER_LIST_T. These reads ensure child legs are correctly identified and mapped before status rows are inserted.

Usage Notes

FTE_TRACKING_WRAPPER is not intended for direct end-user invocation and is referenced by zero other packages in the ETRM metadata, indicating limited internal coupling. It is typically called indirectly during tracking integration flows — for example, when carrier tracking messages are imported and applied to delivery legs, or from functional workflow activities that notify stakeholders of shipment status changes. Implementers customising tracking behaviour should treat POPULATE_CHILD_DELIVERY_LEGS as the principal callable with standard EBS message-list semantics: pass p_init_msg_list, evaluate x_return_status, then iterate x_msg_count and x_msg_data to surface errors. Because the package writes directly to FTE and WSH-related tables, any custom invocation should execute within a controlled transaction and observe the delivered error-status capture pattern to avoid orphaned or inconsistent tracking records.