[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: SV: [ubl-dev] UN/CEFACT SBDH
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.
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: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.
Is SBDH appropriate tool for the task at all ?
Thanks in advance.
Read the scenario and the text around the xml.
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
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.
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: