[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-dev] ebXML Party Identification
Anders,
<From> and <To> identify the "Trading Party" (Generic Term). <From> and <To> contain <PartyId>, value of which is some globally accepted unique identifier such as EAN Global Location Number - GLN. The child element <PartyId> would identify MSH. Further elements within <SOAP:Header><eb:MessageHeader> such as <eb:service> and <eb:Action> give the possibility to the MSH to decide which backend system is involved (or which department message must be routed to).
Kind regards,
Thomas Bikeev
EAN International
Brussels HO
bikeev@ean-int.org
-----Original Message-----
From: Anders Tholen [mailto:anders_tholen@yahoo.com]
Sent: 27 June 2002 13:03
To: ebxml-dev@lists.ebxml.org
Subject: [ebxml-dev] ebXML Party Identification
There will often not be a one-to-one relationship between a organisation and
an MSH. For example a corporation might have multiple MSHs and one MSH might
serve multiple companies, e.g. different subsidiaries with different
DUNS-numbers.
Is the From/PartyID (original sender) and To/Party IDs (ultimate receiver)
in the ebXML MS Message Header intended to represent business parties or
MSHs?
Thanks in advance for any clarifications,
Anders Tholen
anders.tholen@ferrologic.com
<ferrologic>
Mobile : +46 70 787 6787
Steel 24-7: +32 2 334 2407 (Brussels office)
----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC