You are on page 1of 37

Process of importing external bank account data in R12 Oracle Payments

By Kondaiah Mandadi (kondaiah.mandadi@oracle.com) & Anil Kumar Sarada (Anilkumar.sarada@oracle.com)

Change Record
Date 14th Aug 2009 Author Kondaiah Mandadi & Anilkumar Sarada Version 1.0 Change Reference First draft

Table of Contents
1. 2. 3. Introduction .............................................................................................................................................5 Current Process ........................................................................................................................................6 Importing Supplier bank accounts ..............................................................................................................7 3.1. 3.2. 3.3. Prerequisite ...................................................................................................................................7 Importing the bank account at Supplier level along with Supplier data ......................................................7 Importing the bank account at site level along with Supplier and Supplier site ..........................................14 3.3.1. Importing Bank account at site along with supplier and site details. ..........................................................14 3.3.2. Importing bank account along with supplier site for an existing Supplier.................................................15 3.4. 4. Importing the bank accounts for Employee type Supplier

.....................................................................15

Process of importing Customer banks ........................................................................................................17 4.1. 4.2. 4.3. Importing bank account at Customer account level along with Customer account ......................................17 Importing bank account at site level along with Customer account and Customer site.................................23 Importing the bank account for an existing customer ...........................................................................23 4.3.1 Importing the bank account at Customer account level ...............................................................................24 4.3.2 Importing the bank account at Customer site level ......................................................................................24

5.

Table description ....................................................................................................................................25 5.1. 5.2. Table Description - IBY_TEMP_EXT_BANK_ACCTS ......................................................................26 Table and Field description – RA_CUSTOMER_BANKS_INTERFACE ................................................31

................................................................13 Figure 7....................................................................................................................................9 Figure 3......................8 Figure 2 View of the program parameters screen.............View of the parameters – Import options .......11 Figure 5 .View of the Requests status screen............................View of the selecting the new request screen .........22 .......................Table of Figures Figure 1....................Submit new request screen view – Receivables...............................................18 Figure 8 View of the Standard Request submission – parameters selection screen................................................................................................................................. ..............21 Figure 11 .............................................20 Figure 10 .......................Payables.....................View of the request submission screen after selecting the program name and the parameters.....................................................................................................................................................12 Figure 6 -Requests screen showing the phase as ‘Completed’ and status as ‘Normal’.10 Figure 4..........................................View of the parameters LOV...........19 Figure 9 Customer Import – Parameters screen view............ ............................................View of the Requests status screen......

Introduction Oracle supports many Open Interface Programs for importing data from any third party systems. This document helps in understanding the process of importing the external bank accounts data for customers or suppliers. .1. For importing bank account information Oracle provides interface programs named ‘Customer Interface’ for importing Customer bank accounts and ‘Supplier Open Interface/Supplier site interface ’ for importing Supplier bank accounts.

For example. Once the import data is loaded into the interface tables. SQL*Report. please refer to the Payables Reference Guide. An import program is a program that is written to convert data from a third party system into a standard data format that Interface program can read and load in to Oracle eBusiness suite. run the Oracle Interface programs to validate the data and insert in to Oracle tables. The type of feeder program (program that loads the data in to interface tables) depends on the environment from which the data is imported.2. use SQL*Loader. or C to write an import program to import data from a non-Oracle system . Current Process The process of importing supplier’s data has been documented in the Payables Reference Guide R12. PL/SQL. The process of importing customer’s data has been documented in Oracle Trading Community Architecture Reference Guide and Oracle Trading Community Architecture User Guide. For further details on the supplier’s data.

2. The supplier bank accounts can be assigned at the Supplier or Supplier Site or Address or Address Operating Unit level from the user interface. Supplier sites and Bank accounts data are as follows AP_SUPPLIERS_INT IBY_TEMP_EXT_BANK_ACCTS. the ‘Supplier Open Interface Import’ program is run for inserting the data in the R12 tables. Importing bank account along with supplier site for an existing Supplier.oracle. Prerequisite Cash management owns the setting up of Bank and Branch details. the data in the column VENDOR_INTERFACE_ID should be generated sequentially. The import program supports assigning Supplier bank accounts at Supplier or at Supplier Site level only.3. Importing Supplier bank accounts The data to be imported is to be inserted in the interface tables first. c) Importing the bank accounts for Employee type Supplier The detailed steps for each of the scenarios have been mentioned below. Importing the bank account at Supplier level along with Supplier data Please follow the below mentioned steps for importing the bank account at supplier level. Please refer to the Cash management’s white paper on Public APIs for further details 3. ii. Step 1 – Insert the Suppliers data in the interface table AP_SUPPLIERS_INT.com/docs/cd/B40089_05/current/acrobat/120aprg. Importing bank account at site along with supplier and site details. After inserting the data in the interface tables. This is the unique identifier for records in this table The column AP_SUPPLIERS_INT. 3. AP_SUPPLIER_SITES_INT Please refer to the Oracle Payables Reference guide (http://download.VENDOR_INTERFACE_ID is used to link the supplier with the respective site or bank account details.1.pdf) for further details on the tables. The bank account details cannot be imported individually. Step 2 – While inserting the data in the table AP_SUPPLIERS_INT. While importing the external bank accounts data. The main interface tables used for importing Suppliers. After creating the supplier or supplier site. . The following scenarios are covered in this document – a) Importing the bank account at Supplier level along with Supplier data b) Importing the bank account at site level along with Supplier and Supplier site i. An important point to be noted with regard to the supplier bank accounts – the bank accounts data related to the suppliers can only be imported along with the supplier or supplier site. the Bank and Branch details should have been imported in the relevant tables. the bank account can only be added from the user interface.

Step 6 – Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’.Payables. The following screen is displayed. Step 3 – The bank account details should be inserted in the interface table IBY_TEMP_EXT_BANK_ACCTS Step 4 – While inserting the data in the table IBY_TEMP_EXT_BANK_ACCTS. . Step 7 – Select ‘Single Request’ and select ‘OK’ button.CALLING_APP_UNIQUE_APP_REF1 should be updated with the value from its corresponding suppliers AP_SUPPLIERS_INT. After inserting the data in the tables AP_SUPPLIERS_INT and IBY_TEMP_EXT_BANK_ACCTS the data is ready to be imported. the value for the column ‘Status’ should be updated as ‘NEW’ (case sensitive) in both the tables.View of the selecting the new request screen . Figure 1. as the bank account data is being assigned at supplier level. the column IBY_TEMP_EXT_BANK_ACCTS.The sequence AP_SUPPLIERS_INT_S is used to generate the sequential number.VENDOR_INTERFACE_ID Step 5 – While inserting the data in IBY_TEMP_EXT_BANK_ACCTS and AP_SUPPLIERS_INT.

Figure 2 View of the program parameters screen. . Step 8 – In the request name. search and select the program with name ‘Supplier Open Interface Step 9 – Navigate to the parameters LOV and select the options based on the imported data.

select the option ‘New’.Figure 3. select the option ‘Rejected’. . Default value is ‘No’ and can be modified to ‘Yes’. Step 11 – Parameters: Print exceptions only indicate whether the log file should contain only the exception details. select the option ‘All’. Step 14 – Import options LOV: Default value is ‘All’. Step 13 – Parameters: Trace switch indicate whether the trace file of the program should be generated. Step 12 – Parameters: Debug switch indicate whether the log file should contain the debug details. Default value is ‘No’ and can be modified to ‘Yes’. If the program is run to import only the rejected transactions of the earlier run. If the program is to import only the records with the status ‘New’. If the request program is to import all the records in the table.View of the parameters LOV. The default value is 1000 and can be modified. Default value is ‘No’ and can be modified to ‘Yes’. Step 10 – Parameters: Batch size indicates the number of records to be imported in one import program.

Step 16 – The program ‘Supplier Open Interface Import’ automatically calls the ‘Create external bank account’ (IBY_EXT_BANKACCT_PUB. If a record is not imported due to any error.CREATE_EXT_BANK_ACCT) program and imports the bank accounts data related to the supplier. the field will be updated as ‘REJECTED’. . navigate to the ‘View requests’ screen. On successful import of the records the column ‘Status’ will be updated from ‘NEW’ to ‘PROCESSED’.Figure 4. Step 17 – To track the status of the request program.View of the parameters – Import options Step 15 – Select ‘Submit’ button.

View of the Requests status screen Step 18 – When the Phase column shows ‘Completed’ and the status column shows ‘Normal’. select the ‘View Output’ button to know the number of records that have been imported.Figure 5 . .

PARTY_ID). IBY_PMT_INSTR_USES_ALL: For every external bank account created. . a record is inserted in this table. This table also holds relationship between External Payee and External Bank Account Note: 2) While importing the bank account along with the supplier. In other words bank account will be created without the bank and branch if Bank_id and Branch_id is not inserted in IBY_TEMP_EXT_BANK_ACCTS table and FOREIGN_PAYMENT_USE_FLAG is ‘No’. IBY_EXTERNAL_PAYEES_ALL: A record is created in this table with Payee id (equivalent to HZ_PARTIES. IBY_EXT_BANK_ACCOUNTS: A record is inserted in this table with the bank account details provided in IBY_TEMP_EXT_BANK_ACCTS. 3) Bank account can be created without bank and branch details if the bank is not used for making international payments. the supplier data will only be created without the bank details. following IBY Tables are being populated.Figure 6 -Requests screen showing the phase as ‘Completed’ and status as ‘Normal’. Step 19 – Select the ‘View Log’ button to go through the error messages if any. if there is some error in the bank account details. After Successful import of Supplier/Supplier Site with the bank account details.

VENDOR_SITE_INTERFACE_ID. The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing Bank accounts details at supplier level. Importing the bank account at site level along with Supplier and Supplier site While importing the bank details for a supplier site. VENDOR_INTERFACE_ID is used to link the supplier with the respective site details Step 3 – While inserting data in the table AP_SUPPLIER_SITES_INT. AP_SUPPLIER_ SITES_INT and IBY_TEMP_EXT_BANK_ACCTS the data is ready to be imported. . b) Importing bank account along with supplier site for an existing Supplier. The additional interface table for storing the supplier sites data is AP_SUPPLIER_SITES_INT.3. VENDOR_SITE_INTERFACE_ID helps in linking the bank details with its corresponding Supplier site.1. This is the unique identifier for records in this table In the scenario.VENDOR_INTERFACE_ID Step 4 – Insert the bank account details in the interface table IBY_TEMP_EXT_BANK_ACCTS.CALLING_APP_UNIQUE_APP_REF2 should be updated with AP_SUPPLIER_SITES_INT. After inserting the data in the tables AP_SUPPLIERS_INT. Step 5 – As the bank account data is being assigned at supplier site level. Importing Bank account at site along with supplier and site details. 3.VENDOR_INTERFACE_ID should be filled in with the respective suppliers record value of the AP_SUPPLIER_INT. while inserting the data in the table IBY_TEMP_EXT_BANK_ACCTS. the column IBY_TEMP_EXT_BANK_ACCTS. AP_SUPPLIER_ SITES_INT and IBY_TEMP_EXT_BANK_ACCTS. there are two scenarios – a) Importing bank account at site along with supplier and site details. Step 2 – While inserting the data in the table AP_SUPPLIERS_INT. Step 6 – While inserting the data in AP_SUPPLIERS_INT.3. Step 1 – Insert the data in the AP_SUPPLIERS_INT and AP_SUPPLIER_SITES_INT. the column AP_SUPPLIER_SITES_INT. Step 7 – Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’ screen and run the program with name ‘Supplier Open Interface Import’.3. the value for the column ‘Status’ should be updated as ‘NEW’. the data in the column VENDOR_INTERFACE_ID should be generated sequentially.

Step 2 – While inserting the data in the AP_SUPPLIER_SITES_INT.3. After inserting the data in the tables AP_SUPPLIER_ SITES_INT and IBY_TEMP_EXT_BANK_ACCTS the data is ready to be imported. . The column VENDOR_ID is used to link the supplier with the respective Supplier site details.2. the value for the column ‘Status’ should be updated as ‘NEW’.3. the column VENDOR_ID should be updated with the respective supplier for which the supplier site is being created. The field AP_SUPPLIER_ SITES_INT is used to link the supplier site with the respective bank account details. Step 6 – Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’ screen and run the program with name ‘Supplier Sites Open Interface Import’. Step 3 – The bank account details should be inserted in the interface table IBY_TEMP_EXT_BANK_ACCTS. Importing bank account along with supplier site for an existing Supplier The interface table for storing the supplier sites data is AP_SUPPLIER_SITES_INT and the bank account data is IBY_TEMP_EXT_BANK_ACCTS.4. Importing the bank accounts for Employee type Supplier External bank account can be imported for Employee type suppliers while importing the supplier data for the employee. Prerequisite Employee record should have been created in the HR. The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing Bank accounts details at supplier level. while inserting the data in the IBY_TEMP_EXT_BANK_ACCTS the column ‘CALLING_APP_UNIQUE_APP_REF2’ should be updated with the respective VENDOR_SITE_INTERFACE_ID. Step 5 – While inserting the data in AP_SUPPLIER_ SITES_INT and IBY_TEMP_EXT_BANK_ACCTS. Step 4 – As the bank account data is being assigned at supplier site level. 3. Step 1 – Insert the data in the AP_SUPPLIER_SITES_INT.

AP_SUPPLIER_SITES_INT.VENDOR_SITE_INTERFACE_ID. Step 7 – Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’ screen and run the program with name ‘Supplier Open Interface Import’. Step 1 – Insert the data in the AP_SUPPLIERS_INT. VENDOR_SITE_INTERFACE_ID helps in linking the bank details with its corresponding Supplier site. supplier site and the bank account details remain the same . the AP_SUPPLIER_SITES_INT. Step 3 – Insert the data in the AP_SUPPLIER_SITES_INT. while inserting the data in the table IBY_TEMP_EXT_BANK_ACCTS. The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing Bank accounts details at supplier level. Step 6 – As the bank account data is being assigned at supplier site level. Step 5 – Insert the bank account details in the interface table IBY_TEMP_EXT_BANK_ACCTS. the AP_SUPPLIER_INT. AP_SUPPLIER_SITES_INT and IBY_TEMP_EXT_BANK_ACCTS respectively. .The interface tables for storing the supplier.CALLING_APP_UNIQUE_APP_REF2 should be updated with AP_SUPPLIER_SITES_INT.EMPLOYEE_ID should be updated with employee Id and VENDOR_TYPE_LOOKUP_CODE should be updated as ‘EMPLOYEE’. Step 2 – As the data is inserted for an employee type of supplier. Step 4 – As the data is imported for an employee type supplier. the column IBY_TEMP_EXT_BANK_ACCTS.VENDOR_SITE_CODE should be updated as ‘HOME’ or ‘OFFICE’ or ‘PROVISIONAL’ (please note that values are case sensitive and should be given in capitals).

RA_CUSTOMERS_INTERFACE_ALL Step 2 – While inserting the data in the table RA_CUSTOMERS_INTERFACE_ALL. Step 1 – Insert the Customer data in the interface table .pdf) and TCA User guide (http://download. The Customer Interface program validates the data that is loaded in Customer Interface tables by ensuring that the columns in the interface tables reference the appropriate values and columns in the rest of the system. This column forms part of primary key. The detailed steps for each of the scenarios have been mentioned below. the ‘Customer Interface’ program should be submitted for inserting the data in the Oracle base tables. Sites.4. Importing the bank account at Customer account level ii.oracle.1. After inserting the data in the customer interface tables. party information. . Please follow the below mentioned steps for importing the bank account at customer account level for a new customer.com/docs/cd/B40089_05/current/acrobat/120hzug. The following scenarios are covered in this document – a) Importing bank account at Customer account level along with Customer account b) Importing bank account at site level along with Customer account and Customer site c) Importing the bank account for an existing customer i. 4.pdf) for further details on the tables. Profiles and Bank accounts data are as follows RA_CUSTOMERS_INTERFACE_ALL RA_CUSTOMER_BANKS_INTERFACE RA_CUSTOMER_PROFILES_INT_ALL RA_CUST_PAY_METHOD_INTERFACE RA_CONTACT_PHONES_INTERFACE Please refer to the R12 TCA Reference guide (http://download. profile and site information should be successfully imported first before bank account information is inserted. the bank accounts can be imported for the new customers and sites as well as customers and customer sites existing in the system.com/docs/cd/B40089_05/current/acrobat/120hzrg. Process of importing Customer banks The bank accounts for customers can be imported at customer account level or customer site level or for the existing customers. Using the Customer interface program. The main interface tables used for importing Customer accounts.ORIG_SYSTEM_CUSTOMER_REF should be inserted with a value that uniquely identifies the customer in the original system.oracle. Importing bank account at Customer account level along with Customer account To import customer bank account information for new customers that are getting created by using customer interface program. party customer account. the data in the column RA_CUSTOMERS_INTERFACE_ALL. Importing the bank account at Customer site level.

Country.Submit new request screen view – Receivables. the column RA_CUSTOMER_BANKS_INTERFACE. The following screen is displayed. Figure 7.The column. Step 6 – Select ‘Single Request’ radio button and select ‘OK’ button. as the bank account is to be assigned at customer account level. City. As the site is not being created now. Note: The data in the table RA_CUSTOMERS_INTERFACE_ALL is used to import customer and customer sites as well.ORIG_SYSTEM_CUSTOMER_REF is used to link the customer with the respective profile and bank account details. ORIG_SYSTEM_CUSTOMER_REF should be updated with the value from its corresponding customers interface RA_CUSTOMERS_INTERFACE_ALL. The following screen is displayed. Step 3 – Insert the Customer bank account data in the interface table RA_CUSTOMER_BANKS_INTERFACE Step 4 – While inserting the data in the table RA_CUSTOMER_BANKS_INTERFACE. the data need not be provided for the address columns like Original system address reference.ORIG_SYSTEM_CUSTOMER_REF. RA_CUSTOMERS_INTERFACE_ALL. Step 5 – Navigate to the Receivables >> Control: Requests >> Run. etc. Postal code. .

Step 7 – In the request name. .Figure 8 View of the Standard Request submission – parameters selection screen. search and select the program with name ‘Customer Interface’.

If the user does not provide any value. the customer accounts will be automatically created for all the operating units for which the user has the access. the Operating unit field is optional. User is navigated back to the request submission screen. select ‘OK’ button. Step 10 – After selecting the parameters. The LOV displays the operating units that the user has access to. .Figure 9 Customer Import – Parameters screen view Step 8 – Select ‘yes’ or ‘No’ based on the requirement in the ‘Create Reciprocal Customer Accounts’ Default option will be ‘No’. Step 9 – In the parameters screen.

View of the request submission screen after selecting the program name and the parameters. Step 11 – Select the ‘Submit’ button to start the import program. Step 12 – To track the status of the request program. navigate to the ‘View requests’ screen.Figure 10 . .

After Successful import of Customer/Customer Site with the bank account details. following IBY Tables are being populated. IBY_EXTERNAL_PAYEES_ALL: A record is created in this table with Payee id (equivalent to HZ_PARTIES. it indicates that the import process has been completed successfully.Figure 11 . IBY_EXT_BANK_ACCOUNTS: A record is inserted in this table with the bank account details provided in IBY_TEMP_EXT_BANK_ACCTS.View of the Requests status screen. Step 14 – Select the ‘View Log’ button to go through the error messages if any. the customer account will only be imported without the bank account. If there is an exception while inserting the bank account due to error in bank account data.PARTY_ID). Step 13 – If the Phase column shows ‘Completed’ and the status column shows ‘Normal’. Step 15 – Select the ‘View Output’ button to go through the number of records that have been successfully inserted. The bank account will be assigned at the Customer account level. .

This table also holds relationship between External Payee and External Bank Account 4. Importing the bank account for an existing customer Bank accounts can be imported for an existing customer. After inserting the data in the tables RA_CUSTOMERS_INTERFACE_ALL. Step 3 – Insert the Bank details data in the interface table . ORIG_SYSTEM_ADDRESS_REF. the column RA_CUSTOMER_BANKS_INTERFACE. and RA_CUSTOMER_BANKS_INTERFACE the data is ready to be imported The other steps for running the Customer interface program is similar to the steps followed for importing the bank account at customer account level.RA_CUSTOMER_BANKS_INTERFACE Here there can be two scenarios – 1) Importing the bank account at Customer account level.ORIG_SYSTEM_ADDRESS_REF is used to link the customer with the respective profile and bank account details at site level. as the bank account data is being assigned at customer account level. a record is inserted in this table. .RA_CUSTOMER_BANKS_INTERFACE Step 4 – While inserting the data in the table RA_CUSTOMER_BANKS_INTERFACE. RA_CUSTOMERS_INTERFACE_ALL. provide the data for the address fields in the RA_CUSTOMERS_INTERFACE_ALL. Please follow the below mentioned steps for importing the bank account for an existing customer.IBY_PMT_INSTR_USES_ALL: For every external bank account created. the column ORIG_SYSTEM_ADDRESS_REF should also be inserted for uniquely identifying the address record. A customer account and site is also created as per the details given and the bank account will be assigned at the site level. Note: As the customer site needs to be created. Importing bank account at site level along with Customer account and Customer site Step 1 – Insert the Customer data in the interface table .RA_CUSTOMERS_INTERFACE_ALL Step 2 – As the bank account is imported at site level. Insert the Bank details data in the interface table .2. ORIG_SYSTEM_ADDRESS_REF should be updated with the value from its corresponding customers RA_CUSTOMERS_INTERFACE_ALL. 2) Importing the bank account at Customer site level.3. The column. 4.

The other steps for importing the data remain the same. The other steps for importing the data remain the same.4. 4. Run the ‘Customer Interface’ program to import the data. The ‘Customer Interface’ program is run to import the data.ORIG_SYSTEM_REFERENCE The HZ_CUST_ACCT_SITES_ALL. as the bank account is imported for an existing customer.ORIG_SYSTEM_REFERENCE The HZ_CUST_ACCOUNTS.ORIG_SYSTEM_REFERENCE should be updated with the HZ_CUST_ACCT_SITES_ALL. the column RA_CUSTOMER_BANKS_INTERFACE.ORIG_SYSTEM_REFERENCE will link the bank account data that is imported at the Customer account site level.ORIG_SYSTEM_REFERENCE will link the bank account data that is imported at the Customer account level.1 Importing the bank account at Customer account level Step 1 – Insert the Bank details data in the interface table RA_CUSTOMER_BANKS_INTERFACE Step 2 – While inserting the data in the RA_CUSTOMER_BANKS_INTERFACE.3.2 Importing the bank account at Customer site level Step 1 – Insert the Bank details data in the interface table RA_CUSTOMER_BANKS_INTERFACE Step 2 – While inserting the data in the RA_CUSTOMER_BANKS_INTERFACE. the column RA_CUSTOMER_BANKS_INTERFACE. .ORIG_SYSTEM_REFERENCE should be updated with the HZ_CUST_ACCOUNTS.3. as the bank account is imported for an existing customer.

AP_SUPPLIER_SITES_INT holds Supplier Site information that is loaded by the user for import. . Optional Columns You can use some columns in the interface tables to import additional invoice information for the invoices created by Payables Open Interface Import. NOT NULL Columns You must enter values for all NOT NULL columns in the interface tables to successfully save your bank account data in the interface tables. Rejections If an invalid value is encountered when the concurrent process is evaluating each row. In addition to checks done at the database level for correct data types. the validations performed by the Suppliers Open Interface Import program are intended to emulate the processing done by the Supplier Entry form. Internal ID Columns These columns contain values that Payables uses internally and the user never sees. which help in importing the data. Table description The columns have the following attributes. You can obtain these values only by looking in Payables tables.5. If you do not enter a value in a NOT NULL column. Validations As with defaults. the 'REJECT_CODE' column is populated with the relevant rejection message and the 'STATUS' is updated to 'REJECTED'. provided that the information passes the validation checks during Payables Open Interface Import. The columns in the table map to corresponding columns in the PO_VENDOR_SITES_ALL table. then you cannot save the record in the interface table. Payables use this information to create a new Supplier Site record when the Supplier Sites Open Interface Import program is submitted. Processing on that row then stops and the program moves on to the next row. These ID columns correspond to other columns in the interface table. Conditionally Required Columns Payables require you to enter values in a conditionally required column only if you have entered a value in another column on which the conditionally required column is dependent. Payables Open Interface Import imports the data that you load into these optional columns. these validations include checks performed against existing lookup values or values derived from other tables. Required Columns If you do not enter a valid value in a ‘Required’ field. then the specific record will be rejected during import.

5.COUNTRY_CODE Identifier of the bank branch for which this bank account belongs to Validation: HZ_ORGANIZATION_PROFILES.TERRITORY_CODE NOT NULL VARCHAR2(2) Destination: IBY_EXT_BANK_ACCOUNTS.1.EXT_BANK_ACCOUNT_ID NUMBER(15) Destination: None Country Code of the Bank Account Validation: FND_TERRITORIES. Destination: None Bank account Identifier of the table IBY_EXT_BANK_ACCOUNTS Validation: IBY_EXT_BANK_ACCOUNTS. A value is required in this column and this will be automatically derived from the sequence NOT NULL NUMBER(15) IBY_TEMP_EXT_BANK_ACCTS_S. This is not being used while importing the data and only used while creating bank from supplier UI.PARTY_ID NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS. Validation: HZ_ORGANIZATION_PROFILES. Name Table Description . This is not being used while importing the data and only used while creating branch from supplier UI VARCHAR2(30) Null TEMP_EXT_BANK_ACCT_ID EXT_BANK_ACCOUNT_ID COUNTRY_CODE BRANCH_ID BANK_ID BANK_NAME BANK_NUMBER BANK_NAME_ALT BANK_INSTITUTION_TYPE BANK_ADDRESS_ID BRANCH_NUMBER BRANCH_TYPE . VARCHAR2(80) This is not being used while importing the data and only used while creating VARCHAR2(30) bank from supplier UI This is not being used while importing the data and only used while creating VARCHAR2(80) bank from supplier UI. Validation and Destination This is the unique identifier for records in this table. NUMBER(15) This is not being used while importing the data and only used while creating VARCHAR2(30) branch from supplier UI. This is not being used while importing the data and only used while creating bank from VARCHAR2(80) supplier UI.BANK_ID This is not being used while importing the data and only used while creating bank from supplier UI. This field must be populated in the interface table to assign the bank account to the bank.BRANCH_ID NUMBER(15) The Bank Identifier for which the bank account is being created. Bank Institution type of the Bank Account (Bank or Clearing House).PARTY_ID Destination: IBY_EXT_BANK_ACCOUNTS.IBY_TEMP_EXT_BANK_ACCTS Type and Length Description.

BANK_ACCOUNT_NAME Number of the Bank Account. Validation: None VARCHAR2(50) Destination: IBY_EXT_BANK_ACCOUNTS.CURRENCY_CODE International Bank Account Number of the bank account.CHECK_DIGITS Alternate Name for Bank Account. Validation: None VARCHAR2(80) Destination: IBY_EXT_BANK_ACCOUNTS. OWNER_PRIMARY_FLAG Name of the Bank account. Validation: HZ_PARTIES. when there is more than one owner for the Bank Account.IBAN Check Digits for the Bank Account Validation: None VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS.BANK_ACCOUNT_NUM & VARCHAR2(100) IBY_EXT_BANK_ACCOUNTS. Validation: None Destination: IBY_EXT_BANK_ACCOUNTS.BRANCH_NAME BRANCH_NAME_ALT VARCHAR2(80) VARCHAR2(80) This is not being used while importing the data and only used while creating branch from supplier UI This is not being used while importing the data and only used while creating branch from supplier UI This is not being used while importing the data and only used while creating branch from supplier UI BIC RFC_IDENTIFIER BANK_CODE VARCHAR2(30) This is not being used while importing the data and only used while creating branch from supplier UI This is not being used while importing the data and only used while creating VARCHAR2(100) branch from supplier UI This is not being used while importing the data and only used while creating branch from supplier UI NUMBER(15) This field is populated after creating a record in the TCA party table.LOOKUP_TYPE = 'YES/NO' VARCHAR2(1) Destination: IBY_EXT_BANK_ACCOUNTS. Validation: FND_LOOKUP_VALUES.BANK_ACCOUNT_NUM_ELECTRONIC Currency Code for the Bank Account Validation: FND_CURRENCIES.CURRENCY_CODE VARCHAR2(15) Destination: IBY_EXT_BANK_ACCOUNTS. Country Specific Validations are applicable VARCHAR2(320) on this field in particular for the Country Japan VARCHAR2(30) BRANCH_ADDRESS_ID ACCOUNT_OWNER_PARTY_ID OWNER_PRIMARY_FLAG BANK_ACCOUNT_NAME BANK_ACCOUNT_NUM CURRENCY_CODE IBAN CHECK_DIGITS BANK_ACCOUNT_NAME_ALT .PARTY_ID Destination: None NUMBER(15) Indicates Primary owner of the Bank Account.

‘CHECKING’. BANK_ACCOUNT_TYPE Account Suffix for the Bank Account Validation: None VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS. DATE automatically update by application as NULL.LOOKUP_TYPE = 'YES/NO' VARCHAR2(1) Destination: IBY_EXT_BANK_ACCOUNTS Flag that indicates whether to use this bank account for foreign payment Validation: FND_LOOKUP_VALUES.EXCHANGE_RATE_AGREEMENT_TYPE Applicable Exchange Rate for Bank Account Validation: None NUMBER Destination: IBY_EXT_BANK_ACCOUNTS.ACCOUNT_SUFFIX Free text field to enter the description of the Bank Account. Validations: None Destination: IBY_EXT_BANK_ACCOUNTS. .AGENCY_LOCATION_CODE Indicates whether this is a payment factor bank account Validation: FND_LOOKUP_VALUES. Validation: None VARCHAR2(240) Destination: IBY_EXT_BANK_ACCOUNTS.EXCHANGE_RATE Start date of the bank account as provided by user.FOREIGN_PAYMENT_USE_FLAG VARCHAR2(1) Exchange Rate Agreement Number for the Bank Account Validation: None Destination: VARCHAR2(80) IBY_EXT_BANK_ACCOUNTS.START_DATE DATE End date of the bank account as provided by user. ‘SAVINGS’. BANK_ACCOUNT_NAME_ALT Indicates the type of Bank Account Ex. automatically update by application to system date. Validation: None VARCHAR2(25) Destination: IBY_EXT_BANK_ACCOUNTS. If no value is provided.EXCHANGE_RATE_AGREEMENT_NUM Exchange Rate Agreement Type for the Bank Account Validation: None Destination: VARCHAR2(80) IBY_EXT_BANK_ACCOUNTS.BANK_ACCOUNT_TYPE ACCOUNT_SUFFIX DESCRIPTION AGENCY_LOCATION_CODE PAYMENT_FACTOR_FLAG FOREIGN_PAYMENT_USE_FLAG EXCHANGE_RATE_AGREEMENT_NUM EXCHANGE_RATE_AGREEMENT_TYPE EXCHANGE_RATE START_DATE END_DATE Validation: None Destination: IBY_EXT_BANK_ACCOUNTS.LOOKUP_TYPE = 'YES/NO' Destination: IBY_EXT_BANK_ACCOUNTS. etc.DESCRIPTION Agency Location Code for the Bank Account Validation: None VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS. If no value is provided.

END_DATE This is the descriptive flexfield category for the descriptive flexfield information for the Bank Account Validation: None Destination: IBY_EXT_BANK_ACCOUNTS. the structure of the information entered (data types.ATTRIBUTE_CATEGORY This is not used during import program This is not used during import program. After the Suppliers Open Interface Import Program is run.ATTRIBUTE [1-15] STATUS VARCHAR2(30) This column indicates the status of the record in the table. The user should enter 'NEW' (Case sensitive) as the initial value for this column. successfully imported records will be marked as 'PROCESSED' and records that are not imported will be marked as 'REJECTED'. However. Validation: None Destination: IBY_EXT_BANK_ACCOUNTS. The import process will not validate the information entered in these columns. This is the descriptive flexfield information for the External Bank Account. value sets) must match the structure of the descriptive flexfield segments defined for suppliers or users will experience validation problems when trying to access the information through the application.ATTRIBUTE_CATEGORY NOTE NOTE_ALT VARCHAR2(150) VARCHAR2(240) VARCHAR2(240) ATTRIBUTE1 ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) Validations: None Destination: IBY_EXT_BANK_ACCOUNTS. Validation: None .

LAST_UPDATE_DATE NOT NULL LAST_UPDATED_BY NOT NULL CREATION_DATE NOT NULL CREATED_BY NOT NULL LAST_UPDATE_LOGIN REQUEST_ID PROGRAM_APPLICATION_ID PROGRAM_ID PROGRAM_UPDATE_DATE OBJECT_VERSION_NUMBER NOT NULL CALLING_APP_UNIQUE_REF1 CALLING_APP_UNIQUE_REF2 EXT_PAYEE_ID Destination: None Last updated date of the bank account details. This is automatically filled by the application with the system date.VENDOR_INTERFACE_ID VARCHAR2(100) Destination: None This column should be populated if Bank Account is to be created at Supplier site level. Validations: None NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS. NUMBER(15) This is not used during import program.CREATED_BY The user who has created the bank account. Validations: None Destination: IBY_EXT_BANK_ACCOUNTS. VENDOR_INTERFACE_ID.LAST_UPDATE_DATE DATE User who has last updated the bank account details. NUMBER(15) This is not used during import program. VENDOR_SITE_INTERFACE_ID should be of the supplier site that exists in AP_SUPPLIER_SITES_INT Table and is to be imported. Validations: None Destination: IBY_EXT_BANK_ACCOUNTS. This is automatically filled by the application with the system date. Validation: AP_SUPPLIERS_INT.VENDOR_SITE_INTERFACE_ID VARCHAR2(100) Destination: None NUMBER(15) The import program automatically populates this field by referring to External . Validations: None Destination: IBY_EXT_BANK_ACCOUNTS.CREATION_DATE DATE The user who has created the bank account. This is automatically filled by the application with the user Id. Validations: None NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS. NUMBER(15) This is not used during import program.LAST_UPDATE_BY Creation date of the bank. Validations: None NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS. This is automatically filled by the application with the user Id. DATE This is automatically filled by the application with the value 1 (one).LAST_UPDATE_BY NUMBER(15) This is not used during import program. should be of the supplier that exists in AP_SUPPLIERS_INT Table and is to be imported. Validation: AP_SUPPLIER_SITES_INT.OBJECT_VERSION_NUMBER This column should be populated if Bank Account is to be created at Supplier level. This is automatically filled by the application with the user Id.

Validation and Destination Enter the value that represents the customer for which you are inserting bank information. Use the Banks window to define banks and bank accounts for your customers. This column is required. Type and Length Name ORIG_SYSTEM_CUSTOMER_REF ORIG_SYSTEM_ADDRESS_REF REQUEST_ID INTERFACE_STATUS VALIDATED_FLAG BANK_ACCOUNT_NAME NOT NULL .EXT_PAYEE_ID Destination: None 5. Validation: IBY_EXTERNAL_PAYEES_ALL.ACCT_SITE_USE_ID This column is used by Customer Interface.CUST_ACCOUNT_ID Enter the value that represents the customer address for which you are inserting bank information. An active Bill-To business purpose must be associated with this address. Validation: None Destination: None NUMBER(15) This column is used by Customer Interface and should be left null. This column is required. Validation: None VARCHAR2(240) Destination: None This column is used by Customer Interface.Payee Created for the supplier. Validation: None Destination: None VARCHAR2(1) Enter the bank account name to assign to a customer or Bill-To address. and should be left null. and should be left null. the Customer Interface program updates this column with multiple error codes. Validation: The customer reference must exist in HZ_CUST_ACCOUNTS or be successfully validated in RA_CUSTOMERS_INTERFACE. If an interface record has several problems. Validation: For insert. VARCHAR2(240) Destination: IBY_EXTERNAL_PAYERS_ALL. The Customer Interface program updates this column with all error messages that apply to this interface record. This column is required only if you want to insert bank information for a specific Bill-To address. the address reference must exist in HZ_CUST_ACCT_SITES_ALL or be successfully validated in RA_CUSTOMERS_INTERFACE (derived from ORIG_SYSTEM_CUSTOMER_REF) VARCHAR2(240) Destination: IBY_EXTERNAL_PAYERS_ALL. Customer Interface will try to create VARCHAR2(25) it in AP_BANK_ACCOUNTS. If the bank account has not already been defined. Table and Field description – RA_CUSTOMER_BANKS_INTERFACE Null NOT NULL Description.2. This indicates that the External Bank Account is created and is assigned to the External Payee.

BANK_ACCOUNT_NAME Indicates whether this is the primary bank account for this customer or Bill-To address. This column is required. BANK_NAME. Validation: End Date cannot be before the start date. BANK_ACCOUNT_NUM. Must be a valid date format.PRIMARY_FLAG NOT NULL START_DATE NOT NULL END_DATE ATTRIBUTE_CATEGORY ATTRIBUTE1 ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 Validation: Must exist in AP_BANK_ACCOUNTS or. This column is optional.END_DATE DATE() Enter Descriptive Flexfield category information. Validation: Enter 'Y' or 'N.START_DATE Enter the date that this bank account becomes inactive. Customers can be assigned to multiple bank accounts as long as there is no overlapping date range. values must exist for BANK_ACCOUNT_CURRENCY_CODE. DATE() Destination: IBY_PMT_INSTR_USES_ALL. This column is optional. This column is optional. Validation: None VARCHAR2(30) Destination: AP_BANK_ACCOUNT_USES. Validation: End Date cannot be before the start date. Destination: IBY_PMT_INSTR_USES_ALL.ATTRIBUTE1-15 VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) . Customers can be assigned to multiple bank accounts as long as there is no overlapping date range.ORDER_OF_PREFERENCE VARCHAR2(1) Enter the starting date that this bank account becomes active. Validation: None VARCHAR2(150) Destination: AP_BANK_ACCOUNT_USES. Destination: IBY_PMT_INSTR_USES_ALL. if it does not exist. Must be a valid date format.ATTRIBUTE_CATEGORY Enter Descriptive Flexfield information. This column is required. and BANK_BRANCH_NAME.' Only one primary bank account can exist at either the customer level or address level. Destination: IBY_EXT_BANK_ACCOUNTS.

do not enter a value.PARTY_NAME Enter the name of the bank branch for the account you are inserting. Bank_Branch_Name is mandatory when the bank account is not defined. this column is optional. If the bank account already exists. you must enter a value. Validation: None VARCHAR2(35) Destination: HZ_PARTIES. you must enter a value. If the bank account already exists.BANK_ACCOUNT_NUM VARCHAR2(15) Destination: IBY_EXT_BANK_ACCOUNTS. Validation: None VARCHAR2(240) Destination: IBY_EXT_BANK_ACCOUNTS. do not enter a value. If the bank account already exists.BRANCH_NUMBER Enter a description for this bank branch. If the bank account does not exist.MISSION_STATEMENT Enter the street address for this bank branch. VARCHAR2(60) Destination: HZ_PARTIES. Validation: Must be unique. This number must be unique within a bank branch.CURRENCY_CODE Enter the date that this bank account becomes inactive. do not enter a value if the bank account does not exist. This column is optional. VARCHAR2(60) Destination: HZ_PARTIES. This column is optional. This column is optional. depending on the column you choose.PARTY_NAME Enter the number of the bank Branch associated with the bank account.ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 BANK_ACCOUNT_NUM VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) Enter the account number or currency code for this bank account. Validation: Must be a valid date format.DESCRIPTION Enter the name of the bank for the account you are inserting. VARCHAR2(25) Destination: HZ_ORGANIZATION_PROFILES. DATE Destination: IBY_EXT_BANK_ACCOUNTS. This column is optional. Validation: BANK_NAME together with BANK_BRANCH_NAME must be unique. Validation: None VARCHAR2(240) Destination: HZ_PARTIES. If the bank account does not exist. Validation: None VARCHAR2(35) Destination: HZ_PARTIES. Validation: BANK_NAME together with BANK_BRANCH_NAME must be unique. If the bank account does not exist.ADDRESS_LINE2 BANK_ACCOUNT_CURRENCY_CODE BANK_ACCOUNT_INACTIVE_DATE BANK_ACCOUNT_DESCRIPTION BANK_NAME BANK_BRANCH_NAME BANK_NUM BANK_BRANCH_DESCRIPTION BANK_BRANCH_ADDRESS1 BANK_BRANCH_ADDRESS2 .END_DATE Enter a description for this bank account. This column is optional. Validation: If the bank account already exists. you must enter a value. do not enter a value.ADDRESS_LINE1 Enter the street address for this bank branch. VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS.

Validation: None Destination: HZ_PARTIES. Validation: Must exist in FND_TERRITORIES.BANK_BRANCH_ADDRESS3 BANK_BRANCH_CITY BANK_BRANCH_STATE BANK_BRANCH_ZIP BANK_BRANCH_PROVINCE BANK_BRANCH_COUNTRY BANK_BRANCH_AREA_CODE BANK_BRANCH_PHONE BANK_ACCOUNT_ATT_CATEGORY BANK_ACCOUNT_ATTRIBUTE1 BANK_ACCOUNT_ATTRIBUTE10 BANK_ACCOUNT_ATTRIBUTE11 BANK_ACCOUNT_ATTRIBUTE12 BANK_ACCOUNT_ATTRIBUTE13 BANK_ACCOUNT_ATTRIBUTE14 BANK_ACCOUNT_ATTRIBUTE15 BANK_ACCOUNT_ATTRIBUTE2 Enter the street address for this bank branch. This column is optional.PROVINCE Enter the country for this bank branch. Validation: None VARCHAR2(20) Destination: HZ_PARTIES. Validation: None VARCHAR2(25) Destination: HZ_PARTIES. Validation: None VARCHAR2(10) Destination: HZ_CONTACT_POINTS.ATTRIBUTE1-15 VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) .CITY. This column is optional.TERRITORY_CODE. Validation: None VARCHAR2(35) Destination: HZ_PARTIES.ZIP Enter the province for this bank branch. Validation: None VARCHAR2(15) Destination: HZ_CONTACT_POINTS. This column is optional.PHONE_AREA_CODE Enter the telephone number for this bank branch This column is optional.COUNTRY Enter the telephone area code for this bank branch. This column is optional. This column is optional.ATTRIBUTE_CATEGORY Enter Descriptive Flexfield information.PHONE_NUMBER Enter Descriptive Flexfield category information. Validation: None VARCHAR2(25) Destination: HZ_PARTIES. These columns are optional.STATE Enter the postal code for this bank branch. This column is optional. This column is optional.ADDRESS_LINE3 Enter the city for this bank branch. This column is optional. Validation: None VARCHAR2(150) Destination: AP_BANK_ACCOUNTS. Validation: None VARCHAR2(30) Destination: AP_BANK_ACCOUNTS. VARCHAR2(25) Destination: HZ_PARTIES. VARCHAR2(25) Validation: None Enter the state for this bank branch.

This column is optional. Validation: None NUMBER(15) Destination: None BANK_BRANCH_ATTRIBUTE1 BANK_BRANCH_ATTRIBUTE10 BANK_BRANCH_ATTRIBUTE11 BANK_BRANCH_ATTRIBUTE12 BANK_BRANCH_ATTRIBUTE13 BANK_BRANCH_ATTRIBUTE14 BANK_BRANCH_ATTRIBUTE15 BANK_BRANCH_ATTRIBUTE2 BANK_BRANCH_ATTRIBUTE3 BANK_BRANCH_ATTRIBUTE4 BANK_BRANCH_ATTRIBUTE5 BANK_BRANCH_ATTRIBUTE6 BANK_BRANCH_ATTRIBUTE7 BANK_BRANCH_ATTRIBUTE8 BANK_BRANCH_ATTRIBUTE9 LAST_UPDATE_DATE NOT NULL NOT NULL LAST_UPDATED_BY LAST_UPDATE_LOGIN . This column is optional.ATTRIBUTE1-15 VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) Enter the system date. Validation: None VARCHAR2(150) Destination: AP_BANK_BRANCHES. These columns are optional. Validation: None VARCHAR2(30) Destination: AP_BANK_BRANCHES. Validation: None Destination: None NUMBER(15) Enter the login ID. Validation: Must be a valid date format. This column is required.ATTRIBUTE_CATEGORY Enter Descriptive Flexfield information. DATE() Destination: None Enter the user ID that is updating this row. This column is required.BANK_ACCOUNT_ATTRIBUTE3 BANK_ACCOUNT_ATTRIBUTE4 BANK_ACCOUNT_ATTRIBUTE5 BANK_ACCOUNT_ATTRIBUTE6 BANK_ACCOUNT_ATTRIBUTE7 BANK_ACCOUNT_ATTRIBUTE8 BANK_ACCOUNT_ATTRIBUTE9 BANK_BRANCH_ATT_CATEGORY VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) Enter Descriptive Flexfield category information.

GET_VALID_ORG() validates that the ORG_ID is NOT NULL and is on your access list. This column is optional. This column is optional. Validation: Common Utility MO_GLOBAL.BANK_NUMBER Enter the street address for this bank branch. If the bank account already exists. Validation: None Destination: HZ_PARTIES. this column is optional. Validation: Must be unique. This column is required. Destination: HZ_ORGANIZATION_PROFILES. This column is optional. Mandatory when creating a new bank.HOME_COUNTRY . Destination: None Enter the home country code for the bank. This column is optional. do not enter a value. Destination: HZ_ORGANIZATION_PROFILES.EFT_USER_NUMBER Enter the number this bank account prints on checks. Validation: This column is validated against FND_TERRITORIES. Validation: None Destination: IBY_EXT_BANK_ACCOUNTS. Validation: None Destination: HZ_PARTIES. This column is optional. If you do not enter a value. Validation: None Destination: HZ_CONTACT_POINTS.ADDRESS_LINE4 Enter the Country for this bank branch. If the bank account does not exist.CHECK_DIGITS Enter the operating unit for which you want the Customer Interface program to validate and import customer information. Validation: Must be a valid date format. the Customer Interface program validates and imports customer information for all the operating units on your access list. This column is optional. This column is required. Destination: None Enter the user ID that is creating this row.COUNTY Enter the Electronic Funds Transfer user ID.CREATION_DATE NOT NULL DATE() NOT NULL NUMBER(15) CREATED_BY BANK_NUMBER VARCHAR2(30) BANK_BRANCH_ADDRESS4 VARCHAR2(35) BANK_BRANCH_COUNTY VARCHAR2(25) BANK_BRANCH_EFT_USER_NUMBER VARCHAR2(30) BANK_ACCOUNT_CHECK_DIGITS VARCHAR2(30) ORG_ID NUMBER(15) BANK_HOME_COUNTRY VARCHAR2(2) Enter the system date. Validation: None Destination: None Enter the number of the bank associated with the bank account.