Search Results insert_bank_accounts

Overview

XTR_REPLICATE_BANK_ACCOUNTS_P is an Oracle EBS treasury package owned by APPS and classified as OTHER. Its business purpose is to replicate Bank, Bank Branch, and Bank Account data that originates in Oracle Cash Management (CE) into the corresponding ETRM (XTR) tables. This replication ensures that treasury-facing records stay synchronized with the master banking data maintained in Cash Management, allowing downstream treasury processes such as interest schedule handling to operate against a consistent view of bank account information. The package was created on 05-19-2005 by Bhargav Adireddy and carries the header identifier xtrrbacb.pls. Its main entry point, REPLICATE_BANK_ACCOUNTS, is described as being called by CE to push newly created or modified bank and bank account data into the XTR schema. The package supports both insert and update semantics via an action flag, and it follows the standard Oracle EBS API error-handling convention, returning a return status plus message count and message data. Consistent with ETRM coding standards, it relies on FND_MSG_PUB for message stack initialization and FND_API constants such as G_RET_STS_SUCCESS, G_RET_STS_ERR, and G_RET_STS_UNEXP_ERR to communicate success, expected errors, and unexpected errors respectively.

Key Procedures and Functions

The package exposes eight documented procedures and functions. REPLICATE_BANK_ACCOUNTS is the primary public procedure invoked by CE; it accepts a bank account record and an action flag indicating whether data should be inserted or updated, and returns status and message information. INSERT_BANK_ACCOUNTS handles the creation of new bank account rows in the XTR tables. UPDATE_BANK_ACCOUNTS handles modification of existing replicated rows. VALIDATE_BANK_ACCOUNTS performs the validation logic required before data is written, ensuring that incoming bank and bank branch information satisfies the package's business rules. MODIFY_BANK_ACCOUNTS applies the necessary changes to the replicated records. LOG_ERR_MSG is the utility routine used to record error messages, and it is the object most frequently associated with this package in repository searches; it centralizes error capture so that diagnostic information is written consistently during replication. REPLICATE_INTEREST_SCHEDULES extends the replication scope to interest schedule data associated with bank accounts, ensuring that treasury interest calculations remain aligned with the replicated account records. Additional internal logic includes a branch-name lookup cursor that selects the full name from XTR_PARTY_INFO based on the bank code carried on the incoming bank account record, supplying the bank branch name used during replication.

Tables Accessed

The package reads and writes XTR_BANK_ACCOUNTS, the ETRM table that stores the replicated bank account records. This table is central to the package's insert, update, and validation operations, and the package works with a record structure based on its row type. The package also reads XTR_PARTY_INFO, which holds party-level information including bank and bank branch details. In the documented logic, XTR_PARTY_INFO is queried through the branch-name cursor to obtain the full name of the bank branch identified by the party code matching the incoming bank code. Both tables are accessed through APPS synonyms, in keeping with standard EBS naming conventions. Together these tables provide the source bank and branch context plus the destination account storage required for complete replication.

Usage Notes

XTR_REPLICATE_BANK_ACCOUNTS_P is typically invoked programmatically by Oracle Cash Management when bank, bank branch, or bank account data is created or changed, rather than from a standalone form or concurrent program. The action flag distinguishes insert from update processing, so callers must supply the correct flag value when invoking REPLICATE_BANK_ACCOUNTS. Because the package follows the FND_API return-status convention, callers should inspect x_return_status and, when errors occur, use the message count and message data outputs to retrieve details from the message stack. The package is referenced by three other packages, indicating that it functions as a shared replication service within ETRM. Customizations that extend banking replication should call the public procedures rather than modify the package body directly, and error information captured through LOG_ERR_MSG should be reviewed when diagnosing replication failures. As with all APPS-owned EBS objects, changes should be applied through supported patching and an approved custom schema rather than direct edits to the shipped source.