Está en la página 1de 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 Author Version Change Reference

14th Aug 2009 Kondaiah Mandadi & 1.0 First draft


Anilkumar Sarada
Table of Contents
1. Introduction .............................................................................................................................................5

2. Current Process ........................................................................................................................................6

3. Importing Supplier bank accounts ..............................................................................................................7


3.1. Prerequisite ...................................................................................................................................7
3.2. Importing the bank account at Supplier level along with Supplier data ......................................................7
3.3. 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. Importing the bank accounts for Employee type Supplier .....................................................................15

4. Process of importing Customer banks ........................................................................................................17


4.1. Importing bank account at Customer account level along with Customer account ......................................17
4.2. Importing bank account at site level along with Customer account and Customer site.................................23
4.3. 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. Table Description - IBY_TEMP_EXT_BANK_ACCTS ......................................................................26
5.2. Table and Field description – RA_CUSTOMER_BANKS_INTERFACE ................................................31
Table of Figures

Figure 1- View of the selecting the new request screen - Payables...................................................8


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

Oracle supports many Open Interface Programs for importing data from any third party systems. 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.

This document helps in understanding the process of importing the external bank accounts data for customers or
suppliers.
2. Current Process

The process of importing supplier’s data has been documented in the Payables Reference Guide R12. For further
details on the supplier’s data, please refer to the Payables Reference Guide.

The process of importing customer’s data has been documented in Oracle Trading Community Architecture
Reference Guide and Oracle Trading Community Architecture User 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. Once the import data is loaded into the
interface tables, 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. For example, use SQL*Loader, SQL*Report, PL/SQL, or C to write an import program
to import data from a non-Oracle system
3. 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
Please refer to the Oracle Payables Reference guide
(http://download.oracle.com/docs/cd/B40089_05/current/acrobat/120aprg.pdf) for further details on the tables.

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.

3.1. Prerequisite
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.
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.
Figure 3- View of the parameters LOV.

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 15 –
Select ‘Submit’ button.

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.
Figure 5 - 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 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.

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

Note:

2) While importing the bank account along with the supplier, if there is some error in the bank account
details, the supplier data will only be created without the bank details.

3) Bank account can be created without bank and branch details if the bank is not used for making
international payments. 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’.
3.3. Importing the bank account at site level along with Supplier and Supplier site

While importing the bank details for a supplier site, there are two scenarios –

a) Importing bank account at site along with supplier and site details.
b) Importing bank account along with supplier site for an existing Supplier.

3.3.1. Importing Bank account at site along with supplier and site details.
The additional interface table for storing the supplier sites data is AP_SUPPLIER_SITES_INT.

Step 1 –
Insert the data in the AP_SUPPLIERS_INT and AP_SUPPLIER_SITES_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

In the scenario, 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, the column
AP_SUPPLIER_SITES_INT.VENDOR_INTERFACE_ID should be filled in with the
respective suppliers record value of the
AP_SUPPLIER_INT.VENDOR_INTERFACE_ID

Step 4 –
Insert the bank account details in the interface table IBY_TEMP_EXT_BANK_ACCTS.

Step 5 –
As the bank account data is being assigned at supplier site level, while inserting the data
in the table IBY_TEMP_EXT_BANK_ACCTS, the column
IBY_TEMP_EXT_BANK_ACCTS.CALLING_APP_UNIQUE_APP_REF2 should be
updated with AP_SUPPLIER_SITES_INT.VENDOR_SITE_INTERFACE_ID.

VENDOR_SITE_INTERFACE_ID helps in linking the bank details with its


corresponding Supplier site.

Step 6 –
While inserting the data in AP_SUPPLIERS_INT, AP_SUPPLIER_ SITES_INT and
IBY_TEMP_EXT_BANK_ACCTS, the value for the column ‘Status’ should be updated
as ‘NEW’.

After inserting the data in the tables AP_SUPPLIERS_INT, AP_SUPPLIER_


SITES_INT and IBY_TEMP_EXT_BANK_ACCTS the data is ready to be imported.

Step 7 –
Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’ screen and run
the program with name ‘Supplier Open Interface Import’.

The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing
Bank accounts details at supplier level.
3.3.2. 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.

Step 1 –
Insert the data in the AP_SUPPLIER_SITES_INT.

Step 2 –
While inserting the data in the AP_SUPPLIER_SITES_INT, the column VENDOR_ID
should be updated with the respective supplier for which the supplier site is being
created.

The column VENDOR_ID is used to link the supplier with the respective Supplier site
details.

Step 3 –
The bank account details should be inserted in the interface table
IBY_TEMP_EXT_BANK_ACCTS.

Step 4 –
As the bank account data is being assigned at supplier site 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.

The field AP_SUPPLIER_ SITES_INT is used to link the supplier site with the
respective bank account details.

Step 5 –
While inserting the data in AP_SUPPLIER_ SITES_INT and
IBY_TEMP_EXT_BANK_ACCTS, the value for the column ‘Status’ should be updated
as ‘NEW’.

After inserting the data in the tables AP_SUPPLIER_ SITES_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’ screen and run
the program with name ‘Supplier Sites Open Interface Import’.

The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing Bank
accounts details at supplier level.

3.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 interface tables for storing the supplier, supplier site and the bank account details remain the
same - AP_SUPPLIER_SITES_INT, AP_SUPPLIER_SITES_INT and
IBY_TEMP_EXT_BANK_ACCTS respectively.

Step 1 –
Insert the data in the AP_SUPPLIERS_INT.

Step 2 –
As the data is inserted for an employee type of supplier, the
AP_SUPPLIER_INT.EMPLOYEE_ID should be updated with employee Id and
VENDOR_TYPE_LOOKUP_CODE should be updated as ‘EMPLOYEE’.

Step 3 –
Insert the data in the AP_SUPPLIER_SITES_INT.

Step 4 –
As the data is imported for an employee type supplier, the
AP_SUPPLIER_SITES_INT.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).

Step 5 –
Insert the bank account details in the interface table IBY_TEMP_EXT_BANK_ACCTS.

Step 6 –
As the bank account data is being assigned at supplier site level, while inserting the data
in the table IBY_TEMP_EXT_BANK_ACCTS, the column
IBY_TEMP_EXT_BANK_ACCTS.CALLING_APP_UNIQUE_APP_REF2 should be
updated with AP_SUPPLIER_SITES_INT.VENDOR_SITE_INTERFACE_ID.

VENDOR_SITE_INTERFACE_ID helps in linking the bank details with its


corresponding Supplier site.

Step 7 –
Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’ screen and run
the program with name ‘Supplier Open Interface Import’.

The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing Bank
accounts details at supplier level.
4. 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.

After inserting the data in the customer interface tables, the ‘Customer Interface’ program should be submitted for
inserting the data in the Oracle base tables.

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.

Using the Customer interface program, the bank accounts can be imported for the new customers and sites as well
as customers and customer sites existing in the system.

The main interface tables used for importing Customer accounts, Sites, 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.oracle.com/docs/cd/B40089_05/current/acrobat/120hzrg.pdf) and TCA User guide
(http://download.oracle.com/docs/cd/B40089_05/current/acrobat/120hzug.pdf) for further details on the tables.

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. Importing the bank account at Customer account level
ii. Importing the bank account at Customer site level.

The detailed steps for each of the scenarios have been mentioned below.

4.1. 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 information, party customer account, profile and site information should
be successfully imported first before bank account information is inserted.

Please follow the below mentioned steps for importing the bank account at customer account level for a
new customer.

Step 1 –
Insert the Customer data in the interface table - RA_CUSTOMERS_INTERFACE_ALL

Step 2 –
While inserting the data in the table RA_CUSTOMERS_INTERFACE_ALL, the data in the column
RA_CUSTOMERS_INTERFACE_ALL.ORIG_SYSTEM_CUSTOMER_REF should be inserted
with a value that uniquely identifies the customer in the original system. This column forms part of
primary key.
The column, RA_CUSTOMERS_INTERFACE_ALL.ORIG_SYSTEM_CUSTOMER_REF is used
to link the customer with the respective profile and bank account details.

Note: The data in the table RA_CUSTOMERS_INTERFACE_ALL is used to import customer and
customer sites as well. As the site is not being created now, the data need not be provided for the
address columns like Original system address reference, City, Country, Postal code, etc.

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, as the bank
account is to be assigned at customer account level, the column
RA_CUSTOMER_BANKS_INTERFACE. ORIG_SYSTEM_CUSTOMER_REF should be
updated with the value from its corresponding customers interface
RA_CUSTOMERS_INTERFACE_ALL.ORIG_SYSTEM_CUSTOMER_REF.

Step 5 –
Navigate to the Receivables >> Control: Requests >> Run. The following screen is displayed.

Figure 7- Submit new request screen view – Receivables.


Step 6 –
Select ‘Single Request’ radio button and select ‘OK’ button. The following screen is displayed.
Figure 8 View of the Standard Request submission – parameters selection screen.

Step 7 –
In the request name, search and select the program with name ‘Customer Interface’.
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, the Operating unit field is optional. The LOV displays the operating
units that the user has access to. 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.
Step 10 –
After selecting the parameters, select ‘OK’ button. User is navigated back to the request
submission screen.
Figure 10 - 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 11 - View of the Requests status screen.
Step 13 –
If the Phase column shows ‘Completed’ and the status column shows ‘Normal’, it indicates that
the import process has been completed successfully.

Step 14 –
Select the ‘View Log’ button to go through the error messages if any.

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.

If there is an exception while inserting the bank account due to error in bank account data, the customer
account will only be imported without the bank account.

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.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

4.2. 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, the column ORIG_SYSTEM_ADDRESS_REF
should also be inserted for uniquely identifying the address record.

The column, RA_CUSTOMERS_INTERFACE_ALL.ORIG_SYSTEM_ADDRESS_REF is used


to link the customer with the respective profile and bank account details at site level.

Note:
As the customer site needs to be created, provide the data for the address fields in the
RA_CUSTOMERS_INTERFACE_ALL.

Step 3 –
Insert the Bank details data in the interface table - RA_CUSTOMER_BANKS_INTERFACE

Step 4 –
While inserting the data in the table RA_CUSTOMER_BANKS_INTERFACE, as the bank
account data is being assigned at customer account level, the column
RA_CUSTOMER_BANKS_INTERFACE. ORIG_SYSTEM_ADDRESS_REF should be
updated with the value from its corresponding customers
RA_CUSTOMERS_INTERFACE_ALL. ORIG_SYSTEM_ADDRESS_REF.

After inserting the data in the tables RA_CUSTOMERS_INTERFACE_ALL, 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.

A customer account and site is also created as per the details given and the bank account will be assigned
at the site level.

4.3. Importing the bank account for an existing customer

Bank accounts can be imported for an existing customer. Please follow the below mentioned steps for
importing the bank account for an existing customer.

Insert the Bank details data in the interface table - RA_CUSTOMER_BANKS_INTERFACE

Here there can be two scenarios –


1) Importing the bank account at Customer account level.
2) Importing the bank account at Customer site level.
4.3.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, as the bank
account is imported for an existing customer, the column
RA_CUSTOMER_BANKS_INTERFACE.ORIG_SYSTEM_REFERENCE should be
updated with the HZ_CUST_ACCOUNTS.ORIG_SYSTEM_REFERENCE

The HZ_CUST_ACCOUNTS.ORIG_SYSTEM_REFERENCE will link the bank


account data that is imported at the Customer account level.

The other steps for importing the data remain the same. The ‘Customer Interface’
program is run to import the data.

4.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, as the bank
account is imported for an existing customer, the column
RA_CUSTOMER_BANKS_INTERFACE.ORIG_SYSTEM_REFERENCE should be
updated with the HZ_CUST_ACCT_SITES_ALL.ORIG_SYSTEM_REFERENCE

The HZ_CUST_ACCT_SITES_ALL.ORIG_SYSTEM_REFERENCE will link the bank


account data that is imported at the Customer account site level.

The other steps for importing the data remain the same.
Run the ‘Customer Interface’ program to import the data.
5. Table description

The columns have the following attributes, which help in importing the data.

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. If you do not enter a value in a NOT NULL column, then you cannot save the record in
the interface table.

Required Columns
If you do not enter a valid value in a ‘Required’ field, then the specific record will be rejected during import.

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.

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. Payables Open Interface Import imports the data that you load into these
optional columns, provided that the information passes the validation checks during Payables Open Interface
Import.

Internal ID Columns
These columns contain values that Payables uses internally and the user never sees. You can obtain these values
only by looking in Payables tables. These ID columns correspond to other columns in the interface table.

AP_SUPPLIER_SITES_INT holds Supplier Site information that is loaded by the user for import. The columns in
the table map to corresponding columns in the PO_VENDOR_SITES_ALL table. Payables use this information to
create a new Supplier Site record when the Supplier Sites Open Interface Import program is submitted.

Validations
As with defaults, the validations performed by the Suppliers Open Interface Import program are intended to
emulate the processing done by the Supplier Entry form. In addition to checks done at the database level for correct
data types, these validations include checks performed against existing lookup values or values derived from other
tables.

Rejections
If an invalid value is encountered when the concurrent process is evaluating each row, the 'REJECT_CODE'
column is populated with the relevant rejection message and the 'STATUS' is updated to 'REJECTED'. Processing
on that row then stops and the program moves on to the next row.
5.1. Table Description - IBY_TEMP_EXT_BANK_ACCTS

Name Null Type and Length Description, Validation and Destination


This is the unique identifier for records in this table. A value is required in this
column and this will be automatically derived from the sequence
TEMP_EXT_BANK_ACCT_ID NOT NULL NUMBER(15)
IBY_TEMP_EXT_BANK_ACCTS_S.
Destination: None
Bank account Identifier of the table IBY_EXT_BANK_ACCOUNTS
Validation: IBY_EXT_BANK_ACCOUNTS.EXT_BANK_ACCOUNT_ID
EXT_BANK_ACCOUNT_ID NUMBER(15) Destination: None
Country Code of the Bank Account
Validation: FND_TERRITORIES.TERRITORY_CODE
COUNTRY_CODE NOT NULL VARCHAR2(2) Destination: IBY_EXT_BANK_ACCOUNTS.COUNTRY_CODE
Identifier of the bank branch for which this bank account belongs to
Validation: HZ_ORGANIZATION_PROFILES.PARTY_ID
BRANCH_ID NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS.BRANCH_ID
The Bank Identifier for which the bank account is being created. This field must
be populated in the interface table to assign the bank account to the bank.
Validation: HZ_ORGANIZATION_PROFILES.PARTY_ID
BANK_ID NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS.BANK_ID
This is not being used while importing the data and only used while creating
bank from supplier UI.
BANK_NAME VARCHAR2(80)
This is not being used while importing the data and only used while creating
BANK_NUMBER VARCHAR2(30) bank from supplier UI
This is not being used while importing the data and only used while creating
BANK_NAME_ALT VARCHAR2(80) bank from supplier UI.
Bank Institution type of the Bank Account (Bank or Clearing House). This is
not being used while importing the data and only used while creating bank from
BANK_INSTITUTION_TYPE VARCHAR2(80) supplier UI.
This is not being used while importing the data and only used while creating
BANK_ADDRESS_ID NUMBER(15) bank from supplier UI.
This is not being used while importing the data and only used while creating
BRANCH_NUMBER VARCHAR2(30) branch from supplier UI.
This is not being used while importing the data and only used while creating
branch from supplier UI
BRANCH_TYPE VARCHAR2(30)
This is not being used while importing the data and only used while creating
BRANCH_NAME VARCHAR2(80) branch from supplier UI
This is not being used while importing the data and only used while creating
BRANCH_NAME_ALT VARCHAR2(80) branch from supplier UI
This is not being used while importing the data and only used while creating
branch from supplier UI
BIC VARCHAR2(30)
This is not being used while importing the data and only used while creating
RFC_IDENTIFIER VARCHAR2(30) branch from supplier UI
This is not being used while importing the data and only used while creating
BANK_CODE VARCHAR2(100) branch from supplier UI
This is not being used while importing the data and only used while creating
branch from supplier UI
BRANCH_ADDRESS_ID NUMBER(15)
This field is populated after creating a record in the TCA party table.
Validation: HZ_PARTIES.PARTY_ID
ACCOUNT_OWNER_PARTY_ID NUMBER(15) Destination: None
Indicates Primary owner of the Bank Account, when there is more than one
owner for the Bank Account.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO'
OWNER_PRIMARY_FLAG VARCHAR2(1) Destination: IBY_EXT_BANK_ACCOUNTS. OWNER_PRIMARY_FLAG
Name of the Bank account.
Validation: None
BANK_ACCOUNT_NAME VARCHAR2(80) Destination: IBY_EXT_BANK_ACCOUNTS. BANK_ACCOUNT_NAME
Number of the Bank Account.
Validation: None
Destination: IBY_EXT_BANK_ACCOUNTS.BANK_ACCOUNT_NUM &
BANK_ACCOUNT_NUM VARCHAR2(100) IBY_EXT_BANK_ACCOUNTS.BANK_ACCOUNT_NUM_ELECTRONIC
Currency Code for the Bank Account
Validation: FND_CURRENCIES.CURRENCY_CODE
CURRENCY_CODE VARCHAR2(15) Destination: IBY_EXT_BANK_ACCOUNTS.CURRENCY_CODE
International Bank Account Number of the bank account.
Validation: None
IBAN VARCHAR2(50) Destination: IBY_EXT_BANK_ACCOUNTS.IBAN
Check Digits for the Bank Account
Validation: None
CHECK_DIGITS VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS.CHECK_DIGITS
Alternate Name for Bank Account, Country Specific Validations are applicable
BANK_ACCOUNT_NAME_ALT VARCHAR2(320) on this field in particular for the Country Japan
Validation: None
Destination: IBY_EXT_BANK_ACCOUNTS.
BANK_ACCOUNT_NAME_ALT
Indicates the type of Bank Account Ex. ‘SAVINGS’, ‘CHECKING’, etc.
Validation: None
BANK_ACCOUNT_TYPE VARCHAR2(25) Destination: IBY_EXT_BANK_ACCOUNTS. BANK_ACCOUNT_TYPE
Account Suffix for the Bank Account
Validation: None
ACCOUNT_SUFFIX VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS.ACCOUNT_SUFFIX
Free text field to enter the description of the Bank Account.
Validation: None
DESCRIPTION VARCHAR2(240) Destination: IBY_EXT_BANK_ACCOUNTS.DESCRIPTION
Agency Location Code for the Bank Account
Validation: None
AGENCY_LOCATION_CODE VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS.AGENCY_LOCATION_CODE
Indicates whether this is a payment factor bank account
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO'
PAYMENT_FACTOR_FLAG VARCHAR2(1) Destination: IBY_EXT_BANK_ACCOUNTS
Flag that indicates whether to use this bank account for foreign payment
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO'
Destination:
FOREIGN_PAYMENT_USE_FLAG VARCHAR2(1) IBY_EXT_BANK_ACCOUNTS.FOREIGN_PAYMENT_USE_FLAG
Exchange Rate Agreement Number for the Bank Account
Validation: None
Destination:
EXCHANGE_RATE_AGREEMENT_NUM VARCHAR2(80) IBY_EXT_BANK_ACCOUNTS.EXCHANGE_RATE_AGREEMENT_NUM
Exchange Rate Agreement Type for the Bank Account
Validation: None
Destination:
EXCHANGE_RATE_AGREEMENT_TYPE VARCHAR2(80) IBY_EXT_BANK_ACCOUNTS.EXCHANGE_RATE_AGREEMENT_TYPE
Applicable Exchange Rate for Bank Account
Validation: None
EXCHANGE_RATE NUMBER Destination: IBY_EXT_BANK_ACCOUNTS.EXCHANGE_RATE
Start date of the bank account as provided by user. If no value is provided,
automatically update by application to system date.
Validations: None
START_DATE DATE Destination: IBY_EXT_BANK_ACCOUNTS.START_DATE
End date of the bank account as provided by user. If no value is provided,
END_DATE DATE automatically update by application as NULL.
Validations: None
Destination: IBY_EXT_BANK_ACCOUNTS.END_DATE
This is the descriptive flexfield category for the descriptive flexfield information
for the Bank Account
Validation: None
ATTRIBUTE_CATEGORY VARCHAR2(150) Destination: IBY_EXT_BANK_ACCOUNTS.ATTRIBUTE_CATEGORY
NOTE VARCHAR2(240) This is not used during import program
NOTE_ALT VARCHAR2(240) This is not used during import program.
This is the descriptive flexfield information for the External Bank Account. The
import process will not validate the information entered in these columns.
However, the structure of the information entered (data types, 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.
Validation: None
ATTRIBUTE1 VARCHAR2(150) Destination: IBY_EXT_BANK_ACCOUNTS.ATTRIBUTE [1-15]
ATTRIBUTE2 VARCHAR2(150)
ATTRIBUTE3 VARCHAR2(150)
ATTRIBUTE4 VARCHAR2(150)
ATTRIBUTE5 VARCHAR2(150)
ATTRIBUTE6 VARCHAR2(150)
ATTRIBUTE7 VARCHAR2(150)
ATTRIBUTE8 VARCHAR2(150)
ATTRIBUTE9 VARCHAR2(150)
ATTRIBUTE10 VARCHAR2(150)
ATTRIBUTE11 VARCHAR2(150)
ATTRIBUTE12 VARCHAR2(150)
ATTRIBUTE13 VARCHAR2(150)
ATTRIBUTE14 VARCHAR2(150)
ATTRIBUTE15 VARCHAR2(150)
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. After the Suppliers
Open Interface Import Program is run, successfully imported records will be
marked as 'PROCESSED' and records that are not imported will be marked as
'REJECTED'.
STATUS VARCHAR2(30) Validation: None
Destination: None
Last updated date of the bank account details. This is automatically filled by the
application with the system date.
Validations: None
LAST_UPDATE_DATE NOT NULL DATE Destination: IBY_EXT_BANK_ACCOUNTS.LAST_UPDATE_DATE
User who has last updated the bank account details. This is automatically filled
by the application with the user Id.
Validations: None
LAST_UPDATED_BY NOT NULL NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS.LAST_UPDATE_BY
Creation date of the bank. This is automatically filled by the application with
the system date.
Validations: None
CREATION_DATE NOT NULL DATE Destination: IBY_EXT_BANK_ACCOUNTS.CREATION_DATE
The user who has created the bank account. This is automatically filled by the
application with the user Id.
Validations: None
CREATED_BY NOT NULL NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS.CREATED_BY
The user who has created the bank account. This is automatically filled by the
application with the user Id.
Validations: None
LAST_UPDATE_LOGIN NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS.LAST_UPDATE_BY
REQUEST_ID NUMBER(15) This is not used during import program.
PROGRAM_APPLICATION_ID NUMBER(15) This is not used during import program.
PROGRAM_ID NUMBER(15) This is not used during import program.
PROGRAM_UPDATE_DATE DATE This is not used during import program.
This is automatically filled by the application with the value 1 (one).
Validations: None
OBJECT_VERSION_NUMBER NOT NULL NUMBER(15) Destination: IBY_EXT_BANK_ACCOUNTS.OBJECT_VERSION_NUMBER
This column should be populated if Bank Account is to be created at Supplier
level. VENDOR_INTERFACE_ID, should be of the supplier that exists in
AP_SUPPLIERS_INT Table and is to be imported.
Validation: AP_SUPPLIERS_INT.VENDOR_INTERFACE_ID
CALLING_APP_UNIQUE_REF1 VARCHAR2(100) Destination: None
This column should be populated if Bank Account is to be created at Supplier
site level. VENDOR_SITE_INTERFACE_ID should be of the supplier site that
exists in AP_SUPPLIER_SITES_INT Table and is to be imported.
Validation: AP_SUPPLIER_SITES_INT.VENDOR_SITE_INTERFACE_ID
CALLING_APP_UNIQUE_REF2 VARCHAR2(100) Destination: None
EXT_PAYEE_ID NUMBER(15) The import program automatically populates this field by referring to External
Payee Created for the supplier. This indicates that the External Bank Account is
created and is assigned to the External Payee.
Validation: IBY_EXTERNAL_PAYEES_ALL.EXT_PAYEE_ID
Destination: None

5.2. Table and Field description – RA_CUSTOMER_BANKS_INTERFACE

Name Null Type and Length Description, Validation and Destination


ORIG_SYSTEM_CUSTOMER_REF NOT Enter the value that represents the customer for which you are inserting bank
NULL information. This column is required.
Validation: The customer reference must exist in HZ_CUST_ACCOUNTS or
be successfully validated in RA_CUSTOMERS_INTERFACE.
VARCHAR2(240) Destination: IBY_EXTERNAL_PAYERS_ALL.CUST_ACCOUNT_ID
ORIG_SYSTEM_ADDRESS_REF 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. This column is required only if you want to insert bank
information for a specific Bill-To address.
Validation: For insert, 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.ACCT_SITE_USE_ID
REQUEST_ID This column is used by Customer Interface, and should be left null.
Validation: None
NUMBER(15) Destination: None
INTERFACE_STATUS This column is used by Customer Interface and should be left null. The
Customer Interface program updates this column with all error messages that
apply to this interface record. If an interface record has several problems, the
Customer Interface program updates this column with multiple error codes.
Validation: None
VARCHAR2(240) Destination: None
VALIDATED_FLAG This column is used by Customer Interface, and should be left null.
Validation: None
VARCHAR2(1) Destination: None
BANK_ACCOUNT_NAME NOT Enter the bank account name to assign to a customer or Bill-To address. Use the
NULL Banks window to define banks and bank accounts for your customers. If the
bank account has not already been defined, Customer Interface will try to create
VARCHAR2(25) it in AP_BANK_ACCOUNTS. This column is required.
Validation: Must exist in AP_BANK_ACCOUNTS or, if it does not exist,
values must exist for BANK_ACCOUNT_CURRENCY_CODE,
BANK_ACCOUNT_NUM, BANK_NAME, and BANK_BRANCH_NAME.
Destination: IBY_EXT_BANK_ACCOUNTS.BANK_ACCOUNT_NAME
PRIMARY_FLAG NOT Indicates whether this is the primary bank account for this customer or Bill-To
NULL address. This column is required.
Validation: Enter 'Y' or 'N.' Only one primary bank account can exist at either
the customer level or address level.
VARCHAR2(1) Destination: IBY_PMT_INSTR_USES_ALL.ORDER_OF_PREFERENCE
START_DATE NOT Enter the starting date that this bank account becomes active. This column is
NULL required.
Validation: End Date cannot be before the start date. Customers can be
assigned to multiple bank accounts as long as there is no overlapping date range.
Must be a valid date format.
DATE() Destination: IBY_PMT_INSTR_USES_ALL.START_DATE
END_DATE Enter the date that this bank account becomes inactive. This column is optional.
Validation: End Date cannot be before the start date. Customers can be
assigned to multiple bank accounts as long as there is no overlapping date range.
Must be a valid date format.
DATE() Destination: IBY_PMT_INSTR_USES_ALL.END_DATE
ATTRIBUTE_CATEGORY Enter Descriptive Flexfield category information. This column is optional.
Validation: None
VARCHAR2(30) Destination: AP_BANK_ACCOUNT_USES.ATTRIBUTE_CATEGORY
ATTRIBUTE1 Enter Descriptive Flexfield information. This column is optional.
Validation: None
VARCHAR2(150) Destination: AP_BANK_ACCOUNT_USES.ATTRIBUTE1-15
ATTRIBUTE2 VARCHAR2(150)
ATTRIBUTE3 VARCHAR2(150)
ATTRIBUTE4 VARCHAR2(150)
ATTRIBUTE5 VARCHAR2(150)
ATTRIBUTE6 VARCHAR2(150)
ATTRIBUTE7 VARCHAR2(150)
ATTRIBUTE8 VARCHAR2(150)
ATTRIBUTE9 VARCHAR2(150)
ATTRIBUTE10 VARCHAR2(150)
ATTRIBUTE11 VARCHAR2(150)
ATTRIBUTE12 VARCHAR2(150)
ATTRIBUTE13 VARCHAR2(150)
ATTRIBUTE14 VARCHAR2(150)
ATTRIBUTE15 VARCHAR2(150)
BANK_ACCOUNT_NUM Enter the account number or currency code for this bank account, depending on
the column you choose. This number must be unique within a bank branch.
Validation: If the bank account already exists, do not enter a value. If the bank
account does not exist, you must enter a value.
VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS.BANK_ACCOUNT_NUM
BANK_ACCOUNT_CURRENCY_CODE VARCHAR2(15) Destination: IBY_EXT_BANK_ACCOUNTS.CURRENCY_CODE
BANK_ACCOUNT_INACTIVE_DATE Enter the date that this bank account becomes inactive. This column is optional.
Validation: Must be a valid date format.
DATE Destination: IBY_EXT_BANK_ACCOUNTS.END_DATE
BANK_ACCOUNT_DESCRIPTION Enter a description for this bank account. This column is optional.
Validation: None
VARCHAR2(240) Destination: IBY_EXT_BANK_ACCOUNTS.DESCRIPTION
BANK_NAME Enter the name of the bank for the account you are inserting. If the bank account
does not exist, you must enter a value.
Validation: BANK_NAME together with BANK_BRANCH_NAME must be
unique. If the bank account already exists, do not enter a value.
VARCHAR2(60) Destination: HZ_PARTIES.PARTY_NAME
BANK_BRANCH_NAME Enter the name of the bank branch for the account you are inserting. If the bank
account does not exist, you must enter a value.
Validation: BANK_NAME together with BANK_BRANCH_NAME must be
unique. If the bank account already exists, do not enter a value.
Bank_Branch_Name is mandatory when the bank account is not defined.
VARCHAR2(60) Destination: HZ_PARTIES.PARTY_NAME
BANK_NUM Enter the number of the bank Branch associated with the bank account.
Validation: Must be unique. If the bank account already exists, do not enter a
value if the bank account does not exist, this column is optional.
VARCHAR2(25) Destination: HZ_ORGANIZATION_PROFILES.BRANCH_NUMBER
BANK_BRANCH_DESCRIPTION Enter a description for this bank branch. This column is optional.
Validation: None
VARCHAR2(240) Destination: HZ_PARTIES.MISSION_STATEMENT
BANK_BRANCH_ADDRESS1 Enter the street address for this bank branch. This column is optional.
Validation: None
VARCHAR2(35) Destination: HZ_PARTIES.ADDRESS_LINE1
BANK_BRANCH_ADDRESS2 Enter the street address for this bank branch. This column is optional.
Validation: None
VARCHAR2(35) Destination: HZ_PARTIES.ADDRESS_LINE2
BANK_BRANCH_ADDRESS3 Enter the street address for this bank branch. This column is optional.
Validation: None
VARCHAR2(35) Destination: HZ_PARTIES.ADDRESS_LINE3
BANK_BRANCH_CITY Enter the city for this bank branch. This column is optional.
Validation: None
Destination: HZ_PARTIES.CITY.
VARCHAR2(25) Validation: None
BANK_BRANCH_STATE Enter the state for this bank branch. This column is optional.
Validation: None
VARCHAR2(25) Destination: HZ_PARTIES.STATE
BANK_BRANCH_ZIP Enter the postal code for this bank branch. This column is optional.
Validation: None
VARCHAR2(20) Destination: HZ_PARTIES.ZIP
BANK_BRANCH_PROVINCE Enter the province for this bank branch. This column is optional.
Validation: None
VARCHAR2(25) Destination: HZ_PARTIES.PROVINCE
BANK_BRANCH_COUNTRY Enter the country for this bank branch. This column is optional.
Validation: Must exist in FND_TERRITORIES.TERRITORY_CODE.
VARCHAR2(25) Destination: HZ_PARTIES.COUNTRY
BANK_BRANCH_AREA_CODE Enter the telephone area code for this bank branch. This column is optional.
Validation: None
VARCHAR2(10) Destination: HZ_CONTACT_POINTS.PHONE_AREA_CODE
BANK_BRANCH_PHONE Enter the telephone number for this bank branch This column is optional.
Validation: None
VARCHAR2(15) Destination: HZ_CONTACT_POINTS.PHONE_NUMBER
BANK_ACCOUNT_ATT_CATEGORY Enter Descriptive Flexfield category information. This column is optional.
Validation: None
VARCHAR2(30) Destination: AP_BANK_ACCOUNTS.ATTRIBUTE_CATEGORY
BANK_ACCOUNT_ATTRIBUTE1 Enter Descriptive Flexfield information. These columns are optional.
Validation: None
VARCHAR2(150) Destination: AP_BANK_ACCOUNTS.ATTRIBUTE1-15
BANK_ACCOUNT_ATTRIBUTE10 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE11 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE12 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE13 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE14 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE15 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE2 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE3 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE4 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE5 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE6 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE7 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE8 VARCHAR2(150)
BANK_ACCOUNT_ATTRIBUTE9 VARCHAR2(150)
BANK_BRANCH_ATT_CATEGORY Enter Descriptive Flexfield category information. This column is optional.
Validation: None
VARCHAR2(30) Destination: AP_BANK_BRANCHES.ATTRIBUTE_CATEGORY
BANK_BRANCH_ATTRIBUTE1 Enter Descriptive Flexfield information. These columns are optional.
Validation: None
VARCHAR2(150) Destination: AP_BANK_BRANCHES.ATTRIBUTE1-15
BANK_BRANCH_ATTRIBUTE10 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE11 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE12 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE13 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE14 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE15 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE2 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE3 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE4 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE5 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE6 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE7 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE8 VARCHAR2(150)
BANK_BRANCH_ATTRIBUTE9 VARCHAR2(150)
LAST_UPDATE_DATE NOT Enter the system date. This column is required.
NULL Validation: Must be a valid date format.
DATE() Destination: None
LAST_UPDATED_BY NOT Enter the user ID that is updating this row. This column is required.
NULL Validation: None
NUMBER(15) Destination: None
LAST_UPDATE_LOGIN Enter the login ID. This column is optional.
Validation: None
NUMBER(15) Destination: None
CREATION_DATE NOT Enter the system date. This column is required.
NULL Validation: Must be a valid date format.
DATE() Destination: None
CREATED_BY NOT Enter the user ID that is creating this row. This column is required.
NULL Validation: None
NUMBER(15) Destination: None
BANK_NUMBER Enter the number of the bank associated with the bank account.
Validation: Must be unique. If the bank account already exists, do not enter a
value. If the bank account does not exist, this column is optional.
VARCHAR2(30) Destination: HZ_ORGANIZATION_PROFILES.BANK_NUMBER
BANK_BRANCH_ADDRESS4 Enter the street address for this bank branch. This column is optional.
Validation: None
VARCHAR2(35) Destination: HZ_PARTIES.ADDRESS_LINE4
BANK_BRANCH_COUNTY Enter the Country for this bank branch. This column is optional.
Validation: None
VARCHAR2(25) Destination: HZ_PARTIES.COUNTY
BANK_BRANCH_EFT_USER_NUMBER Enter the Electronic Funds Transfer user ID. This column is optional.
Validation: None
VARCHAR2(30) Destination: HZ_CONTACT_POINTS.EFT_USER_NUMBER
BANK_ACCOUNT_CHECK_DIGITS Enter the number this bank account prints on checks. This column is optional.
Validation: None
VARCHAR2(30) Destination: IBY_EXT_BANK_ACCOUNTS.CHECK_DIGITS
ORG_ID Enter the operating unit for which you want the Customer Interface program to
validate and import customer information. This column is optional. If you do not
enter a value, the Customer Interface program validates and imports customer
information for all the operating units on your access list.
Validation: Common Utility MO_GLOBAL.GET_VALID_ORG() validates
that the ORG_ID is NOT NULL and is on your access list.
NUMBER(15) Destination: None
BANK_HOME_COUNTRY Enter the home country code for the bank. This column is optional.
Validation: This column is validated against FND_TERRITORIES.
Mandatory when creating a new bank.
VARCHAR2(2) Destination: HZ_ORGANIZATION_PROFILES.HOME_COUNTRY