Results for “create_bank”

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

Overview

CE_BANK_PUB is a public PL/SQL API package in the APPS schema that provides the canonical programmatic interface for creating and maintaining banking information within Oracle Cash Management. It exposes a controlled, API-driven surface for managing the three tiers of banking setup: banks, bank branches, and bank accounts, together with the account use assignments that link a bank account to a specific application context such as Payables, Receivables, Payroll, or Treasury. Because the package is classified as a PUB (public) API, it is intended for external invocation by other Oracle E-Business Suite modules and by customer-written extensions, rather than being reserved for internal use.

The package coordinates its work across the Cash Management tables and, critically, across the Oracle Trading Community Architecture (TCA) and Oracle Payments (IBY) tables that hold the corresponding party, party site, and external bank account records. This cross-product orchestration is why the API is preferred over direct table inserts: it keeps the banking and TCA/Payments representations synchronized.

Key Procedures and Functions

The documented interface exposes thirteen procedures and functions grouped by banking entity.

• Bank-level operations: CREATE_BANK, UPDATE_BANK, SET_BANK_END_DATE, and CHECK_BANK_EXIST. The create and update routines establish and maintain the bank record; SET_BANK_END_DATE performs an end-dating (inactivation) rather than a physical delete; CHECK_BANK_EXIST validates whether a bank already exists, supporting duplicate prevention in custom code.
• Branch-level operations: CREATE_BANK_BRANCH, UPDATE_BANK_BRANCH, SET_BANK_BRANCH_END_DATE, and CHECK_BRANCH_EXIST. These mirror the bank-level set for the branch entity, which must be associated with a parent bank.
• Account-level operations: CREATE_BANK_ACCT, UPDATE_BANK_ACCT, and SET_BANK_ACCT_END_DATE. These maintain the bank account record itself.
• Account use operations: CREATE_BANK_ACCT_USE and UPDATE_BANK_ACCT_USE. These establish and modify the assignment of an account to a given application use, which governs where the account is available for transaction processing.

Consistent with Oracle API conventions, the create and update procedures are expected to accept a standard API parameter set and to return a standard return status and message, while end-date routines perform logical inactivation. Parameter lists are not enumerated here.

Tables Accessed

The package reads and writes the core Cash Management banking tables through APPS synonyms:

• CE_BANK_ACCOUNTS and CE_BANK_ACCOUNTS_S: the bank account entity and its audit/shadow record.
• CE_BANK_ACCT_USES_ALL and CE_BANK_ACCT_USES_S: account use assignments across operating units, plus the corresponding shadow table.
• CE_GL_ACCOUNTS_CCID: the GL account code combination associated with account uses.

It also touches TCA and Payments tables to keep party and settlement data consistent: HZ_PARTIES, HZ_ORGANIZATION_PROFILES, HZ_RELATIONSHIPS, HZ_CONTACT_POINTS, HZ_CODE_ASSIGNMENTS, IBY_EXT_BANK_ACCOUNTS, and XTR_PARTY_INFO.

Usage Notes

CE_BANK_PUB is invoked from Cash Management setup forms, from other EBS product APIs, and from custom PL/SQL. The ETRM dependency report identifies IBY_EXT_BANKACCT_PUB and POS_SBD_IBY_PKG among its referencing objects. Calls should be wrapped in a savepoint with error handling on the returned status, and direct DML against the underlying CE and HZ tables should be avoided in favor of this API.