Search Results citi_de_eft_dom_payee

Overview

IBY_VALIDATIONSETS_CALLS_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12. It serves as the central invocation layer for payment validation sets used by Oracle Payments (IBY) during payment instruction processing and payment formatting. The package exists to expose individual validation procedures that can be referenced by a validation set definition, allowing Oracle Payments to apply country-specific, bank-specific, or format-specific business rules before a payment is created or released.

The naming convention of the procedures reveals the design intent: each procedure corresponds to a distinct payment validation rule associated with electronic funds transfer (EFT) processing. The prefixes (CITI_AT, CITI_BE, CITI_CH, CITI_DE, AT_EFT, BE_EFT, CH_EFT, DE_EFT) indicate the bank, country, or payment format to which the rule applies. The user search term "at_eft_int_payer" maps directly to the procedure AT_EFT_INT_PAYER, which enforces validation logic for Austria (AT) EFT international payer data. This confirms the package is the repository users encounter when diagnosing why a payment failed a payer-level validation for an international Austrian EFT transaction.

Key Procedures and Functions

The package exposes 127 documented procedures and functions. Representative examples include:

• CITI_AT_EFT_DOM_PAYEE — validates payee data for Citibank Austria domestic EFT payments.
• CITI_AT_EFT_DOM_DOC — validates document-level data for the same Citibank Austria domestic EFT scenario.
• AT_EFT_INT_INTERNAL_BANK — validates the internal bank identifier for Austrian international EFT payments.
• AT_EFT_INT_PAYER — validates payer-level information for Austrian international EFT payments; this is the procedure surfaced by the user search.
• AT_EFT_INT_PAYEE — validates payee-level information for Austrian international EFT payments.
• CITI_BE_EFT_DOM_PAYEE — validates payee data for Citibank Belgium domestic EFT payments.
• BE_EFT_INT_PAYEE and BE_EFT_INT_DOC — validate payee and document data for Belgian international EFT payments.
• CH_EFT_GEN_PAYEE and CH_EFT_GEN_DOC — validate payee and document data for Swiss generic EFT payments.
• DE_EFT_DOM_INTERNAL_BANK and related DE_EFT procedures — validate German domestic EFT internal bank data.

Each procedure follows the same contract shape, accepting a validation assignment identifier, a validation set code, a document identifier, and an online-validation flag, and returning a numeric result. That result is interpreted by the Oracle Payments validation engine to determine whether the payment proceeds or is rejected.

Tables Accessed

The package reads and writes several core Oracle Payments and Receivables tables through APPS synonyms:

• IBY_DOCS_PAYABLE_ALL — the primary source of the payable document being validated.
• IBY_PAYMENTS_ALL and IBY_PAY_INSTRUCTIONS_ALL — supply payment and payment instruction attributes.
• IBY_VAL_ASSIGNMENTS and IBY_VALIDATION_VALUES — store the validation assignment and its configured parameter values.
• IBY_EXTERNAL_PAYEES_ALL, HZ_CONTACT_POINTS, and CE_BANK_ACCOUNTS — supply payee, contact, and bank account details needed for country-specific rules.
• IBY_TRANSACTION_ERRORS, IBY_TRANSACTION_ERRORS_S, and IBY_TRXN_ERROR_TOKENS — record validation failures and their tokens.
• IBY_COMPLETED_PMTS_GROUP_S — supports grouping of completed payments.
• FND_NEW_MESSAGES — provides translatable validation messages.
• DUAL and PLITBLM — utility/scratch references.

Usage Notes

This package is invoked by the Oracle Payments validation framework when a validation set is associated with a payment process profile or payment method. It is not normally called directly by end users; instead, administrators configure validation assignments in the Payments Setup pages, and the engine dispatches to the appropriate procedure at payment creation or formatting time. Because it is a public package referenced by one other package, customizations should call it through the documented procedures rather than modifying its body. Customers diagnosing failures such as "at_eft_int_payer" should inspect the corresponding validation assignment, the values in IBY_VALIDATION_VALUES, and any rows written to IBY_TRANSACTION_ERRORS.