Receivables AR

RA Tables moved to HZ tables in 11i due to TCA Evaluation.
RA_CUSTOMERS-->HZ_PARRIES, HZ_CUST_ACCOUTNS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES...

Pre 11i there were 11 tables...RA_CUSTOMERS, RA_ADDRESSES....But now in 11i these became views. Now RA_CUSTOMERS is a view which is based on HZ_PARTIES, HZ_CUST_ACCOUNTS.

One party can have multiple customer accounts. One record at HZ_PARTIES can have multiple records at HC_CUST_ACCOUNTS.

Once Party becomes customer, customer information will be stored in HZ_CUST_ACCOUNTS.

Flow of customer Interface:
Feedar System(SQL Loader)-->Staging table(Import, Mapping, Validation)-->Customer Interface(Interfaces-->Customer)-->Customer(HZ) Tables
1.RA_CUSTOMERS_INTERFACE_ALL
2.RA_CUSTOMER_PROFILES_INT_ALL
3.RA_CONTACT_PHONES_INT_ALL
4.RA_CUST_PAY_METHOD_INT_ALL
5.RA_CUSTOMER_BANKS_INT_ALL
Base tables:
All HZ Tables+4 tables(RA_CUST_RECEIPT_METHODS, AP_BANK_ACCOUNTS_ALL,AP_BANK_BRANCHES, AP_BANK_ACCOUNT_USES_ALL)

You have to consider AR Setups while doing Customer Interface:
1.Setups
2.Map the interface tables(5Above) at Import program and validations.
3.Run import program
4.Customer-->Interface
Check output for errors.

Validation errors & tips:
1.Customer Number Automatic-->Check the checkbox at System Options window.
2.Use Bulk collect so that cursor will process 10,000 records at a time
3.Make sure that you are populating correct ORG_ID in interface tables.
4.Checkout few profile options(HZ:%) which will impact Customer interface.
Auto Invoice interface:
RA_INTERFACE_LINES_ALL
RA_INTERAFCE_DISTRIBUTIONS_ALL
RA_INTERFACE_SALESCREDITS_ALL
RA_INTERFACE_ERRORS_ALL
Basetables:
RA_CUSTOMER_TRX_ALL
RA_CUSTOMER_TRX_LINES_ALL
RA_CUST_TRX_LINE_GL_DIST_ALL
RA_CUST_TRX_TYPES_ALL
Auto Lock Box:
AR_PAYMENTS_INTERFACE_ALL
Basetables:
AR_PAYMENT_SCHEDULES_ALL
AR_CASH_RECEIPTS_ALL
AR_RECEIVABLE_APPLICATIONS_ALL
Interim tables:
AR_INTERIM_CASH_RECEIPTS_ALL
AR_INTERIM_CASH_REPT_LINES_ALL
AR_INTERIM_POSTING
General Setups Needed for AR:
1.Define which are necessary to creare invoices & Receipts
Customers
Payment terms
System options
Auto Accounting
Transaction Type
Transaction Source
Lookup codes
Dff-->
Kff--> Sales tax location and Territory

Few TCA APIs:
hz_cust_account_v2pub.create_account()-->to create party and account
hz_location_v2pub.create_location()-->to create physical location
hz_party_site_v2pub.create_party_site
hz_cust_acct_site_v2pub.create_cust_acct_site()
hz_cust_acct_site_v2pub.create_cust_site_use()

Different statuses of receipts:
Unidentified-->Lack of customer information
UnApplied-->Lack of invoice info
Applied-->All information is set
On-Account-->Lack of sufficient funds

Few validations during interfaces:
1.Address: If interface table is populated by orig_system_address_ref, we should populate RA_ADDRESSES.ADDRESS1-4 fields
2.Location: Populated fields of city,county should be valid with fnd_territories table.
3.Customer Number: It should be null if automatic customer number is enabled, else it should not be null
4.Customer Status: Should be A-->Actice or I-->Inactice
5.Customer Type: Should be one of value from AR_LOOKUPS

Transaction types:
Oracle provides only invoice/credit memo trans types.
Trans type is used to default payment term,account,tax,freight and other receivable information.
Define new trans types at Receivables resp-->setup-->transactions-->transaction types
http://oracle.anilpassi.com/how-to-define-transaction-types-in-oracle-receivables.html