Search Results fte_invoice_lines_n3

Overview

FTE.FTE_INVOICE_LINES is a transactional table in the Oracle E-Business Suite transportation and freight payment (FTE/ETRM) schema. It stores the line-level detail of freight invoices, capturing rating, discount, surcharge, weight, volume, and approved-amount information for each charge appearing on an invoice header. The table occupies the APPS_TS_TX_DATA tablespace with PCTFREE 10, confirming its role as an active transactional data store rather than a reference or setup entity. In Oracle EBS 12.1.1 and 12.2.2 the table is registered under FND Design Data as FTE.FTE_INVOICE_LINES and carries VALID status in the ETRM dictionary.

The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. Under this modeling suggestion, INVOICE_LINE_ID functions as the hub business key at line grain, while the descriptive rating, discount, surcharge, and measurement attributes (RATE_AMOUNT, TOTAL_WEIGHT, DISCOUNT_AMOUNT, and similar) would behave as satellite attributes. The single foreign key to FTE_INVOICE_HEADERS supplies the associational link back to the invoice header hub.

Key Information Stored

The table contains 30 documented columns. The most significant are:

• INVOICE_LINE_ID — Numeric surrogate primary key of the line record, enforced by the unique index FTE_INVOICE_LINES_U1 and the primary key constraint FTE_INVOICE_LINES_PK. This is the join key used by every dependent object.
• INVOICE_HEADER_ID — Foreign key to FTE_INVOICE_HEADERS, tying the line to its parent invoice.
• INVOICE_LINE_NUM — Business-facing line sequence number (VARCHAR2(30)); indexed non-uniquely by FTE_INVOICE_LINES_N2.
• INVOICE_LINE_TYPE — Classification of the line charge (for example freight, accessorial, or discount); indexed by FTE_INVOICE_LINES_N3.
• LADING_QUANTITY, LADING_UNIT — Shipped quantity and its unit of measure. The metadata does not identify INVOICE_LINE_NUM or any other column as a unique business key beyond the surrogate key.
• DESCRIPTION — Free-text description of the line, up to 1000 characters.
• FREIGHT_CLASS — Freight classification code used for rating.
• TOTAL_WEIGHT / WEIGHT_UOM, TOTAL_VOLUME / VOLUME_UOM — Weight and volume bases with their units.
• RATE_AMOUNT / RATE_TYPE / RATE_BASIS / RATE_BASIS_UOM — The rate charged and the basis on which it was applied.
• DISCOUNT_AMOUNT / DISCOUNT_TYPE / DISCOUNT_UOM / DISCOUNT_DISC — Discount applied at line level and its description.
• SURCHARGE_AMOUNT / SURCHARGE_TYPE / SURCHARGE_UOM / SURCHARGE_DISC — Surcharge applied at line level and its description.
• APPROVED_AMOUNT — The approved payable amount for the line.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns.

Common Use Cases and Queries

Typical reporting scenarios include reconciling approved freight charges to invoice headers, analyzing accessorial spend by INVOICE_LINE_TYPE, and tracing a payable line to its downstream accounting distribution. Because INVOICE_LINE_ID is the unique access path, most queries filter or join on it.

• Retrieve all lines for a header: SELECT * FROM FTE.FTE_INVOICE_LINES WHERE INVOICE_HEADER_ID = :header_id;
• Look up a single line by surrogate key: SELECT * FROM FTE.FTE_INVOICE_LINES WHERE INVOICE_LINE_ID = :line_id;
• Aggregate approved spend by line type: SELECT INVOICE_LINE_TYPE, SUM(APPROVED_AMOUNT) FROM FTE.FTE_INVOICE_LINES GROUP BY INVOICE_LINE_TYPE;
• Join to the header for header-level context: SELECT l.INVOICE_LINE_NUM, l.APPROVED_AMOUNT, h.* FROM FTE.FTE_INVOICE_LINES l, FTE.FTE_INVOICE_HEADERS h WHERE l.INVOICE_HEADER_ID = h.INVOICE_HEADER_ID;

Search terms such as "fte_invoice_lines_u1" indicate the user is targeting the unique index on INVOICE_LINE_ID, which is the correct access path for point lookups. Because the column is unique, queries using it return at most one row.

Related Objects

The table participates in a hub-and-spoke relationship pattern. FTE_INVOICE_HEADERS is the parent referenced via INVOICE_HEADER_ID. Numerous downstream objects reference INVOICE_LINE_ID and provide linkage into accounting, receivables, and lease subsystems:

• FV_IPAC_IMPORT / FV_IPAC_IMPORT_HISTORY — IPAC import staging, joined on INVOICE_LINE_ID.
• FII_AR_REVENUE_B / FII_AR_REVENUE_STG — Receivables revenue tables, joined on INVOICE_LINE_ID.
• FII_AR_TRX_DIST_F / FII_AR_TRX_DIST_FSTG / FII_AR_TRX_DIST_F_DLOG — Receivables transaction distribution and its staging shadow, joined on INVOICE_LINE_ID.
• AP_EXPENSE_FEED_DISTS_ALL — Payables expense distribution feed, joined on INVOICE_LINE_ID.
• AP_PPA_INVOICE_LINES_GT / AP_INVOICE_LINES_INTERFACE — Payables invoice line interface and global temporary tables referencing the line.
• FA_LEASE_PAYMENT_ITEMS — Fixed assets lease payment items, joined on INVOICE_LINE_ID.
• OKL_XTL_PAY_INVS_ALL_B — Lease payment invoices, referencing the line.
• FTE_FAILURE_REASONS — References this table via PARENT_ID and records failure reasons associated with an invoice line.

The breadth of dependent objects demonstrates that FTE_INVOICE_LINES is the central transactional record through which freight charges are conveyed into Oracle Payables, Receivables, and Fixed Assets processes.