Escolar Documentos
Profissional Documentos
Cultura Documentos
Preface
In this book I have given basic of TCA Architecture with technical details.
Author:
Email:
Dinesh Kumar S
Dineshcse86@Gmail.Com
1
Contents
About TCA
TCA Key Entities
TCA Logical Data Model
TCA in R12
EBS Modules uses TCA
TCA Model Table
Information
TCA API Information
2
About
TCA
What
is
Trading
Community?
Trading
Community
=
Par8cipants
in
community
+
Rela3onship
b/w
par3cipants
In
other
words,
It
refers
to
group
of
en33es
taking
part
in
e-Commerce.
Competitor of
Employee of
Partner of
Supplier of
Trading Community:
What
is
TCA?
It
refers
to
a
data
model,
not
a
module.
Provides
a
single,
universal
deni8on
of
trading
partners
across
applica8ons
and
job
func8on.
It
is
a
way
to
understand
who
our
trading
partners
interact
with
inside
and
outside
the
enterprise.
Oracle E-Business Suite Application Families*
SCM
HR
o Prospects,
Customers,
Contacts,
Employees,
Partners,
Distributors,
Suppliers,
Banks,
etc.
Addi8onally
3
new
trading
en88es
been
introduced
into
TCA,
Suppliers
Bank
&
Bank
Branches
Legal
En3ty
Prior to TCA :
There
were
mul8ple
deni8ons
of
Trading
En88es
across
the
EBS,
ie:
Customers,
Suppliers
and
Employees.
In
some
cases,
the
same
data
had
to
be
held
in
several
dierent
modules;
o Human
Resource
(HR)
employees
who
were
paid
through
Payables
(AP)
had
to
be
created
again
as
suppliers
in
AP;
o bank
details
were
held
in
HR,
AP
and
CM
(Cash
Management).
All
these
deni8ons
where
independent
of
each
other
and
there
were
no
links
between
them.
For
example,
separate
payments
had
to
be
made
from
each
module,
so
you
could
not
see
a
balance
of
a
single
bank
account
of
an
en8ty.
Therefore
it
was
impossible
to
have
a
view
of
the
full
picture
and
it
was
tough
to
understand
the
rela8onships
between
en88es.
10
What
is
Par3es?
An
individual
en3ty
in
Trading
Community
Architecture.
It
can
be
a
separate
individual
en8ty
or
have
some
rela8onship
with
other
en88es.
It
can
be
an,
Organiza8on
Person
Rela8onships
Groups
For
example,
11
John
Employer of
What
is
Loca3on?
Loca3on:
A
geographical
Loca8on
(or)
a
physical
place
usually
with
address.
No
duplica8on
of
address
Each
Loca8on
have
its
Uses
i.e.
it
can
be
Bill-to,
Ship-To,
Receiving
Site.
Party
Sites:
Links
a
party
with
a
loca8on
and
describes
the
usage
of
the
loca8on.
Par8es
may
be
associated
to
one
or
more
Loca8ons
and
any
one
loca8on
may
have
one
or
more
uses.
13
What
is
Accounts?
Represents
a
selling
Rela8onship.
Exists
only
when
selling
rela8onship
exists.
Each
Unique
business
rela3onship
is
Account.
An
account
cannot
be
created
without
a
party.
An
account
site
is
a
party
site
that
is
used
in
the
context
of
a
customer
account
for
specic
purpose.
An
account
can
have
mul8ple
account
sites.
A
customer
address
is
an
account
site
that
is
used
for
billing,
shipping,
or
other
purposes.
An
account
rela/onship
is
established
between
dierent
accounts
of
a
party
to
allow
sharing
of
billing,
shipping,
and
pricing
informa8on.
Account of
John
For
example,
Savings
account
of
John
with
American
Bank.
Investment/Demat
account
of
John
with
American
account.
14
What is Contact?
15
Party Layer
Customer
Account
Layer
16
17
18
19
20
21
22
23
TCA in R12
24
Cash
Management
Payables
Bank
Receivables
Bank
Branch
Bank Account
Payroll
Treasury
25
Oracle 11i
Oracle R12
Banks/Branches dened in AP
26
OU
B
Single
Payment
Instruc3on
OU C
Payments
Bank
Invoices
27
Supplier
Representa3on
The
Supplier,
Sites/Loca8ons,
and
their
Contact
informa8on
is
migrated
to
TCA.
Suppliers
Supplier
Account
for
a
Party
in
TCA.
Supplier
Sites
The
supplier
sites
table
will
store
the
Site
account
amributes
per
Opera8ng
Unit,
which
will
default
into
transac8ons.
Going
forward,
supplier
site
crea8on
will
involve
either
selec8ng
an
exis8ng
loca8on
for
the
supplier
or
crea8ng
a
new
loca8on
in
HZ_LOCATIONS.
The
user
will
then
have
to
select
the
Opera8ng
Unit
based
on
the
security
prole,
and
enter
the
site
amributes
as
they
are
entered
today.
Contacts
Contacts
are
modeled
as
a
child
en8ty
to
Supplier
Sites
in
Release
12.
.
Each
contact
(person)
is
represented
as
a
Party
rst.
A
rela3onship
is
then
created
between
the
person
party
and
the
organiza8on
party
(customer,
supplier,
etc).
This
rela8onship
itself
is
reected
as
a
party
record
in
TCA.
The
contact
informa8on
can
be
dened
for
a
Party,
Party
Site,
and
Party
Rela8onship
in
TCA.
28
29
30
Oracle 11i
Oracle R12
31
OU
1
OU
1
OU
1
OU
1
32
33
Legal
En3ty
In
TCA,
Legal
en3ty
is
created
as
a
party
of
party
type
ORGANIZATION
or
PERSON
An
establishment
is
created
as
a
party
of
party
type
ORGANIZATION.
TCA
creates
a
new
classica8on
category
called
Business
Func3on.
It
is
used
mainly
to
model
what
business
func8ons
a
party
can
perform
in
E-Business
Suite.
For
modeling
legal
en88es
and
establishments
in
TCA,
classica8on
code
Legal
En8ty
and
Establishment
are
created
under
the
Business
Func8on
class
category
An
establishment
is
created
as
a
party
and
always
link
to
a
party
that
is
classied
as
a
legal
en8ty
through
the
rela8onship
model.
34
35
HZ_PARTY_SITES
HZ_PARTY_SITE_USES
HZ_LOCATIONS
HZ_ORG_CONTACTS
36
HZ_PARTY_RELATIONSHIPS
HZ_PERSON_PROFILES
HZ_ORGANIZATION_PROFIL
ES
HZ_CONTACT_POINTS
37
38
Applica8ons
in
the
Oracle
E-Business
Suite
can
use
the
TCA
public
APIs
to
insert
and
update
en88es
in
the
TCA
model.
Data
migra8on
from
legacy
systems
into
the
TCA
model.
Access
to
the
TCA
model
from
custom
applica8ons
built
by
deploying
companies
and
Oracle
Consul8ng.
39
Granular
APIs
manipulate
data
at
the
granular
Oracle
Trading
Community
Architecture
en8ty
level.
Oracle
Seeded
business
objects,
which
can
contain
other
business
objects,
granular
en88es,
or
both.
When
a
business
object
API
is
called,
it
can
subsequently
call
granular
APIs.
Advantages
of
Business
Object
APIs:
For
example,
the
Person
business
object
contains
various
business
objects
and
granular
en88es,
including
the
Party
Site
business
object
and
Rela8onship
en8ty.
When
the
Create
Person
Business
Object
API
procedure
is
called,
it
subsequently
calls
the
Create
Party
Site
Business
Object
procedure
and
the
Create
Rela8onship
granular
API
procedure.
So
instead
of
three
separate
ini8al
API
calls,
as
is
the
case
with
the
granular
APIs,
you
can
use
just
one
business
object
API
to
create
the
same
person
informa8on.
40
Granular API
41
Features of APIs:
Modular
Approach:
The
modular
approach
defaults
and
validates
user-entered
informa8on.
Excep8on
Handling
&
Return
Messages:
The
APIs
provide
an
extensive
set
of
error-
handling
and
error-repor8ng
mechanisms
so
that
errors
encountered
in
the
dierent
phases
of
API
execu8on
are
reported
and
put
on
the
message
stack.
-
The
return
status
(x_return_status)
of
the
API
informs
the
caller
about
the
result
of
the
opera8on
or
opera8ons
performed
by
the
API.
Statuses
include
Success,
Error
&
unexpected
error.
Messages:
The
APIs
put
result
messages
into
a
message
list.
Programs
calling
these
APIs
can
then
get
the
messages
from
the
list
and
process
those
messages
by
issuing
them,
loading
them
into
a
database
table,
or
wri8ng
them
to
a
log
le.
Robust
Valida8on:
The
APIs
collect
all
the
valida8on
errors
encountered
and
put
them
on
the
message
stack.
The
relevant
en8ty
handler
is
called
only
if
no
errors
are
reported
during
the
valida8on
phases.
Locking
Mechanism:
The
TCA
public
APIs
provide
a
new
locking
mechanism
for
update
procedures,
based
on
the
new
OBJECT_VERSION_NUMBER
column,
which
has
been
included
in
all
HZ
tables.
1
New
Record
Exis8ng
value
+
1
Update
Record
Null
Exis8ng
Record
prior
to
locking
mechanism
42
Required?
Type
Yes
INOUT
p_init_msg_list
Op8onal
IN
x_return_status
--
OUT
p_<en8ty>_object_ver
sion_number
Descrip3on
43
API informa3on
Party
HZ_PARTY_V2PUB
Party Informa8on
HZ_PARTY_INFO_V2PUB
HZ_PARTY_CONTACT_V2PUB
Person Informa8on
HZ_PERSON_INFO_V2PUB
Organiza8on Informa8on
HZ_ORGANIZATION_INFO_V2PUB
Loca8on
HZ_LOCATION_V2PUB
Party Site
HZ_PARTY_SITE_V2PUB
Contact Point
HZ_CONTACT_POINT_V2PUB
Rela8onship
HZ_RELATIONSHIP_V2PUB
Hierarchy Retrieval
HZ_HIERARCHY_V2PUB
Customer Account
HZ_CUST_ACCOUNT_V2PUB
HZ_CUST_ACCOUNT_SITE_V2PUB
Note**
Listed
only
some
important
APIs
name.
44
45