Friday, September 7, 2012

CUSTOMER CONVERSION IN ORACLE APPS R12 via API's - OVERVIEW



In this post, we have tried to describe the process flow of customer conversion in graphical manner and Oracle Standard API’s to load the data into R12 Target System. The methodology described here is one of the proven strategies which we used in our conversion project. This will give you an approach for your customer requirements.



Functional Setups need to be considered/verified

Below are the important entities need to be setup before running the customer conversion loading program in the target system
  1. External Banks
  2. Orig System
  3. Customer profile classes
  4. Collectors
  5. Statement cycles
  6. Grouping rules
  7. Payment terms   
  8. Dunning Letter Sets
  9. Various lookups used in party/customer account related entities


Loading Party Data - R12
In order to reduce the size of the post, we have published it in another link,

Loading Customer Account Data - R12
In order to reduce the size of the post, we have published it in another link,
http://www.shareoracleapps.com/2012/09/customer-conversion-loading-customer.html


Tables/views involved Brief Overview:

Table/View name
Purpose
AR_CUST_RECEIPT_METHODS_V
Stores the payment method information of  the customer
RA_TERMS
Contains the payment term details
AR_DUNNING_LETTER_SETS
Stores dunning letter master details
AR_STATEMENT_CYCLES
Statement cycle details
HZ_CUST_PROFILE_CLASSES
Master table for customer account profile classes
AR_COLLECTORS
Master table for collector information
AR_AUTOCASH_HIERARCHIES
Master table for hierarches details related to Lockbox program
GL_CODE_COMBINATIONS_KFV
Stores the account code combinations
HZ_PARTIES
Stores the party information
HZ_PARTY_SITES
Master table for party site
HZ_LOCATIONS
Master table for addresses
HZ_PARTY_SITES
Master table for party sites
HZ_CUST_ACCOUNTS
Master table for customer account details
HZ_CUST_ACCT_SITES_ALL
Master table for customer account sites
HZ_CUST_SITE_USES_ALL
Master table for customer account site uses
HZ_CUSTOMER_PROFILES
Master table for customer account/site profiles
HZ_CUST_PROFILE_AMTS
Master table for customer account/site profile amounts
HZ_CUST_ACCOUNT_ROLES
Master table for customer account/site contacts
HZ_ROLE_RESPONSIBILITIES
Master table for customer account/site contact responsibilities
HZ_RELATIONSHIPS
Master table for storing party relationship details
HZ_CODE_ASSIGNMENTS
Master table for party organization classifications
HZ_ORGANIZATION_PROFILES
Master table for storing the organization type party profiles
HZ_PERSON_PROFILES
Master table for storing the person type party profiles
HZ_ORG_CONTACTS
Master table for storing the organization contact details
HZ_ORG_CONTACT_ROLES
Master table for storing the organization contact roles responsibilities
HZ_CONTACT_POINTS
Master table for storing the party/party site contact point details


Query's related to Party/Customer

1. Query to Fetch Customer Payment Attribute Details and Receipt Methods

2. Query to Fetch Party,Customer, Site Details

3. Query to Fetch Customer Account Profile Details

4. Query to Fetch Customer Account Credit Card Details

5. Query to Fetch Customer Bank Account Details,


Happy Sharing!! Enjoy Learning!!!!

6 Responses to “CUSTOMER CONVERSION IN ORACLE APPS R12 via API's - OVERVIEW”

Sree said...
September 15, 2012 at 9:47 AM

Excellent Post. Thank You So Much.

regards,
Sree


Anonymous said...
November 29, 2012 at 7:59 AM

Thank you for sharing.

Venkat


Anonymous said...
May 22, 2013 at 12:19 AM

superb way of explanation


Anonymous said...
July 11, 2013 at 2:09 AM

Useful post


Anonymous said...
July 14, 2014 at 7:15 AM

thank u


Anonymous said...
May 25, 2015 at 4:01 AM

Thanks for sharing. This is excellent site.


Post a Comment

Disclaimer

The ideas, thoughts and concepts expressed here are my own. They, in no way reflect those of my employer or any other organization/client that I am associated. The articles presented doesn't imply to any particular organization or client and are meant only for knowledge Sharing purpose. The articles can't be reproduced or copied without the Owner's knowledge or permission.