This page describes the XML orderimport for Kennis Transport & Logistics. When following these guidelines, you’ll make sure that the orderfile you create can be imported in our TMS through the standard orderimport.
Not all the fields are discussed here. Please contact the projectmanager if extra information is needed about the XML file.
We will keep improving the provided information about the use of XML file’s when there are any changes.
Index:
- 1 Module
- 2 Webservice
- 3 Filetransfer
- 4 XSD
- 5 Example files
- 6 Structure of the XML file
- 7 Definitions
- 8 Matchmodes
- 9 Transportbooking element
- 10 Shipment element
- 11 Sender element
- 12 Receiver element
- 13 Pickupaddress element
- 14 Deliveryaddress element
- 15 Cargo element
- 16 Dangerous goods element
- 17 Document element
- 18 Capabilities
Module
For the orderimport you’ll need the standard Kennis Transport & Logistics Orderimport XML, you can find Example’s under the “Example files“
Webservice
There is no webservice available At this moment.
Filetransfer
Orderfiles should be put on our sFTP server. Our TMS has the functionality to automatically process them.
XSD
there is no XSD file available at this moment.
Example files
Here you can download our XML file
Structure of the XML file
Data is imported from an XML file. The structure of this XML file represents the structure of a booking. With one or more shipments.
There are several elements:
- transportbooking
- shipments
- shipment
- sender
- receiver
- pickupaddress
- deliveryaddress
- cargo
- goodslines
- goodsitems
- goodslines
- shipment
- shipments
NB: all elements in small letters.
There are other levels aswell, like Hazardous Materials, Cash on delivery (COD) and Documents.
- 1 Transportbooking can have 1 or more shipments.
- 1 File can have 1 or more transportbookings.
Definitions
A transportbooking is the main level. It has a customer, which normally is the one who provides this XML.
Each booking in our TMS has one or more shipments. A shipment contains a loading address, unloading address and information about the product that needs to be transported. A shipment can also contain a sender and receiver, which are by default the pickup address and delivery address. In some cases the goods has to be picked up in Hamburg, while the Sender is in China. And to be delivered in Rotterdam while the receiver is in Canada.
If the goods are simple, just use the Cargo level to provide information about the goods, e.g. 1 load of sand, or 33 europallets of vegetables. When the load contains more different units, it can be useful to use Goodslines, so for every unit you can add a goodsline.
In some cases the goodslines need to be specified, you can use the goodsitems level for this.
The use of “Goodslines” is preferred. Normally “Goodsitems” is not used, only if goodslines have to be split up in several goodsitems, when a more detailed level is necessary. Without goods lines, its possible to only use the element “cargo”. There can only be 1 unit specified in this element.