Search Results document_payable

Overview

The view IBY_EXT_FD_DOC_ERR_1_0_V is a reporting and integration object owned by the APPS schema within the Oracle Payments (IBY) module. It presents transaction-level error information associated with payable documents, exposing both the raw error attributes and their decoded lookup meanings. The view is intended to support external-facing diagnostics, error dashboards, and integration reconciliation scenarios where consumers need to understand why a payable document failed processing.

Because the object follows the extensible external-facing naming convention (the _1_0_V suffix), it functions as a versioned interface view. It shields callers from the underlying transactional schema while exposing a stable, decoded representation of payment document errors. This is particularly relevant to users searching for document_payable, as the central key column DOCUMENT_PAYABLE_ID links the error records directly to payable documents. The view is valid in both 12.1.1 and 12.2.2, and its definition relies on standard Oracle Payments base objects.

Underlying Base Objects

The view is defined over several documented objects, joined to produce a decoded error listing:

• IBY_DOCS_PAYABLE_ALL (synonym) — the payable documents table, aliased as DOC. It supplies the DOCUMENT_PAYABLE_ID.
• IBY_TRANSACTION_ERRORS (synonym) — the error transaction table, aliased as ERR. It provides error type, code, message, date, and status, filtered to TRANSACTION_TYPE = 'DOCUMENT_PAYABLE'.
• FND_LOOKUPS (view) — joined twice. FND_ERR_TYPE_LOOKUP decodes the error type against the IBY_TRANSACTION_ERROR_TYPES lookup type; FND_ERR_ST_LOOKUP decodes the error status against IBY_TRANSACTION_ERROR_STATUSES.
• FND_GLOBAL (package) — a standard Oracle Application Object Library dependency used within the IBY environment for context resolution.

The join between DOC and ERR is driven by DOC.DOCUMENT_PAYABLE_ID = ERR.TRANSACTION_ID, ensuring each returned row ties a document error to its parent payable document. The error type lookup is an outer join ((+)), so errors with unrecognized type codes are still returned, while the error status lookup is an inner join.

Key Columns

The view exposes the following columns, which constitute the diagnostic payload:

• DOCUMENT_PAYABLE_ID — the identifier of the payable document; the linking key for consumers searching on document_payable.
• TRANSACTION_ERROR_ID — the unique identifier of the error transaction record.
• ERROR_TYPE — the raw error type lookup code.
• ERROR_TYPE_MEANING — the decoded meaning of the error type from IBY_TRANSACTION_ERROR_TYPES.
• ERROR_CODE — the specific code identifying the error condition.
• ERROR_MESSAGE — the human-readable description of the failure.
• ERROR_DATE — the timestamp at which the error was recorded.
• ERROR_STATUS — the raw status lookup code.
• ERROR_STATUS_MEANING — the decoded status meaning from IBY_TRANSACTION_ERROR_STATUSES.

Common Use Cases and Queries

Typical scenarios include diagnosing failed payable documents, building exception reports, and feeding error records to external reconciliation systems. A straightforward query retrieving all errors for a given document is:

SELECT document_payable_id, error_type_meaning, error_code, error_message, error_date, error_status_meaning FROM apps.iby_ext_fd_doc_err_1_0_v WHERE document_payable_id = :p_document_payable_id;

To list open errors by status, the decoded status column supports filtering:

SELECT document_payable_id, error_message, error_date FROM apps.iby_ext_fd_doc_err_1_0_v WHERE error_status_meaning = 'OPEN' ORDER BY error_date DESC;

Because the view already joins the lookup tables, no additional decoding is required by the caller, making it well suited to operational dashboards and integration extracts referencing the document payable identifier.