Search Results retrieve_transaction_errors

Overview

IBY_DISBURSE_SINGLE_PMT_PKG is the core payments disbursement engine within the Oracle Payments (IBY) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It orchestrates the end-to-end processing of a single payment request, from initial insertion through document validation, payment instruction creation, formatting, and issuance. The package encapsulates the state machine that governs payment request status transitions (for example INSERTED, SUBMITTED, ASSIGNMENT_COMPLETE, DOCUMENTS_VALIDATED, PAYMENTS_CREATED) and payment status transitions (for example INSTRUCTION_CREATED, ISSUED, FORMATTED, FAILED_VALIDATION, VOID_BY_SETUP, VOID_BY_OVERFLOW). Because the payments flow involves multiple dependent steps that may fail independently, the package also provides diagnostic facilities for surfacing errors back to the calling process, which is where the RETRIEVE_TRANSACTION_ERRORS procedure is relevant.

Key Procedures and Functions

• SUBMIT_SINGLE_PAYMENT — The principal driver procedure. It initiates and coordinates processing of an individual payment request through the disbursement lifecycle, invoking the validation, creation, and instruction steps.
• INSERT_PAYREQ — Creates the initial payment request record that seeds the disbursement flow, establishing the request in its starting status before downstream processing begins.
• POPULATEOUTPARAMS — Populates output parameters returned to the caller, allowing the calling process to receive status, identifiers, or diagnostic information about the completed or failed operation.
• RETRIEVE_TRANSACTION_ERRORS — The procedure most commonly referenced in troubleshooting. It queries the transaction error repository to return errors associated with a given payment request or payment, distinguishing between error types by transaction type. The package declares constants for these types, including TRXN_TYPE_DOC ('DOCUMENT_PAYABLE') and TRXN_TYPE_PMT, indicating errors are segregated between document-level and payment-level failures. This is the standard mechanism for retrieving why a payment request or payment failed processing.
• PROVIDE_PMT_REFERENCE_NUM — Supplies the payment reference number associated with a payment, supporting reconciliation and downstream identification of disbursed payments.
• PRINT_DEBUGINFO — Emits debug information for diagnostic purposes, typically gated by debug settings, to aid developers and support personnel in tracing execution.

Tables Accessed

• IBY_PAYMENTS_ALL — The master payment record; updated as payment statuses advance through creation, issuance, and formatting.
• IBY_PAY_INSTRUCTIONS_ALL — Stores payment instructions; instructions are created with the CREATED status constant.
• IBY_DOCS_PAYABLE_ALL — Holds documents payable that are validated and bound to the payment request.
• IBY_TRANSACTION_ERRORS — The error repository read by RETRIEVE_TRANSACTION_ERRORS, keyed by transaction type.
• IBY_PAY_SERVICE_REQUESTS — Tracks service requests raised during processing, including retry scenarios such as RETRY_DOCUMENT_VALIDATION and RETRY_PAYMENT_CREATION.
• IBY_PROCESS_FUNCTIONS and IBY_PROCESS_ORGS — Resolve the applicable processing functions and organizational configuration governing the payment flow.
• IBY_PAYMENT_REFERENCES — Consulted or populated by PROVIDE_PMT_REFERENCE_NUM.
• IBY_USED_PAYMENT_DOCS and CE_PAYMENT_DOCUMENTS — Link payable documents to the resulting cash management payment documents.
• PLITBLM — The standard EBS PL/SQL table type used for bulk/array processing within the package.

Usage Notes

This package is invoked by the Oracle Payments disbursement infrastructure rather than by end users directly. The Payment Process Request (PPR) concurrent programs call into the single-payment logic as they process each request in a batch, and the payment creation and formatting concurrent programs drive the same routines across large volumes of payments. Direct invocation from custom code is uncommon but possible where a bespoke disbursement process must submit an individual payment or, more frequently, must retrieve the reasons a payment failed. In that troubleshooting context, RETRIEVE_TRANSACTION_ERRORS is the documented entry point: it reads IBY_TRANSACTION_ERRORS, filtered by the appropriate transaction type, to return document-payable and payment-level errors. Two other packages reference IBY_DISBURSE_SINGLE_PMT_PKG, confirming its role as a shared lower-level component. Because the header reflects a 12.1.1-era build (120.55.12010000.2), behavior is consistent across 12.1.1 and 12.2.2, with the principal differences in the 12.2 line residing in the surrounding payments architecture rather than in this disbursement routine.