Results for “fte_tender_snapshot”

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

Overview

The FTE_TENDER_SNAPSHOT table resides in the FTE schema and belongs to the Oracle E-Business Suite Transportation Execution (FTE) product family. Its documented purpose is to store a snapshot of trip stops at the moment a load tender is transmitted to a carrier. Because tendering is a point-in-time contractual event, the operational values that exist on the trip and its stops (weight, volume, and associated units of measure) may change after the tender is issued. The snapshot table preserves those values as they stood when the tender was sent, insulating the historical record from subsequent operational edits.

The table is classified heuristically as a standalone object under the Data Vault modeling convention. This suggests it is best treated as a satellite-like structure keyed by a composite business key rather than as a hub or link, since it stores descriptive attitudinal data (quantities and UOMs) captured at a specific event rather than resolving many-to-many relationships among hubs.

Key Information Stored

Within Oracle EBS 12.1.1 and 12.2.2, FTE_TENDER_SNAPSHOT contains 16 documented columns. The following are the most significant:

• LOAD_TENDER_NUMBER — the tender identifier that groups snapshot rows belonging to a single tender event. This column participates in the unique index and is the principal business-key candidate.
• TRIP_ID — foreign key to WSH_TRIPS, identifying the trip whose stops are being snapshotted.
• STOP_ID — foreign key to WSH_TRIP_STOPS, identifying the individual stop within the trip.
• TOTAL_WEIGHT and WEIGHT_UOM — the aggregated stop weight and its unit of measure at tender time.
• TOTAL_VOLUME and VOLUME_UOM — the aggregated stop volume and its unit of measure at tender time.
• SESSION_VALUE — an internal session/context value used to tie the snapshot rows back to the tendering operation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the process that created or modified the row.

A single-column surrogate primary key is not documented; the business-key candidate is the unique index FTE_TENDER_SNAPSHOT_U1, defined on (LOAD_TENDER_NUMBER, STOP_ID, TRIP_ID). This composite key confirms that one snapshot row exists per tender, per stop, per trip.

Common Use Cases and Queries

Typical scenarios involve reconciling the tendered quantities against the current operational values on WSH_TRIP_STOPS, auditing carrier disputes, and reconstructing the state of a shipment as of tender transmission.

To retrieve all snapshot lines for a tender:

• SELECT * FROM FTE.FTE_TENDER_SNAPSHOT WHERE LOAD_TENDER_NUMBER = :tender_number;

To compare tendered versus current stop weights:

• SELECT s.STOP_ID, s.TOTAL_WEIGHT AS TENDERED_WT, t.GROSS_WEIGHT AS CURRENT_WT FROM FTE.FTE_TENDER_SNAPSHOT s JOIN WSH.WSH_TRIP_STOPS t ON t.STOP_ID = s.STOP_ID WHERE s.LOAD_TENDER_NUMBER = :tender_number;

Reporting patterns commonly aggregate TOTAL_WEIGHT and TOTAL_VOLUME by WEIGHT_UOM or VOLUME_UOM across tenders to validate rating and freight calculations.

Related Objects

The most significant related objects, grounded in documented foreign-key relationships, include:

• WSH_TRIPS — joined via TRIP_ID; the parent trip definition.
• WSH_TRIP_STOPS — joined via STOP_ID; the live stop records from which the snapshot is taken.
• FTE_LOAD_TENDER (and related tender tables) — the tender header that owns LOAD_TENDER_NUMBER.
• WSH_TRIP_STOP_DETAILS — line-level detail supporting stop quantities.
• FTE_TENDER_SNAPSHOT_U1 — the unique index enforcing the composite business key.

These objects form the practical join path when validating tendered data against live transportation execution records.