Search Results fte_invoice_headers_pk

Overview

FTE.FTE_INVOICE_HEADERS is a Transportation Execution (FTE) table that stores invoice header information for freight and carrier billing within Oracle E-Business Suite. In ETRM 12.1.1 and 12.2.2, it functions as the master record for each transportation invoice, capturing the billing party, shipment context, route details, and monetary totals that downstream payables and settlement processes rely upon. It is owned by the FTE schema and is marked VALID.

The ETRM metadata classifies this object heuristically as standalone under its Data Vault model. In practice, that classification suggests the table behaves as a self-contained record with no upstream foreign-key dependency, but it still acts as a parent for detail lines. Its documented physical schema in 12.2.2 exposes 55 columns, and the primary key constraint FTE_INVOICE_HEADERS_PK is defined on INVOICE_HEADER_ID.

Key Information Stored

The table centers on the surrogate primary key INVOICE_HEADER_ID, which uniquely identifies each invoice header and is referenced by child line records. Business context is provided primarily by the bill and carrier attributes, including BILL_NUMBER, BILL_DATE, BILL_TYPE, BILL_STATUS, BILL_REF, and BOL (bill of lading). The parties involved are captured through CARRIER_ID, CARRIER_NAME, SUPPLIER_ID, SUPPLIER_SITE_ID, and SCAC_CODE.

Route and movement details are stored using PICKUP_DATE, PICKUP_LOCATION_ID, DROPOFF_DATE, and DROPOFF_LOCATION_ID, supplemented by address components such as PICKUP_LOC_CITY, DROPOFF_LOC_CITY, and their related postal fields. Transportation characteristics are held in MODE_OF_TRANSPORT, VEHICLE_TYPE, LOADED_DISTANCE with LOADED_DISTANCE_UOM, UNLOADED_DISTANCE, and BILLED_TIME.

Financial amounts are recorded in TOTAL_AMOUNT, APPROVED_AMOUNT, and CURRENCY_CODE. Multi-organization security is enforced through ORG_ID, and the accounting linkage is provided by DISTRIBUTION_ACCOUNT_ID. Standard audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE are also present. The metadata documents only the surrogate key; no separate business-key unique index is identified.

Common Use Cases and Queries

Typical reporting scenarios include carrier spend analysis, freight invoice aging, and reconciliation of billed versus approved amounts. A common query pattern retrieves header records for a specific carrier and status:

• SELECT INVOICE_HEADER_ID, BILL_NUMBER, BILL_DATE, BILL_STATUS, TOTAL_AMOUNT, APPROVED_AMOUNT FROM FTE.FTE_INVOICE_HEADERS WHERE CARRIER_ID = :p_carrier AND BILL_STATUS = :p_status ORDER BY BILL_DATE DESC;
• SELECT INVOICE_HEADER_ID, BILL_NUMBER, TOTAL_AMOUNT, CURRENCY_CODE FROM FTE.FTE_INVOICE_HEADERS WHERE ORG_ID = :p_org AND TRUNC(BILL_DATE) BETWEEN :p_start AND :p_end;

These queries support invoice detail drill-down when joined to FTE_INVOICE_LINES on INVOICE_HEADER_ID, enabling amount comparison between header totals and summed line values.

Related Objects

The most significant dependent object is FTE_INVOICE_LINES, which references this table through the foreign key FTE_INVOICE_LINES.INVOICE_HEADER_ID → FTE_INVOICE_HEADERS.INVOICE_HEADER_ID. This one-to-many relationship allows a single invoice header to carry multiple charge lines. Additional related objects include the carrier and supplier master tables referenced indirectly through CARRIER_ID, SUPPLIER_ID, and SUPPLIER_SITE_ID, as well as general ledger distribution references tied to DISTRIBUTION_ACCOUNT_ID. Reporting views over FTE invoice data typically join the header to its lines and to supplier and carrier lookups to produce complete freight settlement reports.