Results for “fte_shipment_status_headers”

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

Overview

The FTE_SHIPMENT_STATUS_HEADERS table is a core operational data object within the FTE (Transportation Execution) module of Oracle E-Business Suite, available in both release 12.1.1 and 12.2.2. According to the ETRM documentation, this table holds the main body of the ShowShipment message. In practical terms, it serves as the primary repository for shipment status header information exchanged with carriers, third-party logistics providers, and trading partners through the transportation execution integration framework. Each row represents a discrete shipment status header record, capturing the physical, temporal, and documentary attributes of a shipment movement as it progresses through the logistics lifecycle.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign key structure indicates that this object is standalone. This suggests a modeling recommendation to treat FTE_SHIPMENT_STATUS_HEADERS as a self-contained entity rather than as a dependent satellite or an associative link. The absence of parent-child FK dependencies within the FTE schema reinforces its role as a message-level staging and persistence structure for inbound or outbound shipment status communication.

Key Information Stored

The table contains seventy-eight documented columns. The surrogate primary key is SHIPMENT_STATUS_ID, enforced by the unique index FTE_SHIPMENT_STATUS_HEADERS_U1 and the constraint FTE_SHIPMENT_STATUS_HEADERS_PK. This column uniquely identifies each shipment status header record and is the business-key candidate for the table.

• DELIVERY_ID and DELIVERY_LEG_ID — link the header to a specific delivery and its leg within Oracle Shipping Execution.
• CONTAINER_ID — references the packed container associated with the shipment, joined to WSH_PACKED_CONTAINERS.
• MESSAGE_TYPE and STATUS — identify the nature of the ShowShipment message and its current processing state.
• CARRIER_NAME, TRACKING_ID, TRACKING_ID_TYPE, and BILL_OF_LADING — capture carrier identification and consignment tracking references.
• GENERATION_DATE, SHIPPED_DATE, ARRIVAL_DATE, ESTIMATED_ARRIVAL_DATE, and ESTIMATED_DEPARTURE_DATE — provide the temporal backbone for shipment milestone tracking.
• SHIP_UNIT_QUANTITY, VOLUME, and WEIGHT (with their respective UOM columns) — hold quantitative shipment measures.
• ROUTE_ID and ROUTE_TYPE — identify the routing plan associated with the movement.
• WF_ITEM_KEY — associates the record with an Oracle Workflow process instance for status-driven notifications.
• ACTIVITY_ID and TRANSACTION_ID — correlate the header with execution transactions and activities.
• Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE track row-level change history.

Common Use Cases and Queries

Reporting and integration teams commonly query this table to reconcile shipment status messages against delivery legs and packed containers. A typical join retrieves shipment tracking details for a given delivery:

• SELECT h.tracking_id, h.carrier_name, h.status, h.estimated_arrival_date FROM fte.fte_shipment_status_headers h WHERE h.delivery_leg_id = :leg_id;
• Joining to WSH_DELIVERY_LEGS on DELIVERY_LEG_ID to enrich shipment status with delivery leg attributes.
• Joining to WSH_PACKED_CONTAINERS on CONTAINER_ID to identify container-level shipment contents.
• Aggregating SHIP_UNIT_QUANTITY, VOLUME, and WEIGHT by CARRIER_NAME or ROUTE_ID for freight spend and capacity analysis.
• Filtering on GENERATION_DATE or STATUS to monitor inbound message processing backlogs.

Related Objects

The principal related objects, derived from documented foreign key relationships, are:

• WSH_DELIVERY_LEGS — referenced through DELIVERY_LEG_ID; provides the delivery leg context for each shipment status header.
• WSH_PACKED_CONTAINERS — referenced through CONTAINER_ID; supplies container and packing detail.
• WSH_DELIVERIES — logically related through DELIVERY_ID for delivery-level reporting, although the direct FK documented is to the delivery leg.
• WF_ITEM_KEY / Oracle Workflow — the workflow item key column links the header to workflow processes driving shipment event actions.
• FTE_SHIPMENT_STATUS_HEADERS_PK / _U1 — the primary key and unique index constraints defined on SHIPMENT_STATUS_ID that enforce record uniqueness.

Together, these relationships establish FTE_SHIPMENT_STATUS_HEADERS as the central header store for ShowShipment messaging, linking transportation execution events to Oracle Shipping Execution delivery and container structures.