Results for “document_payable”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBY_EXT_FD_DOC_ERR_1_0_V is an Oracle E-Business Suite reporting view owned by the APPS schema, defined over the Payments (IBY) module tables that track payment document errors. Its purpose is to expose, in a single denormalised result set, the transaction errors associated with payable documents — payment instructions, payment processes, and related disbursement artifacts — together with the human-readable meanings of the error type and error status lookup codes. The view is part of the Oracle Payments external-facing "FD" (financial document) interface family, whose members are commonly consumed by integration extracts, notifications, and diagnostic reports that ship payment status back to source systems.

Because it resolves both the error type and error status against FND_LOOKUPS, the view removes the need for downstream code to perform lookup joins manually. This makes it particularly useful when payment failures must be surfaced to accounts payable users or to external banking interfaces in business language rather than as internal codes. The view is read-only and is not intended for direct DML.

Underlying Base Objects

The documented definition joins four objects:

• IBY_DOCS_PAYABLE_ALL (synonym over the IBY base table) — the driving table, supplying DOCUMENT_PAYABLE_ID, the primary key of a payable document.
• IBY_TRANSACTION_ERRORS (synonym) — the error fact table, joined on TRANSACTION_ID = DOCUMENT_PAYABLE_ID with TRANSACTION_TYPE constrained to the literal 'DOCUMENT_PAYABLE'.
• FND_LOOKUPS (view) — joined twice. One instance, aliased FND_ERR_TYPE_LOOKUP, supplies the MEANING for LOOKUP_TYPE = 'IBY_TRANSACTION_ERROR_TYPES'; the second, FND_ERR_ST_LOOKUP, is joined for LOOKUP_TYPE = 'IBY_TRANSACTION_ERROR_STATUSES'.
• FND_GLOBAL (package) — referenced in the documented base-object list, typically to provide session context such as ORG_ID or USER_ID when the view is invoked within a multi-org or security-enabled runtime.

Note the outer join (+) on the error-type lookup join: documents whose ERROR_TYPE has no matching lookup definition are still returned, with the type MEANING null. By contrast, the error-status lookup join is inner, so only statuses defined in IBY_TRANSACTION_ERROR_STATUSES are returned.

Key Columns

• DOCUMENT_PAYABLE_ID — identifier of the payable document; use this to link back to IBY_DOCS_PAYABLE_ALL for document-level attributes such as payment method, amount, and status.
• TRANSACTION_ERROR_ID — unique identifier of the individual error record in IBY_TRANSACTION_ERRORS.
• ERROR_TYPE — lookup code categorising the failure (for example, formatting, validation, or transmission errors).
• MEANING — the descriptive text resolved from FND_LOOKUPS for the error type; note that the view selects this column twice, so a consuming query should alias the duplicates or enumerate columns explicitly.
• ERROR_CODE — code returned by the originating process or external system.
• ERROR_MESSAGE — free-text diagnostic message.
• ERROR_DATE — timestamp the error was recorded.
• ERROR_STATUS — lookup code indicating whether the error is open, resolved, or otherwise dispositioned.

Common Use Cases and Queries

Typical uses include a Payment Errors dashboard, an AP troubleshooting report, and extract programs feeding a bank or middleware layer. The view also serves as a convenient source when reconciling documents that failed during payment processing.

SELECT e.DOCUMENT_PAYABLE_ID,
       d.PAYMENT_INSTRUCTION_ID,
       e.ERROR_TYPE,
       e.MEANING       AS ERROR_TYPE_MEANING,
       e.ERROR_CODE,
       e.ERROR_MESSAGE,
       e.ERROR_DATE,
       e.ERROR_STATUS
FROM   APPS.IBY_EXT_FD_DOC_ERR_1_0_V e,
       APPS.IBY_DOCS_PAYABLE_ALL d
WHERE  d.DOCUMENT_PAYABLE_ID = e.DOCUMENT_PAYABLE_ID
AND    e.DOCUMENT_PAYABLE_ID = :p_document_payable_id
ORDER  BY e.ERROR_DATE DESC;

A second pattern filters to currently open errors for a date range:

SELECT *
FROM   APPS.IBY_EXT_FD_DOC_ERR_1_0_V
WHERE  ERROR_STATUS = 'OPEN'
AND    ERROR_DATE >= TRUNC(SYSDATE) - 7;

Because the definition exposes both error fact rows and lookup meanings, queries against this view are well suited to read-only reporting and integration extraction, and should not be used for authoritative status updates, which remain the responsibility of the Oracle Payments error-handling APIs.