- OracleApps Epicenter - http://www.oracleappshub.com -
Customer Interface Vs TCA API
Posted By Sanjit Anand On October 27, 2008 @ 9:19 am In Oracle Receivable,Oracle TCA | No Comments
Customer Interface aka RACUST is a concurrent program that is responsible for the import and update of AR customer information from open interface tables to AR Customer tables. Check out the details here .
TCA Application Programming Interface (API)
TCA API's are an integrated set of PL/SQL code designed in a highly modular fashion, that are easy to understand, maintain and extend.These are modular approach defaults and validates users who enter information, defaults information not provided by the user and calls the appropriate entity handler to perform the business related tasks.
Use of the TCA APIs allows you much more control of inserts and updates over the customer interface.
EXCEPTION AND ERROR MESSAGES
What are those TCA APIs
Main categories of entities covered with ability to “create” or “update”
TCA API - Advantages
Are there load limitations for Customer Interface?
A performance problem have been experienced in RACUST in earlier releases when loading customer address/site use and profile information in batches of 15,000+records.
Customer Interface runs optimally for a maximum of up to 10000 customers in the interface tables, so distributing the customers to be entered into batches of a maximum of 10000 each is good practice.
When Running Customer Import RACUST these table get affected
In R12 , bank information is moved to other tables in that case, these table is no use.
Debugging you TCA API's
Follow these steps for debugging your TCA API's
1) Set the following profile options as mentioned below from the applications :
FND: Debug Log Enabled - Yes
FND: Debug Log Module - AR
FND: Debug Log Filename <Blank>
FND: Debug Log Level - Statement
AR: Enable Debug Message Output - Yes
2) Now, execute DBMS_APPLICATION_INFO.SET_CLIENT_INFO(&org_id);
Pass your Org_id.
3) Run this query
select value from v$parameter where name='utl_file_dir';
This will return Util File Dir returned, you need to pass the same to the following script
Just make sure you have write access to /usr/tmp and also if /usr/tmp is defined as 'utl_file_dir' using the following query
4) Then aall the arp_standard.enable_file_debug ('&util_file_dir','&log_file_name'); from your script to get the debug messages
What are the criteria for Options for RACUST or API
You can decide which options should be safer if you fullfill these checklist.
If customer import is not catering your 100% requirement , then you can combine with TCA API's update scripts for addressing business need. One such example is discussed here  .
Where I can get details
Article printed from OracleApps Epicenter: http://www.oracleappshub.com
URL to article: http://www.oracleappshub.com/accounts-receivable/customer-interface-vs-tca-api/
URLs in this post:
 here: http://www.oracleappshub.com/accounts-receivable/deep-drive-customer-interface-in-ar/
 Error code: http://www.oracleappshub.com/accounts-receivable/deep-drive-customer-interface-in-ar/#comment-1236
 Here: http://www.oracleappshub.com/account-payable/r12-supplier-bank-techno-functional-guide/
 here: http://www.oracleappshub.com/account-payable/r12-ebs-banking-model-in-demanding-and-changing-world/
 here: http://www.oracleappshub.com/accounts-receivable/dealing-with-addressee-on-customer-master/
 Trading Community Architecture (TCA) 101: http://www.oracleappshub.com/accounts-receivable/oracle-tca/trading-community-architecture-tca-101/
 TCA Customer setup in Oracle EBS: http://www.oracleappshub.com/accounts-receivable/oracle-tca/tca-customer-setup-in-oracle-ebs/
Disclaimer The opinions expressed here represent solely my own represent personal conjecture based upon experience, practice and observation and does not represent the thoughts, intentions, plans or strategies of my current & previous employers and their clients. Copyright © 2007-2010 OracleApps Epicenter. All rights reserved.