Professional Documents
Culture Documents
Customer Interface AR
Customer Interface AR
"A customer is someone who makes use of or receives the products or services of an
individual or organization." Its means it is one who become a entity in your business
world, irrespective of your line of business. If you are manufacturer the customer is one
to whom you provide the product and get the money or services for which your get paid.
Time to time the customer definition has been changed and now in today economy it can
be redefined as:
Typical information required for any customer is address, contact, bank , profile,class.
Oracle standard form does have more than 8 tabs which hold most of the information. A
typical flow of customer setup in Oracle is as;
Customer Interface is a oracle seeded tool that is used to import and validate current or
historical customer information from other systems into Receivables. Once customer
information is imported into the system, you can use Customer Interface to import
additional data for that customer (such as additional contacts or addresses) and to update
existing information. This is yet another options to enter Customer information other than
manually update and enter new information using the Customer windows.
If you are coming from some old version, if have been noticed few things has been
changed:
• Customer tables have changed, to move customer in TCA model, it means
o The HZ tables
o The role of Parties
Note:Added in order to track prospective customers Due to CRM
integration and adds “benefit†of having all customer
“groups†stored in one location.
The Change
Here is significant changes has been noticed from pre 11i and r11i version.
FIND screen
Customer screen
Customer Tables
The following diagram shows how customer information is imported into the customer
tables.
Here is summarize information for interface Vs base table. Once Customer Import get
completed successfully , the data moved to these tables:
Please take a note, the bank model has been changed in r12, this will have till 11.5.10.2.
If you are looking for R12 , refer to trm guide.
• Be sure to set up new data in Receivables that the Customer Interface should
import. For example:
o AutoCash Rule Sets
o AutoInvoice Grouping Rules
o Collectors
o Customer Addresses
o Customer Bank Information
o Customer Exemptions
o Customer Profile Classes
o Demand Classes
o Dunning Letter Sets
o Freight Carriers
o Payment Methods
o Payment Terms
o Statement Cycles
o Tax Codes
• Be sure to also set up Lookups in Receivables that the Customer Interface should
import. These are the lookups:
o Countries
o Site Use Codes
o Credit Ratings
o Risk Codes
o Account Statuses
o Communication Types
o Customer Classes
• RA_CUSTOMER_INTERFACE_ALL
o ORIG_SYSTEM_CUSTOMER_REF
o CUSTOMER_NAME
o CUSTOMER_STATUS
o INSERT_UPDATE_FLAG
o CUSTOMER_NUMBER
o ORIG_SYSTEM_ADDRESS_REF
o PRIMARY_SITE_USE_FLAG
o SITE_USE_CODE
o ADDRESS1
o COUNTRY
o LOCATION
• RA_CUSTOMER_PROFILES_INT_ALL
o CUSTOMER_PROFILE_CLASS_NAME
o ORIG_SYSTEM_CUSTOMER_REF
o INSERT_UPDATE_FLAG
o CREDIT_HOLD
o ORIG_SYSTEM_ADDRESS_REF
• RA_CONTACT_PHONES_INT_ALL
o ORIG_SYSTEM_CUSTOMER_REF
o ORIG_SYSTEM_TELEPHONE_REF
o TELEPHONE
o TELEPHONE_TYPE
o INSERT_UPDATE_FLAG
o ORIG_SYSTEM_ADDRESS_REF
o ORIG_SYSTEM_CONTACT_REF
o CONTACT_LAST_NAME
• RA_BANKS_INTERFACE
o ORIG_SYSTEM_CUSTOMER_REF
o PRIMARY_FLAG
o START_DATE
o BANK_ACCOUNT_NAME
oBANK_ACCOUNT_CURRENCY_CODE
oBANK_ACCOUNT_NUM
oBANK_BRANCH_NAME
oORIG_SYSTEM_ADDRESS_REF
• RA_CUST_PAY_METHOD_INTERFACE
o ORIG_SYSTEM_CUSTOMER_REF
o START_DATE
o PAYMENT_METHOD_NAME
o PRIMARY_FLAG
o ORIG_SYSTEM_ADDRESS_REF
From R11 and 11i, you cannot change the sequence via the forms and therefore any
change that you make to the sequence would have to be
through SQLPlus and that would not be supported.
3. When doing Migration from other system, adviced to use TRIM Function
• When loading interface tables remove all trailing spaces from import data.
Example: LTRIM(RTRIM(customer_name))
4.If importing large number of customers, run in smaller batches instead of all at
once.
Oracle benchmark is about 10,000 records per batch is ideal, it is suggested to keep the
batch size small.
5.When rolling out in Multi-Org , then you must populate the org_IDs in the
interface tables and run the customer interface for each organization set-up
responsiblity.