Present were Kees, Kenneth and Peter
-
New issues
-
Make TransportUserParty optional in Transport Execution Plan Request and Transport Execution Plan
Reason: Since TransportUserParty is not nessesary the receiver or sender of the document, it could be made optional. One case is that a Carrier requests a Customs declation from the freight forwarder. Here the Carrier is not the transport user
Resolution: The carrier is not the transport user but the requester of the transport service, and by that seen as a transport user. Agreed to no change.
-
Receiver party in Manifest
Reason. Often the receiver of the manifest is not a public authority, but a terminal operator.
Resolution: Aggreed to add TerminalOperatorParty on header level in the Manifest
-
GoodsItem in Consignment
Reason: Often the carrier does not know in what transport handling unit a given GoodItem is placed in a consignment. It would therefore be good to have goodsitem directly on consignment level just like in the Shipment
Resolution: Kees will research more on the consequenses for this.
-
PreviousDocumentReference in CustomsDeclarations
Reason: In Customs Declarations it is often required to specify a Precious Document (CL228). There has been specified a Prious Customs Declarations and there exists a Additional Document Reference, but not a document reference for this semantic.
Resolution: PreviousDocumentReference is added to Customs Declarations.
-
New document types for Delivery Note and Work Statement
There were no time for these issues left.