Results for “fte_load_headers”

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

Overview

FTE_LOAD_HEADERS is the master header table within the Oracle E-Business Suite Transportation Execution (FTE) module. It stores the header-level description of a shipment, functioning as the central anchor record for all downstream transportation data associated with a given load. In Oracle EBS 12.1.1 and 12.2.2, this table captures the identifying and party-related attributes of a load, while its child tables hold the granular detail lines, charges, pricing attributes, and shipment-specific records that roll up to the same load identifier.

The ETRM metadata notes "Not implemented in this database" for DBA data, indicating that the table may be absent or unused in certain instance configurations, though the object remains part of the documented FTE data model.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is hub-leaning. This suggests FTE_LOAD_HEADERS can be modeled as a hub: a table holding a stable business identifier (LOAD_ID) with minimal descriptive attributes, while the many dependent tables behave as satellites or links radiating from that hub. Practitioners building a warehouse layer over FTE should consider this classification as a design suggestion rather than a normative model.

Key Information Stored

The primary key is defined by the constraint FTE_LOAD_HEADERS_PK, which enforces uniqueness on the LOAD_ID column. LOAD_ID is the surrogate and business key candidate for a shipment load and is the column propagated to every dependent child table. The most significant attributes documented include:

• LOAD_ID — The unique identifier for the load (primary key).
• SHIPPER_ID — Foreign key to HZ_PARTIES; identifies the party shipping the goods.
• CONSIGNEE_ID — Foreign key to HZ_PARTIES; identifies the party receiving the goods.

Because the ETRM excerpt is limited, it does not enumerate the full column set. Header-level attributes typical of this object (load name/number, status, carrier, dates, and modes) should be confirmed against the live data dictionary in the target instance. Where documented, only SHIPPER_ID and CONSIGNEE_ID appear as foreign keys referencing HZ_PARTIES, making them the principal business-meaningful references beyond the primary key.

Common Use Cases and Queries

Typical use cases involve listing loads by shipper or consignee, joining header data to shipment line detail, and reporting on transportation charges. A representative query resolving party names follows:

• Select load and consignee: SELECT lh.LOAD_ID, hp.PARTY_NAME FROM FTE_LOAD_HEADERS lh, HZ_PARTIES hp WHERE lh.CONSIGNEE_ID = hp.PARTY_ID;
• Aggregate detail per load: join FTE_LOAD_HEADERS to FTE_LOAD_DETAILS on LOAD_ID to summarize line items per shipment.
• Charge reporting: join to FTE_LOAD_CHARGES on LOAD_ID to report total charges by load.
• History analysis: join to FTE_LOAD_HISTORY on LOAD_ID to trace status changes.

Related Objects

FTE_LOAD_HEADERS is referenced by several dependent tables through the LOAD_ID foreign key, and it in turn references party data:

• HZ_PARTIES — Parent for SHIPPER_ID and CONSIGNEE_ID.
• FTE_LOAD_DETAILS — Child detail lines via LOAD_ID.
• FTE_LOAD_CHARGES — Charge records via LOAD_ID.
• FTE_LOAD_HISTORY — Historical/audit records via LOAD_ID.
• FTE_LOAD_PRC_ATTRIBUTES — Pricing attributes via LOAD_ID.
• FTE_PA_SHIP_DETAILS — Shipment details via LOAD_ID and SUB_LOAD_ID.

These relationships confirm FTE_LOAD_HEADERS as the hub of the FTE shipment model, with all transactional detail keyed to its LOAD_ID.