ubl:TransportExecutionPlan

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

Example value: urn:fdc:peppol.eu:logistics:trns:transport_execution_plan:1

Business process type identifier
Identifies the BII profile or business process context in which the transaction appears. There are two ProfileIDs defined for the Transport Execution Plan. One profile is used when a request is expected, the other is used when no request message is expected. Possible choices are: "urn:fdc:peppol.eu:logistics:bis:transport_execution_plan_w_request:1" and "urn:fdc:peppol.eu:logistics:bis:transport_execution_plan_only:1".

Example value: urn:fdc:peppol.eu:logistics:bis:transport_execution_plan_w_request:1

Profile Execution ID
Identifies an instance of executing a profile, to associate all transactions in a collaboration.

Example value: XZ-4532

Document identifier
An transaction instance must contain an identifier. The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process.

Example value: 691278571829041271246

Dispatch advice issue date
The date when the Transport Execution Plan is issued. Format = "YYYY-MM-DD".

Example value: 2021-09-29

Dispatch advice issue time
The time when the Transport Execution Plan is issued. Format = "hh:mm:ss".

Example value: 09:49:00+02:00

Transport Execution Plan status code
A code signifying the status of the Transport Execution Plan. Default is Original (9)

Example value: 9

Note
Free-form text pertinent to this document, conveying information that is not contained explicitly in other structures.

Example value: Textual notes

Transport Service Provider Remarks
Remarks from the transport user regarding the transport operations copied from the Transport Execution Plan Request. Not used in the Transport Execution Plan Only profile

Example value: Some remarks

Transport User Remarks
Remarks from the transport service provider regarding the transport operations referred to in the Transport Execution Plan.

Example value: Some remarks

Sender party
The party sending the Transport Execution Plan.

Receiver Party
The party receiving the Transport Execution Plan.

Transport user party
The party requesting the transport services referenced in the Transport Execution Plan.

Transport service provider party
The party providing the transport services referenced in the Transport Execution Plan.

Bill To Party
The party that will pay for the transport service(s) referred to in this Transport Execution Plan.

Additional document reference
Reference to a Transport Execution Plan Request. Mandatory if it is not

Additional document reference
Reference to additional documents relevant for this Transport Execution Plan.

Main Transportation Service
A description of the main transportation service referenced in the Transport Execution Plan.

Additional Transportation Service
A description of an additional transportation service referenced in the Transport Execution Plan. Can only be used in conjunction with a main transportation service.

Consignment information
An identifiable collection of goods items sent from one party (the Despatch Party) to another party (the Consignee) via one or more modes of transport.