TCA-Customer Model in Oracle Fusion

 

🧠 Mastering the TCA Customer Model in Oracle Fusion

                                                            Doc by Venkat

1️⃣ Introduction

The Trading Community Architecture (TCA) in Oracle Fusion is the backbone of customer and supplier data management. It provides a unified framework that ensures consistency across modules like Order Management and Receivables, enabling seamless integration and data governance.

2️⃣ Core Concepts in TCA

• Party – The base entity representing a customer or supplier.

• Customer Account – Created when a party establishes a sales relationship.

• Sites and Site Uses – Define operational locations and their purposes (Bill-To, Ship-To, Sold-To, Deliver-To).

• Centralized Architecture – Both suppliers and customers reside within the same TCA structure.

4️⃣ Visual: TCA Customer Model Hierarchy

Caption: This diagram illustrates the hierarchical relationship between Parties, Accounts, Sites, Site Uses, Locations, and Contacts — the foundation of Oracle Fusion’s TCA model.

5️⃣ Application UI Interaction

• Access via Order Management or Receivables.

• Use Manage Customers to query, update, or create customers.

• Registry ID and Account Number are auto-generated.

• Define contact points and assign responsibilities per site.

6️⃣ Querying Customer Data (SQL Best Practices)

SELECT * FROM hz_parties WHERE party_number = '1142348';

SELECT * FROM hz_cust_accounts WHERE account_number = '148138';

SELECT * FROM hz_cust_acct_sites WHERE cust_account_id = 300000331230011;

SELECT * FROM hz_cust_site_uses_all WHERE cust_acct_site_id = 300000331230012;

SELECT * FROM hz_locations WHERE creation_date >= SYSDATE - 1/24;

Tips:

• Use single quotes for alphanumeric values.

• Numeric IDs don’t require quotes.

• Use LISTAGG for consolidating multiple contact points.

7️⃣ Visual: UI and Database Interaction

Caption: This flowchart shows how the Manage Customers task interacts with backend tables — translating UI actions into real-time database operations.

8️⃣ Real-World Hierarchy

1. Party → HZ_PARTIES

2. Customer Account → HZ_CUST_ACCOUNTS

3. Sites → HZ_PARTY_SITES, HZ_CUST_ACCOUNT_SITES

4. Site Uses → HZ_CUST_SITE_USES_ALL

5. Locations → HZ_LOCATIONS

6. Contacts → HZ_CONTACT_POINTS

Conclusion: Mastering the TCA Customer Model

The TCA framework is the cornerstone of Oracle Fusion’s customer intelligence. By understanding its hierarchy, UI interactions, and lifecycle flow, consultants can design robust, scalable solutions that unify customer data across modules.