Search Results get_default_payee_bank_acc

Overview

IBY_DISBURSEMENT_COMP_PUB is the public PL/SQL specification that exposes the disbursement compatibility engine used by Oracle Payments (IBY) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its central purpose is to determine, for a given payment transaction context, which payees, bank accounts, payment methods, payment formats, delivery channels, and payment profiles are valid and applicable. The specification is declared AUTHID CURRENT_USER and carries the header identifier ibydiscs.pls. It defines package-level constants for the debug module (iby.plsql.IBY_DISBURSEMENT_COMP_PUB) and for the lookup types IBY_BANK_CHARGE_BEARER and IBY_SETTLEMENT_PRIORITY.

The package declares global record and table types used as the input contract for its APIs. The Trxn_Attributes_Rec_Type record captures the transaction identity and routing attributes, including Application_Id, Payer_Legal_Entity_Id, Payer_Org_Id, Payer_Org_Type, Payee_Party_Id, Payee_Party_Site_Id, Supplier_Site_Id, Pay_Proc_Trxn_Type_Code, Payment_Currency, Payment_Amount, and Payment_Function. A companion Payment_Method_Rec_Type carries the payment method name, code, and billing attributes. These structures allow callers to pass a single transaction snapshot rather than a long positional parameter list.

Key Procedures and Functions

The documented API surface comprises twelve public procedures and functions, all oriented toward compatibility evaluation:

• GET_APPLICABLE_PAYEE_BANKACCTS — returns the payee bank accounts eligible for the transaction context; this is the entry point associated with the search term "get_applicable_payee_bankaccts."
• GET_DEFAULT_PAYEE_BANK_ACC — identifies the default payee bank account when multiple accounts qualify.
• GET_APPLICABLE_PAYEE_ACC_LIST — returns a broader list of applicable payee accounts for selection and display.
• GET_APPLICABLE_PAYMENT_METHODS — resolves the payment methods valid for the payer, payee, and transaction attributes.
• GET_DEFAULT_PAYMENT_ATTRIBUTES — supplies defaulted payment attributes derived from the applicable rules and profiles.
• GET_APPLICABLE_PAYMENT_FORMATS — determines the payment formats compatible with the resolved method.
• GET_APPLICABLE_PMT_PROFILES — returns the payment profiles applicable to the payer/payee combination.
• GET_PMT_PROFILES_INTERSECT — computes the intersection of payment profiles across multiple applicability sets.
• GET_APPL_DELIVERY_CHANNELS — identifies the delivery channels available for the selected payment method and format.
• GET_APPLICABLE_PAYMENT_REASONS — returns valid payment reasons for the transaction.
• GET_PAYMENT_FIELD_PROPERTIES — exposes field-level properties and behavior for payment attributes rendered in calling UIs.
• VALIDATE_DOCUMENTS — validates documents against the compatibility rules before payment processing proceeds.

Tables Accessed

The package reads the transaction and payee foundation tables IBY_DOCS_PAYABLE_ALL, IBY_EXTERNAL_PAYEES_ALL, IBY_TRXN_TYPES_B, and IBY_INTERNAL_PAYERS_ALL to establish the disbursement context. Party and site data are resolved through HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS. Applicability rules and configuration are drawn from IBY_APPLICABLE_PMT_MTHDS, IBY_APPLICABLE_PMT_PROFS, IBY_EXT_PARTY_PMT_MTHDS, IBY_PAYMENT_METHODS_B, IBY_PAYMENT_RULES, IBY_RULE_CONDITIONS, and IBY_PMT_INSTR_USES_ALL. PLITBLM is used as the standard PL/SQL table for ID list handling. The package is referenced by a further ten packages, confirming its role as a shared compatibility service.

Usage Notes

IBY_DISBURSEMENT_COMP_PUB is invoked during payment setup and processing, most visibly when the Payments workbench and payment creation forms must populate eligible payee bank accounts, payment methods, formats, and delivery channels for the selected transaction. Concurrent programs responsible for payment instruction building and document validation also call these APIs, particularly VALIDATE_DOCUMENTS and the GET_APPLICABLE_* family. Custom extensions that build payment flows should call this public specification rather than query the underlying IBY tables directly, because the package encapsulates the payer/payee rule evaluation logic. Callers should populate the global record types defined in the specification and rely on the AUTHID CURRENT_USER semantics, ensuring the invoking schema has appropriate grants on the APPS synonyms.