Skip to content

Commit

Permalink
Payload compliance and spelling issues
Browse files Browse the repository at this point in the history
  • Loading branch information
Hans Petersen committed Sep 24, 2024
1 parent 63b8c7d commit dedd0be
Show file tree
Hide file tree
Showing 3 changed files with 29 additions and 3 deletions.
2 changes: 2 additions & 0 deletions guides/compliance/main.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -22,4 +22,6 @@ include::sender.adoc[]

include::receiver.adoc[]

include::payload.adoc[]

:leveloffset: -1
18 changes: 18 additions & 0 deletions guides/compliance/payload.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
= Payload compliance to BIS
[horizontal]

== Processing of rules
* The value of the SBDH element "Sender/Identifier" MUST be equivalent to the value in the sender party's "Party/EndpointID" element and its "schemeID" attribute.

* The value of the SBDH element "Receiver/Identifier" MUST be equivalent to the value in the receiver's party "Party/EndpointID" element and its "schemeID" attribute.

example:
[attributes]
====
SBDH representation:
<Identifier Authority="iso6523-actorid-upis">0088:7315458756324</Identifier>
UBL representation:
<cbc:EndpointID schemeID="0088">7315458756324</cbc:EndpointID>
====

See Policy for use of Identifiers
12 changes: 9 additions & 3 deletions guides/release-notes/v3.0.14.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,11 @@ Release date:: November 2024
* BIS Ordering and Order Only
** Added sample file and use case which describes consignment orders and vendor-managed inventory

== Changes to Compliance BIS document
* Added new compliance on SBDH and BIS3 payload
** The value of the SBDH element "Sender/Identifier" MUST be equivalent to the value in the sender party’s "Party/EndpointID" element and its "schemeID" attribute.
** The value of the SBDH element "Receiver/Identifier" MUST be equivalent to the value in the receiver’s party "Party/EndpointID" element and its "schemeID" attribute

== Changes to syntax
* Order transaction (T01)
** Added optional element ID to AdditionalItemProperty with corresponding update in Use Case 4.
Expand All @@ -23,12 +28,13 @@ Release date:: November 2024
* Order Response transaction Advanced (T116)
* Despatch Advice (T16)
** Optional attribute added to indicate the scheme of the Transport Handling Unit identifier.
** Added optional element ID to AdditionalItemProperty .
** Added optional element ID to AdditionalItemProperty.
* Catalogue transaction (T19)
** Added optional element ID to AdditionalItemProperty with corresponding update in Use Case 5.
* Punchout transaction (T77)
Add ”cac:DocumentReference” to Certificate.
this may contain vital information regarding the label and has a simular function as in Catalogue.
** Added optional element ID to AdditionalItemProperty.
** Added ”cac:DocumentReference” to Certificate.
*** this may contain vital information regarding the label and has a similar function as in Catalogue.

== Changes to code lists and validation artefacts
* Added new codelist with code values SSCC (Serial Shipping Container Code) and ZZZ (Mutually defined) to the optional attribute that indicates the type/scheme for Transport handling unit identifier (in Despatch Advice)
Expand Down

0 comments on commit dedd0be

Please sign in to comment.