TCA

Key Features

INDEX
Introduction TCA Overview Data Model Technicalities Application Program Interfaces Literature

Introduction
Objective:
To explain the features and technicalities of Trading Community Architecture (TCA).

Assumption:
Oracle EBS 11i TCA model is explained in this exercise along with corresponding 12i features and extensions.

TCA Overview
TCA:
Trading Community Architecture is a data model designed to enable critical data exchange between various components of Oracle EBS and Third party Applications.

Stake holding Components:

1) 2) 3)

ERP CRM E Business Suite

In 11i EBS, the Customer data is maintained at global level and shared between ERP and CRM for better and faster access of Customer data.

TCA: Customer Base Data Model

HZ_LOCATIONS

Location_id

Party_id

HZ_PARTIES

Party_id

HZ_CUST_ACCOUNTS

HZ_PARTY_SITES

PARTY_SITE_ID

HZ_CUST_ACCOUNT_SITES

HZ_PARTY_SITE_USES

HZ_CUST_ACCT_SITE_USES

CUST_ACC_SITE_ID

PARTY_SITE_ID

CUST_ACC_ID

Technicalities
Bulk Import Customer Interface Third party Data Integration Party Merge Customer Merge(12i) Resource Manager(12i) Application Program Interfaces

Bulk Import
Loading Data into the Interface Tables Import Batch to TCA Registry Import Batch De-Duplication Report Import Process Import Address Validation Matching Records with Source System Management Import Validations Post import Processes Resolving Import Errors TCA Import Batch Purge

Customer Interface
We can use Customer Interface to import current or historical customer info from other systems into database.

RA_CUSTOMERS_INTERFACE: Mandatory columns

1) ORG_ID 2) ORIG_SYSTEM_CUSTOMER_REF 3) INSERT_UPDATE_FLAG 4) CUSTOMER_NAME 5) CUSTOMER_NUMBER (if you are not using Automatic Customer Numbering) 6) CUSTOMER_STATUS 7) PRIMARY_SITE_USE_FLAG (if you are inserting an address) 8) LOCATION (if you are not using Automatic Site Numbering) 9) SITE_USE_CODE (if you are inserting an address) 10) ADDRESS1 11) Who columns

Base Tables Impacted by Customer Interface:

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17) 18) HZ_CONTACT_POINTS HZ_CUST_ACCT_RELATE_ALL HZ_CUST_ACCT_ROLES HZ_CUST_ACCT_SITES_ALL HZ_CUST_ACCOUNTS HZ_CUST_PROFILE_AMTS RA_CUST_RECEIPT_METHODS HZ_CUST_SITE_USES_ALL HZ_CUSTOMER_PROFILES HZ_LOCATIONS HZ_ORG_CONTACTS HZ_PARTIES HZ_PARTY_SITES HZ_PARTY_SITE_USES HZ_PERSON_PROFILES AP_BANK_ACCOUNT_USES AP_BANK_ACCOUNTS AP_BANK_BRANCHES

Running The Customer Interface:

The Customer Interface program can be used to import and validate customer information from the interface tables into the Customer tables. 1) 2) Run your custom import program to load the Customer Interface tables. Run the Customer Interface program from SRS window We can specify the operating unit and we can also mention yes or no for creating reciprocal customers while submitting the import program. The Customer Interface Transfer Report is generated with the details of the number of records imported into each table and records specific error messages describing any problems. Three main sections of this report are 1) Header 2) Summary of Transfer 3) Exception Records

3)

Third Party Integration

D&B
1) What is D&B 2) The Importance of D&B data for the client 3) Data sent by D&B Data Products Business Info reports 4) On-Line Purchasing and Batch loading

D&B Continued

D&B Data Products:

1) 2) 3) 4) 5) 6) 7) Business Verification GDP Quick Check GDP Delinquency Score Global Failure Risk Score Financial Standing Decision Support Enterprise Management

8)

Commercial Credit Score (USA)

D&B Continued 2)

Data Elements sent by D&B: More than 150 elements. For ex: Duns Number Duns Risk Creating Party with D&B Info:
When you online purchase or batch load D&B information for a party that does not yet exist in the TCA Registry, you create a new party and load its D&B data. For this party, both a D&B and a user-entered record are created in these tables:

HZ_ORGANIZATION_PROFILES HZ_LOCATIONS HZ_PARTY_SITES

The user-entered records are also created because they are needed for the party to be visible in the Oracle e-Business Suite applications. In all other tables where D&B data is stored, only the D&B records are created. When D&B data is later refreshed for this party, only the D&B records are updated, even in the above three tables. If the D&B data refresh results in changes of the party address, only new D&B location and party site records are created. The user-entered location and party site records are not created or updated.

Party Merge
Overview Creating Merge Batches Merging Parties Merging Party Sites of a Party Processing Merge Batches Reviewing the Party Merge Log Party and Customer Merge

Party Merge Continued..

What Drives Party Merge Consolidate duplicate parties or party sites Ex: Merge Vision Corp. into Vision Corporation Merge duplicate party sites for a party

Party Merge Continued..

Overview
Can merge parties or party sites that belong to a party To merge Sites between parties first merge parties Can select to Delete Merged Party No Party data is physically deleted

Party Merge Continued..

What party data is merged: Party Relationships Contacts Profiles Customer Accounts Information from 3rd Party Sources

Party Merge Continued..

Merge Batches
Unique batch name Merge Reason To define details of Merge From and To party records are locked till the batch is executed Batch duplicate identification process

Party Merge Continued.. Processing Merge Batches Preview merge batch and the outcome of the merge process before submitting the Party Merge process Submit the Party Merge process immediately after entering merge details Save your work and submit the Party Merge process at a later time

Party Merge Continued..

Review Merge Log Log of the Party Merge process to review the parties and related entities affected by the process Automatically generated Very detailed log for all applicable applications modules

Customer Merge
Merging Customers Merging Sites for the Same Customer Merging Different Customers Submitting the Merge Process Customer Merge Execution Report Reviewing Merged Customers

Resource Manager in 12i

The most important extension/feature of 12i TCA Architecture.
Resource Manager enables other modules and applications to use resources no matter where they were created.
It acts as a central repository for various types of resources.

We can further define your resources by organizing them into groups and teams and assigning various roles to them.
We can import various types of resources, such as employees, suppliers, parties, or partners, which are created in other Oracle applications into Resource Manager. Resource Manager can be accessed from Forms and HTML depending on use and who is using it.

Application Program Interfaces

hz_party_v2pub hz_cust_account_v2pub hz_location_v2pub hz_party_site_v2pub hz_cust_account_site_v2pub hz_customer_profile_v2pub

LITERATURE
TCA User Guide TCA Administrative Guide TCAAPI.pdf