Results for “fte_tracking_wrapper”

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

Overview

The APPS.FTE_TRACKING_WRAPPER package is a PL/SQL wrapper in Oracle E-Business Suite that supports the FTE (Freight and Transportation Execution) tracking functionality, which forms part of the Oracle Transportation Management integration layer. In EBS 12.1.1 and 12.2.2, this package serves as the bridging API that moves shipment and delivery tracking data captured in FTE interface tables into the core Oracle Shipping (WSH) delivery structures and FTE status tables. Specifically, it inserts header interface data into the WSH_DELIVERY_LEG_ACTIVITIES and WSH_DELIVERY_LEG_DETAILS tables and removes duplicate records from the detail interface tables, as described in the source header comments. The package encapsulates several lower-level tracking operations so that upstream processes — typically concurrent programs that process inbound tracking status messages from carriers — can invoke a single, controlled entry point rather than manipulating the interface and base tables directly.

Key Procedures and Functions

The documented package exposes six procedures/overloads that together cover the tracking data lifecycle:

• GET_DELIVERY_OR_CONTAINER — Retrieves delivery or container information associated with a transaction and returns exception, return status, and error token information to the caller.
• GET_DELIVERY_DETAILS — Fetches delivery detail information for a given transaction and carrier, returning exception message, return status, and error token outputs.
• INSERT_ERROR_STATUS — Writes an error record into the FTE interface error tables, capturing the interface error identifier, interface table name, message code/name, error message, and carrier context.
• CALL_LAST_DELIVERY_LEG — Provided in two overloaded forms. The first accepts a delivery leg identifier and received date; the second adds the standard API parameters (API version, initialization message list, and return status/message count/message data outputs). Both invoke processing logic for the final delivery leg.
• POPULATE_CHILD_DELIVERY_LEGS — Introduced as an MDC change for Release 12, this procedure populates child delivery legs using init message list, delivery leg ID, transaction ID, and carrier ID inputs, returning standard API status outputs.

Tables Accessed

The package reads from and writes to several FTE and Oracle Shipping tables via APPS synonyms. The core shipping tables include WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS, and WSH_CARRIERS, which provide delivery, assignment, and carrier context. The FTE tracking tables — FTE_TRACKING_TRANSACTION_S, FTE_TRACKING_STATUS_S, FTE_SHIPMENT_STATUS_HEADERS, FTE_SHIPMENT_STATUS_DETAILS, and FTE_SHIPMENT_STATUS_EXCEPTIONS — store the shipment status and tracking transaction records. Supporting tables include FTE_DELIVERY_PROOF, the FTE message tables (FTE_MESSAGE_ADDRESS, FTE_MESSAGE_CONTACT, FTE_MESSAGE_LOCATION, FTE_MESSAGE_PARTNER), plus HZ_PARTIES and WF_PARAMETER_LIST_T for party and workflow parameter context.

Usage Notes

FTE_TRACKING_WRAPPER is referenced by zero other PL/SQL packages in the documented metadata, indicating it is called directly by external drivers rather than nested within other PL/SQL APIs. It is typically invoked from FTE tracking concurrent programs and inbound message processing flows that consume carrier tracking data, and may also be called from custom code or forms that require programmatic delivery leg tracking. Because it interacts with open interfaces (WSH delivery leg activities and details), it should be scheduled during controlled windows, and callers should inspect the return status and exception message outputs to detect interface errors logged through INSERT_ERROR_STATUS.