Search Results fte_load_headers




Overview
Explore in AI Chat

Overview

The FTE_LOAD_HEADERS table is a core data object within the Oracle E-Business Suite Transportation Execution (FTE) module. It serves as the primary repository for the header-level description of a shipment or load, acting as the master record for a consolidated freight unit. This table is fundamental to the shipment lifecycle, providing the overarching structure to which all associated details, charges, and history are linked. Its role is to define the key parties, dates, and statuses of a transportation load, enabling comprehensive freight management, planning, and execution processes.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the documented foreign key relationships and primary key structure reveal the critical data entities stored. The primary identifier is the LOAD_ID. The table centrally stores references to key business entities involved in the shipment, notably the SHIPPER_ID and CONSIGNEE_ID, which are foreign keys to the HZ_PARTIES table in the Trading Community Architecture. This links the load to standardized party records. Other essential data points typically housed in this header include load creation date, status, planned and actual shipment dates, service level, and references to associated freight documents or trip information.

Common Use Cases and Queries

This table is central to queries that provide a summary view of shipments. Common reporting use cases include tracking load status, analyzing shipper and consignee activity, and auditing shipment timelines. A typical query would join FTE_LOAD_HEADERS with HZ_PARTIES to retrieve party names and with detail tables for a complete view. For example, to list all loads for a specific shipper:

Another critical use case is integrity validation, ensuring detail records exist for each header, or tracing the financial and operational history of a specific LOAD_ID through its related tables.

Related Objects

The FTE_LOAD_HEADERS table has a central, parent relationship with numerous operational and transactional tables in the FTE schema, as defined by its foreign keys. Key child tables include:

Its primary dependency on the master HZ_PARTIES table for shipper and consignee information underscores its integration with the enterprise's unified party model.