Search Results get_payreq_status

Overview

IBY_DISBURSE_SUBMIT_PUB_PKG is the public PL/SQL package body that drives the Oracle Payments (IBY) disbursement submission process in Oracle E-Business Suite 12.1.1 and 12.2.2. It is the orchestration layer that accepts a payment process request (PPR), validates and prepares the underlying documents payable, creates payment instructions, and submits the request to the payment engine for actual disbursement. The header revision (ibybildb.pls 120.79) confirms this is the shipping, production version of the package shipped with the Payments product family.

The package is classified as an "OTHER" API type under the APPS schema. It exposes a narrow public surface, with internal helper routines that operate on payment request statuses such as INSERTED, SUBMITTED, ASSIGNMENT_COMPLETE, DOCUMENTS_VALIDATED, PAYMENTS_CREATED, and PENDING_REVIEW. These constants reflect the state machine that governs a disbursement request from initial insertion through payment creation. The delete_docspaytab entry that prompted this search corresponds to the DELETE_DOCSPAYTAB procedure, which clears the document/payable association staging area during reprocessing or cleanup.

Key Procedures and Functions

The 23 documented routines fall into several functional groups:

• SUBMIT_PAYMENT_PROCESS_REQUEST — the primary entry point that kicks off the disbursement workflow for a payment process request, transitioning statuses from INSERTED/SUBMITTED toward payment creation.
• DELETE_DOCSPAYTAB — removes or clears the DOCS_PAYABLE staging rows associated with a payment request, supporting retry and revalidation scenarios.
• GET_PAYREQ_LIST, GET_PAYREQ_STATUS — retrieval routines that return the list of payables for a request and the current request status.
• INSERT_PAYREQ, GETNEXTPAYREQID — insert the payment request row and obtain the next sequence identifier.
• INSERT_PAYREQ_DOCUMENTS, GETNEXTDOCUMENTPAYABLEID, GETNEXTDOCUMENTPAYABLELINEID — populate the documents payable and document lines, generating next IDs for both headers and lines.
• CHECKIFDUPLICATE — performs duplicate detection on payable documents.
• DERIVEPAYEEIDFROMCONTEXT, DERIVEEXACTPAYEEIDFROMCONTEXT — derive payee identifiers from the submission context.
• DERIVEDISTINCTACCESSTYPSFORREQ, INSERTDISTINCTACCESSTYPSFORREQ — derive and persist the distinct access types applicable to a request.
• SET_PROFILE_ATTRIBS, GET_PROFILE_PROCESS_ATTRIBS, CHECKIFDEFAULTPMTDOCONPROFILE — manage payment profile attributes and determine whether a default payment document exists on the profile.
• CHECKIFPMTSINMODIFIEDSTATUS, CHECKIFPMTSINMODBANKACCSTATUS — status-check helpers that detect payments in MODIFIED or MODIFIED_PAYEE_BANK_ACCOUNT conditions.
• PRINT_DEBUGINFO — diagnostic output routine used during troubleshooting.

Tables Accessed

The package reads and writes the core Payments staging and reference tables:

• IBY_DOCS_PAYABLE_ALL, IBY_GEN_DOCS_PAYABLE, IBY_DOCUMENT_LINES (and their _S synonyms) — the documents payable header and line records that represent each payment being disbursed.
• IBY_PAY_SERVICE_REQUESTS — the payment service request record that tracks submission status.
• IBY_PMT_CREATION_RULES — determines how payments are grouped and created from documents.
• IBY_EXTERNAL_PAYEES_ALL — the payee master used to resolve derivation logic.
• IBY_PAYMENT_METHODS_B, IBY_SYS_PMT_PROFILES_B, IBY_PROCESS_ORGS, IBY_PROCESS_FUNCTIONS — configuration and process-definition tables.
• CE_BANK_ACCOUNTS, CE_PAYMENT_DOCUMENTS — cash management references for bank accounts and payment documents.
• FND_APPLICATION — application reference lookup.

Usage Notes

This package is invoked internally by the Oracle Payments disbursement framework rather than called directly by users. It is referenced by six other packages, which call SUBMIT_PAYMENT_PROCESS_REQUEST when a payment process request is submitted from the Payments Dashboard, the Payment Process Requests form, or a scheduled concurrent program. Custom code and extensions should invoke the public routines only as documented, and should not attempt to manipulate the IBY staging tables directly, since status transitions are tightly coupled to the submission workflow. The DELETE_DOCSPAYTAB and duplicate-check routines are commonly exercised during retry of failed validation or payment creation, making them useful touchpoints when diagnosing reprocessing issues in 12.1.1 and 12.2.2.