Examples of Loading Banks
A bank is a financial institution that can have multiple branches. External bank accounts are associated with bank branches. Bank, Bank Branch, and External Bank Account are business objects whose details are stored in non-HCM tables.
However, you can load them using HCM Data Loader. This topic describes aspects of the Bank object that you must understand to load banks successfully.
Loading Banks
You load bank data in a Bank.dat file for processing by HCM Data Loader. To provide a unique reference to a bank when you create it, you must supply either the Bank Name or the Bank Number attribute. You must also supply the Country Code attribute.
You are recommended to use source keys when creating banks. This makes it easier to reference the bank when creating branches or external bank accounts.
METADATA|SourceSystemOwner|SourceSystemId|Bank|BankName|BankNumber|CountryCode
MERGE|Bank|VISION|CA10001A|Vision Bank|100001A|CA
This example Bank.dat file creates a Bank object using user keys. Both the Bank Name and Bank Number attributes are provided.
METADATA|Bank|BankName|BankNumber|CountryCode
MERGE|Bank|Vision Bank|100001A|CA
Deleting Banks
You can't delete Bank objects using HCM Data Loader. However, you can inactivate banks that are either no longer required or were entered in error. This feature, which isn't available on the Manage Banks pages, enables you to maintain an audit trail.
This example Bank.dat file provides an end date for a Bank object to inactivate it. To identify an existing bank uniquely, you can use the Country Code and either the Bank Name or the Bank Number. Alternatively, supply the source key to identify the bank to be inactivated.
METADATA|Bank|BankNumber|CountryCode|EndDate
MERGE|Bank|100001A|CA|2016/03/01