Martin,
This means the way that it is communicated is as follows:
<cbc:OrderResponseCode
listID=”UNCL1225”>30</cbc:OrderResponseCode>
Let us have a look at another field, the LineStatusCode.
In the Peppol variant it probably looks as follows:
<cbc:LineStatusCode
listID=”UNCL1225”>29</cbc:LineStatusCode>
In the UBL
variant is looks as follows:
<cbc:LineStatusCode listAgencyID="UBL" listName="Line Status">NoStatus</cbc:LineStatusCode>
Why is it not done conform the CEN/BII Guidelines Data Format ?
<cbc:LineStatusCode listID=”1225” listAgencyID="6">29</cbc:LineStatusCode>
2.1.3 Code types
Code types are used to specify allowed values in elements (BBIEs) as well as for
lists of options.
Code types are different to IDs in that allowed values have standardized meanings that can be known by the
recipient.
BII uses two types of codes:
- Defined codes, based on standards such as ISO or UN/CEFACT
- Bilaterally agreed codes.
Bilaterally agreed codes are usually used without attributes but standardised codes list may require
metadata that can be given in attributes.
When using Code lists for code values in BII instances, the attribute listID and listAgencyID are mandatory
The following table shows the use of attributes for Code Types that are issued by third
parties (other
than
UBL).
listID Identifier for the code list 3055 Mandatory.
listAgencyID Identifier for the issuer of the code list 6 Mandatory.
Kind regards
Danny Gaethofs
From: Martin Forsberg <martin.forsberg@ecru.se>
To: Danny Gaethofs <dgaethofs@yahoo.com>; UBL-Dev <ubl-dev@lists.oasis-open.org>
Sent: Thursday, October 3, 2013 3:40 PM
Subject: SV: SV: [ubl-dev] UBL OrderResponseCode
Hi,
The Order-specification is just about to be finalized (one or two more weeks). I will make sure that the publication
will be announced on this list.
/Martin
Från: Danny Gaethofs [mailto:dgaethofs@yahoo.com]
Skickat: den 3 oktober 2013 15:28
Till: Martin Forsberg; UBL-Dev
Ämne: Re: SV: [ubl-dev] UBL OrderResponseCode
Can you point the way to the implementation guide ?
I have been looking at all the deliverables
but somehow I do not seem to find the document you are refering to.
In the PEPPOL implementation guide for order and order response (based on CENBII) we use the following codes:
30 -- Accepted with amendment in detail section
Från: Danny Gaethofs [mailto:dgaethofs@yahoo.com]
Skickat: den 3 oktober 2013 13:23
Till: UBL-Dev
Ämne: [ubl-dev] UBL OrderResponseCode
The OrderResponseCode has been added to UBL 2.1 - at least what I understand or can find about this -- some questions:
- what was / is used in UBL 2.0 to exchanges the status of the order response : rejected, accepted , accepted with amendmends ?
- what is the preferrerd listAgencyID or name and what are the listID's
Can the UN/EDIFACT values used in the BGM 1225 be used and what would then be the listAgencyID ?
1225=29 Accepted without amendment, Referenced message is entirely accepted.
|
|
| |
| |
| |
1225=4 Change. Message containing items (e.g. line items, goods items, Customs items, equipment items) to be changed in a previously sent message.
|
|
1225=34 Accepted with amendment. The referenced message is accepted but amended.
IF NO delivery date LIN+DTM+69 is available 1225=45 Accepted with reserve. >> no delivery date known
|
|