ubl:TransportExecutionPlanRequest
- Namespace
- ublurn:oasis:names:specification:ubl:schema:xsd:TransportExecutionPlanRequest-2
- Child elements
- 
    Card Name Description 1..1 cbc:CustomizationID 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_request:11..1 cbc:ProfileID 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 Request. 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:11..1 cbc:ID 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: 1412785718290412412411..1 cbc:IssueDate Dispatch advice issue date 
 The date when the Transport Execution Plan Request is issued. Format = "YYYY-MM-DD".Example value: 2021-09-291..1 cbc:IssueTime Dispatch advice issue time 
 The time when the Transport Execution Plan Request is issued.Example value: 09:49:00+02:000..1 cbc:DocumentStatusCode Transport Execution Plan Request status code 
 A code signifying the status of the Transport Execution Plan Request. Default is Original (9)Example value: 90..1 cbc:TransportUserRemarks Transport User Remarks 
 Remarks from the transport user regarding the transport operations referenced in the Transport Execution Plan Request.Example value: Some remarks1..1 cac:TransportUserParty Transport user party 
 The party requesting the transport services referenced in the Transport Execution Plan Request and the sender of the Transport Execution Plan.1..1 cac:TransportServiceProviderParty Transport service provider party 
 The party providing the transport services referenced in the Transport Execution Plan Request. The receiver of the Transport Execution Plan.0..1 cac:PayeeParty Payee party 
 The party that will pay for the transport service(s) referred to in a Transport Execution Plan.0..n cac:AdditionalDocumentReference Additional document reference 
 Reference to additional documents relevant for this Transport Execution Plan Request.1..1 cac:MainTransportationService Main Transportatin Service 
 A description of the main transportation service referenced in the Transport Execution Plan Request.0..n cac:AdditionalTransportationService Additional Transportatin Service 
 A description of an additional transportation service referenced in the Transport Execution Plan Request. Can only be used in conjunction with a main transportation service.1..1 cac:Consignment Consignment information 
 
- Rules
- 
            
    Identifier/Error message Flag PEPPOL-T123-B00101 
 Element 'cbc:CustomizationID' MUST be provided.fatal PEPPOL-T123-B00102 
 Element 'cbc:ProfileID' MUST be provided.fatal PEPPOL-T123-B00103 
 Element 'cbc:ID' MUST be provided.fatal PEPPOL-T123-B00104 
 Element 'cbc:IssueDate' MUST be provided.fatal PEPPOL-T123-B00105 
 Element 'cbc:IssueTime' MUST be provided.fatal PEPPOL-T123-B00106 
 Element 'cac:TransportUserParty' MUST be provided.fatal PEPPOL-T123-B00107 
 Element 'cac:TransportServiceProviderParty' MUST be provided.fatal PEPPOL-T123-B00108 
 Element 'cac:MainTransportationService' MUST be provided.fatal PEPPOL-T123-B00109 
 Element 'cac:Consignment' MUST be provided.fatal PEPPOL-T123-B00110 
 Document MUST not contain schema location.fatal PEPPOL-T123-B00111 
 Document MUST NOT contain elements not part of the data model.fatal