TECHNICAL DETAILS OF BANK SETUPS Impact of Upgrade from R11 to R12 With Upgrade, banks and branches migrated to TCA parties; banks are merged if the following attributes are all the same: a. b. c. d. e. f. g. h. Bank Number Institution type Country Bank admin email Bank name alt Tax payer ID Tax reference number Description, Effective dates

Bank accounts, Bank account uses are migrated into cash management. Transactions are stamped with the bank account uses identifiers as part of the upgrade Oracle Tables Involved Bank Data in R11i was stored in the following tables: 1. AP_BANK_BRANCHES 2. AP_BANK_ACCOUNT_USES_ALL 3. AP_BANK_ACCOUNTS_ALL The new equivalent tables in R12 are now under Cash Management product as follows: 1. CE_BANK_ACCOUNTS: contains Legal Entity Level bank account information. Each bank account must be affiliated with one bank branch. 2. CE_BANK_ACCT_USES_ALL: stores Operating Unit level bank account use information 3. CE_PAYMENT_DOCUMENTS: Payment Documents to be used for Printed type Payments 4. CE_BANK_BRANCHES_V: view: Bank/Branches Info 5. CE_BANK_ACCT_USES_OU_V: view: Internal Bank Account Uses Info

The following tables are obsolete: 1. AP_BANK_BRANCHES 2. AP_BANK_ACCOUNTS_ALL 3. AP_BANK_ACCOUNTS_USES_ALL Note: The bank setup has been moved from AP CE module, and one should use a Cash Management responsibility with all grants and permissions to create and maintain bank accounts. The grants must be done by Sysadmin in User management responsibility. •IBY_EXTERNAL_PAYEES_ALL: This stores supplier information and customer information •IBY_EXT_BANK_ACCOUNTS: This storage for bank accounts .IBY_EXT_PARTY_PMT_MTHDS: This storage for payment method usage rules. •IBY_CREDITCARD: stores the credit card information for a customer •IBY_EXT_BANK_ACCOUNTS: This Stores external bank accounts. These records have bank_account_type = Supplier •IBY_ACCOUNT_OWNERS: stores the joint account owners of a bank account •IBY_PMT_INSTR_USES_ALL: This stores data AP_BANK_ACCOUNT_USES_ALL for payment instruments assignments. from

•HZ_PARTIES: This table stores the bank and bank branches information. Creating a supplier in AP now creates a record in HZ_PARTIES. In the create supplier screen, you will notice that the registry_id is the party_number in the table HZ_PARTIES •HZ_PARTY_USG_ASSIGNMENTS: This table stores the party_usage_code (supplier) and also contains the given party_id for that supplier. •IBY_EXTERNAL_PAYEES_ALL and IBY_EXT_PARTY_PMT_MTHDS: These tables store payment related details of supplier are also inserted. •The master record that replaces PO_VENDORS is now AP_SUPPLIERS. PO_VENDORS is a view that joins AP_SUPPLIERS and HZ_PARTIES. •The table that holds mappings between AP_SUPPLIERS.VENDOR_ID and HZ_PARTIES.PARTY_ID is PO_SUPPLIER_MAPPINGS. Query by party_id. •The bank branch number can be found in the table: HZ_ORGANIZATION_PROFILES .The HZ_ORGANIZATION_PROFILES table stores a variety of information about a party. This table gets populated when a party of the Organization type is created.

Link between Supplier and Banks and TCA table •The link between PO_VENDORS and HZ_PARTIES is PO_VENDORS.party_id. The link between PO_VENDOR_SITES_ALL and HZ_PARTY_SITES is PO_VENDOR_SITES_ALL.party_site_id. •When a Supplier is created Record will be inserted in HZ_PARTIES. When the Supplier Site is created Record will be inserted in HZ_PARTY_SITES. When Address is created it will be stored in HZ_LOCATIONS •When a bank is created, the banking information will be stored in IBY_EXT_BANK_ACCOUNTS IBY_EXT_BANK_ACCOUNTS.BANK_id=hz_paties.party_id •When the Bank is assigned to Vendors then it will be updated in HZ_CODE_ASSIGNMENTS. HZ_CODE_ASSIGNMENTS.owner_table_id = IBY_EXT_BANK_ACCOUNTS.branch_id. •The PARTY_SITE_ID column is the link between the tables IBY_EXTERNAL_PAYEES_ALL& PO_VENDOR_SITES_ALL Driving Bank account associated with a Supplier Site in R12 •In R12 a Supplier Site is stored, in TCA, as a Party_Site. The Party Site has the Party ID of the Party that represents the Supplier record.