FprEN 17016-2
(Main)Electronic Public Procurement - Ordering - Part 2: Transactions
Electronic Public Procurement - Ordering - Part 2: Transactions
This document describes the transaction information requirements of the transactions used in the collaborations described in EN 17016-1:2024. For each transaction are specified the transaction business requirements, the transaction information data model containing definitions of terms, usage descriptions and cardinality of the information elements and the transaction business rules.
This document describes the following transactions:
1) Order;
2) Order Change;
3) Order Cancellation;
4) Order Response Simple
5) Order Confirmation;
6) Order Rejection;
7) Order Response;
8) Order Change Confirmation;
9) Order Change Rejection;
10) Order Cancellation Confirmation;
11) Order Cancellation Rejection;
12) Order Agreement.
How to claim compliance to a transaction is specified in Clause 6.
How to claim conformance to a transaction is also specified in Clause 6.
Elektronisches öffentliches Beschaffungswesen - Bestellung - Teil 2: Transaktionen
Dieses Dokument beschreibt die Anforderungen an Transaktionsinformationen hinsichtlich der Transaktionen, die im Rahmen der in EN 17016 1:2024 beschriebenen Formen der Zusammenarbeit verwendet werden. Für jede Transaktion werden die transaktionsbezogenen geschäftlichen Anforderungen, das Datenmodell für die Transaktionsinformationen, welches Begriffsdefinitionen, Anwendungs¬beschreibungen und Kardinalität der Informationselemente umfasst, sowie Transaktionsgeschäftsregeln festgelegt.
Dieses Dokument beschreibt die folgenden Transaktionen:
1) Bestellung;
2) Bestellungsänderung;
3) Bestellungsstornierung;
4) einfache Bestellantwort
5) Bestellbestätigung;
6) Bestellablehnung;
7) Bestellantwort;
8) Bestellungsänderungsbestätigung;
9) Bestellungsänderungsablehnung;
10) Bestellungsstornierungsbestätigung;
11) Bestellungsstornierungsablehnung;
12) Bestellungsvereinbarung.
Wie die Compliance mit dieser Transaktion beansprucht wird, ist in Abschnitt 6 festgelegt.
Wie die Conformance mit einer Transaktion beansprucht wird, ist in Abschnitt 6 festgelegt.
Passation électronique des marchés publics - Gestion des commandes - Partie 2 : Transactions
Le présent document décrit les exigences en matière d'informations sur les transactions utilisées dans les collaborations décrites dans l'EN 17016-1:2024, Passation électronique des marchés publics - Gestion des commandes - Partie 1 : Chorégraphies. Pour chaque transaction sont spécifiées les exigences commerciales de la transaction, le modèle de données d'information de la transaction contenant les définitions des termes, les descriptions d'utilisation et la cardinalité des éléments d'information, ainsi que les règles commerciales de la transaction.
Le présent document décrit les transactions suivantes :
1) commande ;
2) modification de commande ;
3) annulation de commande ;
4) accusé de réception de commande simple ;
5) confirmation de commande ;
6) refus de commande ;
7) accusé de réception de commande ;
8) confirmation de modification de commande ;
9) refus de modification de commande ;
10) confirmation d'annulation de commande ;
11) refus d'annulation de commande ;
12) contrat de commande.
Le présent document sur les transactions est identifié par la référence EN 17016-2:20XX.
L'Article 6 précise les critères à respecter pour revendiquer la conformité à une transaction.
L'Article 6 précise également les critères à respecter pour revendiquer la conformité à une transaction.
Elektronska javna naročila - Naročanje - 2. del: Transakcije
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
oSIST prEN 17016-2:2024
01-november-2024
Elektronska javna naročila - Naročanje - 2. del: Transakcije
Electronic Public Procurement - Ordering - Part 2: Transactions
Elektronisches öffentliches Beschaffungswesen - Bestellung - Teil 2: Transaktionen
Passation électronique des marchés publics - Gestion des commandes - Partie 2 :
Transactions
Ta slovenski standard je istoveten z: prEN 17016-2
ICS:
03.100.10 Nabava. Dobava. Logistika Purchasing. Procurement.
Logistics
35.240.20 Uporabniške rešitve IT pri IT applications in office work
pisarniškem delu
35.240.63 Uporabniške rešitve IT v IT applications in trade
trgovini
oSIST prEN 17016-2:2024 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
oSIST prEN 17016-2:2024
oSIST prEN 17016-2:2024
DRAFT
EUROPEAN STANDARD
prEN 17016-2
NORME EUROPÉENNE
EUROPÄISCHE NORM
August 2024
ICS 35.240.63
English Version
Electronic Public Procurement - Ordering - Part 2:
Transactions
Passation électronique des marchés publics - Gestion Elektronisches öffentliches Beschaffungswesen -
des commandes - Partie 2 : Transactions Bestellung - Teil 2: Transaktionen
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 440.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 17016-2:2024 E
worldwide for CEN national Members.
oSIST prEN 17016-2:2024
prEN 17016-2:2024 (E)
Contents Page
European foreword . 5
Introduction . 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 7
4 Positioning in EIRA (European Interoperability Reference Architecture) . 8
5 Collaborations and Transactions . 9
5.1 Transactions involved in Ordering choreography . 9
5.2 Transaction identifiers . 12
6 Compliance and Conformance . 13
7 Business requirements . 13
7.1 Common business requirements . 13
7.2 Order (T-17016-2:20xx-1) specific business requirements . 14
7.3 Order change (T-17016-2:20xx-2) specific business requirements . 15
7.4 Order Cancellation (T-17016-2:20xx-3) specific business requirements . 17
7.5 Order Response Simple (T-17016-2:20xx-4) specific business requirements . 17
7.6 Order Confirmation (T-17016-2:20xx-5) specific business requirements . 17
7.7 Order Rejection (T-17016-2:20xx-6) specific business requirements . 17
7.8 Order Response (T-17016-2:20xx-7) specific business requirements . 17
7.9 Order Change Confirmation (T-17016-2:20xx-8) Specific business requirements . 18
7.10 Order Change Rejection (T-17016-2:20xx-9) specific business requirements . 18
7.11 Order Cancellation Confirmation (T-17016-2:20xx-10) specific business
requirements . 19
7.12 Order Cancellation Rejection (T-17016-2:20xx-11) specific business requirements . 19
7.13 Order Agreement (T-17016-2:20xx-12) specific business requirements . 19
8 Data models . 21
8.1 Use of the ePo ontology . 21
8.2 Legend . 21
8.3 Order data model (T-17016-2:20xx-1) . 23
8.4 Order Change data model (T-17016-2:20xx-2) . 86
8.5 Order Cancellation data model (T-17016-2:20xx-3) . 86
8.6 Order Response Simple data model (T-17016-2:20xx-4) . 87
8.7 Order Confirmation data model (T-17016-2:20xx-5) . 87
8.8 Order Rejection data model (T-17016-2:20xx-6) . 87
8.9 Order Response data model (T-17016-2:20xx-7) . 87
8.10 Order Change Confirmation data model (T-17016-2:20xx-8) . 88
8.11 Order Change Rejection data model (T-17016-2:20xx-9) . 88
8.12 Order Cancellation Confirmation data model (T-17016-2:20xx-10) . 88
8.13 Order Cancellation Rejection data model (T-17016-2:20xx-11) . 88
8.14 Order Agreement data model (T-17016-2:20xx-12) . 89
9 Business rules . 90
9.1 Common business rules . 90
9.2 Order (T-17016-2:20xx-1) business rules . 91
oSIST prEN 17016-2:2024
prEN 17016-2:2024
9.3 Order Change (T-17016-2:20xx-2) business rules . 92
9.4 Order Cancellation (T-17016-2:20xx-3) business rules . 92
9.5 Order Response Simple (T-17016-2:20xx-4) business rules . 93
9.6 Order Confirmation (T-17016-2:20xx-5) business rules . 93
9.7 Order Rejection (T-17016-2:20xx-6) business rules . 93
9.8 Order Response (T-17016-2:20xx-7) business rules . 93
9.9 Order Change Confirmation (T-17016-2:20xx-8) business rules . 94
9.10 Order Change Rejection (T-17016-2:20xx-9) business rules . 94
9.11 Order Cancellation Confirmation (T-17016-2:20xx-10) business rules . 94
9.12 Order Cancellation Rejection (T-17016-2:20xx-11) business rules . 95
9.13 Order Agreement (T-17016-2:20xx-12) business rules . 95
Bibliography . 97
Tables
Table 1 — Positioning in EIRA .9
Table 2 — Roles, capabilities, basic collaborations and transactions per variant . 10
Table 3 — Transaction identifiers . 13
Table 4 — Common business requirements. 13
Table 5 — Order business requirements . 14
Table 6 — Order change business requirements . 15
Table 7 — Order cancellation business requirements . 17
Table 8 — Order Response Simple business requirements . 17
Table 9 — Order Confirmation business requirements. 17
Table 10 — Order Rejection business requirements . 17
Table 11 — Order Response business requirements . 18
Table 12 — Order Change Confirmation business requirements . 18
Table 13 — Order Change Rejection business requirements . 18
Table 14 — Order Cancellation Confirmation business requirements . 19
Table 15 — Order Cancellation Rejection business requirements . 19
Table 16 — Order Agreement business requirements . 19
Table 17 — Order semantic data model . 23
Table 18 — Order Change semantic data model . 86
Table 19 — Order Cancellation semantic data model . 87
Table 20 — Order Response Simple semantic data model . 87
oSIST prEN 17016-2:2024
prEN 17016-2:2024 (E)
Table 21 — Order Confirmation semantic data model . 87
Table 22 — Order Rejection semantic data model . 87
Table 23 — Order Response semantic data model . 88
Table 24 — Order Change Confirmation semantic data model . 88
Table 25 — Order Rejection data model . 88
Table 26 — Order Cancellation Confirmation data model . 88
Table 27 — Order Cancellation Rejection data model . 89
Table 28 — Order Rejection data model . 89
Table 29 — Common business rules. 90
Table 30 — Order business rules . 91
Table 31 — Order Change business rules . 92
Table 32 — Order Cancellation business rules . 93
Table 33 — Order Response Simple business rules . 93
Table 34 — Order Confirmation business rules . 93
Table 35 — Order Rejection business rules . 93
Table 36 — Order Response business rules . 94
Table 37 — Order Change Confirmation business rules . 94
Table 38 — Order Change Rejection business rules . 94
Table 39 — Order Cancellation Confirmation business rules . 95
Table 40 — Order Cancellation Rejection business rules . 95
Table 41 — Order Agreement business rules . 95
oSIST prEN 17016-2:2024
prEN 17016-2:2024
European foreword
This document (prEN 17016-2:2024) has been prepared by the Technical Committee CEN/TC 440
“Electronic public procurement”, the secretariat of which is held by DIN.
This document is currently submitted to the CEN Enquiry.
This document falls under a CEN-CENELEC pilot on derivative use (as approved by the CEN/CA
(Administrative Board) through decision 37/2019). For more information about the implementation of
derivative use in CEN/TC 440, see here.
This document is part of a series of multi-part documents prepared, or under preparation, by
CEN/TC 440:
— 17011-series: eProcurement Architecture, providing a set of specifications outlining different
aspects of the eProcurement architecture for Business Interoperability Specifications.
— 17014-series: Pre-Award Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the Pre-Award phase in Public Procurement.
— 17015-series: eCatalogue Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the catalogue process.
— 17016-series: eOrdering Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the ordering process.
— 17017-series: eFulfilment Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the fulfilmet process.
The terms "shall", "shall not", "should", "should not", "may", "can" and "cannot" are interpreted according
to Clause 7 of the CEN-CENELEC Internal Regulations Part 3 .
https://boss.cen.eu/reference-material/refdocs/pages/
oSIST prEN 17016-2:2024
prEN 17016-2:2024 (E)
Introduction
Derivative use pilot
This document falls under a CEN-CENELEC pilot on derivative use (as approved by the CEN/CA
(Administrative Board) through decision 38/2019).
CEN has the copyright to all CEN publications, including their entire content and associated metadata, as
specified in CEN-CENELEC Guide 10 "Policy on the distribution, sale and copyright of CEN and CENELEC
Content". However, through the derivative use pilot, CEN gives permission to the copying, replication and
translation of content from CEN/TC 440 deliverables in specific circumstances.
Under the derivative use pilot, specific sections of CEN/TC 440 publications may be copied, replicated
and translated in cases where this is a necessary condition for the meaningful implementation of the
publication. The sections which fall under derivative use will typically be elements such as semantic
definitions and rules related to the use of information elements and the name, definition and description
of processes and transactions, which are needed in software solutions, whether intended for sale in the
private market or for use in the public sector, and documents guiding the implementation and use in
specific countries and/or business sectors.
Under derivative use, any use of content which has been copied, replicated or translated from a
CEN/TC 440 publication, should comply with the intended use of the publication. Derivative use cannot
be applied in use cases other than those the publication is intended to support. The intended use of this
publication is set out below.
Intended use of this publication
This document has been developed for any organization looking for guidance on the implementation and
use of electronic procurement deliverables as well as for organizations developing or implementing
software applications related to electronic procurement, such as software providers, business entities
and national authorities. These software applications should be in conformance with this publication.
Parts of the document to which derivative use apply
Each subclause which falls under derivative use will be clearly marked with a note. The degree to which
the specific content can be modified is defined in CEN/TS 17011-3:— , Electronic Public Procurement —
Architecture — Part 3: Customization Guideline.
Annex A provides an overview of the line number references to all subclauses of the publication which
fall under derivative use.
Use of ePO ontology
This document uses the ePO ontology, owned by the European Union, available here
(https://github.com/OP-TED/ePO) and licensed under a CC BY 4.0 licence.
Under preparation. Current stage: FprCEN/TS 17011-3:2024.
oSIST prEN 17016-2:2024
prEN 17016-2:2024
1 Scope
This document describes the transaction information requirements of the transactions used in the
collaborations described in EN 17016-1:2024, Electronic Public Procurement — Ordering — Part 1:
Choreographies. For each transaction are specified the transaction business requirements, the
transaction information data model containing definitions of terms, usage descriptions and cardinality of
the information elements and the transaction business rules.
This document describes the following transactions:
1) Order;
2) Order Change;
3) Order Cancellation;
4) Order Response Simple
5) Order Confirmation;
6) Order Rejection;
7) Order Response;
8) Order Change Confirmation;
9) Order Change Rejection;
10) Order Cancellation Confirmation;
11) Order Cancellation Rejection;
12) Order Agreement.
The identifier of this transactions document is EN 17016-2:20XX.
How to claim compliance to a transaction is specified in Clause 6.
How to claim conformance to a transaction is also specified in Clause 6.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— IEC Electropedia: available at https://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp/
3.1
agent
person, organization, or system that acts in procurement or has the power to act in procurement
oSIST prEN 17016-2:2024
prEN 17016-2:2024 (E)
3.2
business process
sequence or network of activities and collaborations between two or more agents
3.3
business process variant
specification of a business process belonging to a choreography
Note 1 to entry: Different variants may support different electronic information exchange or collaborations.
Agents may publicly advertise their capability to support one or more variants in an automated fashion.
3.4
choreography
set of business processes having the same goals
3.5
collaboration
interaction between two or more agents that result in the exchange of data between the agents involved
as part of a business process
3.6
role
part played by an agent in a particular business process, including its responsibilities (options and
obligations) to perform certain activities and collaborations in that business process
Note 1 to entry: The role is used to show the division of labour and responsibility amongst the agents involved in
the process or within the organization of an agent.
3.7
state
set of options and obligations of the participating agents at a defined step in a business process to perform
specific activities and collaborations
Note 1 to entry: Additional information: an activity of an agent or a collaboration may cause the transition of one
state to another in a predefined set of next steps.
3.8
transaction
content of data exchanged or shared between the agents in a collaboration
Note 1 to entry: A transaction is the atomic unit that leads to a synchronized state in the information systems of
collaborating agents. It is the basic building block to define the choreography between agents. When an agent
recognizes an event that changes the state of a business object within a business process, it uses a transaction to
synchronize with the collaborating agent. A transaction therefore changes the state of a business process. It carries
the intention of the initiating agent and is represented by a data structure that is defined by a data model. The
exchange of a transaction may alter legal obligations between business partners.
4 Positioning in EIRA (European Interoperability Reference Architecture)
EIRA (European Interoperability Reference Architecture) provides a reference model that enables
architects to position the IOP (InterOPerability) specifications. This document provides a domain-specific
IOP specification to which any SBB (Solution Building Block) implementing the ABB (Architecture
Building Block) should be compliant to. The positioning of this document in the EIRA context is specified
in Table 1.
oSIST prEN 17016-2:2024
prEN 17016-2:2024
IoP specifications provide a valuable source of information to formulate requirements during
architecture development and solution development. By identifying architectural building blocks
through a common terminology, it:
— helps the reuse of cross domain building blocks such as e.g. eSignature Verification and Validation
Service, and eTimestamp Creation Service;
— helps the synchronization with European solutions such as CEF eDelivery; and
— will provide guidance in using them to provide the prescribed capability enabling, thus managing
and rationalizing IT portfolios.
Table 1 — Positioning in EIRA
EIRA ID Title Domain Interface Scope Modality
EN 17016-2:20XX Electronic Procurement Machine • eProcurement Endorsing
Public /Customer extension of
Procurement ABB176
Machine
- Ordering - Organizational
/Supplier
Transactions Interoperability
Specification
• eProcurement
extension of
ABB170 Exchange
of Business
Information
• eProcurement
extension of ABB16
Business Rule
5 Collaborations and Transactions
5.1 Transactions involved in Ordering choreography
Table 2 lists the transactions and the collaborations in which they are used .
See EN 17016-1:2024, Electronic Public Procurement – Ordering – Part 1: Choreographies, Clause 6.
oSIST prEN 17016-2:2024
prEN 17016-2:2024 (E)
Table 2 — Roles, capabilities, basic collaborations and transactions per variant
Role Capability Collaboration Collaboration Transaction Transaction Variant
ID ID
A B C D E F G H
Buyer Send Order BC-17016- Buyer sends T-17016- Order M M M M M M M
1:2024-1 Order 2:20XX-1
Seller Receive BC-17016- Buyer sends T-17016- Order M M M M M M M
Order 1:2024-1 Order 2:20XX-1
Buyer Change an BC-17016- Buyer T-17016- Order Change M M M M
Order 1:2024-2 changes Order 2:20XX-2
Seller Receive an BC-17016- Buyer T-17016- Order Change M M M M
Order Change 1:2024-2 changes Order 2:20XX-2
Buyer Cancel an BC-17016- Buyer cancels T-17016- Order M M M M
Order 1:2024-3 Order 2:20XX-3 Cancellation
Seller Receive an BC-17016- Buyer cancels T-17016- Order M M M M
Order 1:2024-3 Order 2:20XX-3 Cancellation
Cancellation
Seller Acknowledge BC-17016- Seller T-17016- Oder M M
an Order 1:2024-4 acknowledges 2:20XX-4 Response
Order Simple
Buyer Receive an BC-17016- Seller T-17016- Oder M M
Order 1:2024-4 acknowledges 2:20XX-4 Response
Response Order Simple
Simple
Seller Accept an BC-17016- Seller T-17016- Order M M M M M
Order 1:2024-5 confirms 2:20XX-5 Confirmation
without Order
changes
Buyer Receive an BC-17016- Seller T-17016- Order M M M M M
Order 1:2024-5 confirms 2:20XX-5 Confirmation
Confirmation Order
Seller Reject an BC-17016- Seller rejects T-17016- Order M M M M M
Order 1:2024-6 Order 2:20XX-6 Rejection
Buyer Receive an BC-17016- Seller rejects T-17016- Order M M M M M
Order 1:2024-6 Order 2:20XX-6 Rejection
Rejection
Seller Accept BC-17016- Seller T-17016- Order Change M M M
changes to an 1:2024-7 confirms 2:20XX-8 Confirmation
Order Order Change
Buyer Receive an BC-17016- Seller T-17016- Order Change M M M
Order Change 1:2024-7 confirms 2:20XX-8 Confirmation
Confirmation Order Change
oSIST prEN 17016-2:2024
prEN 17016-2:2024
Role Capability Collaboration Collaboration Transaction Transaction Variant
ID ID
A B C D E F G H
Seller Reject BC-17016- Seller rejects T-17016- Order Change M M M
changes to an 1:2024-8 Order Change 2:20XX-9 Rejection
Order
Buyer Receive an BC-17016- Seller rejects T-17016- Order Change M M M
Order Change 1:2024-8 Order Change 2:20XX-9 Rejection
Rejection
Seller Accept an BC-17016- Seller T-17016- Order M M M
Order 1:2024-9 confirms 2:20XX-10 Cancellation
Cancellation Order Confirmation
Cancellation
Buyer Receive BC-17016- Seller T-17016- Order M M M
Order 1:2024-9 confirms 2:20XX-10 Cancellation
Cancellation Order Confirmation
Confirmation Cancellation
Seller Reject an BC-17016- Seller rejects T-17016- Order M M M
Order 1:2024-10 Order 2:20XX-11 Cancellation
cancellation Cancellation Rejection
Buyer Receive an BC-17016- Seller rejects T-17016- Order M M M
Order 1:2024-10 Order 2:20XX-11 Cancellation
Cancellation Cancellation Rejection
Rejection
Seller Accept an BC-17016- Seller accepts T-17016- Order M M M
Order 1:2024-11 Order 2:20XX-7 Response
partially or partially or
with changes with changes
Buyer Receive an BC-17016- Seller accepts T-17016- Order M M M
Order 1:2024-11 Order 2:20XX-7 Response
Response partially or
with changes
Seller Change a BC-17016- Seller changes T-17016- Order M M M
confirmed 1:2024-12 Order 2:20XX-7 Response
Order
Buyer Receive an BC-17016- Seller changes T-17016- Order M M M
Order Change 1:2024-12 Order 2:20XX-7 Response
Buyer Accept an BC-17016- Buyer T-17016- Order Change M M
Order 1:2024-13 confirms 2:20XX-8 Confirmation
Response Order
Response
oSIST prEN 17016-2:2024
prEN 17016-2:2024 (E)
Role Capability Collaboration Collaboration Transaction Transaction Variant
ID ID
A B C D E F G H
Seller Receive an BC-17016- Buyer T-17016- Order Change M M
Order 1:2024-13 confirms 2:20XX-8 Confirmation
Response Order
Confirmation Response
Buyer Reject an BC-17016- Buyer rejects T-17016- Order Change M M
Order 1:2024-14 Order 2:20XX-9 Rejection
Response Response
Seller Receive an BC-17016- Buyer rejects T-17016- Order Change M M
Order 1:2024-14 Order 2:20XX-9 Rejection
Response Response
Rejection
Buyer Accept BC-17016- Buyer T-17016- Order Change M M
changes to an 1:2024-15 confirms 2:20XX-8 Confirmation
Order Order Change
Seller Receive an BC-17016- Buyer T-17016- Order Change M M
Order Change 1:2024-15 confirms 2:20XX-8 Confirmation
Confirmation Order Change
Buyer Reject BC-17016- Buyer rejects T-17016- Order Change M M
changes to an 1:2024-16 Order Change 2:20XX-9 Rejection
Order
Seller Receive an BC-17016- Buyer rejects T-17016- Order Change M M
Order Change 1:2024-16 Order Change 2:20XX-9 Rejection
Rejection
Seller Send Order BC-17016- Seller sends T-17016- Order M
Agreement 1:2024-17 Order 2:20XX-12 Agreement
Agreement
Buyer Receive BC-17016- Seller sends T-17016- Order M
Order 1:2024-17 Order 2:20XX-12 Agreement
Agreement Agreement
Key
M Mandatory for the capability in the variant.
5.2 Transaction identifiers
Table 3 specifies the identifier of the transactions described in this document.
oSIST prEN 17016-2:2024
prEN 17016-2:2024
Table 3 — Transaction identifiers
ID Name of the transaction
T-17016-2:20xx-1 Order
T-17016-2:20xx-2 Order Change
T-17016-2:20xx-3 Order Cancellation
T-17016-2:20xx-4 Order Response Simple
T-17016-2:20xx-5 Order Confirmation
T-17016-2:20xx-6 Order Rejection
T-17016-2:20xx-7 Order Response
T-17016-2:20xx-8 Order Change Confirmation
T-17016-2:20xx-9 Order Change Rejection
T-17016-2:20xx-10 Order Cancellation Confirmation
T-17016-2:20xx-11 Order Cancellation Rejection
T-17016-2:20xx-12 Order Agreement
6 Compliance and Conformance
The content of this clause will be defined in accordance with WG1 after the completion of the work on
CEN/TS 17011-3 customization guideline and in alignment with the work in TC 434.
7 Business requirements
7.1 Common business requirements
Table 4 specifies the business requirements common to all transactions.
Table 4 — Common business requirements
ID Description
R-TC440-1 A transaction shall provide information about its identity, type (Order,
Order Change etc), business process variant, issue date and validity.
R-TC440-2 All amounts in a transaction shall be stated in the same currency.
R-TC440-3 A transaction shall contain non-negative prices and non-negative
quantities.
R-TC440-4 A transaction shall contain elements for identifying the Buyer and Seller
with legal name, legal registration ID and the country of establishment -
residence.
R-TC440-5 A transaction shall provide for the Buyer’s and the Seller’s electronic
address.
R-TC440-6 Each line in a transaction shall be clearly identified to enable referencing
from other transactions.
R-TC440-7 For any information, the specific business term shall be used, if existing.
oSIST prEN 17016-2:2024
prEN 17016-2:2024 (E)
7.2 Order (T-17016-2:20xx-1) specific business requirements
Table 5 specifies the business requirements of the Order.
Table 5 — Order business requirements
ID Description
T-17016-2:20xx-1-R-1 An Order shall enable the Buyer to reference tenders, contracts and
documents that are relevant to prices and terms, including terms of
delivery.
T-17016-2:20xx-1-R-2 In an Order it shall be possible to reference another Order.
T-17016-2:20xx-1-R-3 In an Order it shall be possible to specify a Buyer’s accounting reference.
T-17016-2:20xx-1-R-4 In an Order it shall be possible to provide for contact details of the
department of the Buyer or natural person inside the Buyer who
originated the order as a whole.
T-17016-2:20xx-1-R-5 In an Order it shall be possible to provide for information about the
department of the Buyer or the external organization that is in charge of
receiving and treating the invoice(s) related to the Order.
T-17016-2:20xx-1-R-6 In an Order it shall be possible to provide for details about delivery
location (address and ID), some basic delivery terms, delivery time and
contact person for the purpose of delivery.
T-17016-2:20xx-1-R-7 In an Order it shall be possible to provide for information about the
external organization to which the goods are to be sent and that will take
possession of them after delivery.
T-17016-2:20xx-1-R-8 In an Order it shall be possible to provide for information about the dates
before and/or after which the Order lines shall be delivered.
T-17016-2:20xx-1-R-9 In an Order it shall be possible to provide for information about the value
of items ordered and what prices, charges and totals (including estimate
of VAT) are expected to be paid in a way that can be matched against an
invoice.
T-17016-2:20xx-1-R-10 In an Order it shall be possible provide information needed to specify
estimated allowance and charges on document level that apply to the
order as a whole.
T-17016-2:20xx-1-R-11 In an Order is shall be possible to specify amounts to be paid in advance.
T-17016-2:20xx-1-R-12 In an Order it shall be possible to provide for information about the final
price that the buyer expects to pay exclusive of any VAT. This makes it
possible for the seller to verify against his price lists and contracts.
T-17016-2:20xx-1-R-13 An Order line shall provide for information about the quantity ordered
and its unit of measure.
T-17016-2:20xx-1-R-14 An Order line shall provide for the name of the item.
T-17016-2:20xx-1-R-15 In an Order line it shall be possible to specify a Seller’s identifier for the
item.
T-17016-2:20xx-1-R-16 In an Order line it shall be possible to specify a standard identifier for the
item.
oSIST prEN 17016-2:2024
prEN 17016-2:2024
ID Description
T-17016-2:20xx-1-R-17 In an Order line it shall be possible to specify a Buyer’s identifier for the
item.
T-17016-2:20xx-1-R-18 An Order line shall provide for the price of the item.
T-17016-2:20xx-1-R-19 In an Order line it shall be possible to provide for the base quantity to
which the price applies.
T-17016-2:20xx-1-R-20 In an Order line it shall be possible to state a price discount in terms of
percentage on the gross price or a per unit discount.
T-17016-2:20xx-1-R-21 In an Order line it shall be possible to state estimated allowances or
charges.
T-17016-2:20xx-1-R-22 In an Order line it shall be possible to specify a Buyer’s accounting
reference.
T-17016-2:20xx-1-R-23 In an Order line it shall be possible to specify the delivery location.
T-17016-2:20xx-1-R-24 In an Order line it shall be possible to specify a referenced catalogue line.
T-17016-2:20xx-1-R-25 In an Order line it shall be possible to specify a referenced document.
T-17016-2:20xx-1-R-26 An Order line shall provide for the item VAT category.
T-17016-2:20xx-1-R-27 An Order line shall provide for the item VAT percentage.
T-17016-2:20xx-1-R-28 An Order line shall provide for the total amount excluding VAT.
7.3 Order change (T-17016-2:20xx-2) specific business requirements
Table 6 specifies the business requirements of the Order change.
Table 6 — Order change business requirements
ID Description
T-17016-2:20xx-2-R-1 An Order Change shall enable the Buyer to reference tenders, contracts
and documents that are relevant to prices and terms, including terms of
delivery.
T-17016-2:20xx-2-R-2 An Order Change shall specify the Order that has to be changed.
T-17016-2:20xx-2-R-3 In an Order Change it shall be possible to specify a Buyer’s accounting
reference.
T-17016-2:20xx-2-R-4 In an Order Change it shall be possible to provide for contact details of the
department of the Buyer or natural person inside the Buyer who
originated the order as a whole.
T-17016-2:20xx-2-R-5 In an Order Change it shall be possible to provide for information about
the department of the Buyer or the external organization that is in charge
of receiving and treating the invoice(s) related to the Order Change.
In an Order Change it shall be possible to provide for details about delivery
T-17016-2:20xx-2-R-6 location (address and ID), some basic delivery terms, delivery time and
contact person for the purpose of delivery.
T-17016-2:20xx-2-R-7 In an Order Change it shall be possible to provide for information about
the external organization to which the goods are to be sent and that will
take possession of them after delivery.
oSIST prEN 17016-2:2024
prEN 17016-2:2024 (E)
ID Description
T-17016-2:20xx-2-R-8 In an Order Change it shall be possible to provide for information about
the dates before and/or after which the Order Change lines shall be
delivered.
T-17016-2:20xx-2-R-9 In an Order Change it shall be possible to provide for information about
the value of items ordered and what prices, charges and totals (including
estimate of VAT) are expected to be paid in a way that can be matched
against an invoice.
T-17016-2:20xx-2-R-10 In an Order Change it shall be possible provide information needed to
specify estimated allowance and charges on document level that apply to
the order as a whole.
T-17016-2:20xx-2-R-11 In an Order Change is shall be possible to specify amounts already paid.
T-17016-2:20xx-2-R-12 In an Order Change it shall be possible to provide for information about
the final price that the buyer expects to pay exclusive of any VAT. This
makes it possible for the seller to verify against his price lists and
contracts.
T-17016-2:20xx-2-R-13 An Order Change line shall provide for information about the quantity
ordered and its unit of measure.
T-17016-2:20xx-2-R-14 An Order Change line shall provide for the name of the item.
T-17016-2:20xx-2-R-15 In an Order Change line it shall be possible to specify a Seller’s identifier
for the item.
T-17016-2:20xx-2-R-16 In an Order Change line it shall be possible to specify a standard identifier
for the item.
T-17016-2:20xx-2-R-17 In an Order Change line it shall be possible to specify a Buyer’s identifier
for the item.
T-17016-2:20xx-2-R-18 An Order Change line shall provide for the price of the item.
T-17016-2:20xx-2-R-19 In an Order Change line it shall be possible to provide for the base quantity
to which the price applies.
T-17016-2:20xx-2-R-20 In an Order Change line it shall be possible to state informative price
discounts.
T-17016-2:20xx-2-R-21 In an Order Change line it shall be possible to state estimated allowances
or charges.
T-17016-2:20xx-2-R-22 In an Order Change line it shall be possible to specify a Buyer’s accounting
reference.
T-17016-2:20xx-2-R-23 In an Order Change line it shall be possible to specify the delivery location.
T-17016-2:20xx-2-R-24 In an Order Change line it shall be possible to specify a referenced
catalogue line.
T-17016-2:20xx-2-R-25 In an Order Change line it shall be possible to specify a referenced
document.
T-17016-2:20xx-2-R-26 An Order Change line shall provide for the item VAT category.
T-17016-2:20xx-2-R-27 An Order Change line shall provide for the item VAT percentage.
T-17016-2:20xx-2-R-28 An Order Change line shall provide for the total amount excluding VAT.
T-17016-2:20xx-2-R-29 An Order Change line shall provide for information about the type of
change made.
oSIST prEN 17016-2:2024
prEN 17016-2:2024
7.4 Order Cancellation (T-17016-2:20xx-3) specific business requirements
Table 7 specifies the business requirements of the Order cancellation.
Table 7 — Order cancellation business requirements
ID Description
T-17016-2:20xx-3-R-1 An Order Cancellation shall refer to the Order that has to be cancelled.
T-17016-2:20xx-3-R-2 An Order Cancellation shall cancel the full/complete Order.
7.5 Order Response Simple (T-17016-2:20xx-4) specific business requirements
Table 8 specifies the business requirements of the Order Response Simple.
Table 8 — Order Response Simple business requirements
ID Description
T-17016-2:20xx-4-R-1 An Order Response Simple shall refer to the Order that has to be
acknowledged.
T-17016-2:20xx-4-R-2 An Order Response Simple shall acknowledge the full/complete Order.
7.6 Order Confirmation (T-17016-2:20xx-5) specific business requirements
Table 9 shows the business requirements of the Order Confirmation.
Table 9 — Order Confirmation business
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.