Search Results rej_lvl_payee




Overview
Explore in AI Chat

Overview

IBY_VALIDATIONSETS_PUB is the public validation engine for Oracle Payments (IBY) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its central purpose is to apply configurable validation sets against payment documents, payment instructions, and payments before those documents are released to payment processing. The package implements the document validation flow that takes a payment request from a state of READY_FOR_VALIDATION through validation, and either marks the associated documents VALIDATED or rejects them as REJECTED, FAILED_VALIDATION, FAILED_BY_RELATED_DOCUMENT, FAILED_BY_REJECTION_LEVEL, or FAILED_BY_CALLING_APP.

The package exposes user-visible rejection-level behavior through the constants REJ_LVL_REQUEST, REJ_LVL_DOCUMENT, REJ_LVL_PAYEE, and REJ_LVL_NONE, and it updates the parent payment request status to VALIDATION_FAILED, DOCUMENTS_VALIDATED, or PENDING_REVIEW_DOC_VAL_ERRORS. It also supports the payment creation flow by driving documents toward the INSTRUCTION_CREATED payment status. The header comment (120.60.12010000.1, dated 2008/07/28) confirms this body is the working implementation of validation-set evaluation and error reporting.

Key Procedures and Functions

The 31 documented units fall into initialization, evaluation, failure handling, and error-logging groups.

  • INITDOCUMENTDATA, INITCHARVALDATA, INITPAYMENTDATA, INITINSTRUCTIONDATA — initialize the in-memory caches and record structures that later validation steps consult for documents, characteristic values, payments, and payment instructions.
  • APPLYDOCUMENTVALIDATIONSETS and PERFORMONLINEVALIDATIONS — the core validation drivers. They evaluate the applicable validation sets and conditions against the current document set and determine per-document pass/fail outcomes.
  • EVALUATECONDITION — evaluates an individual validation condition, typically combining document fields, payment fields, and request attributes.
  • GETPARAMVALUE, GETDOCUMENTFIELDVALUE, GETPAYMENTFIELDVALUE, GETINSTRUCTIONFIELDVALUE, GETREQUESTATTRIBUTES — accessor routines that resolve values for use in condition evaluation.
  • FAILRELATEDDOCS, FAILALLDOCSFORPAYEE, FAILALLAWTDOCS, FAILALLDOCSFORREQUEST — failure propagation routines that cascade a failure result to related documents, all documents for a payee, all documents awaiting processing, or all documents tied to a request, according to rejection level.
  • INSERT_TRANSACTION_ERRORS, INSERTINTOERRORTABLE — write validation error records so that failures are visible to users and downstream processing. TRXN_TYPE_DOC, the constant referenced in the header, supplies the transaction type value used when inserting into IBY_TRANSACTION_ERRORS.
  • PERFORMDBUPDATES — performs the persistent status updates after validation outcomes are computed.
  • RAISEBIZEVENTS — raises Oracle Workflow business events so subscribing processes are notified of validation outcomes.

Tables Accessed

The package reads and writes through APPS synonyms, principally IBY_DOCS_PAYABLE_ALL, IBY_DOCUMENT_LINES, IBY_PAYMENTS_ALL, IBY_PAY_INSTRUCTIONS_ALL, and IBY_PAY_SERVICE_REQUESTS for the documents and instructions under validation. IBY_TRANSACTION_ERRORS and IBY_TRXN_ERROR_TOKENS hold the error rows and message tokens produced during failed validation, with TRXN_TYPE_DOC identifying the transaction category. IBY_DELIVERY_CHANNELS_B, IBY_EXTERNAL_PAYEES_ALL, and IBY_INTERNAL_PAYERS_ALL supply payee, payer, and delivery-channel context. CE_BANK_ACCOUNTS is consulted for bank account validation, and HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS provide party and address data. FND_NEW_MESSAGES supplies the message text used in the error token substitution.

Usage Notes

IBY_VALIDATIONSETS_PUB is invoked by the Payments validation flow, including the concurrent programs and forms that submit payment requests for validation, and is referenced by 13 other packages within the IBY schema. Subscribing applications typically call the public entry points to validate a request or document set, then inspect the IBY_TRANSACTION_ERRORS rows for rejection detail. Because it is classified PUB, it is the supported API surface; custom code should call the documented procedures rather than the internal evaluation and failure-propagation helpers. The package assumes calling applications have set the request to READY_FOR_VALIDATION and correctly configured validation sets; misconfigured rejection levels can cause broad failure propagation through FAILALLDOCSFORREQUEST or FAILALLDOCSFORPAYEE.