Search Results trxn_type_pmt

Overview

IBY_SINGPAY_PUB is a public PL/SQL package body in the Oracle Payments (IBY) module of Oracle E-Business Suite, shipped under the APPS schema. It implements the single payment creation flow, the process by which one or more documents payable are validated, grouped into a payment, and submitted through the payment system. The package body carries header version 120.31, consistent with the 12.1.1 code line and carried forward into 12.2.2.

Its primary responsibility is orchestration and state management. The body declares constant lists that drive the status transitions applied across the flow: document statuses such as VALIDATED, PAYMENTS_CREATED, FAILED_BY_CALLING_APP, FAILED_BY_RELATED_DOCUMENT, PAYMENT_FAILED_VALIDATION, and FAILED_BY_REJECTION_LEVEL; payment statuses such as REJECTED, FAILED_VALIDATION, CREATED, and FAILED_BY_REJECTION_LEVEL; payment request statuses such as PAYMENTS_CREATED, FAILED_PAYMENT_VALIDATION, PENDING_REVIEW, and PENDING_REVIEW_PMT_VAL_ERRORS. These constants ensure consistent status values across the flow and across calling applications.

The package also defines the supported rejection level system options: REJ_LVL_REQUEST ('REQUEST'), REJ_LVL_PAYMENT ('PAYMENT'), and REJ_LVL_NONE ('NONE'). The rejection level controls how a rejected payment is handled relative to the originating payment request, and the FAILED_BY_REJECTION_LEVEL status values are applied when a payment fails at the configured rejection level.

Key Procedures and Functions

The documented API surface comprises five procedures.

• CREATEPAYMENTS — The principal entry point for the single payment creation flow. It accepts the documents to be paid, performs validation, groups eligible documents into a payment, and persists the resulting payment and payment request records.
• PERFORMDBUPDATES — Applies the database changes associated with the creation flow, writing the document, payment, and payment request statuses determined during processing.
• INITIALIZEPMTS — Initialises the payment structures and working state required before creation processing begins.
• NEGATIVEPMTAMOUNTCHECK — Validates that a payment amount is not negative, returning an error condition when the check fails.
• PRINT_DEBUGINFO — Emits debugging information for the flow, used during diagnostics and troubleshooting.

Tables Accessed

The package reads and writes the core Payments tables through APPS synonyms:

• IBY_DOCS_PAYABLE_ALL — documents payable submitted for payment; statuses such as VALIDATED and PAYMENTS_CREATED are applied here.
• IBY_PAYMENTS_ALL — the payment records created and updated by the flow.
• IBY_PAY_SERVICE_REQUESTS — payment service requests, including the payment request statuses listed above.
• IBY_INTERNAL_PAYERS_ALL and IBY_EXTERNAL_PAYEES_ALL — payer and payee definitions used during validation and payment construction.
• IBY_TRANSACTION_ERRORS and IBY_TRXN_ERROR_TOKENS — error capture and tokenised error messages generated during validation and creation.
• PLITBLM — the PL/SQL table (index-by-table) utility used for in-memory collections.

Usage Notes

IBY_SINGPAY_PUB is invoked by the standard Oracle Payments payment creation flow rather than directly by end users. It is called from the Payments user interface and from the payment processing logic that drives single payment creation, including the handling of rejection levels configured in the system options. ETRM records no other packages referencing this package, indicating that it sits at the top of its calling hierarchy rather than being consumed internally by other APIs. Custom code integrating with Oracle Payments should call the documented procedures only, and must avoid direct updates to the status columns whose values are centralised here, since the rejection level and status constants in this body define the expected transitions across the flow.