Search Results iby_disbursement_setup_pub




Overview
Explore in AI Chat

Overview

IBY_DISBURSEMENT_SETUP_PUB is a public PL/SQL package body in the APPS schema that centralizes the setup and maintenance of disbursement-related master data within Oracle Payments (IBY). Its principal responsibility is the creation, validation, and update of external payees, their payment instrument assignments, and temporary external bank accounts. In Oracle E-Business Suite 12.1.1 and 12.2.2, Payments acts as the central disbursement engine for Payables, Receivables, Payroll, and other source products; this package provides the programmatic entry point through which those products register a party as a payable entity and associate the payment methods, formats, and instruments that govern how funds are disbursed. Because the package is classified as a public (PUB) API and is referenced by eighteen other database objects, it functions as a shared infrastructure component rather than a private utility. It is marked VALID in the data dictionary, indicating that the compiled body is consistent with its specification at the documented release levels.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions that constitute the public interface of this package:

  • CREATE_EXTERNAL_PAYEE — Registers a new external payee record, establishing the party, supplier, or customer as a disbursable entity within Payments.
  • UPDATE_EXTERNAL_PAYEE — Modifies attributes of an existing external payee, such as effective dates, addresses, or payment preferences.
  • VALIDATE_EXTERNAL_PAYEE — Performs the business-rule checks required before a payee can be committed, returning validation outcomes to the caller.
  • SET_PAYEE_INSTR_ASSIGNMENT — Creates or changes the association between a payee and specific payment instruments or payment method usages.
  • GET_PAYEE_INSTR_ASSIGNMENTS — Retrieves the instrument assignments currently held by a given payee.
  • GET_PAYEE_ALL_INSTRUMENTS — Returns the complete set of instruments available or assigned to a payee across payment methods.
  • CREATE_TEMP_EXT_BANK_ACCT — Establishes a temporary external bank account record prior to full validation and promotion into the permanent account structure.
  • VALIDATE_TEMP_EXT_BANK_ACCT — Validates the temporary bank account data, typically invoking external bank account validation routines.

Parameter lists are not reproduced here; callers should consult the package specification for exact signatures.

Tables Accessed

The package reads and writes the core Payments setup tables. IBY_EXTERNAL_PAYEES_ALL and its sequence IBY_EXTERNAL_PAYEES_ALL_S store the payee master records. IBY_PMT_INSTR_USES_ALL and IBY_PMT_INSTR_USES_ALL_S hold payment instrument usage assignments, while IBY_EXT_PARTY_PMT_MTHDS and its sequence capture party-level payment method preferences. Bank account setup flows through IBY_EXT_BANK_ACCOUNTS_V, IBY_TEMP_EXT_BANK_ACCTS, IBY_EXT_BANKACCT_PUB, and IBY_EXT_BANKACCT_VALIDATIONS, with CE_BANKS_V and CE_BANK_BRANCHES_V supplying bank and branch reference data. Party, site, and location data are drawn from HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL. Supplier information comes from AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL. Configuration lookups include IBY_PAYMENT_METHODS_B and its VL view, IBY_FORMATS_VL, IBY_PAYMENT_REASONS_VL, IBY_DELIVERY_CHANNELS_VL, IBY_ACCOUNT_OWNERS, and IBY_CREDITCARD. Error handling and diagnostics rely on FND_MESSAGE, FND_MSG_PUB, FND_NEW_MESSAGES, FND_LOG, and IBY_DEBUG_PUB.

Usage Notes

The package is typically invoked by Payments setup forms, by concurrent programs that batch-load payees and bank accounts, and by the public APIs of dependent products such as IBY_FNDCPT_SETUP_PUB and IBY_EXT_BANKACCT_PUB, which call into it rather than manipulating the underlying tables directly. Custom integrators should call these routines instead of issuing DML against IBY_EXTERNAL_PAYEES_ALL or IBY_PMT_INSTR_USES_ALL, because the package enforces validation, sequence generation, and message-stack conventions through FND_API and FND_MSG_PUB. Temporary bank accounts created by CREATE_TEMP_EXT_BANK_ACCT should be validated with VALIDATE_TEMP_EXT_BANK_ACCT before promotion. Diagnostics can be enabled through IBY_DEBUG_PUB and FND_LOG for troubleshooting. Because the package is referenced by eighteen objects, changes to its behavior can ripple across Payables, Receivables, and Payroll disbursement flows; extensions should therefore be confined to wrapper packages.