EDI to UBL

[Oriol Baus� <oriol@tradise.com>]

Dear all,

We are working in the implementation of UBL 1.0 in different scenarios in
Spain. One of the sectors we are working with have some companies that are
still transacting electronically with EDI messages based on the UN/EDIFACT
standard.

Now, we are proposing them the use of UBL for those of their trader partners
who are not able to setup an EDI environment, based on ease of use and
economical criteria. Those companies have received our proposal with a high
degree of approval.

So, as the EDI users need to receive documents in EDI format and new trader
partners are sending messages in UBL format, we need to develop a data
mapper between EDI and UBL, and we are starting with the Invoice.

In that scenario we have some questions that need to be answered:

1.- In EDI there are many roles defined by NAD 3035 Party qualifier element.
And so herein Spain, the EDI users use some of those qualifiers to establish
basically the following items:

	a) From the Buyer point of view
		The Buyer
		The people who asked for the goods
		The Invoice recipient
		The payer
		The goods recipient
		The document recipient
	b) From the Seller point of view
		The seller
		The provider
		The invoice issuer
		The payee

As in UBL there are only two main Parties, the SellerParty and the
BuyerParty without a qualification, we would like to know how we can map
those different EDI parties in UBL. 

The different options as long as we can see are:

	1) Using AdditionalAccountID in BuyerParty or SellerParty. The
problem with that way is that we cannot qualify the ID.
	2) Incrementing the Party cardinality inside the BuyerParty or
SellerParty. That way we also need a party qualifier inside the party.
	3) Locate each different role in its correspondant localization. For
instance, the payer can be placed in
cac:PaymentMeans/cac:PayerFinancialAccount/cac:ID. The problem with that
approach is the disability to define that party attributes.

We are looking forward to hearing from anyone who can give us an advice on
how to implement that EDI to UBL mapping.

Best regards.
 

 
Oriol Baus� Peris
Tradise


--Av�s--

Aquest missatge electr�nic es dirigeix nom�s al seu destinatari. Pot
contenir informaci� privilegiada o confidencial i/o dades de car�cter
personal regulades per la Llei Org�nica de Protecci� de Dades i la Llei de
Serveis de la Societat de la Informaci�. Si Vost� no n'�s el destinatari, ha
de saber que la seva lectura, c�pia i �s est� prohibida. Li preguem que ens
avisi immediatament per aquesta mateixa via i que procedeixi a la seva
destrucci�. Les opinions, conclusions i la resta de informaci� inclosa en
aquest missatge, que no estiguin relacionades amb assumptes professionals de
Tradise, no estan recolzades per l'empresa.



--Aviso--

Este mensaje se dirige exclusivamente a su destinatario y puede contener
informaci�n privilegiada o confidencial y/o datos de car�cter personal, cuya
difusi�n est� regulada por la Ley Org�nica de Protecci�n de Datos y la Ley
de Servicios de la Sociedad de la Informaci�n. Si usted no es el
destinatario indicado (o el responsable de la entrega al mismo), no debe
copiar o entregar este mensaje a terceros bajo ning�n concepto. Si ha
recibido este mensaje por error o lo ha conseguido por otros medios, le
rogamos que nos lo comunique inmediatamente por esta misma v�a y proceda a
su eliminaci�n irreversible. Las opiniones, conclusiones y dem�s informaci�n
incluida en este mensaje que no est�n relacionadas con asuntos profesionales
de Tradise no est�n respaldadas por la empresa.

 

--Notice--

This e-mail message is solely intended for its addressee and may contain
confidential information. If you are not the addressee of this e-mail you
should know that it is forbidden to read it, copy or use it. Please, notify
us of receipt immediately via e-mail and delete it. Opinions, and other
informations included in this message not related with Tradise professional
activity will not be endorsed.