Next Blog Create Blog | Sign In

SEARCH BLOG FLAG BLOG

Sunday
Customer Interface Tables
Customer Interface Table Descriptions and Validation

1- RA_CUSTOMERS_INTERFACE
This table stores customer, address, and business purpose
information. You do not have to enter values in this table if you do
not want to import customers, addresses, or business purposes.

1- ADDRESS1 through 4: Enter the address for your customer in
these four columns. You can enter up to four lines of an address.
Validation: If you enter a value in ORIG_SYSTEM_ADDRESS_REF,
you must enter a value in ADDRESS1. For multiple rows with the
same address reference, insert values in address 1-4.
Destination:
1- RA_ADDRESSES.ADDRESS1,
2- RA_ADDRESSES.ADDRESS2,
3- RA_ADDRESSES.ADDRESS3,
4- RA_ADDRESSES.ADDRESS4

2- CITY STATE PROVINCE COUNTY POSTAL_CODE COUNTRY:
Enter the city, state, province, county, and postal code for this
customer's address. You must enter values that have already been
defined in AR_LOCATION_VALUES if Address Validation is set
to 'Error' and you are calculating sales tax. You must do this for
each address component on which your tax location flexfield
structure is based.

If Address Validation is set to 'No Validation' and you pass a value
that does not exist in AR_LOCATION_VALUES, Customer Interface
inserts this value into AR_LOCATION_VALUES.
You must always enter a value for Country.
Validation: The county must exist in FND_TERRITORIES.
Destination:
RA_ADDRESSES.CITY,
home profile feed
Page 1 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html

RA_ADDRESSES.STATE,
RA_ADDRESSES.PROVINCE,
RA_ADDRESSES.COUNTY
RA_ADDRESSES.POSTAL_CODE,
RA_ADDRESSES.COUNTRY

3- ADDRESS_KEY: This column is not currently used by Customer
Interface.

4- BILL_TO_ORIG_ ADDRESS_REF: Enter the Bill-To location that
you want to associate with the Ship-To address on this record.
Validation: You can enter a value only if the SITE_USE_CODE
column in this record is 'Ship-To'. Also, the Bill-To address must
exist for this customer or any related customers.
Destination: RA_SITE_USES.BILL_TO_SITE_USE_ID

5- CUSTOMER_ ATTRIBUTE_ CATEGORY: Enter Descriptive
Flexfield category information. These columns are optional.

6- ADDRESS_ ATTRIBUTE_ CATEGORY
7- SITE_USE_ ATTRIBUTE_ CATEGORY
Validation: None
Destination:
RA_CUSTOMERS.ATTRIBUTE_CATEGORY,
RA_ADDRESSES.ATTRIBUTE_CATEGORY,
RA_SITE_USES.ATTRIBUTE_CATEGORY

8- CUSTOMER_ ATTRIBUTE_1 to 15: Enter Descriptive Flexfield
information. These columns are optional.

9- ADDRESS_ ATTRIBUTE_1 to 15
10- SITE_USE_ ATTRIBUTE_1 to 25
Validation: None
Destination:
RA_CUSTOMERS.ATTRIBUTE1 to 15,
RA_ADDRESSES.ATTRIBUTE1 to 15,
RA_SITE_USES.ATTRIBUTE1 to 25

10- CUSTOMER_ CATEGORY_CODE: Enter a category to
categorize your customer. Use customer categories that you
previously defined in the QuickCodes window. This column is
Multiple Reporting
Page 2 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
required.
Validation:
AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
= 'CUSTOMER_CATEGORY'
Destination: RA_CUSTOMERS.CUSTOMER_CATEGORY_ CODE

11-CUSTOMER_ CLASS_CODE: Enter the customer class for this
customer. Use customer classes that you previously defined in the
QuickCodes window. This column is optional.
Validation:
AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE = 'CUSTOMER
CLASS'
Destination: RA_CUSTOMERS.CUSTOMER_CLASS

12-CUSTOMER_KEY: This column is not currently used by
Customer Interface.

13-CUSTOMER_NAME: Enter the name of your customer. This
column is required.
Validation:
The same customer reference cannot have different customer
names within this table.
Destination: RA_CUSTOMERS.CUSTOMER_NAME

14- CUSTOMER_ NUMBER: Enter this customer's number.
Validation: Must be null if you are using Automatic Customer
Numbering. Must exist if you are not using Automatic Customer
Numbering. This value must be unique within RA_CUSTOMERS.
Destination: RA_CUSTOMERS.CUSTOMER_NUMBER

15- CUSTOMER_STATUS: Enter the status of this customer. This
column is required.
Validation: Must equal 'A' for Active or 'I' for Inactive.
Destination: RA_CUSTOMERS.STATUS

16- CUSTOMER_TYPE: Enter 'Internal' or 'External' to indicate
customer type for this customer. This column is optional.
Validation: AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
= 'CUSTOMER_TYPE' Multiple rows with the same customer
reference must have the same customer type.

Oracle Knowledge
Page 3 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
17- CUST_TAX_CODE SITE_USE_TAX_ CODE: Enter the tax code
that you want to assign to this customer or business purpose,
depending on the column you choose. You must use tax codes that
you previously defined in the Tax Codes and Rates window. These
columns are optional.
Validation: Must exist in AR_VAT_TAX.
Destination: RA_CUSTOMERS.TAX_CODE RA_SITE_USES.TAX_CODE

18- CUST_TAX_ EXEMPT_NUM: This column is not currently used
by Customer Interface and must be left blank.
Validation: None
Destination: None

19- CUST_TAX_ REFERENCE: Enter the tax registration number
for this customer. This column is optional.
Validation: None
Destination: RA_CUSTOMERS.TAX_REFERENCE

20- CUST_SHIP_ VIA_CODE SITE_SHIP_ VIA_CODE: Enter the
freight carrier you want to assign to this customer or business
purpose, depending on the column you choose. Use freight carriers
that you previously defined in the Freight Carriers window. This
column is optional.
Validation: Must exist in ORG_FREIGHT.
Destination: RA_CUSTOMERS.SHIP_VIA, RA_SITE_USES.SHIP_VIA

21- CREATED_BY:Enter the user id that is creating this row. This
column is required.
Validation: None
Destination: None

22- CREATION_DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

23- DEMAND_ CLASS_CODE: Enter the demand class for this
address. Use demand classes that you previously defined in the
Demand Classes window. This column is optional.
Validation: Must exist in FND_COMMON_LOOKUPS
Destination: RA_SITE_USES.DEMAND_CLASS_CODE
Page 4 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html

24- INSERT_UPDATE_ FLAG: Specify whether you are inserting a
new record or updating an existing record. This column is required.
Validation: 'I' for insert or 'U' for update.
Destination: None

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

26- LOCATION: Enter a shorthand name for this business purpose.
You use this value to quickly refer to a business purpose during
data entry.
Validation: If automatic site numbering is set to No, you must
enter a value in this column. If not, do not enter a value. Values
for this column must be unique.
Destination: RA_SITE_USES.LOCATION
[Attention: This column is not updatable.]

27- LOCATION_CCID: This column is used by Customer Interface
and should be left null. Customer Interface stores the code
combination id of valid addresses in this column.
Validation: None
Destination: None

28- LAST_UPDATED_ BY: Enter the user id that is updating this
row. This column is required.
Validation: None
Destination: None

29- LAST_UPDATE_ DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

30- LAST_UPDATE_ LOGIN: Enter the login id. This column is
optional.
Validation: None
Page 5 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
Destination: None

31- LANGUAGE: Enter the language used by this customer site.
This column is optional.
Validation: Must exist in FND_LANGUAGES.NLS_LANGUAGE
Destination: RA_ADDRESSES.LANGUAGE

32- MESSAGE_ TEXT: This column is used by Customer Interface
and should be left null.
Validation: None
Destination: None

33- ORIG_SYSTEM_ ADDRESS_REF: Enter a value you can use to
uniquely identify this address in your original system.
This column forms part of the primary key for
RA_CUSTOMERS_INTERFACE. The primary key is a combination of
ORIG_SYSTEM_CUSTOMER_REF, ORIG_SYSTEM_ADDRESS_REF, and
SITE_USE_CODE.
To enter multiple addresses for a customer, enter multiple records
in RA_CUSTOMERS_INTERFACE with identical customer
information, but with different address information.
This column is required if you are either inserting or updating
address information.
Validation: Must not already exist in RA_ADDRESSES for insert.
Must already exist in RA_ADDRESSES for update.
Destination:RA_ADDRESSES.ORIG_SYSTEM_REFERENCE

34- ORIG_SYSTEM_ CUSTOMER_REF: Enter a value that uniquely
identifies this customer in your original system.
This column forms part of the primary key for
RA_CUSTOMERS_INTERFACE. The primary key is a combination of
ORIG_SYSTEM_CUSTOMER_REF, ORIG_SYSTEM_ADDRESS_REF, and
SITE_USE_CODE.
If you are entering a new customer, you must also enter a
customer level profile in RA_CUSTOMER_PROFILES_INTERFACE.
This column is required.
Validation: Must not exist in RA_CUSTOMERS for insert. Must exist
in RA_CUSTOMERS for update. The same customer reference
cannot have different customer names within this table. Inserts
for this column must be unique.
Destination: RA_CUSTOMERS.ORIG_SYSTEM_REFERENCE
Page 6 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html

35- ORIG_SYSTEM_ PARENT_REF: Enter the original system
reference of the related customer, if there is one. If you enter a
value in this column, the system checks
RA_SYSTEM_PARAMETERS.CREATE_RECIPROCAL_FLAG to determine
whether the application should automatically create the
reciprocal relationship. If
RA_SYSTEM_PARAMETERS.CREATE_RECIPROCAL_FLAG is set to 'Y',
the system creates an additional, opposite entry in
RA_CUSTOMER_RELATIONSHIPS. This column is optional.
Validation: Must exist in RA_CUSTOMERS.
ORIG_SYSTEM_REFERENCE. Multiple rows with the same customer
reference must have the same ORIG_SYSTEM_PARENT_REF.
Destination: Inserts into RA_CUSTOMER_RELATIONSHIPS.
CUSTOMER_ID select CUSTOMER_ID from RA_CUSTOMERS where
ORIG_SYSTEM_ REFERENCE = RA_CUSTOMERS_INTERFACE.
ORIG_SYSTEM_PARENT_REF.

36- PRIMARY_SITE_ USE_FLAG: Enter 'Y' or 'N' to indicate whether
this is the primary business purpose. Enter a value in this column
only if the INSERT_UPDATE_FLAG is 'Y' and you enter a value in
ORIG_SYSTEM_ADDRESS_REF.
Validation: Must have only one primary business purpose for each
usage (Bill-To, Ship-To, etc.). Must be null, 'Y,' or 'N'. Mandatory
when inserting an address and must be null when the record is for
updating purposes. Not updateable.
Destination: RA_SITE_USES.PRIMARY_FLAG

37- REQUEST_ID: This column is used by Customer Interface and
should be left null.

38- SITE_USE_CODE: Enter the business purpose for this
customer's address. Use business purposes you previously defined
in the Receivables QuickCodes window with a QuickCode type
of 'Business purposes for a customer address.'
This column forms part of the primary key for
RA_CUSTOMERS_INTERFACE. The primary key is a combination of
ORIG_SYSTEM_CUSTOMER_REF, ORIG_SYSTEM_ADDRESS_REF, and
SITE_USE_CODE.
If you enter a value in ORIG_SYSTEM_ ADDRESS_REF, you must
enter a value in this column. To enter multiple business purposes
Page 7 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
for an address, enter multiple records in
RA_CUSTOMERS_INTERFACE with identical customer and address
information, but with different site uses. You can only assign one
type of business purpose to each address.
Validation: Must equal a value in AR_LOOKUPS. LOOKUP_CODE
where LOOKUP_TYPE = 'SITE_USE_CODE'. This column must be null
if you are updating PRIMARY_SITE_USE_FLAG, LOCATION,
SITE_SHIP_VIA_CODE, SITE_USE_TAX_CODE or
SITE_USE_TAX_REFERENCE. Inserts for this column must be unique.
Destination: RA_SITE_USES.SITE_USE_CODE

39- SITE_USE_TAX_ EXEMPT_NUM: This column is not currently
used by Customer Interface and must be left blank.
Validation: None
Destination: None

40- SITE_USE_TAX_ REFERENCE: Enter the tax registration
number for this site. This column is optional.
Validation: None
Destination: RA_SITE_USES.TAX_REFERENCE

41- VALIDATED_FLAG: This column is used by Customer Interface
and should be left null.
Destination: RA_CUSTOMERS.CUSTOMER_TYPE

42- WARNING_TEXT: This column is not currently used by
Customer Interface.

43- RA_CUSTOMER_PROFILES_INTERFACE: This table stores
customer profile information. If you are entering a new customer
in RA_CUSTOMERS_INTERFACE, you must either pass a customer
profile class that already exists or customer profile values. You do
not have to enter values in this table if you are not entering a new
customer or assigning customer profile information to customer
addresses.

ACCOUNT_STATUS: Enter the status of this customer's account.
Use account statuses you previously defined in the Receivables
QuickCodes window with a QuickCode type of 'Account Status.'
This column is optional.
Validation: AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
Page 8 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
= 'ACCOUNT_STATUS'
Destination: AR_CUSTOMER_PROFILES.ACCOUNT_STATUS

44- ATTRIBUTE_ CATEGORY , AMOUNT_ ATTRIBUTE_
CATEGORY: Enter Descriptive Flexfield category information.
These columns are optional.
Validation: None
Destination: AR_CUSTOMER_PROFILES. ATTRIBUTE_CATEGORY
AR_CUSTOMER_PROFILE_AMOUNTS. ATTRIBUTE_CATEGORY

45- ATRIBUTE 1 through 15 AMOUNT_ ATTRIBUTE 1 through 15:
Enter Descriptive Flexfield information. These columns are
optional.
Validation: None
Destination: AR_CUSTOMER_PROFILES. ATTRIBUTE1 through 15
AR_CUSTOMER_PROFILE_AMOUNTS. ATTRIBUTE1 through 15

46- AUTO_REC_INCL_ DISPUTED_FLAG: Specify whether to
include debit items that have been placed in dispute when you
create automatic receipts for your customers. Defaults to No if
null.
Validation: Must equal 'Y' (Yes) or 'N' (No)'. Mandatory when profile
class is null.
Destination: AR_CUSTOMER_PROFILES.AUTO_REC_
INCL_DISPUTED_FLAG

47- AUTOCASH_ HIERARCHY_NAME: Enter the AutoCash Rule set
to assign to this customer. Use AutoCash Rules sets that you
previously defined in the AutoCash Rule Sets window.
Validation: Must exist in AR_AUTOCASH_HIERARCHIES. Mandatory
when no profile class specified.
Destination: AR_CUSTOMER_PROFILES. AUTOCASH_HIERARCHY_ID

48- AUTO_REC_MIN_ RECEIPT_AMOUNT: Enter the minimum
receipt amount that must be specified for this customer when you
create automatic receipts in this currency. This column is optional.
Validation: None
Destination: AR_CUSTOMER_PROFILE_AMOUNTS.
AUTO_REC_MIN_RECEIPT_AMOUNT

49- CHARGE_ON_ FINANCE_ CHARGE_FLAG: Specify whether you
Page 9 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
want to compound interest for this customer.
Validation: Must equal 'Y' (Yes) or 'N' (No). Required if
INTEREST_CHARGES is set to 'Y' and no profile class is specified. Do
not enter a value if INTEREST_CHARGES is null or set to 'N'.
Destination: AR_CUSTOMER_PROFILES.CHARGE_ON_
FINANCE_CHARGE_FLAG

50- CLEARING_DAYS: Enter the number of clearing days for this
customer profile.
Validation: Must be an integer greater than or equal to zero.
Destination: AR_CUSTOMER_PROFILES.CLEARING_DAYS

51-COLLECTOR_NAME: Enter the collector assigned to this
customer profile.
Validation: Must be unique in AR_COLLECTORS and STATUS = 'A'
(Active). Mandatory when no profile class specified.
Destination: AR_CUSTOMER_PROFILES.COLLECTOR_ID (derived
from CUSTOMER_NAME)

52- CREATED_BY: Enter the user id that is creating this row. This
column is required.
Validation: None
Destination: None

53- CREATION_DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

54- CREDIT_BALANCE_ STATEMENTS: Specify whether to send
statements to customers with credit balances.
Validation: Must equal 'Y' (Yes) or 'N' (No) Must be 'N' when
STATEMENTS = 'N.' Mandatory when no profile class specified.
Mandatory when STATEMENTS = Yes. Must be null when
STATEMENTS is null.
Destination:
AR_CUSTOMER_PROFILES.CREDIT_BALANCE_STATEMENTS

55- CREDIT_HOLD: Specify whether to put a hold on your
customer's credit.
Validation: Must equal 'Y' (Yes) or 'N' (No)'.
Page 10 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
Destination: AR_CUSTOMER_PROFILES.CREDIT_HOLD

56- CREDIT_RATING: Enter the credit rating for this customer.
Use credit ratings you previously defined in the Receivables
QuickCodes window using the QuickCode Type 'Credit rating for
customers.' This column is optional.
Validation: AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
= 'CREDIT_RATING'
Destination: AR_CUSTOMER_PROFILES.CREDIT_RATING

57- CURRENCY_CODE: Enter a currency code to define customer
profile amounts for this customer. Use currency codes previously
defined in the Currencies window. Regardless of the value stored
in INSERT_UPDATE_FLAG, Customer Interface always inserts and
updates customer profile amount values you pass in this table. You
must enter a value if any one of the following columns have values:
INTEREST_RATE
MIN_DUNNING_AMOUNT
MIN_DUNNING_INVOICE_AMOUNT
MIN_FC_BALANCE_AMOUNT
MIN_FC_INVOICE_AMOUNT
MIN_STATEMENT_AMOUNT
OVERALL_CREDIT_LIMIT
TRX_CREDIT_LIMIT
Validation: Must exist in FND_CURRENCIES. Mandatory when a
profile amount value is populated. (Profile amount columns are
listed above.)
Destination: AR_CUSTOMER_PROFILE_AMOUNTS. CURRENCY_CODE

58- CUSTOMER_PROFILE_CLASS_NAME: Enter the name of the
customer profile class you want to assign to this customer or Bill-
To address.
If you enter a value in this column, the system will use the profile
values associated with this customer profile class. However, you
can override these default values by passing new values in the
appropriate columns. This column is optional.
If you do not enter a value in this column you must enter values in
the following columns:
COLLECTOR_NAME
CREDIT_BALANCE_STATEMENTS
CREDIT_CHECKING
Page 11 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
AUTO_REC_INCL_DISPUTED_FLAG
DISCOUNT_TERMS
DUNNING_LETTERS (if 'Y', you must also enter a value in
DUNNING_LETTER_SET_NAME)
INTEREST_CHARGES (if 'Y', you must also enter values in
INTEREST_PERIOD_DAYS and CHARGE_ON_FINANCE_CHARGE_FLAG.)
STATEMENTS (if 'Y', you must also enter a value in
STATEMENT_CYCLE_NAME.)
TOLERANCE
TAX_PRINTING_OPTION
OVERRIDE_TERMS
GROUPING_RULE_NAME
Validation: Must equal AR_CUSTOMER_PROFILE_CLASSES. NAME
and STATUS = 'A' (Active)
Destination: AR_CUSTOMER_PROFILES.
CUSTOMER_PROFILE_CLASS_ID (derived from
CUSTOMER_PROFILE_CLASS_NAME)

59- DISCOUNT_TERMS, CREDIT_CHECKING, DUNNING_LETTERS,
INTEREST_CHARGES, STATEMENTS: Specify whether to allow
discounts, check credit, send dunning letters, charge interest or
and send statements.
Validation: Must equal 'Y' (Yes) or 'N' (No). Mandatory when no
profile class specified.
Destination: AR_CUSTOMER_PROFILES.DISCOUNT_TERMS
AR_CUSTOMER_PROFILES.CREDIT_CHECKING
AR_CUSTOMER_PROFILES. DUNNING_LETTERS
AR_CUSTOMER_PROFILES. INTEREST_CHARGES
AR_CUSTOMER_PROFILES.STATEMENTS

60- DISCOUNT_ GRACE_DAYS: Enter the number of days after the
discount date that this customer can still take discounts.
Validation: Number must be non-negative (must be >=0). Must be
null when DISCOUNT_TERMS is null or 'No'.
Destination: AR_CUSTOMER_PROFILES.DISCOUNT_ GRACE_DAYS

61- DUNNING_LETTER_ SET_NAME: Enter the dunning letter set
to associate with this customer. Use dunning letters that you
previously defined in the Dunning Letter Sets window.
Validation: Must exist in AR_DUNNING_LETTER_SETS. Mandatory
when DUNNING_LETTERS is Yes. Must be null when
Page 12 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
DUNNING_LETTERS is No or null.
Destination: AR_CUSTOMER_PROFILES.DUNNING_ LETTER_SET_ID
(derived from DUNNING_LETTER_SET_NAME)

62- GROUPING_ RULE_NAME: Enter the grouping rule to assign to
this customer. Use grouping rules you previously defined in the
Grouping Rules window.
Validation: Must exist in RA_GROUPING_RULES. Mandatory when
no profile class is specified.
Destination: AR_CUSTOMER_PROFILES.GROUPING_ RULE_ID
(derived from GROUPING_RULE_NAME)

63- 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 which apply to this
interface record. If an interface record has several problems, the
Customer Interface program updates this column with multiple
error codes which are described later in this section.
Validation: None
Destination: None

64- INSERT_ UPDATE_FLAG: Enter a value to indicate whether
you are inserting a new record or updating an existing record.
Regardless of the value you enter in this column, you cannot insert
or update profile information in the following columns:
CURRENCY_CODE,
AUTO_REC_MIN_RECEIPT_AMOUNT,
INTEREST_RATE,
MAX_INTEREST_CHARGE,
MIN_DUNNING_AMOUNT,
MIN_DUNNING_INVOICE_AMOUNT,
MIN_FC_BALANCE_AMOUNT,
MIN_FC_INVOICE_AMOUNT,
MIN_STATEMENT_AMOUNT,
OVERALL_CREDIT_LIMIT,
TRX_CREDIT_LIMIT,
AMOUNT_ATTRIBUTE_CATEGORY and
AMOUNT_ATTRIBUTE1 through AMOUNT_ATTRIBUTE15.
If you are tying to insert new profile amount information,
Customer Interface will automatically insert this information even
if this column is set to 'U.' For example, if you want to update the
Page 13 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
tax printing option value for a record that you have already
inserted and at the same time enter a new currency code for this
customer profile, enter 'U' in this column. Customer Interface will
automatically update the tax printing option value and
automatically insert the new currency code.
This column is required.
Validation: I' for insert, 'U' for update
Destination: None

65- INTEREST_ PERIOD_DAYS: Enter the number of days to which
the interest rate refers.
Validation: Number must be positive. Mandatory when
INTEREST_CHARGES is Yes. Must be null when INTEREST_CHARGES
is No or null.
Destination: AR_CUSTOMER_PROFILES.INTEREST_ PERIOD_DAYS

66- INTEREST_RATE: Enter the interest rate to charge this
customer for this currency. This column is optional.
Validation: None
Destination: AR_CUSTOMER_PROFILE_AMOUNTS. INTEREST_RATE

67- LAST_UPDATED_ BY: Enter the user id that is updating this
row. This column is required.
Validation: None
Destination: None

68- LAST_UPDATE_ DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

69- LAST_UPDATE_ LOGIN: Enter the login id. This column is
optional.
Validation: None
Destination: None

70- MAX_INTEREST_ CHARGE: Enter the maximum amount of
interest to charge this customer in this currency for each invoice.
This column is optional.
Validation: None
Destination: AR_CUSTOMER_PROFILE_AMOUNTS.
Page 14 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
MAX_INTEREST_CHARGE

71- MIN_DUNNING_ AMOUNT: Enter the minimum amount in this
currency that must be past due for this customer before you select
these customers for dunning. This column is optional.
Validation: None
Destination: AR_CUSTOMER_PROFILE_AMOUNTS.
MIN_DUNNING_AMOUNT

72- MIN_DUNNING_ INVOICE_AMOUNT: Enter the minimum
invoice amount in this currency that must be past due for this
customer before you select these customers for dunning. This
column is optional.
Validation: None
Destination: AR_CUSTOMER_PROFILE_AMOUNTS.
MIN_DUNNING_INVOICE_AMOUNT

73- MIN_FC_BALANCE_ AMOUNT: Enter the minimum customer
balance that you require before you charge this customer finance
charges for past due items in this currency. This column is
optional.
Validation: None
Destination: AR_CUSTOMER_PROFILE_AMOUNTS.
MIN_FC_BALANCE_AMOUNT

74- MIN_FC_INVOICE_ AMOUNT: Enter the minimum invoice
balance that you require before you charge this customer finance
charges for past due items in this currency. This column is
optional.
Validation: None
Destination: AR_CUSTOMER_PROFILE_AMOUNTS.
MIN_FC_INVOICE_AMOUNT

75- MIN_STATEMENT_ AMOUNT: Enter the minimum outstanding
balance in this currency that this customer must exceed in order
for the system to generate a statement. This column is optional.
Validation: None
Destination: AR_CUSTOMER_PROFILE_AMOUNTS.
MIN_STATEMENT_AMOUNT

76- ORIG_SYSTEM_ CUSTOMER_REF: Enter the value that
Page 15 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
represents the customer or Bill-To site for which you are
inserting or updating customer profile information.
Validation: For insert, this customer reference must exist in
RA_CUSTOMERS or be successfully validated in
RA_CUSTOMERS_INTERFACE. For update, this customer reference
must exist in RA_CUSTOMERS.
Destination: AR_CUSTOMER_PROFILES.CUSTOMER_ID (Derived
from ORIG_SYSTEM_CUSTOMER_REF)

77- ORIG_SYSTEM_ ADDRESS_REF: Enter the value that
represents the customer Bill-To address for which you are
inserting or updating customer profile information. An active Bill-
To business purpose must be associated with this address.
Validation: For insert, this address reference must exist in
RA_ADDRESSES or be successfully validated in
RA_CUSTOMERS_INTERFACE. For update, this address reference
must exist in RA_ADDRESSES.
Destination: AR_CUSTOMER_PROFILES.SITE_USE_ID (derived from
ORIG_SYSTEM_ADDRESS_REF)

78- OVERALL_ CREDIT_LIMIT: Enter the total amount of credit to
give to this customer in this currency. This column is optional.
Validation: TRX_CREDIT_LIMIT and OVERALL_CREDIT_ LIMIT must
both be filled in, or both be null. TRX_CREDIT_LIMIT may not be
greater than the OVERALL_CREDIT_LIMIT.

79- OVERRIDE_TERMS: Specify whether you want to be able to
enter payment terms that are different from the payment term
you enter in STANDARD_TERM_NAME.
Validation: Must equal 'Y' (Yes) or 'N' (No). Mandatory when no
profile class is specified.
Destination: AR_CUSTOMER_PROFILES.OVERRIDE_TERMS

80- PAYMENT_ GRACE_DAYS: Enter the number of days you will
allow this customer's receipt to be overdue before you will initiate
collection action.
Validation: Number must be non-negative (must be >=0).
Destination: AR_CUSTOMER_PROFILES.PAYMENT_ GRACE_DAYS

81- PERCENT_ COLLECTABLE: Enter the percentage of this
customer's account balance that you expect to collect regularly.
Page 16 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
This column is optional.
Validation: Must be between 0 to 100.
Destination: AR_CUSTOMER_PROFILES.PERCENT_ COLLECTABLE

82- REQUEST_ID: This column is used by Customer Interface, and
should be left null.
Validation: None
Destination: None

83- RISK_CODE: Enter the risk code for this customer. Use risk
codes you previously defined in the QuickCodes window with a
QuickCode type of 'Customer credit risk.' This column is optional.
Validation: AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
= 'RISK_CODE'
Destination: AR_CUSTOMER_PROFILES.RISK_CODE

84- STANDARD_ TERM_NAME: Enter the standard payment terms
for this customer. Use payment terms that you previously defined
in the Payment Terms window. This column is optional.
Validation: Must exist in RA_TERMS. Must have a unique value.
Mandatory when no profile class is specified.
Destination: AR_CUSTOMER_PROFILES.STANDARD_ TERMS.
(derived from STANDARD_TERM_NAME)

85- STATEMENT_ CYCLE_NAME: Enter the statement cycle to
associate with this customer. Use statement cycles that you
previously defined in the Statement Cycles window.
Validation: Must exist in AR_STATEMENT_CYCLES. Must be null
when STATEMENTS is No or null. Mandatory when STATEMENTS is
Yes. Must have a unique value.
Destination: AR_CUSTOMER_PROFILES.STATEMENT_ CYCLE_ID
(derived from STATEMENT_CYCLE_NAME)

86- TAX_PRINTING_ OPTION: Enter a tax printing option to
indicate how you want to print tax information for this customer's
invoices.
Validation: AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
= 'TAX_PRINTING_OPTION'. Mandatory when no profile class
specified.
Destination: AR_CUSTOMER_PROFILES. TAX_PRINTING_OPTION

Page 17 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
87- TOLERANCE: Enter the percent over the credit limit that
this customer can exceed before you will act.
Validation: Must be between -100 and 100. Mandatory when no
profile class specified.
Destination: RA_CUSTOMER_PROFILES.TOLERANCE

88- TRX_CREDIT_ LIMIT: Enter the amount of credit for each
order that you want to give to this customer in this currency.
Validation: TRX_CREDIT_LIMIT and OVERALL_CREDIT_ LIMIT must
both be filled in, or both be null. TRX_CREDIT_LIMIT may not be
greater than the OVERALL_CREDIT_LIMIT.
Destination: AR_CUSTOMER_PROFILE_AMOUNTS. TRX_CREDIT_LIMIT

89- VALIDATED_FLAG: This column is used by Customer Interface,
and should be left null.
Validation: None
Destination: None
Destination:
AR_CUSTOMER_PROFILE_AMOUNTS. OVERALL_CREDIT_LIMIT



RA_CONTACT_PHONES_INTERFACE
This table stores telephone numbers for customers, addresses and
contacts as well as contacts for customers and addresses. You do
not have to enter values in this table if you do not want to pass
telephone or contact information.

1- CONTACT_ ATTRIBUTE_ CATEGORY,
PHONE_ ATTRIBUTE_ CATEGORY: Enter Descriptive Flexfield
category information. These columns are optional.
Validation: None
Destination: RA_CONTACTS.ATTRIBUTE_CATEGORY
RA_PHONES.ATTRIBUTE_CATEGORY

2- CONTACT_ ATTRIBUTE 1 through 25, PHONE_ ATTRIBUTE 1
through 15: Enter Descriptive Flexfield information. These
columns are optional.
Validation: None
Destination: RA_CONTACTS.ATTRIBUTE1 through 25

Page 18 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
3- CONTACT_ FIRST_NAME: Enter the contact's first name. This
column is optional.
Validation: None
Destination: RA_CONTACTS.FIRST_NAME

4- CONTACT_ JOB_TITLE: Enter the job title or responsibility for
this contact. Use contact job titles that you previously defined in
the QuickCodes window. This column is optional.
Validation: AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
= 'JOB_TITLE'
Destination: RA_CONTACTS.JOB_TITLE.

5- CONTACT_ LAST_NAME: Enter the contact's last name. If
ORIG_SYSTEM_CONTACT_REF is filled in, then you must enter a
value in this column. Otherwise, this column is optional.
Validation: None
Destination: RA_CONTACTS.LAST_NAME

6- CONTACT_TITLE: Enter the title for this contact. This column
is optional.
Validation: AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
= 'CONTACT_TITLE'
Destination: RA_CONTACTS.TITLE

7- CREATED_BY: Enter the user id that is creating this row. This
column is required.
Validation: None
Destination: None

8- CREATION_DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

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

10- INSERT_ UPDATE_FLAG: Enter a value to indicate whether
Page 19 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
you are inserting a new record or updating an existing record.
This column is required.
Validation: 'I' for insert, 'U' for update.
Destination: None

11- LAST_UPDATED_ BY: Enter the user id that is updating this
row. This column is required.
Validation: None
Destination: RA_PHONES.ATTRIBUTE1 through 15

12- LAST_UPDATE_ DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

13- LAST_UPDATE_ LOGIN: Enter the login id. This column is
optional.
Validation: None
Destination: None

14- ORIG_SYSTEM_ CUSTOMER_REF: Enter a value that you can
use to uniquely identify this customer in your original system.
Validation: Must equal RA_CUSTOMERS.ORIG_SYSTEM_ REFERENCE
for update. If you are entering either contact or telephone
information, you must enter a value in this column.
Destination: RA_CUSTOMERS.ORIG_SYSTEM_REFERENCE

15- ORIG_SYSTEM_ ADDRESS_REF: Enter a value that you can use
to uniquely identify this address in your original system.
If this column is null, the phone or contact that you enter refers to
the customer.
Validation: Must equal RA_ADDRESSES.ORIG_SYSTEM_ REFERENCE
for update. If you are entering information that refers to an
address, such as a contact or telephone, then you must enter a
value in this column.
Destination: RA_ADDRESSES.ORIG_SYSTEM_REFERENCE

16- ORIG_SYSTEM_ CONTACT_REF: Enter a value that you can
use to uniquely identify this contact in your original system.
This column forms part of the primary key for
RA_CONTACT_PHONES_ INTERFACE. The primary key is a
Page 20 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
combination of ORIG_SYSTEM_CONTACT_REF and
ORIG_SYSTEM_TELEPHONE_ REF.
To enter a contact for a customer, do not enter a value in
ORIG_SYSTEM_ ADDRESS_REF.
If you are entering a contact for a specific address, then enter
values in both ORIG_ SYSTEM_CUSTOMER_REF and
ORIG_SYSTEM_ADDRESS_REF.
Validation: Must equal RA_CONTACTS.ORIG_SYSTEM_ REFERENCE
for update. If you are entering contact information or information
that refers to a contact, such as a telephone number assigned to a
contact, you must enter a value in this column.
Destination: RA_CONTACTS.ORIG_SYSTEM_REFERENCE

17- ORIG_SYSTEM_ TELEPHONE_REF: Enter a value that you can
use to uniquely identify this telephone in your original system.
This column forms part of the primary key for
RA_CONTACT_PHONES_ INTERFACE. The primary key is a
combination of ORIG_SYSTEM_CONTACT_REF and
ORIG_SYSTEM_TELEPHONE_REF.
To enter a telephone for a customer, do not enter values in
ORIG_SYSTEM_ADDRESS_REF or ORIG_SYSTEM_CONTACT_REF.
To enter a telephone for a specific address, enter values in
ORIG_SYSTEM_CUSTOMER_REF and ORIG_SYSTEM_ADDRESS_ REF.
To enter telephones for a specific contact, enter values in
ORIG_SYSTEM_CUSTOMER_REF, ORIG_SYSTEM_CONTACT_REF, and
ORIG_SYSTEM_ADDRESS_REF, if the contact is associated with an
address.
Validation: Must equal RA_PHONES.ORIG_SYSTEM_ REFERENCE.
Mandatory when specifying telephone information.
Destination: RA_PHONES.ORIG_SYSTEM_REFERENCE

18- REQUEST_ID: This column is used by Customer Interface and
should be left null.

19- TELEPHONE: Enter the telephone number for the customer,
address, or contact.
Validation: Mandatory when specifying telephone information (for
example, if ORIG_SYSTEM_TELEPHONE_REF is filled in).
Destination: RA_PHONES.PHONE_NUMBER

20- TELEPHONE_ AREA_CODE, TELEPHONE_ EXTENSION: Enter
Page 21 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
the area code or extension for the telephone number, depending
on the column you choose. These columns are optional.
Validation: None
Destination: RA_PHONES.AREA_CODE RA_PHONES.EXTENSION

21- TELEPHONE_TYPE: Enter the type of telephone number such
as General, Fax, or Telex. Use telephone types that you previously
defined in the QuickCodes window with a QuickCode type of 'Types
of communication used in contacting customers.'
Validation: AR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE
= 'COMMUNICATION_TYPE.' Mandatory when specifying telephone
information (for example, if ORIG_SYSTEM_TELEPHONE_REF is
filled in).
Destination: RA_CONTACTS.PHONE_TYPE

22- VALIDATED_FLAG: This column is used by Customer Interface
and should be left null.



RA_CUSTOMER_BANKS_INTERFACE
This table stores bank information for a customer or for a specific
Bill-To address. You do not have to enter values in this table if you
do not want to insert or assign customer bank information. If you
associate an automatic payment method to a customer or a
customer's Bill-To business purpose, you must enter a bank
account for this customer.

1- ATTRIBUTE_ CATEGORY: Enter Descriptive Flexfield category
information. This column is optional.
Validation: None
Destination: AP_BANK_ACCOUNT_USES.ATTRIBUTE_ CATEGORY

2- ATTRIBUTE 1 through 15: Enter Descriptive Flexfield
information. This column is optional.
Validation: None
Destination: AP_BANK_ACCOUNT_USES.ATTRIBUTE 1 through 15

3- BANK_ ACCOUNT_NUM, BANK_ACCOUNT_ CURRENCY_CODE:
Enter the account number or currency code for this bank account,
depending on the column you choose. This number must be unique
Page 22 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
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.
Destination: AP_BANK_ACCOUNT.BANK_ACCOUNT_NUM
AP_BANK_ACCOUNTS.CURRENCY_CODE

4- BANK_ACCOUNT_ INACTIVE_DATE: Enter the date that this
bank account becomes inactive. This column is optional.
Validation: Must be a valid date format.
Destination: AP_BANK_ACCOUNTS.INACTIVE_DATE

5- BANK_ACCOUNT_ DESCRIPTION: Enter a description for this
bank account. This column is optional.
Validation: None
Destination: AP_BANK_ACCOUNTS.DESCRIPTION

6- BANK_ ACCOUNT_CHECK_ DIGITS: Enter the number this bank
account prints on checks. This column is optional.
Validation: None
Destination: AP_BANK_ACCOUNT.CHECK_DIGITS

7- BANK_ ACCOUNT_NAME: Enter the bank account name to
assign to this customer or Bill-To address. Use the 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 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: AP_BANK_ACCOUNTS.BANK_ACCOUNT_ NAME

8- BANK_NAME, BANK_ BRANCH_NAME: Enter the name of the
bank or 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.
Destination: AP_BANK_ACCOUNTS.BANK_NAME
AP_BANK_BRANCHES.BANK_BRANCH_NAME

Page 23 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
9- 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.
Destination: AP_BANK_BRANCHES.BANK_NUMBER

10- BANK_NUM: Enter the number of the bank branch associated
with the bank account you are inserting.
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.
Destination: AP_BANK_BRANCHES.BANK_NUM

11- BANK_BRANCH_ DESCRIPTION: Enter a description for this
bank branch. This column is optional.
Validation: None
Destination: AP_BANK_BRANCHES.DESCRIPTION

12- BANK_BRANCH_ ADDRESS 1 through 4: Enter the street
address, city, county, state, postal code, or province for this bank
branch. These columns are optional.
BANK_ BRANCH_CITY
BANK_ BRANCH_COUNTY
BANK_ BRANCH_STATE
BANK_ BRANCH_ZIP
BANK_ BRANCH_PROVINCE
Validation: None
Destination: AP_BANK_BRANCHES.ADDRESS_LINE1-3
AP_BANK_BRANCHES.CITY
AP_BANK_BRANCHES.STATE
AP_BANK_BRANCHES.ZIP
AP_BANK_BRANCHES.PROVINCE

13- BANK_ BRANCH_COUNTRY: Enter the country for this bank
branch. This column is optional.
Validation: Must exist in FND_TERRITORIES.TERRITORY_CODE.
Destination: AP_BANK_BRANCHES.COUNTRY

14- BANK_ BRANCH_PHONE : Enter the telephone number or
telephone area code for this bank branch. These columns are
Page 24 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
optional.
BANK_ BRANCH_ AREA_CODE
Validation: None
Destination: AP_BANK_BRANCHES.PHONE
AP_BANK_BRANCHES.AREA_CODE

15- BANK_BRANCH_EFT_USER_NUMBER: Enter the Electronic
Funds Transfer user id. This column is optional.
Validation: None
Destination: AP_BANK_BRANCHES.EFT_USER_NUMBER

16- BANK_ACCOUNT_ ATT_CATEGORY : Enter Descriptive
Flexfield category information. These columns are optional.
BANK_ BRANCH_ ATT_CATEGORY
Validation: None
Destination: AP_BANK_ACCOUNTS.ATTRIBUTE_ CATEGORY
AP_BANK_BRANCHES.ATTRIBUTE_CATEGORY

17- BANK_ACCOUNT_ ATTRIBUTE 1 through 15, BANK_
BRANCH_ ATTRIBUTE 1 through 15: Enter Descriptive Flexfield
information. These columns are optional.
Validation: None
Destination: AP_BANK_ACCOUNTS.ATTRIBUTE1 through 15
AP_BANK_BRANCHES.ATTRIBUTE1 through 15

18- CREATED_BY: Enter the user id that is creating this row. This
column is required.
Validation: None
Destination: None

19- CREATION_DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

20- 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.
Destination: AP_BANK_ACCOUNT_USES.END_DATE
Page 25 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html

21- 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
Destination: None

22- LAST_UPDATED_ BY: Enter the user id that is updating this
row. This column is required.
Validation: None
Destination: None

23- LAST_UPDATE_ DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

24- LAST_UPDATE_ LOGIN: Enter the login id. This column is
optional.
Validation: None
Destination: None

25- ORIG_SYSTEM_ CUSTOMER_REF: Enter the value that
represents the customer for which you are inserting bank
information. This column is required.
Validation: The customer reference must exist in RA_CUSTOMERS
or be successfully validated in RA_CUSTOMERS_INTERFACE.
Destination: AP_BANK_ACCOUNT_USES.CUSTOMER_ID (derived
from ORIG_SYSTEM_CUSTOMER_REF)

26- ORIG_SYSTEM_ ADDRESS_REF: Enter the value that represent
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
RA_ADDRESSES or be successfully validated in
RA_CUSTOMERS_INTERFACE (derived from
Page 26 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
ORIG_SYSTEM_CUSTOMER_REF)
Destination: AP_BANK_ACCOUNT_USES.CUSTOMER_SITE_USE_ID

27- PRIMARY_FLAG: Indicates whether this is the primary bank
account for this customer or Bill-To 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.
Destination: AP_BANK_ACCOUNT_USES.PRIMARY_FLAG

28- REQUEST_ID: This column is used by Customer Interface, and
should be left null.
Validation: None
Destination: None

29- START_DATE: Enter the starting date that this bank account
becomes active. This column is 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.
Destination: AP_BANK_ACCOUNT_USES.START_DATE

30- VALIDATED_FLAG: This column is used by Customer Interface,
and should be left null.
Validation: None
Destination: None


RA_CUST_PAY_METHOD_INTERFACE
This table stores payment method information for a customer or
for a specific Bill-To address. If you associate an automatic
payment method to a customer or a customer's Bill-To address, a
bank account must exist for this customer. You do not have to
enter values in this table if you do not want to assign a payment
method to a customer. You cannot insert payment methods using
Customer Interface. You must use the Payment Methods window to
create new payment methods.

1- ATTRIBUTE_ CATEGORY, ATTRIBUTE 1 through 15: Enter
Descriptive Flexfield category information. This column is optional.
Validation: None
Page 27 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
Destination: RA_CUST_RECEIPT_METHODS.
ATTRIBUTE_CATEGORY
RA_CUST_RECEIPT_METHODS.ATTRIBUTE 1 through 15

2- CREATED_BY: Enter the user id that is creating this row. This
column is required.
Validation: None
Destination: None

3- CREATION_DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

4- END_DATE: Enter the date that this payment method becomes
inactive. This column is optional.
Validation: Customers can be assigned to multiple payment
methods as long as there is no overlapping date range. Must be a
valid date format.
Destination: RA_CUST_RECEIPT_METHODS.END_DATE

5- 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
Destination: None

6- LAST_UPDATED_ BY: Enter the user id that is updating this
row. This column is required.
Validation: None
Destination: None

7- LAST_UPDATE_ DATE: Enter the system date. This column is
required.
Validation: Must be a valid date format.
Destination: None

8- LAST_UPDATE_ LOGIN: Enter the login id. This column is
optional.
Page 28 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
Validation: None
Destination: None

9- ORIG_SYSTEM_ CUSTOMER_REF: ATTRIBUTE 1 through 15:
Enter the value that represents the customer for which you are
inserting a payment method. This column is required.
Validation: The customer reference must exist in RA_CUSTOMERS
or be successfully validated in RA_CUSTOMERS_INTERFACE.
Destination: RA_CUST_RECEIPTS_METHODS. CUSTOMER_ID
(derived from ORIG_SYSTEM_CUSTOMER_REF)

10- ORIG_SYSTEM_ ADDRESS_REF: Enter the value that
represents the customer address for which you are inserting a
payment method. An active Bill-To business purpose must be
associated with this address. This column is required only if you
are inserting a payment method for a specific Bill-To address.
Validation: This address reference must exist in RA_ADDRESSES or
be successfully validated in RA_CUSTOMERS_INTERFACE.
Destination: RA_CUST_RECEIPT_METHODS.SITE_USE_ID (derived
from ORIG_SYSTEM_ADDRESS_REF)

11- PAYMENT_ METHOD_NAME: Enter the name of the payment
method that you want to assign to this customer or Bill-To
address. This column is required.
Validation: Must exist in AR_RECEIPT_METHODS.
Destination: RA_CUST_RECEIPTS_METHODS. RECEIPT_METHOD_ID
(derived from PAYMENT_METHOD_NAME)

12- PRIMARY_FLAG: Enter 'Y' or 'N' to indicate whether this is the
primary payment method for this customer or Bill-To address. This
column is required.
Validation: Only one primary payment method can exist at either
the customer level or Bill-To address level.
Destination: RA_CUST_RECEIPTS_METHODS. PRIMARY_FLAG

13- REQUEST_ID: This column is used by Customer Interface and
should be left null.
Validation: None
Destination: None

14-START_DATE: Enter the starting date that this payment
Page 29 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html
method becomes active. This column is required.
Validation: Customers can be assigned to multiple payment
methods as long as there is no overlapping date range. Must be a
valid date format.
Destination: RA_CUST_RECEIPT_METHODS.START_DATE

15- VALIDATED_FLAG: This column is used by Customer Interface
and should be left null.
Validation: None
Destination: None
Posted by Ajeet Singh at 02:06
0 comments:
Post a Comment
Home
Subscribe to: Post Comments (Atom)
Newer Post Older Post
Cargo Insurance Online
Instant Cover, Save Up to 95% Leading
Provider 866-755-6937
Page 30 of 30 Oracle Financials: Customer Interface Tables
4/23/2009 http://asoracle.blogspot.com/2007/11/customer-interface-tables.html