Importing Supplier bank accounts
The data to be imported is to be inserted in the interface tables first. After inserting the data in the interface tables, the ‘Supplier Open Interface Import’ program is run for inserting the data in the R12 tables.
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 account details cannot be imported individually. After creating the supplier or supplier site, the bank account can only be added from the user interface.
The supplier bank accounts can be assigned at the Supplier or Supplier Site or Address or Address Operating Unit level from the user interface. The import program supports assigning Supplier bank accounts at Supplier or at Supplier Site level only.
The main interface tables used for importing Suppliers, Supplier sites and Bank accounts data are as follows - AP_SUPPLIERS_INT IBY_TEMP_EXT_BANK_ACCTS. AP_SUPPLIER_SITES_INT
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. Importing bank account at site along with supplier and site details. ii. Importing bank account along with supplier site for an existing Supplier. c) Importing the bank accounts for Employee type Supplier
The detailed steps for each of the scenarios have been mentioned below.
Cash management owns the setting up of Bank and Branch details. While importing the external bank accounts data, the Bank and Branch details should have been imported in the relevant tables.
Please refer to the Cash management’s white paper on Public APIs for further details
3.2. 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.
Step 1 – Insert the Suppliers data in the interface table AP_SUPPLIERS_INT.
Step 2 – While inserting the data in the table AP_SUPPLIERS_INT, the data in the column VENDOR_INTERFACE_ID should be generated sequentially. This is the unique identifier for records in this table
The column AP_SUPPLIERS_INT.VENDOR_INTERFACE_ID is used to link the supplier with the respective site or bank account details.
The sequence AP_SUPPLIERS_INT_S is used to generate the sequential number.
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, as the bank account data is being assigned at supplier level, the column IBY_TEMP_EXT_BANK_ACCTS.CALLING_APP_UNIQUE_APP_ REF1 should be updated with the value from its corresponding suppliers AP_SUPPLIERS_INT.VENDOR_INTERFACE_ID
Step 5 – While inserting the data in IBY_TEMP_EXT_BANK_ACCTS and AP_SUPPLIERS_INT, the value for the column ‘Status’ should be updated as ‘NEW’ (case sensitive) in both the tables.
After inserting the data in the tables AP_SUPPLIERS_INT and IBY_TEMP_EXT_BANK_ACCTS the data is ready to be imported.
Step 6 – Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’. The following screen is displayed.
Figure 1- View of the selecting the new request screen - Payables.
Step 7 –
Select ‘Single Request’ and select ‘OK’ button.
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.
Step 10 – Parameters: Batch size indicates the number of records to be imported in one import program. The default value is 1000 and can be modified.
Step 11 – Parameters: Print exceptions only indicate whether the log file should contain only the exception details. Default value is ‘No’ and can be modified to ‘Yes’.
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’.
Step 13 – Parameters: Trace switch indicate whether the trace file of the program should be generated. Default value is ‘No’ and can be modified to ‘Yes’.
Step 14 – Import options LOV: Default value is ‘All’. If the program is to import only the records with the status ‘New’, select the option ‘New’. If the program is run to import only the rejected transactions of the earlier run, select the option ‘Rejected’. If the request program is to import all the records in the table, select the option ‘All’.
Figure 4- View of the parameters – Import options
Step 16 – The program ‘Supplier Open Interface Import’ automatically calls the ‘Create external bank account’ (IBY_EXT_BANKACCT_PUB.CREATE_EXT_BANK_ACCT) program and imports the bank accounts data related to the supplier.
On successful import of the records the column ‘Status’ will be updated from ‘NEW’ to ‘PROCESSED’. If a record is not imported due to any error, the field will be updated as ‘REJECTED’.
Step 17 – To track the status of the request program, navigate to the ‘View requests’ 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.
Step 19 – Select the ‘View Log’ button to go through the error messages if any.
After Successful import of Supplier/Supplier 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.PARTY_ID).
IBY_EXT_BANK_ACCOUNTS : A record is inserted in this table with the bank account details provided in IBY_TEMP_EXT_BANK_ACCTS.
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