Syntax Mapping T018 - Tendering Message Response 1.1

Notice publication response, root element

UBL version identifier
Requires UBL version 2.2

Fixed value: 2.2

Specification identification
Identifies the specification of content and rules that apply to the transaction.

Example value: urn:fdc:peppol.eu:prac:trns:t018:1.1

Business process type identifier
Identifies the BII profile or business process context in which the transaction appears.

Fixed value: urn:fdc:peppol.eu:prac:bis:p010:1.1

Response identifier
A transaction instance must contain an identifier. The identifier enables positive referencing the transaction instance for various purposes including referencing between transactions that are part of the same process. Must be expressed as a UUID.

Example value: 123e4567-e89b-12d3-a456-426614174000

Response issue date
The date on which the transaction instance was issued. Format "YYYY-MM-DD"

Example value: 2018-05-18

Response issue time
The time at which the transaction instance was issued. Format "hh:mm:ss

Example value: 14:44:33+01:00

Sender information
The party sending an electronic Tendering Message Response back to the sending party of the business document.

Contracting body electronic address identifier
Electronic address of the sending party.

Example value: DE122268496

Scheme identifier
Scheme identifier for the electronic address

Example value: 9930

Receiver information
The party, an electronic Tendering Message Response was addressed to, and who is supposed to process the Tendering Message Response. This is the same party as the sender of the business document.

Economic operator electronic address identifier
Electronic address of the receiving party

Example value: 500820007

Scheme identifier
Scheme identifier for the electronic address

Example value: 9946

Document response
The tendering response is used to indicate the result of business document validation. The element 'cac:DocumentResponse/cac:Response/cbc:ResponseCode' MUST contain the overall result code.

Response information

Message response code
An indicator stating whether the referenced message was cleared through validation and advanced to the next step in the process. A "rejection" states that the request was not processed because of identified issues. "Conditionally accepted" indicates that the request may not be correctly handled because of warnings indicated in the message. "Accepted" indicates that the tendering message will be processed as anticipated.

Example value: RE

Response textual notes
Used to make any comments or instructions relevant to the response. The use of this element may require manual assessment by the receiver. Standard should be the full name of the used Message Response Code.

Example value: Rejected

Document reference
The document reference is used to provide a reference to the tendering message on which the Tendering Message Response is based. The Tendering Message Response message may only cover exactly one business document. The element 'cac:DocumentResponse/cac:DocumentReference/cbc:ID' MUST contain the instance identifier of the notice of the original business document.

Tendering message identifier
Specifies the unique identifier of the container on which the Tendering Message Response is based.

Example value: 4e3517fd-724d-44fc-b90b-5743c33ff68e

PEPPOL transaction schema
An identification of the transaction on which the tendering message is based upon.

Example value: urn:fdc:peppol.eu:prac:trns:t010:1.1

Line response information
A response to a particular line in the document. If the document response is negative (code='RE|CA'), the line response element is used to specify the errors in the business document.

Line reference
Identifies the line in the business document to which the reported issue applies.

Section identifier
Identifies the section of the tendering message to which the reported issue applies. The LineID element must be used to indicate where in the notice the error occurred by using XPath to reference the element causing the error. To cater for scenarios where it is not possible to provide XPath, a dummy value must be applied. The dummy value must consist of the standard header of the tendering message, depending on its type. This is due to that the LineID element is mandatory in the ApplicationResponse message in UBL 2.1 on which the TMR message is based.

Example value: /TenderWithdrawal/cbc:CustomizationID

Line response information

Line response code
A code stating whether the referenced line was accepted or rejected.

Example value: RE

Issue description
The description of the issue identified in the transaction document. If applicable this should be the error message from the schematron or syntax validation. If not the description of the used status reason code should be used.

Example value: Error associated with a syntax violation that indicates a problem that leads to the rejection of the referenced message.

Status details

Issue type code
A codified version of the issue description that describes the nature of the issue e.g. Syntax violation, Business rule violation, etc.

Example value: BV