Search Results ce_bank_and_account_util




Overview
Explore in AI Chat

Overview

CE_BANK_AND_ACCOUNT_UTIL is a utility package in the Oracle E-Business Suite Cash Management (CE) module, owned by the APPS schema and classified as a UTIL object within the ETRM documentation set for release 12.1.1 and 12.2.2. Its principal business purpose is to centralize common bank and bank account handling logic that would otherwise be duplicated across Cash Management forms, concurrent programs, and dependent packages. The package provides callers with a consistent, security-aware view of bank account data, most notably by translating a raw bank_account_id into a display-ready account number that respects the masking rules configured at the site level. Because seven other packages reference this package, it functions as a foundational shared service rather than a standalone business API. The header comment in the source ($Header: cebautls.pls 120.2 ... noship $) indicates the file has been stable since a 2005 revision, consistent with its role as low-level infrastructure that changes infrequently.

Key Procedures and Functions

The package exposes six documented routines, of which five are public entry points.

  • GET_MASKED_BANK_ACCT_NUM — Accepts a bank_account_id and returns the corresponding bank account number rendered with the mask dictated by the profile option CE: Mask Internal Bank Account Numbers. This is the routine most frequently searched by developers and is the canonical way to obtain a masked account number for display or logging.
  • GET_MASKED_IBAN — Provides the analogous masked representation for International Bank Account Numbers, applying the same profile-driven masking philosophy to the IBAN attribute.
  • GET_ORG_BANK_ACCT_LIST — Accepts an org_id and returns the set of bank accounts that the organization is permitted to access, formatted as a single string of bank_account_id values separated by the '@' delimiter. This supports org-level access scoping in inquiry and setup screens.
  • GET_INTERNAL_BANK_ACCTS — Retrieves internal bank accounts, supporting processes that distinguish the deploying organization's own accounts from external or supplier accounts.
  • SQL_ERROR — A public procedure that standardizes unhandled SQL error handling. It sets an error message and raises an exception on behalf of calling routines, typically invoked from exception handlers in the other functions in this package.
  • BankAcctIdTable — A declared PL/SQL collection type based on ce_bank_accounts.bank_account_id%TYPE, used internally to pass arrays of bank account identifiers between routines.

Tables Accessed

The package reads from two Cash Management tables through APPS synonyms. CE_BANK_ACCOUNTS is the primary source for account numbers and IBAN values keyed by bank_account_id, and it also supplies the anchored data type for the BankAcctIdTable collection. CE_BANK_ACCT_USES_ALL provides the organization-level usage and access information required by GET_ORG_BANK_ACCT_LIST and GET_INTERNAL_BANK_ACCTS, since a bank account's visibility to a given operating unit is defined by its use records rather than by the account header alone. PLITBLM is referenced for error message text retrieval, which is consistent with the SQL_ERROR routine's responsibility to populate a meaningful error message before raising the exception. No insert, update, or delete activity is documented; the package is read-only with respect to business data.

Usage Notes

CE_BANK_AND_ACCOUNT_UTIL is predominantly consumed by other server-side code rather than by end users directly. The seven documented referencing packages confirm that it is invoked as a dependency from higher-level Cash Management APIs and validation routines. Typical invocation points include:

  • Forms and OAF pages that must display a bank account without exposing the full number, calling GET_MASKED_BANK_ACCT_NUM or GET_MASKED_IBAN at query time.
  • Concurrent programs and reports that list accounts for a specific operating unit, using GET_ORG_BANK_ACCT_LIST to enforce org-level access before rendering output.
  • Custom code and extensions that should reuse the standard masking logic instead of implementing their own, ensuring behavior remains aligned with the CE: Mask Internal Bank Account Numbers profile option.

Developers embedding these routines should call SQL_ERROR from their own exception handlers to preserve consistent error semantics, and must not assume the returned account list is in any particular sort order, as the '@'-delimited format is intended for consumption by downstream parsing logic.