Search Results fte_failure_reasons_s

Overview

FTE_FPA_UTIL is a utility package body in the APPS schema that supports the Oracle E-Business Suite Freight and Payment Analysis (FPA) subsystem, part of the Oracle Transportation Management / Landed Cost and Freight functionality delivered through the FTE module. The package encapsulates reusable PL/SQL logic that bridges Oracle Payables invoice and payment data with Oracle Shipping freight cost data, allowing the application to determine how freight charges should be allocated, paid, and reconciled against supplier invoices. Because it is classified as a UTIL package, it is not an externally callable business API but rather an internal helper layer invoked by other FTE packages and concurrent programs. The package body is documented as VALID in both 12.1.1 and 12.2.2, and ETRM records that it is referenced by one other APPS package while depending on a broad set of Payables, Shipping, General Ledger, and Workflow objects.

Key Procedures and Functions

The package exposes seven documented routines, each performing a discrete utility task:

• GET_PAYMENT_METHOD — Resolves the payment method associated with a supplier or invoice so that freight liabilities can be settled correctly through Payables.
• CALCULATE_PO_FREIGHT — Computes freight charges associated with purchase order receipt transactions, drawing on receipt charge data maintained in the shipping and purchasing tables.
• GET_LEGAL_ENTITY — Determines the legal entity (via HR organization information and GL sets of books) that owns the transaction, which is essential for accounting and intercompany treatment.
• UPDATE_STATUS — Updates the processing status of an FTE record, typically after successful or failed freight allocation or invoice matching.
• GET_FRACCT_CCID — Returns the Flexfield Accounting (FRACCT) code combination identifier used to build the accounting entry for a freight transaction.
• LOG_FAILURE_REASON — Records an error or exception against the FTE failure reason tables, providing the audit trail used by support and reconciliation reports.
• START_FRACCT_WF_PROCESS — Initiates the Workflow process responsible for generating freight accounting entries, submitting the request through the Workflow engine and directory services.

Tables Accessed

FTE_FPA_UTIL reads and writes a cross-functional set of tables. On the Payables side it references AP_CHECKS_ALL, AP_INVOICES_ALL, and AP_INVOICE_PAYMENTS_ALL to obtain payment, invoice, and disbursement context. On the FTE side it manipulates FTE_INVOICE_HEADERS, FTE_INVOICE_LINES, FTE_FAILURE_REASONS, and FTE_FAILURE_REASONS_S, the latter being the synonym the user searched for and the object that stores failure reason definitions and translations. Freight and shipping data come from WSH_FREIGHT_COSTS, WSH_FREIGHT_COST_TYPES, WSH_CARRIERS, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS, WSH_DELIVERY_LEGS, WSH_TRIPS, WSH_TRIP_STOPS, and WSH_SHIPPING_PARAMETERS. Purchase order receipt charges are read from PO_RCV_CHARGES and PO_CHARGES_GRP, while item categorization derives from MTL_ITEM_CATEGORIES, MTL_CATEGORIES_KFV, and MTL_CATEGORY_SETS. Supplier data is sourced from PO_VENDORS and PO_VENDOR_SITES_ALL, and organizational context from HR_ORGANIZATION_INFORMATION. Currency conversion and accounting use GL_CURRENCY_API and GL_SETS_OF_BOOKS.

Usage Notes

FTE_FPA_UTIL is invoked internally rather than called directly by end users. Typical entry points include the FTE invoice and freight reconciliation concurrent programs, Payables invoice validation workflows that must resolve freight liabilities, and the freight accounting Workflow initiated through START_FRACCT_WF_PROCESS. Because the package depends on Workflow (WF_CORE, WF_ENGINE, WF_ITEM, WF_DIRECTORY), FND_API, FND_MSG_PUB, and FND_GLOBAL, it inherits the standard EBS error-handling and multi-org conventions of those components. Customizations that attempt to call these routines directly should account for the fact that the package is not designed as a public API, has no documented inbound parameters in ETRM, and may change between point releases. Support and reconciliation queries against FTE_FAILURE_REASONS and its translated synonym FTE_FAILURE_REASONS_S provide visibility into failures logged by LOG_FAILURE_REASON.