Version 1.1

Release date

2024-11-xx

This is the first release update of the Peppol Logistics standard. This time only minor changes are included.

New BIS documents

  • No BIS documents are added in this release.

Updated BIS documents

  • PEPPOL BIS Advanced Despatch Advice Only 1.3

  • PEPPOL BIS Advanced Despatch Advice with Receipt Advice 1.1

  • PEPPOL BIS Weight Statement 1.3

  • PEPPOL BIS Transport Execution Plan with Request 1.1

  • PEPPOL BIS Transport Execution Plan only 1.1

  • PEPPOL BIS Waybill 1.1

  • PEPPOL BIS Transportation Status with Request 1.1

  • PEPPOL BIS Transportation Status only 1.1

New Transactions

  • No transactions are added in this release.

Updated Transactions

  • Peppol Advanced Despatch Advice 1.3 (T120)

  • Peppol Weight Statement 1.3 (T122)

  • Peppol Transport Execution Plan Request 1.1 (T123)

  • Peppol Transport Execution Plan 1.1 (T124)

  • Peppol Waybill 1.1 (T125)

  • Peppol Transportation Status Request 1.1 (T126)

  • Peppol Transportation Status 1.1 (T127)

  • Peppol Receipt Advice 1.1 (T128)

New Codelists

  • TransportHandlingUnitIDType Added to specify which type of Transport Handling Unit ID that is used. It is linked to @schemeID under cac:TransportHandlingUnit/cbc:ID.

  • ConsignmentIDType Added to specify which type of Consignment ID that is used. It is linked to @schemeID under cac:Consignment/cbc:ID

  • ShipmentIDType Added to specify which type of Shipment ID that is used. It is linked to @schemeID under cac:Shipment/cbc:ID.

Updated Codelists

  • UNCL7143 Two values added, upgrading the codelist to version D23A.

New Rules

  • No rules are added in this release.

Updated Rules

  • No rules are changed in this release.

Request For Change (RFC) that are included/solved in Release 1.1

  • LLC-1 Add option to set an attribute on the Transport Handling Unit ID when SSCC identities are used in Transport Execution Plan Request (TEPR), Transport Execution Plan (TEP), Transportation Status Request (TSR) and Transportation Status (TS).

  • LLC-3 Receipt Advice - Add option to set an attribute on the Transport Handling Unit ID when SSCC identities are used.

  • LLC-4 Add option to use and identify globally unique identities on Consignment in Transport Execution Plan Request (TEPR), Transport Execution Plan (TEP), Transportation Status Request (TSR) and Transportation Status (TS).

  • LLC-5 Waybill - Add option to use and identify globally unique identities on Shipment and Consignment.

  • LLC-6 Waybill - Add option to set an attribute on the Transport Handling Unit ID when SSCC identities are used.

  • LLC-7 Weight Statement - Add option to use and identify globally unique identities on Shipment.

  • LLC-9 Change "Euro Step" to "Euro Stage"

  • LLC-10 Advanced Despatch Advice - Add option to use and identify globally unique identities on Shipment and Consignment.

  • LLC-11 Advanced Despatch Advice - Add option to set an attribute on the Transport Handling Unit ID when SSCC identities are used.

  • LLC-12 Recipt Advice - Add option to use and identify globally unique identities on Shipment and Consignment

Changes that are a part of Release 1.1

  • Attribute @schemeID added to cbc:ID under cac:Shipment and a codelist is attached to @schemeID. A description how to use GS1 GSIN is also added, both in description and in BIS document.

  • Attribute @schemeID added to cbc:ID under cac:Consignment and a codelist is attached to @schemeID. A description how to use GS1 GINC is also added, both in description and in BIS document.

  • Attribute @schemeID added to cbc:ID under cac:TransportHandlingUnit and a codelist is attached to @schemeID. A description how to use GS1 SSCC is also added, both in description and in BIS document.

  • "Euro Step" is changed to "Euro Stage" which is the correct name on engine types when reporting fuel consumption in the Advanced Despatch Advice.

  • Usecase examples are changed accordingly.

Version 1.0

Release date

2023-12-20

This is the first release containing profiles and transactions to be part of the OpenPeppol Logistics Domain. The content is developed in the Logistics Incubation project with BEAst and Offshore Norge as main contributors.

New BIS documents

  • Advanced Despatch Advice Only 1.2

  • Advanced Despatch Advice with Receipt Advice 1.0

  • Weight Statement 1.2

  • Transport Execution Plan with Request 1.0

  • Transport Execution Plan Only 1.0

  • Waybill 1.0

  • Transportation Status with Request 1.0

  • Transportation Status Only 1.0

New transactions

  • Advanced Despatch Advice 1.2 (T120)

  • Weight Statement 1.2 (T122)

  • Transport Execution Plan Request 1.0 (T123)

  • Transport Execution Plan 1.0 (T124)

  • Waybill 1.0 (T125)

  • Transportation Status Request 1.0 (T126)

  • Transportation Status 1.0 (T127)

  • Receipt Advice 1.0 (T128)

Validation artefacts for each BIS

Rules

For each BIS there are three sets of rules:

Common rules

These are rules that apply to all transaction and address issues such as, there may not be empty elements or that a date must be structure following the YYYY-MM-DD ISO format.

Each common rule has an identifier. As example "PEPPOL-COMMON-R001"

Basic rules

These are rules that are automatically generated based on the syntax datamodel. These include rules on:

  • Cardinality of elements and classes.

  • Allowed fixed values for elements and attributes.

  • Allowed codes in code lists.

Each basic rule has an identifier that include the transaction id and a sequential number starting with a B. As example "PEPPOL-T120-B00101"

Business rules

There are business rules that can not be automatically generated from the data model. These are mainly rules that concern relations between elements, such as:

  • Conditional values (IF-THEN)

  • Calculations of elements.

  • Minimum and maximum values.

  • Dependencies between elements.

Each business rule has an identifier that include the transaction id and a sequential number starting with a R. As example "PEPPOL-T120-R001"

Downloads

These contain two type.

  • Schematron files that can be used for validating a transactions.

    • Schematron files for all transactions are provided in a single zip file.

  • Example files that can be used in tests and as reference in implementations.

    • Example files for all transaction are also provided in a single zip file.

Codes

The documentation includes a listing of all code lists used in one or more transactions. The code lists are fully populated with information on where they are used, what their code values are and their definitions.

When a BIS specification defines how a code is used that definition overrules the general definition in the code list.