- OracleApps Epicenter - http://www.oracleappshub.com -
Trading Community Architecture (TCA) 101
Posted By Sanjit Anand On October 22, 2008 @ 12:05 am In Oracle TCA | 3 Comments
Trading Community Architecture (TCA) is a structure which was based out of R11 Customer Model designed to support complex trading relationships to cater additional need which further extended in R12 with Supplier and Bank. So, TCA is a data model that allows you to manage complex information about the parties, or customers or suppliers or bank who belong to your commercial community, including organizations, locations, and the network of hierarchical relationships among them.
What is Trading Community Architecture (TCA)?
What is TCA, the Trading Community Architecture? Is TCA an Oracle Applications module? Is it functionality within an Oracle module? These are few common question, and there are often many answers given.
The TCA is a data model that supports the entry and management of entities that you interact with. So lets revisit the concept.
Trading Community Architecture is a Very flexible, very robust model which defines the components involve in trading within in E-business Suite.
The implementation of technology and applications to allow users to create and maintain relationships among entities
The universal data schema for customers, prospects, suppliers, distributors, resellers, consortiums, bank across all Oracle EBS applications
TCA not only allows for the tracking of relationships between the implementing organization and its trading partners, but also tracks relationships between the trading partners themselves.
You should also note, TCA is neither an Oracle Applications module nor requires separate license.
If you see TCA guide, you can find these are the key features of TCA
Fig 1: TCA Logical Diagram
You can also define contact people, bank accounts, payment methods, telephone numbers, and relationships for each customer account.
You can also maintain multiple customer accounts for a customer that transacts business with more than one line of business in your organization. You maintain separate customer profiles, addresses, and contacts for each customer account.
A party site is the location where a particular party is physically located. Every party has only one identifying address, but a party can have multiple party sites.
A customer address is a party site used in the context of a customer account for billing, shipping, or other purposes.
A contact communicates for or acts on behalf of a party or customer account. A contact can exist for a customer at the account or address level. A person usually acts as a contact for an organization, but can also be a contact for another person. For example, an administrative assistant could be the contact for an executive.
Old Model vs New Customer Model
Fig 2; Customer old model and TCA model
Factors which you can consider for TCA entities
TCA Setup Considerations
When you are doing TCA customer Modeling, keep these things in mind;
TCA Integration with Other Oracle Products
This is how TCA data is tighten with other Oracle products.
TCA Technical Tables
Here are Technical details for R12 Supplier in TCA. You can also refer old post for more details .
Check out this .
Article printed from OracleApps Epicenter: http://www.oracleappshub.com
URL to article: http://www.oracleappshub.com/accounts-receivable/oracle-tca/trading-community-architecture-tca-101/
URLs in this post:
 customer model: http://www.oracleappshub.com/accounts-receivable/deep-drive-customer-interface-in-ar/
 details: http://www.oracleappshub.com/account-payable/r12-suppliers-trading-community-architecture/
 this: http://www.oracleappshub.com/account-payable/r12-bank-trading-community-architecturetca/
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.