Oracle Trading Community Architecture (TCA) in R12
Oracle Trading Community Architecture (TCA) in R12 | TCA Architecture in Oracle Apps
Description
Oracle Trading Community Architecture (TCA) Course
Oracle Trading Community Architecture (TCA) is a data model that allows you to manage complex information about the parties, or customers, who belong to your commercial community, including organizations, locations, and the network of hierarchical relationships among them.
This Course includes What is TCA, TCA Matters Before and After, TCA Data Model Components, TCA in R12 Includes, TCA in R12 MOAC, TCA in R12 Bank Account Model, TCA in R12 Legal Entities, TCA API's, TCA Tables.
How TCA Matters?
Before TCA:
There are multiple customer definitions across the enterprise.
It was very difficult to track current and historical information about the customers.
There was a lack of support for mixed business.
It was quite tough to understand relationships between customers and others (suppliers, partners, competitors)
After TCA:
Create a central repository for the entire E-Business Suite to store information relating to all members of a trading community versus separate tables for each member-Prospects, Customers, Contacts, Employees, Partners, Distributors, Suppliers, Banks, etc.
Record complex business relationships between Trading Community entities (including 3rd party relationships).
Support all business models, industries, and geographies.
The key entities in TCA include:
Parties: Entities of type Person or Organization that can enter into business relationships. Parties can also be of type Relationship. For example, Joe as himself is a party of type Person, but Joe as a contact for Vision Corporation is a party of type Relationship. Every party in the TCA Registry has a unique Registry ID.
TCA includes an extensive variety of information for parties, for example party name, addresses, contacts, and contact points. Joe as a person can have a personal phone number that differs from the phone number for the relationship of Joe as a contact.
Party sites: Addresses that parties use for specific purposes, or uses.
Customers: Parties with whom you have a selling relationship.
Customer accounts: The business relationships between you and your customers.
Customer account sites: Party sites used in the context of customer accounts for specific purposes, or uses, for example ship-to and bill-to account sites.
Locations: Geospatial points, usually defined by an address.
Contacts: People who have a contact or employment relationship with an organization or person.
Contact points: Means of contact, for example, phone and e-mail address.
TCA also includes conceptual functionality that helps you manage and understand your trading community. For example, you can use relationships to model the roles that parties play with respect to one another, and classifications to classify entities
What You Will Learn!
- TCA Matters Before & After
- TCA Data Model Components
- TCA in R12 Includes
- TCA in R12 MOAC
- TCA in R12 Bank Account Model
- TCA in R12 Legal Entities
- TCA API's
- TCA Tables
Who Should Attend!
- Any Professional with basic knowledge in Oracle Apps R12 Functional Modules