Sie sind auf Seite 1von 8

Introduction

Oracle Trading Community Architecture (TCA) is a data model. It allows managing


information about customers including organizations, locations, Persons and the network of
hierarchical relationships among them. This information is maintained in the TCA Registry,
which is the single source for any Customer Detail. TCA Registry is stored under HZ schema.

The key entities in TCA:


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.

Customers

Parties with whom you have a selling relationship. . This


selling relationship can result from the purchase of products
and services or from the negotiation of terms and conditions
that provide the basis for future purchases.

Customer accounts

The business relationships between you and your


customers. The account has information about the terms and
conditions of doing business with the party.
You can create multiple customer accounts for a party, to
maintain information about different categories of business
activities. E.g shipping account, Billing Account, Credit
account etc
A location is a point in space described by an address.
A party site is the location where a party is physically
located. Every party has
only one identifying address, but a party can have multiple
party sites.
An account site is a party site that is used in the context of
an account. An account can have multiple account sites that
is used for billing, shipping, or other purposes.

Sites/Addresses

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.

Relationship

A party relationship is a party's role in the context of


another party. Party relationships can be either seeded or
user defined.
An account relationship is established between different
accounts of a party to allow sharing of billing, shipping, and
pricing information.

Table Details
Name

Description

HZ_PARTIES

This table stores basic information about parties. 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 three types:
Organization (for example, Oracle Corporation).
Person (for example, Jane Doe).
Group (for example, World Wide Web Consortium).

HZ_PARTY_SITES

This table stores all the addresses associated to a party. If


the address does not exist as a location, then a new location
is created and the associated between the location and the
party , along with the location-specific party information such
as MAILSTOP and ADDRESSEE., is stored in this table.
One party can have one or more party sites and alternatively,
an address could be associated to multiple parties or
accounts.
For example, 500 Oracle Parkway, Redwood City, CA can be
specified as a party site for Oracle Corporation. This party
site can also be used for multiple accounts created for Oracle
Corporation.

HZ_PARTY_SITE_USES

This table stores information about how a party site is used.


Party sites can have multiple uses, for example Ship-To, BillTo, Deliver-To.
The HZ_PARTY_USAGES_B table stores the definition of a
party usage. For example, it stores information on which
party type can use a particular usage code as well as if the
usage code is active, etc.

HZ_PARTY_USG_ASSIGNMENT
S

This table Stores information about party usage assignments


to the Parties.

HZ_ORIG_SYSTEM_REFERENC
ES

This table stores the mapping between source system


references and the owner tables. Source System of each
party record.
Actual Source System details are stored in the table
HZ_ORIG_SYSTEMS_B.
The Source Systems that are mapped to different tables are
stored in HZ_ORIG_SYS_MAPPING. Tables could reference
the Source systems mapped to them.
This table stores information about a delivery or postal
address such as building number, street address, postal
code, and directions to a location. This table provides
physical location information about parties (organizations and

HZ_LOCATIONS

people) and customer accounts.


For example, this table stores a physical location such as
Building 300, 500 Oracle Parkway, CA, US 94065.

HZ_RELATIONSHIPS
HZ_RELATIONSHIP_TYPES

The HZ_RELATIONSHIPS table stores information about a


relationship between two parties. The SUBJECT_ID and
OBJECT_ID columns specify the two parties and the
relationship_type store the relationship. This table can also
be used to specify the start and end dates of the relationship
as the subject or object of a relationship can change over
time.
For example, A relationship between the holding company
and on of its subsidaries would be captured in this table as
two entries. One with the relationship type as Parent-Of, and
the holding company as a Subject and its subsidiary as
theObject and the other entry would have the relationship
type as Subsidiary-Of and the subject is the subsidiary
company and the holding company as the object.
Similarly, when a creating a party contact, the relationship is
stored in the HZ_RELATIONSHIPS table as two entires. One
with the relationship_type of Contact and the party as the
Subject and the contact person as the Object and the other
with the relationship_type of Contact-Of and the contact
person as the subject and the party as the object.

NOTE:

The HZ_RELATIONSHIP_TYPES table defines


the business rules that are associated with a relationship
type. A non-directional relationship type consists of a single
record with the same forward (FORWARD_REL_CODE) and
backward (BACKWARD_REL_CODE) relationship codes. A
directional relationship type consists of two records: one for
the parent (DIRECTION_CODE is P) and the other for a child
(DIRECTION_CODE is C) of that parent. Forward and
backward relationship codes are validated against the
PARTY_RELATIONS_TYPE lookup type.

HZ_CUST_ACCOUNTS

This table stores information about customer accounts, or


business relationships that the deploying company
establishes with a party of type Organization or Person. This
table focuses on business relationships and how transactions
are conducted in the relationship.
Since a party can have multiple customer accounts, this table
might contain several records for a single party. For example,
an individual person can establish a personal account, family
account, and a professional account for a consulting practice.

HZ_CUST_ACCT_SITES_ALL

This table stores the all the customer account sites across all

operating units. Customer account sites are customer


account addresses with which the deploying company does
business. One customer account can have multiple customer
account sites, and customer account sites for one customer
account can belong to multiple operating units.

HZ_CUST_SITE_USES_ALL

This table stores business purposes


assigned to customer account sites, for example Bill-To, ShipTo, and statements. Each customer account site can have
one or more purposes. This table is a child of the
HZ_CUST_ACCT_SITES_ALL table, with the foreign
key CUST_ACCT_SITE_ID. The
HZ_CUST_SITE_USES_ALL table also stores operating unit
identifier, though the HZ_CUST_ACCT_SITES_ALL table
itself stores the
operating unit for customer account sites.

HZ_ORG_CONTACTS

This table stores information about the position of the contact


for a party or party site. The records in this table provide
information about a contact position such as JOB_TITLE,
RANK, and general contact information. This table is not used
to store information about a specific person or organization,
such as name and identification codes. That information is
stored in the HZ_PARTIES table.

HZ_ORG_CONTACT_ROLES

For example, this table would indicate the position of an


Organization Contact as an Accounts Payables Supervisor
and the contact belongs to the Finance department.

NOTE:

The HZ_ORG_CONTACT_ROLES table stores


information about the role of the contact position that is
specified in the HZ_ORG_CONTACTS table. Contacts may
have multiple roles. For example, a vice president of
manufacturing may have a custom-defined role as a member
of a capital expenditures review board.

HZ_CONTACT_POINTS
This table stores information about how to communicate to
parties or party sites using electronic media or methods such
as Electronic Data Interchange (EDI), e-mail, telephone,
telex, and the Internet. For example, telephone-related data
can include the type of telephone line, a touch tone indicator,
a country code, the area code, the telephone number, and an
extension number to a specific

Structure of the HZ Tables.


Microsoft Office
Excel 97-2003 Worksheet

Sample Data
Note: This sample is a representation to give an understanding on how the basic information
provided in the Customer UI is stored in the HZ tables and to provide an insight into the relationship of
data between important tables.
Scenario: In customer center,
1.) Customer AT&Tis created with Address: 455 Main Dr, Suite 65,Chicago,IL 560001 and
Contact: Joe Atkins.
2.) Customer Bell Labs is created with Address: 1 Centre Road , MS 424, Foster City, CA,
94404 Contact: Lucy Li

Hz_Parties
PARTY_I
D

PARTY_NUMB
ER

PARTY_NAME

PARTY_TYPE

ORIG_SYSTEM_REFER
ENCE

4430

1001

AT&T

Organization

1147

4431

CONTACT1001

Joe Atkins

Person

Joe Atkins
AT&T

Party_Relations
hip

4432
4433

1002

Bell Labs

Organization

4434

CONTACT_1
002

Lucy Li

Person

Lucy LiLucent

Party_Relations
hip

4435

HZ_Party_Usg_Assignments

SIEBEL021501

PARTY_USG_ASSIG
NMENT_ID

PARTY_ID

PARTY_USAGE_CO
DE

EFFECTIVE_STA
RT_DATE

10595

4430

SUPPLIER

06-AUG-2011

21264

4433

CUSTOMER

06-JAN-2011

22542

4439

BANK

30-APR-07

HZ_ORIG_SYS_REFERENCES
ORIG_SYSTEM_
REF_ID

ORIG_SYSTE
M

ORIG_SYSTEM_REF
ERENCE

OWNER_TABLE_NAME

10705 DNB

1147

HZ_Parties

4430

16596 SIEBEL

SIEBEL021501

HZ_PARTIES

4433

94669

HZ_CUST_ACCOUN
TS

4439

ORIG_SYS
16565 4111

Owner_tabl
e_id

Hz_Relationships
PARTY_RELATIO
NSHIP_ID

PARTY_I
D

SUBJECT_I
D

Subject_typ
e

OBJECT_
ID

Object_Type

RELATIONSHIP_
TYPE

3240

4432

4431

Person

4430

Organizatio
n

Contact_of

3241

4432

4430

Organizati
on

4431

Person

Contact_of

Hz_Locations
LOCATION_ID

ADDRESS1

ADDRESS2

CITY

STATE

ZIPCODE

26301

455 Main Dr

Suite 65

Chicago

IL

56001

26302

1 Centre
Road

MS 424

Foster City

CA

94404

Hz_Party_Sites
PARTY_SITE_ID

LOCATION_ID

PARTY_ID

STATUS

3930

26301

4432

3931

26301

4430

HZ_Party_Site_Uses

PARTY_SITE_USE_ID

PARTY_SITE_ID

Status

SITE_USE_TYPE

2225

3930

BILL_TO

2226

3930

SHIP_TO

2227

3931

BILL_TO

2228

3931

SHIP_TO

Hz_Cust_Accounts
CUST_ACCO
UNT_ID

PARTY_ID

ACCOUNT_NUMB
ER

ACCOUNT_NAME

1000

4430

60000

AT&T

1001

4433

60001

Bell Labs

1002

4439

61021

Business World

Hz_Org_Contacts

ORG_CONT
ACT_ID

PARTY_RELATI
ONSHIP_ID

CONTACT_NUMBER

DEPARTMENT

JOB_TITLE

81000

3240

234-789-1234

Finance

Accounts Payable
Supervisor

81001

3241

234-789-1235

IT

IT Manager

81002

3242

234-789-1236

OPS

Manufacturing Vice
President

Hz_Cust_Acct_Sites_All
CUST_ACCT
_SITE_ID

CUST_ACCOU
NT_ID

PARTY_SITE_I
D

LANGUAGE
STATUS

1025

1000

3930 A

US

1026

1001

3931 A

US

Hz_Cust_Site_Uses_All

SITE_USE
_ID

CUST_ACC
T_SITE_ID

SITE_USE_
CODE

PRIMARY_
FLAG

STATU
S

START_DATE

END_DATE

21000

1025

BILL_TO

01-Jan-2011

21001

1025

BILL_TO

13-Sep-2011

31-Dec-2011

21002

1026

BILL_TO

13-Sep-2010

31-Dec-4712

21003

1026

SHIP_TO

12-Jun-2007

12-Jun-2020