Download Export as RTF

telema_module - Document Parties
D
oc
u
m
en
t
Pa
rti
es
Triin
u
Him
ma
2012
/06/0
1
09:1
6
Table of Contents
Page 1 - last modified by Triinu Himma on 2012/06/01 09:16
telema_module - Document Parties
Basic order/invoice EDI process requires 3 parties: Buyer, Delivery and Seller. Other parties can be used in more
complex sales logistics processes.
eDoc MCO Desc
node
riptio
n
Doc
umen
tParti
es/
Deliv M
Part
eryP
y
arty
wher
e
good
s (the
order
)
were
deliv
ered.
This
is
assu
med
also
as
invoic
e
recei
ver.
Identi
fies
and
descr
ibes
speci
fic
shop
or
DC of
retail
partn
er
(refer
ence
d as
recei
ver in
docu
ment
“
Head
er”)
Buye M
Buye
rPart
r
y
legal
entity
and
payer
of
invoic
e
Selle M
Selle
rPart
r
y
legal
entity
that
issue
s the
invoic
e
Page 2 - last modified by Triinu Himma on 2012/06/01 09:16
telema_module - Document Parties
Supp C
lierP
arty
Orde C
rPart
y
Fact C
orPa
rty
(refer
ence
d as
send
er in
docu
ment
“Hea
der”)
Part
y
suppl
ying
good
s in
3PL
logisti
c
proce
ss.
Mand
atory
data
for
3PL
Use
d in
case
when
Orde
rPart
y is
differ
ent
than
Deliv
eryP
arty.
Mand
atory
in
DC-b
uyer
proce
ss.
Repr
esent
sa
partic
ular
shop
Part
y to
who
m
Seller
Party
is
sellin
g its
acco
unts
recei
vable
(e.g.
invoic
e)
Contents of party description block (most used details):
eDoc Type MCO Desc
node
riptio
Page 3 - last modified by Triinu Himma on 2012/06/01 09:16
telema_module - Document Parties
Party Part C
Code yRef
erenc
eTyp
e
Nam Nam M
e
eText
Type
VAT Reg C
Reg Type
Num
Reg RegT C
Num ype
GLN GLN C
Type
Cont
actD
ata/
Pho Nor O
neNu malT
m
extTy
pe
Emai Emai O
lAddr lType
ess
Actu
alAdd
ress/
n
Eithe
r
Party
Code
or
GLN
must
be
provi
ded
Man
dator
y for
Seller
Party
,
Buye
rPart
y,
Facto
rPart
y
Man
dator
y for
Seller
Party
,
Buye
rPart
y,
Facto
rPart
y
Eithe
r
Party
Code
or
GLN
must
be
provi
ded
Rec
omm
ende
d to
provi
de
struct
ured
addre
ss
data
as
Page 4 - last modified by Triinu Himma on 2012/06/01 09:16
telema_module - Document Parties
Addr Nor M
ess1 malT
extLa
ngTy
pe
City
Post
alCo
de
Cou
nty
Cou
ntryC
ode
Acco
untInf
o/
Nor
malT
extLa
ngTy
pe
Post
alCo
deTy
pe
Nor
malT
extLa
ngTy
pe
Cou
ntryC
odeT
ype
much
as
appli
cable
by
partic
ular
ERP
syste
m
At
least
basic
addre
ss
infor
matio
n
must
be
provi
ded
for
every
party
(for
more
struct
ured
addre
sses
there
is
also
node
Addr
ess2)
O
O
O
O
Bank
acco
unt
info
is
mand
atory
for
Seller
Party
,
Buye
rPart
y,
Facto
rPart
Page 5 - last modified by Triinu Himma on 2012/06/01 09:16
telema_module - Document Parties
IBAN Acco C
untTy
pe
BIC
BICT C
ype
y
IBA
N
acco
unt
numb
er
Bank
SWIF
T
code
Bank Nor C
Nam malT
e
extTy
pe
Sample party data block:
<SellerParty context=”self”>
<PartyCode>640</PartyCode>
<Name>Meat Factory AS</Name>
<RegNum>10169266</RegNum>
<VATRegNum>EE100203367</VATRegNum>
<ContactData>
<ActualAddress>
<Address1>Saeveski 12</Address1>
<City>Tallinn</City>
<PostalCode>11214</PostalCode>
<County>Harjumaa</County>
<CountryCode>EE</CountryCode>
</ActualAddress>
</ContactData>
<AccountInfo>
<AccountNum>221001120098</AccountNum>
<IBAN>EE332200221001120098</IBAN>
<BIC>HABAEE2X</BIC>
<BankName>Swedbank</BankName>
</AccountInfo>
</SellerParty>
It is important to indicate “ context” attribute for “ SellerParty” as “ self”, for “ BuyerParty” and “
DeliveryParty” as “ partner”.
Page 6 - last modified by Triinu Himma on 2012/06/01 09:16