Results for “create_bank_acct_use”

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

Overview

CE_BANK_PUB is the public PL/SQL package in the APPS schema that provides the canonical application programming interface for creating and maintaining bank, bank branch, bank account, and bank account use records within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Cash Management (CE) product family and functions as the supported entry point for external and internal callers that need to register or amend banking information without writing directly to the underlying Cash Management and Trading Community (HZ) tables.

Because the object is documented with an API classification of PUB, it is intended for invocation by other Oracle modules, by customer extensions, and by integration code. The package encapsulates the business rules, validations, and multi-table writes required to keep bank master data, bank account data, and the associated Trading Community party and party-site records synchronized. It also coordinates with IBY (Payments) external bank account structures, ensuring that payment-related bank account representations remain consistent with Cash Management definitions.

Key Procedures and Functions

The package body exposes thirteen documented routines, grouped by the entity they operate on.

• Bank-level routines: CREATE_BANK creates a new bank record; UPDATE_BANK modifies attributes of an existing bank; SET_BANK_END_DATE applies an end date to retire a bank; CHECK_BANK_EXIST validates whether a bank already exists, typically as a duplicate-avoidance check before creation.
• Branch-level routines: CREATE_BANK_BRANCH creates a new bank branch; UPDATE_BANK_BRANCH amends branch attributes; SET_BANK_BRANCH_END_DATE inactivates a branch; CHECK_BRANCH_EXIST tests for the prior existence of a branch.
• Account-level routines: CREATE_BANK_ACCT creates a bank account; UPDATE_BANK_ACCT amends account details; these routines interact with the Cash Management account tables and, where relevant, the Payments external bank account model.
• Account use routines: CREATE_BANK_ACCT_USE creates a bank account use, which associates an account with a specific operating unit, internal or external use, and ledger context; UPDATE_BANK_ACCT_USE amends that association; SET_BANK_ACCT_END_DATE terminates an account use.

This last group is directly relevant to the search term ce_bank_acct_uses_s, because account use creation and maintenance cause rows to be inserted or updated in CE_BANK_ACCT_USES_ALL and its corresponding _S (security/denormalized) table.

Tables Accessed

The package reads and writes the core Cash Management bank tables CE_BANK_ACCOUNTS and CE_BANK_ACCOUNTS_S, together with CE_BANK_ACCT_USES_ALL and CE_BANK_ACCT_USES_S. It also references CE_GL_ACCOUNTS_CCID for general ledger account code combinations associated with bank accounts, and CE_BANK_BRANCHES_V for branch data. Trading Community tables HZ_PARTIES, HZ_ORGANIZATION_PROFILES, HZ_RELATIONSHIPS, HZ_CONTACT_POINTS, and HZ_CODE_ASSIGNMENTS hold the party, party site, and classification information that underpins bank and branch entities. Payments tables IBY_EXT_BANK_ACCOUNTS and IBY_EXT_BANKACCT_PUB support the external bank account representation. XTR_PARTY_INFO and XTR_PARTIES_V are referenced for treasury-related party replication. Validation logic is delegated to CEP_STANDARD, CE_BANK_AND_ACCOUNT_VALIDATION, and CE_VALIDATE_BANKINFO, while FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and FND_PROFILE supply standard API, environment, and messaging services.

Usage Notes

CE_BANK_PUB is normally invoked indirectly through the Oracle Payments and Cash Management setup forms, where user actions such as defining a bank, branch, or account trigger the corresponding public procedure. It is also called by concurrent programs and by downstream modules that need to propagate banking data, such as payments processing and treasury. Custom code and integration interfaces should call these procedures rather than performing direct DML on the Cash Management and Trading Community tables, since the package enforces validations, manages message stacks, and maintains the _S tables and Payments external account records. Because the package is not referenced by any database object according to the metadata, it is a top-level API intended for external entry rather than an internal utility. Callers should initialize the FND message stack and use the standard commit and rollback conventions expected of FND_API-based public packages.