Syntax Mapping T007 - Tendering Questions 1.1

Tendering Questions transaction model.

UBL version identifier
Requires UBL version 2.2

Fixed value: 2.2

Specification identification
An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms.

Fixed value: urn:fdc:peppol.eu:prac:trns:t007:1.1

Business process type identifier
Identifies the business process context in which the transaction appears. It enables the buyer to process the document in an appropriate way.

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

Document identifier
Identifies the tendering questions as issued by the economic operator. Must be expressed as a UUID

Scheme identifier

Fixed value: urn:uuid

Document issue date
The date on which the tendering questions is issued.

Document issue time
The time when the tendering questions is issued. The issue time must have granularity of seconds, and include time zone information.

The economic operator
Party information of the economic operator

Economic operator electronic address identifier
The electronic address of the economic operator.

Example value: 500820007

Scheme identifier

Example value: 9946

Party identification

Economic operator identifier
An identifier that identifies the economic operator, such as a legal registration identifier. Can be the registration number in the professional registry.

Example value: 7300010000001

Scheme identifier

Example value: 0088

Party name

Economic operator name
The name of the economic operator.

The contracting body
Party information of the contracting body

Contracting body electronic address identifier
Electronic address of the contracting body.

Example value: DE122268496

Scheme identifier

Example value: 9930

Party identification

Contracting body identifier
The national identifier of a contracting body as it is legally registered (e.g. VAT identification, such as KBO)

Example value: 991-1234512345-06

Scheme identifier

Example value: 0204

Party name

Contracting body name
The name of the contracting body as it is registered.

Additional document references.
Additional document reference is used for identifying the procurement procedure and the questions for the procurement project. The ContractFolderID must be at least provided. Additional references may be included to locate the questions for LotGroups or Lots.

Document identifier
Used as a link to the call for tenders (also known as procurement project identifier, procurement reference number or contract folder identifier). The contract folder ID must be at least provided. Element can be repeated and also used as an identifier to the LotGroups and Lots to which the tendering question applies. XPath expressions are used to locate the questions.

Scheme name
Valid values are ContractFolderID, LotGroup or Lot.

Reference to an cac:Attachment
An xpath expression to reference an cac:Attachment where questions can be described or referenced to an attached file within the ASiC-e.

Attachment
An attached tendering request or files which must be referenced by an cac:AdditionalDocumentReference

External reference
An external reference to place your questions or add an attachment to express questions in more detail.

Mime code of the file
A code signifying the mime type of the external object.

A reference to an ASiC-e attachment.
A file reference within the ASiC-e which may contain additional information to express questions in more detail.

Tendering request
The tendering request about the procurement procedure.