--100437715-TCA-R12--

8/20/2019 --100437715-TCA-R12--

1/8

R 12 Customer TCA Architechture

Purpose

This bulletin describes the changes that will be occurring in Project Billing to obsolete the use of

Receivables views relating to customer and contact information, and to replace them with directreferences to the underlying "Trading Community Architecture" (TCA) tables.

Scope and Application

This note is intended for anyone who must upgrade queries or customizations from 11i which refer to anyof the following views or anyone who requires an understanding of the TCA architecture to create newqueries or customizations:

RA_CUSTOMERS

RA_ADDRESSES

RA_SITE_USES

RA_CONTACTS

RA_CONTACT_ROLES

Projects Uptake of the TCA Architecture in Release 12

1. The TCA Architecture

8/20/2019 --100437715-TCA-R12--

2/8

The following sections describe the individual views that are being replaced by the TCA (HZ) tables alongwith a mapping of view columns to HZ table columns and the query conditions that should be used toretrieve them

2.1 RA_CUSTOMERS

In the 11i architecture RA_CUSTOMERS is a synonym in the APPS schema which points to theview RA_HCUSTOMERS.

The source file for RA_HCUSTOMERS in 11i is archz.odf.

The table below lists the corresponding HZ table and column for various columns in the currentRA_CUSTOMERS view:

Column in RA_CUSTOMERS Corresponding Table Column

customer_name hz_parties substrb(party_name,1,50)

customer_id hz_cust_accounts cust_account_id

customer_number hz_cust_accounts account_number

status hz_cust_accounts status

Source Tables: HZ_PARTIES, HZ_CUST_ACCOUNTS

Join Conditions:

HZ_CUST_ACCOUNTS..Party_Id = HZ_PARTIES.Party_Id

8/20/2019 --100437715-TCA-R12--

3/8

2.2 RA_ADDRESSES

In the 11i architecture RA_ADDRESSES is a multi-org striped view based onRA_ADDRESSES_ALL. RA_ADDRESSES_ALL is a synonym for the viewRA_ADDRESSES_MORG.

The source file for view RA_ADDRESSES_MORG in 11i is archz.odf.

The table below lists the corresponding HZ table and column for various columns in the currentRA_ADDRESSES view:

Column in RA_ADDRESSES Corresponding Table Column

address_id hz_cust_acct_sites_all cust_acct_site_id

status hz_cust_acct_sites_all status

address1 hz_locations address1




city hz_locations city

state hz_locations state

postal_code hz_locations postal_code

county hz_locations county

country hz_locations country

language hz_locations language

Source Tables: HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_ACCT_SITES_ALL

Join Conditions:

HZ_CUST_ACCT_SITES_ALL.party_site_id = HZ_PARTY_SITES.party_site_idHZ_LOCATIONS.location_id = HZ_PARTY_SITES.location_id

2.3 RA_SITE_USES

In the 11i architecture RA_SITE_USES is a multi-org striped view based onRA_SITE_USES_ALL. RA_SITE_USES_ALL is a synonym for the viewRA_SITE_USES_MORG.

The source file for view RA_SITE_USES_MORG in 11i is archz.odf

The table below lists the corresponding HZ table and column for various columns in the currentRA_SITE_USES view:

Column in RA_SITE_USES Corresponding Table Column

site_use_id hz_cust_site_uses site_use_id

site_use_code hz_cust_site_uses site_use_code

status hz_cust_site_uses status

address_id hz_cust_site_uses cust_acct_site_id

8/20/2019 --100437715-TCA-R12--

4/8

Source Tables: HZ_CUST_SITE_USES

Join Conditions: none

2.4 RA_CONTACTS

In the 11i architecture RA_CONTACTS is a synonym for the view RA_HCONTACTS

The source file for view RA_HCONTACTS in 11i is archz.odf The table below lists the corresponding HZ table and column for various columns in the current

RA_CONTACTS view:

Column inRA_CONTACTS

Corresponding Table Column

contact_id hz_cust_account_roles cust_account_role_id

status hz_cust_account_roles status

customer_id hz_cust_account_roles cust_account_id

address_id hz_cust_account_roles cust_acct_site_id

first_name hz_parties substrb(person_first_name,1,40) last_name hz_parties substrb(person_last_name,1,50)

Source Tables: HZ_CUST_ACCOUNT_ROLES, HZ_PARTY_RELATIONSHIPS, HZ_PARTIES

Join Conditions:

HZ_CUST_ACCOUNT_ROLES.party_id = HZ_PARTY_RELATIONSHIPS.party_idHZ_CUST_ACCOUNT_ROLES.role_type = 'CONTACT'HZ_PARTIES.party_id = HZ_PARTY_RELATIONSHIPS.subject_id

2.5 RA_CONTACT_ROLES

In the 11i architecture RA_CONTACT_ROLES is a synonym for the viewRA_HCONTACT_ROLES

The source file for view RA_HCONTACT_ROLES in 11i is archz.odf

The table below lists the corresponding HZ table and column for various columns in the currentRA_CONTACT_ROLES view:

Column in RA_CONTACT_ROLES Corresponding Table Column

contact_id hz_role_responsibility cust_account_role_id

usage_code hz_role_responsibility responsibility_type

primary_flag hz_role_responsibility primary_flag

Source Tables: HZ_ROLE_RESPONSIBILITY

Join Conditions: none.

11i Table R12 Change

ra_addresses_all SELECT acct_site.cust_account_id customer_id,acct_site.cust_acct_site_id address_id

FROM hz_party_sites party_site,

8/20/2019 --100437715-TCA-R12--

5/8

hz_loc_assignments loc_assign,

hz_locations loc,

hz_cust_acct_sites_all acct_site

WHERE acct_site.party_site_id = party_site.party_site_id

AND loc.location_id = party_site.location_id

AND loc.location_id = loc_assign.location_id

AND NVL (acct_site.org_id, -99) = NVL (loc_assign.org_id,-99)

ra_site_uses_all SELECT site_use_id, LOCATION, attribute1

FROM hz_cust_site_uses_all

ra_customers SELECT cust_acct.cust_account_id customer_id,

SUBSTRB (party.party_name, 1, 50) customer_name,

cust_acct.account_number customer_number

FROM hz_parties party, hz_cust_accounts cust_acct

WHERE cust_acct.party_id = party.party_id

RA_ADDRESSES_ALL is obsolete table in Release 11.5.10 and Release 12. You can get the customeraddress information from the following tables in Release 12.

HZ_CUST_ACCT_SITES_ALLHZ_PARTY_SITESHZ_LOCATIONS

Here is the Linking information:

- HZ_CUST_ACCT_SITES_ALL & HZ_PARTY_SITES - Link column PARTY_SITE_ID- HZ_PARTY_SITES & HZ_LOCATIONS - Link column is LOCATION_ID.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

1. What is TCA? Tables? A) Trading Community Architecture. It is a centralized repository of businessentities such as Partners, Customers, and Organizations etc. It is a newframework developed in Oracle 11i.

8/20/2019 --100437715-TCA-R12--

6/8

HZ_PARTIES: The HZ_PARTIES table stores basic information about parties thatcan be shared with any relationship that the party might establish with anotherparty. Although a record in the HZ_PARTIES table represents a unique party,multiple parties can have the same name. The parties can be one of four types:Organization for example, Oracle CorporationPerson for example, JaneDoeGroup for example, World Wide Web ConsortiumRelationship for example,

Jane Doe at Oracle Corporation.

HZ_LOCATIONS: The HZ_LOCATIONS table stores information about a deliveryor postal address such as building number, street address, postal code, anddirections to a location. This table provides physical location information aboutparties (organizations and people) and customer accounts.

HZ_PARTY_SITES: The HZ_PARTY_SITES table links a party (see HZ_PARTIES)and a location (see HZ_LOCATIONS) and stores location-specific partyinformation. One party can optionally have one or more party sites. Onelocation can optionally be used by one or more parties. This party site can thenbe used for multiple customer accounts within the same party.

HZ_CUST_ACCT_SITES_ALLHZ_CUST_SITE_USES_ALLHZ_CUST_CONTACT_POINTS etc.

2. What are Base Tables or Interface Tables for Customer Conversions,Autolockbox, Auto Invoice? A) Customer Conversion:Interface Tables : RA_CUSTOMERS_INTERFACE_ALL,RA_CUSTOMER_PROFILES_INT_ALL,RA_CONTACT_PHONES_INT_ALL,RA_CUSTOMER_BANKS_INT_ALL,RA_CUST_PAY_METHOD_INT_ALL

Base Tables : RA_CUSTOMERS, RA_ADDRESSES, RA_SITE_USES_ALL,RA_CUSTOMER_PROFILES_ALL, RA_PHONES etcB) Auto Invoice:Interface Tables : RA_INTERFACE_LINES_ALL,RA_INTERFACE_DISTRIBUTIONS_ALLRA_INTERFACE_SALESCREDITS_ALL, RA_INTERFACE_ERRORS_ALLBase Tables : RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL,RA_CUST_TRX_LINE_GL_DIST_ALL, RA_CUST_TRX_LINE_SALESREPS_ALL,RA_CUST_TRX_TYPES_ALLC) AutoLockBox:Interface Tables : AR_PAYMENTS_INTERFACE_ALL (POPULATED BY IMPORTPROCESS)

Interim tables : AR_INTERIM_CASH_RECEIPTS_ALL (All Populated by SubmitValidation): AR_INTERIM_CASH_RCPT_LINES_ALL,AR_INTERIM_POSTINGBase Tables : AR_CASH_RECEIPTS_ALL, AR_RECEIVABLE_APPLICATIONS_ALL,AR_PAYMENT_SCHEDULES_ALL ( All Populated by post quick cash)

8/20/2019 --100437715-TCA-R12--

7/8

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Expalin TCA architecture, why it was introduced in R12?

Answer

# 4

TCA : The summation of all

entities, inclusive of partners,suppliers, and competitors, thatare related to yourcustomers is called a TradingCommunity

BEFORE TCA :1.There are multiple customerdefinitions across theenterprise.

2.It was very difficult to trackcurrent and historicalinformation about the customers.3.There was a lack of support formixed business.4.It was quite tough to understand

relationships betweencustomers and others (suppliers,partners, competitors)

Trading Community Architecture:Trading Community Architecture isthe implementation of

technology and applications toallow users to create andmaintain relationships amongentities. It is a way to

understand who your customerinteracts with inside andoutside the enterprise.

The Purpous of Interduce TCA.1.Create a central repository forthe entire E-Business

Suite to store informationrelating to all members of atrading community versus separate

http://www.allinterview.com/viewpost/396538.htmlhttp://www.allinterview.com/viewpost/396538.htmlhttp://www.allinterview.com/viewpost/396538.htmlhttp://www.allinterview.com/viewpost/396538.html

8/20/2019 --100437715-TCA-R12--

8/8

tables for each member-Prospects, Customers, Contacts,Employees, Partners,Distributors, Suppliers, Banks,etc.

2.Record complex businessrelationships between TradingCommunity entities (including 3rdparty relationships).3.Support all business models,industries, and geographies*** By Using the TCA we can avoidethe Duplicity of TradingPartner records and its alsoimpacted byt the MOAC and

other few concepts where we canuse the Suppliers banks andCustomers acrros the Business Unitleve

.

Documents

--100437715-TCA-R12--