Search Results fte_failure_reasons




Overview
Explore in AI Chat

Overview

FTE_FAILURE_REASONS is a Transportation Execution (FTE) module table in Oracle E-Busness Suite Release 12.1.1 and 12.2.2, owned by the FTE schema and documented with VALID status in the ETRM repository. Its stated purpose is to store failure reasons associated with FPA (Freight Payment and Audit) processing. When freight invoices, bills of lading, or related transportation documents fail automated validation, matching, or audit rules, the system records the failure detail in this table so that exceptions can be reviewed, categorized, and resolved by transportation or payables personnel.

The object is physically documented in the 12.2.2 schema with 11 columns and a primary key constraint named FTE_FAILUER_REASONS_PK (the spelling reflects the delivered constraint name) built on INVOICE_REJECT_ID. A unique index, FTE_FAILURE_REASONS_U1, also exists on INVOICE_REJECT_ID, making that column both the surrogate primary key and the single documented business-key candidate. The ETRM metadata additionally exposes a self-referencing foreign key on PARENT_ID, indicating a hierarchical structure in which failure reason rows may be nested beneath a parent row. Where the metadata provides a heuristic Data Vault classification, this table is best modeled as a link, since it exists to associate invoice lines with their failure conditions rather than functioning as a standalone reference hub or a pure descriptive satellite.

Key Information Stored

The table centers on the identity and description of each recorded failure:

  • INVOICE_REJECT_ID — the surrogate primary key and sole documented unique business-key candidate; uniquely identifies each failure reason record.
  • PARENT_ID — self-referencing foreign key that supports hierarchical grouping of failure reasons and also participates in the relationship to FTE_INVOICE_LINES.
  • PARENT_NAME — descriptive label for the parent grouping, useful for reporting without a recursive join.
  • BOL — the bill of lading reference associated with the failing transaction, linking the exception to the physical shipment.
  • FAILURE_TYPE — the category or classification of the failure, supporting grouping and trend analysis.
  • FAILURE_REASON — the textual explanation of why the invoice or document failed validation.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording row creation and modification.

Common Use Cases and Queries

Typical scenarios include freight payment exception reporting, root-cause analysis of recurring invoice rejections, and reconciliation dashboards for transportation audit teams. A basic lookup of failures for a given invoice line pattern follows:

  • SELECT INVOICE_REJECT_ID, BOL, FAILURE_TYPE, FAILURE_REASON FROM FTE.FTE_FAILURE_REASONS WHERE CREATION_DATE >= :start_date;
  • SELECT FAILURE_TYPE, COUNT(*) FROM FTE.FTE_FAILURE_REASONS GROUP BY FAILURE_TYPE ORDER BY 2 DESC;
  • SELECT r.INVOICE_REJECT_ID, r.FAILURE_REASON, p.PARENT_NAME FROM FTE.FTE_FAILURE_REASONS r, FTE.FTE_FAILURE_REASONS p WHERE r.PARENT_ID = p.INVOICE_REJECT_ID;

Because no invoice number column is documented, joins to FTE_INVOICE_LINES are required to attribute a failure to a specific line and supplier invoice.

Related Objects

The primary relationships documented in the ETRM metadata are:

  • FTE_INVOICE_LINES — referenced via FTE_FAILURE_REASONS.PARENT_ID; the principal link between failure reasons and freight invoice lines.
  • FTE_FAILURE_REASONS (self-reference) — PARENT_ID points back to the table's own INVOICE_REJECT_ID, enabling hierarchical failure explanation.
  • The FTE_INVOICE_HEADERS family and the FPA (Freight Payment and Audit) concurrent programs consume this table when generating exception reports and rejection summaries.

DBA activities should account for the FTE_FAILURE_REASONS_PK and FTE_FAILURE_REASONS_U1 indexes when planning maintenance or gathering statistics.