Results for “ap_iby_utility_pkg”

40 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.AP_IBY_UTILITY_PKG package body is a shared utility package within the Oracle Payables (AP) module that provides supporting logic for the Payments Integration (IBY) infrastructure in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to resolve default disbursement bank account information for suppliers and supplier sites during payment processing. The package bridges Payables supplier master data with the Payments (IBY) module, which is responsible for payment instruction creation, disbursement processing, and bank account validation.

Because it is an internal utility package rather than a public API, it is not exposed to end users directly. Instead, it is consumed by higher-level payment and disbursement components that require a consistent method of determining which supplier bank account should be used as the default when creating or validating payments. The package is classified as OTHER in the ETRM repository, indicating that it is not part of the formal public API surface but is nevertheless a valid and actively referenced database object in the APPS schema.

Key Procedures and Functions

The ETRM documentation records one documented procedure or function within this package body:

  • GET_DEFAULT_IBY_BANK_ACCT_ID — This function resolves the default IBY bank account identifier for a given supplier or supplier site. It encapsulates the logic required to determine which supplier bank account should be treated as the default for disbursement purposes, returning the bank account ID used by the IBY payment infrastructure. It is the single documented entry point in the package and is the reason the package is referenced by other Payables and Payments components.

No other procedures or functions are documented in the ETRM metadata for this package body. The package depends on the FND_API, FND_MESSAGE, FND_MSG_PUB, and FND_LOG packages for error handling, message retrieval, and logging, and it references IBY_DISBURSEMENT_COMP_PUB, indicating that it interacts with the disbursement completion public API during account resolution.

Tables Accessed

The package accesses the following documented tables, referenced through APPS synonyms:

  • AP_SUPPLIERS — The supplier header table, read to identify the supplier record and its associated default bank account configuration. It supplies supplier-level attributes required to determine the correct disbursement account.
  • AP_SUPPLIER_SITES_ALL — The supplier site table, read to resolve site-level bank account defaults. Because payments can be made at either the supplier or the supplier site level, both tables are consulted to determine the appropriate default account for the payment context.

The package body also performs SQL statements (documented as [SQL Statements] in the ETRM dependency listing) that query these tables as part of the default account lookup logic. No write operations to these tables are documented.

Usage Notes

AP_IBY_UTILITY_PKG is an internal utility package that is not invoked directly by end users. It is typically called by other Payables and Payments packages when a default supplier bank account must be determined during payment creation, payment formatting, or disbursement processing. The ETRM metadata confirms that the package is referenced by three other database objects, reflecting its role as a shared dependency rather than a standalone API. It is not referenced by any external or public database object beyond those internal callers.

Because the package is not part of the formal public API, customizations should avoid calling it directly; instead, developers should use supported public APIs such as IBY_DISBURSEMENT_COMP_PUB for disbursement operations. When troubleshooting payment default account issues in EBS 12.1.1 or 12.2.2, this package may appear in dependency chains or error stack traces, and its GET_DEFAULT_IBY_BANK_ACCT_ID function is the relevant entry point for analysis. The package body status is VALID in the APPS schema, and its dependency on FND_LOG and FND_MSG_PUB indicates that it participates in the standard EBS logging and message framework.