OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: SV: [ubl-dev] UN/CEFACT SBDH

Hi Darko,


We encountered the same issue in Sweden when we implemented SBDH a couple of years ago. We decided to extend/modify the SBDH-schema to allow for unbounded xs:any. Since our usage of SBDH by that became incompatible against SBDH, we also changed the targetnamespace.


/Martin Forsberg


Från: Darko Gulija [mailto:Darko.Gulija@infodom.hr]
Skickat: den 8 mars 2011 10:41
Till: Crawford, Mark; 'tim.mcgrath@documentengineeringservices.com'
Kopia: 'ubl-dev@lists.oasis-open.org'; 'ubl@lists.oasis-open.org'
Ämne: RE: [ubl-dev] UN/CEFACT SBDH


How could we deliver packet of invoices (e.g. all of the invoices for one month) in a single message using SBDH ?


We are developing an e-Invoicing platform, and need the functionality that invoice issuer delivers packet of invoices to the platform to be delivered to the users, and would like to be able to use standards-based format.


As Martin indicated earlier, SBDH shema (latest version I found was 1.3) does not support multiple XML elements after the header:



      <xs:complexType name="StandardBusinessDocument">


                  <xs:element ref="StandardBusinessDocumentHeader" minOccurs="0"/>

                  <xs:any namespace="##other" processContents="lax"/>




Which is strange, since Manifest contains repeatable ManifestItem, so it is capable of “manifesting” multiple documents.

Should we “invent “ our own envelope element and then put all the <invoice> elements in there ? Does UBL 2.1 already provide / draft some solution ?


Is SBDH appropriate tool for the task at all ?


Thanks in advance.

Darko Gulija




Darko Gulija
Izvršni direktor za e-Poslovanje i ESB


Executive Director for e-Business


InfoDom d.o.o.
A. Žaje 61/1
10000 Zagreb
tel:        +385 (0)1 3090 507
fax:        +385 (0)1 3040 593

web:      http://www.infodom.hr





From: Crawford, Mark [mailto:mark.crawford@sap.com]
Sent: Saturday, January 22, 2011 2:03 AM
To: 'tim.mcgrath@documentengineeringservices.com'
Cc: 'ubl-dev@lists.oasis-open.org'; 'ubl@lists.oasis-open.org'
Subject: Re: [ubl-dev] UN/CEFACT SBDH


Read the scenario and the text around the xml.

Mark Crawford
SAP Standards Strategist
Platform Strategy Group
Technology Strategy Team, Office of the CTO
Mobile: (703) 485-5232


From: Tim McGrath [mailto:tim.mcgrath@documentengineeringservices.com]
Sent: Friday, January 21, 2011 07:08 PM
To: Crawford, Mark
Cc: ubl-dev@lists.oasis-open.org <ubl-dev@lists.oasis-open.org>; 'ubl@lists.oasis-open.org' <ubl@lists.oasis-open.org>
Subject: Re: [ubl-dev] UN/CEFACT SBDH

I am aware you stated this  earlier and that it says so on the metamodel but the implementation that is published in CEFACT XML appears to be limited, as Martin responded last month to your earlier comment.  See http://lists.oasis-open.org/archives/ubl-dev/201012/msg00006.html

As Sweden are actually using the SBDH in real applications I respect that they understand the issue and need a solution.

This may be why the 'misunderstanding' continues - the practice does not seem to match the expectation.  So it appears we need a UBL messaging architecture solution (like GS1 and others have done).  But we certainly dont want to reinvent yet another envelope for the sake of it and the SBDH metamodel (which is based on a myriad of others) is a great place to start.

On 22/01/2011 12:08 AM, Crawford, Mark wrote:

From the UBL Atlantic minutes of 18 January 2011:


    “My initial reaction was to adopt an

    existing solution such as the UN/CEFACT Standard Business

    Document Header (SBDH), as was done with Svefaktura in Sweden;

    but the SBDH is a relatively small document structure that is

    limited to a single document, and the requirement from BII is

    support for sending a batch of related documents in a single



I am not sure why this misunderstanding of SBDH 1.3 continues.  It is most likely driven by the name of the specification (singular business document) rather than an understanding of the specification. In terms of the specification, a business document is a single exchange – not a single transaction.  The metamodel clearly shows that SBDH fully supports sending a packet of related documents inside a single business document header.  A business document as defined in SBDH Application A, Data Store 1 on line 578 “one internally formatted BD which may contain one or more individual transactions of a single (or multiple closely related) business document types(s) such as purchase order, INVOIC/TAXCON, or shipment request, etc.”


As I do not have posting rights on the UBL list, if someone who does would share this with UBL I would be greatful.


Kind Regards,


Mark Crawford

SAP Standards Strategist

Platform Strategy Group

Technology Strategy Team, Office of the CTO

(o) +1 703 6700920 (m) +1 703 4855232 (f) +1 610 492 1293





Izjava o odricanju od odgovornosti:

Ova poruka elektroničke pošte je povjerljiva i može sadržavati povlaštene informacije. U slučaju da ste je primili pogreškom, niste ovlašteni čitati, printati, pohraniti, obrađivati ili priopćavati ovu poruku. Ako ste ovu poruku primili greškom, molimo Vas da o tome odmah obavijestite pošiljatelja i izbrišete ovu poruku, njene privitke i kopije iz svojega računalnog sustava. Infodom ne preuzima nikakvu odgovornost s obzirom na bilo koju moguću netočnost bilo kojeg podatka koji je sadržan u ovoj poruci ako takav podatak nije povezan s registriranim predmetom poslovanja Infodom-a. Sadržaj, stavovi i mišljenja izražena u ovoj poruci ne odražavaju nužno službena stajališta Infodom-a. Hvala!

Disclaimer :

This e-mail is confidential and may also contain privileged information. If you are not the intended recipient, you are not authorised to read, print, save, process or disclose this message. If you have received this message by mistake, please inform the sender immediately and delete this e-mail, its attachments and any copies from your computer system. Infodom does not take any responsibility with regards to any possible inaccuracy of any data contained in this e-mail if such data do not relate to the registered operations of Infodom. Content, attitudes and opinions expressed in this e-mail do not necessarily reflect the official positions of Infodom. Thank you!

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]