R12 Banks and Branches Model

As discussed in earlier post about the new tables in R12 Banks and Branches, today lets go through the internal and external uses of bank accounts. When a bank account is created in Cash Management they are created as Internal bank Accounts, and the bank accounts created using the Supplier form or customer form through are created as External Bank Accounts. To be more specific when the user defines a new bank account using the supplier form the information is stored in the IBY_EXT_BANK_ACCOUNTS and the internal bank accounts are stored in the CE_BANK_ACCOUNT.

The ability to share bank and bank account information between internal bank account definitions from different modules like Payables, Receivables, Treasury, Payroll and Global Financials is provided by Cash Management.

As we know TCA party model is used to model banks and bank branches as parties with the associated Relationships, Address, Contacts and Locations. Cash Management uses the following TCA tables for modeling banks and bank Branches

1) HZ_PARTIES
2) HZ_RELATIONSHIPS
3) HZ_RELATIONSHIP_TYPES
4) HZ_CONTACT_POINTS
5) HZ_PARTY_SITES
6) HZ_LOCATIONS
7) HZ_ORGANIZATION_PROFILES
8) HZ_ORG_CONTACTS
9) HZ_ORG_CONTACT_ROLES

HZ_ORGANIZATION_PROFILES --Stores attributes of banks and bank branches with the history of changes made to banks and bank branches.
HZ_PARTIES -- The contacts of a person at the bank, bank branch and bank account are defined as a party
HZ_CONTACT_POINTS -- Stores the contact details
HZ_ORG_CONTACTS --Stores the contact’s title
HZ_ORG_CONTACT_ROLES --Stores the contact’s purpose or role
HZ_LOCATIONS -- Stores the address details of banks and bank branches
HZ_PARTY_SITES --Stores party sites

CE_GL_ACCOUNTS_CCID -- Stores the accounting data pertaining to the bank account use

The bank, branch and bank account related attributes in AP_BANK_BRANCHES and AP_BANK_ACCOUNTS_ALL tables will be upgraded to HZ_PARTIES and the new tables in Cash Management as mentioned in my earlier post. The new data model allows the bank and bank branch entities to be defined separately allowing users more flexibility and to establish a hierarchical relationship between them.

R12 Bank Data

1.What are the new tables in R12?

The following tables were obsoleted in R12:

AP_BANK_BRANCHES
AP_BANK_ACCOUNTS_ALL
AP_BANK_ACCOUNTS_USES_ALL

The new tables in R12 are now under Cash Management module: Here are the tables

CE_BANK_ACCOUNTS: This table contains Legal Entity Level bank account information. Each bank account must be affiliated with one bank branch.

CE_BANK_ACCT_USES_ALL: This table stores Operating Unit level bank account use information

CE_PAYMENT_DOCUMENTS: This table Payment Documents to be used for Printed type Payments

CE_BANK_BRANCHES_V: view: Bank/Branches Info

CE_BANK_ACCT_USES_OU_V: view: Internal Bank Account Uses Info

The bank setup has been moved from AP to CE module, one should use Cash Management responsibility with all grants and permissions in order to create and maintain bank accounts. All the grants and permissions are done by Sysadmin using User management responsibility.

R12 Supplier Banks

Supplier Bank Accounts can be imported during Supplier and Supplier Site Open Interface

Successfull creation of Supplier and Supplier Site a Payee is created in IBY (Payments application) for the Supplier and Supplier Site.If corresponding rows are created in IBY_TEMP_EXT_BANK_ACCTS table then we can use IBY_EXT_BANKACCT_PUB.CREATE_EXT_BANK_ACCT to create bank account and associate it with the payee.In order to import supplier bank accounts during Supplier and Supplier Site Open Interface, we have to populate the IBY_TEMP_EXT_BANK_ACCTS table.
Each row in the IBY_TEMP_EXT_BANK_ACCTS table is associated with the Supplier or Supplier Site if the following condition satisfied

IBY_TEMP_EXT_BANK_ACCTS.calling_app_unique_ref1 = AP_SUPPLIERS_INT.vendor_interface_id (for Suppliers)
OR
IBY_TEMP_EXT_BANK_ACCTS.calling_app_unique_ref2 = AP_SUPPLIER_SITES_INT.vendor_site_interface_id (for Supplier Sites)