Search Results actual_arrival_date




Overview
Explore in AI Chat

Overview

APPS.FTE_PTRK_TOKENS_V is an Oracle E-Business Suite reporting view owned by the APPS schema. The name combines the Oracle Transportation Management "FTE" (Freight/Transportation Engine) prefix, "PTRK" (possibly pertaining to "Token Tracking"), and "TOKENS", suggesting the view flattens one row per delivery leg into a set of informational "token" fields used by downstream reporting or integration layers. Specifically, it denormalizes transportation stop and location information associated with a delivery leg, exposing origin and destination geography together with formatted shipment date components. The view is read-only and is intended for query and integration consumption rather than transactional use. In EBS 12.1.1 and 12.2.2, the view is a convenience layer over Oracle Shipping (WSH) tables, sparing report developers the complexity of joining delivery legs, trip stops, and locations themselves. The searched term actual_departure_date corresponds directly to a source column mapped into the view's SHIP_FROM_DATE output, confirming its relevance in shipment tracking and delivery-performance reporting.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over three referenced base objects, each exposed via a SYNONYM resolving to the WSH schema:

The join path is: LEGS.PICK_UP_STOP_ID = STOPS1.STOP_ID; LEGS.DROP_OFF_STOP_ID = STOPS2.STOP_ID; STOPS1.STOP_LOCATION_ID = LOC1.WSH_LOCATION_ID; STOPS2.STOP_LOCATION_ID = LOC2.WSH_LOCATION_ID. Note the column naming is unintuitive: LOC1 populates the DESTINATION_* columns while LOC2 populates the ORIGIN_* columns.

Key Columns

  • DELIVERY_LEG_ID — unique identifier of the delivery leg; the de facto primary key of the view.
  • SHIP_FROM_DATE — formatted from STOPS1.ACTUAL_DEPARTURE_DATE using the mask 'YYYY-MM-DD-HH24:MI:SS'. This is the searched field users often refer to as actual_departure_date.
  • SHIP_FROM_YEAR / SHIP_FROM_MONTH / SHIP_FROM_DAY — derived character components of the departure date for grouping and calendar reporting.
  • SHIP_TO_DATE, SHIP_TO_YEAR, SHIP_TO_MONTH, SHIP_TO_DAY — analogous fields derived from STOPS2.ACTUAL_ARRIVAL_DATE.
  • ORIGIN_* and DESTINATION_* — POSTAL_CODE, CITY, STATE, COUNTRY_CODE for each endpoint.

Because dates are stored as character strings, ordering or filtering on SHIP_FROM_DATE relies on the ISO-like format sort order rather than native DATE arithmetic.

Common Use Cases and Queries

Typical uses include shipment performance analysis, lane/geography reporting, and data feeds to external transportation or analytics systems. A representative query listing recent departures by destination:

SELECT delivery_leg_id, ship_from_date, ship_to_date,
       origin_city, destination_city, destination_country_code
FROM   apps.fte_ptrk_tokens_v
WHERE  ship_from_year = '2024'
ORDER BY ship_from_date;

A performance comparison of actual departure versus arrival, or a filter on a specific postal code destination, both leverage the same denominator columns. Because ACTUAL_DEPARTURE_DATE may be null until a stop is confirmed, consumers should treat blank SHIP_FROM_DATE as "not yet departed." Developers requiring true date arithmetic should cast the formatted strings back to DATE or query WSH_TRIP_STOPS directly.