Search Results fte_failure_reasons_u1

Overview

The FTE.FTE_FAILURE_REASONS table is a transactional data store within the Oracle E-Business Suite Freight and Transportation Execution (FTE) module. In Oracle EBS 12.1.1 and 12.2.2, this table records the reasons associated with failure processing for FPA (Freight Payment and Audit). Each row captures a discrete failure event tied to an invoice rejection, preserving the diagnostic context needed to understand why a freight invoice or line could not be processed successfully.

The object resides in the FTE schema, is documented as VALID, and is registered in FND Design Data as FTE.FTE_FAILURE_REASONS. Its physical storage is allocated to the APPS_TS_TX_DATA tablespace with a PCT Free of 10, while its indexes reside in APPS_TS_TX_IDX. Under the heuristic Data Vault classification mined from the foreign-key structure, this table is best modeled as a link object: it connects a parent entity (referenced through PARENT_ID) to an invoice rejection, functioning as an associative relationship that resolves many-to-many style associations between rejections and their originating records.

Key Information Stored

The table contains eleven documented columns. The most significant are summarized below, with the surrogate primary key distinguished from the business-key candidate.

• INVOICE_REJECT_ID (NUMBER) — The surrogate primary key, enforced by the primary key constraint FTE_FAILUER_REASONS_PK. It also carries the unique index FTE_FAILURE_REASONS_U1, making it the principal business-key candidate for uniquely identifying a failure record.
• PARENT_NAME (VARCHAR2(30)) — Stores the name of the parent entity, derived from PARENT_ID.
• PARENT_ID (NUMBER) — Holds the identifier of the parent record and acts as the linking foreign key. The metadata documents references toward FTE_INVOICE_LINES.
• BOL (VARCHAR2(30)) — The Bill of Lading number associated with the failed transaction; indexed by FTE_FAILURE_REASONS_N2.
• FAILURE_TYPE (VARCHAR2(30)) — Categorizes the nature of the failure.
• FAILURE_REASON (VARCHAR2(30)) — Provides the descriptive reason for the failure event.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard EBS "WHO" audit columns that track record creation and modification history.

The PARENT_ID column is additionally served by the non-unique index FTE_FAILURE_REASONS_N1, supporting efficient lookups by parent reference.

Common Use Cases and Queries

Typical scenarios include diagnosing freight payment audit failures, reconciling rejected invoices against their originating invoice lines, and building exception reports for logistics operations. A common query retrieves failures for a specific invoice line:

• SELECT INVOICE_REJECT_ID, PARENT_NAME, BOL, FAILURE_TYPE, FAILURE_REASON FROM FTE.FTE_FAILURE_REASONS WHERE PARENT_ID = :parent_id;
• Tracing failures by Bill of Lading: WHERE BOL = :bol;
• Aggregating failure frequency: SELECT FAILURE_TYPE, FAILURE_REASON, COUNT(*) FROM FTE.FTE_FAILURE_REASONS GROUP BY FAILURE_TYPE, FAILURE_REASON;

Because the table is indexed by INVOICE_REJECT_ID, PARENT_ID, and BOL, these access paths are efficient for both online diagnostics and batch reporting.

Related Objects

The relationship data identifies the most significant dependencies:

• FTE.FTE_INVOICE_LINES — Referenced via PARENT_ID; the principal parent table for failure records.
• FTE.FTE_FAILURE_REASONS itself is exposed through the APPS synonym APPS.FTE_FAILURE_REASONS, which applications and reports query.
• Constraint FTE_FAILUER_REASONS_PK and unique index FTE_FAILURE_REASONS_U1 govern integrity on INVOICE_REJECT_ID.
• Supporting indexes FTE_FAILURE_REASONS_N1 (PARENT_ID) and FTE_FAILURE_REASONS_N2 (BOL) optimize access.

The table does not reference any other database object directly beyond the PARENT_ID linkage, and it is referenced by the APPS synonym layer. These relationships position it as a focused diagnostic store within the FTE freight payment audit flow.