Cargowise Integrations via eAdaptor
Introduction
FreightTracker is able to provide integration with Cargowise using the standard Cargowise XML Files.
Integration can be achieved using FTP/SFTP to transfer files although use of the eAdaptor and API file transfer is preferred.
If the Cargowise eADaptor details are provided FreightTracker is able to send the Cargowise Universal Events (XUE) for the milestones directly to Cargowise.
Freighttracker is able to store the results of transfer back to Cargowise in the Logging section.
Cargowise Files Accepted.
FreightTracker can handle the following Cargowise files.
Universal Shipment (XUS)
ForwardingConsol/Forwarding shipment/ Customs Declaration - Consols with Shipments (and Customs Declarations ) otherwise known as "S" Jobs.
CustomsDeclaration - Customs Brokerage jobs, otherwise known as "B" Jobs
Native XML (NTM)
Organisation - used for Organisation Imports
Products - used to import Cargowise Product files.
Currently the Transport Booking files are not accepted as there is not enough information to create a Container booking. This may change in the future.
Receive Files from Cargowise via Api transfer
In order to receive files from Cargowise the customer must be able to send their files via API.
Create a new Integration Authentication (booking) that will be used to provide the Endpoint for the connection.
1. Click Settings
2. Click Integrations
3. Select Authentication tab
4. Click Add New
1. Select Booking from the Drop Down Integration type.
2. Select Restful API from the Service Drop down
3. Select the Direction of In.
4. Provide a descriptive name of the API Connection
5. Create a user name that will be provided to the Cargowise customer.
6. Create a password that will be provided to the Cargowise customer.
7. Set the Active status to Yes.
8. Save the Integration record.
Provide the customer with the following information
FreightTracker Endpoint: https:<carrierName>.freighttracker.com.au/api/edi/booking
Authentication: Basic Provide the username and password created int step 5 and 6.
Body: Raw (JSON)
The Data of the XML is added in the Body of the Request.
Send files back to Cargowise via eAdaptor
1. Click Settings
2. Click Integrations
3. Select Authentication tab
4. Click Add New
1. Select Booking from the Integration Type drop down
2. Select Restful API from the Service drop down
3. Select the Direction as OUT.
4. Provide a name - recommend <CustomerName> eAdaptor
5. Enter the host name provided - it is often https://xxxyyyservices.wisegridnet/eAdaptor where "xxx" is the customer company code and "yyy" is the server name
6. Enter the username that was provided by the Customer.
7. Enter the password that was provided by the Customer
8. Set Active to Yes
9. Ensure Deleted is set to No
10. Save the Record.
Create the Cargowise Integration Record.
1. Click Settings
2. Click Integration
3. Select the Integration tab
4. Click Add New.
1. Select the Booking from the Integration Type drop down.
2. Select the Customer that will be sending the bookings.
3. Type in the Cargowise Code that will be sent in the XML file. - optional, this is used for integrations where there are more than one Cargowise customer on the same Cargowise server.
4. Type in the FreightTracker Code that will be used in creating the XML file - Not used if sending back via ediAdaptor directly.
5. Select Restful API from the Service Drop down.
6. Choose "CARGOWISE XUS FILES (NEW) from the processor dropdown.
7. Select the connection that was created in the first steps.
8. Set the Enabled flag to Yes.
9. The Own charge to is used when the customer is creating jobs and would prefer to show the Billing Customer as the charge To address. Contact FreightTracker support for more information.
10. Set the Lock EDI update flag to force all incoming bookings to be locked from updates upon importing.
11 Set the Auto Accept to ensure that the Bookings are always accepted.
1. Select the Milestone Tab to enable the Milestones to go back to Cargowise
2. Select Restful API from the Service drop down.
3. Select CARGOWISE RESTFUL API DELIVERY from the processor drop down.
4. Select the outbound Connection from the Previous section
5. Ensure that the Enabled flag is set to yes.
1. Select the POD's tab to enable the sending of POD's to Cargowise
2. Set the service to Email (which will use the Cargowise eDocs auto Allocate function)
3. Enter the email address given by the Customer that will be the Cargowise system email address.
4. Set the Processor to CW_UNIVERSAL
If the CW_UNIVERSAL Processor is used the Subject is correctly formatted for Cargowise by the application and the subject does not need to be set.
5. Set the enabled flag to Yes.
Related Articles
Set EDI return messages (Milestones) to go to Customers for all jobs.
Introduction Currently in order to send EDI Messages to a Customer they must have an Integration and it must be set to send return messages. By default return messages will only be generated and sent if the bookings are created via EDI. However if a ...Job Booking BULK UPLOAD
How can I upload bulk jobs from a template? Overview FreightTracker has released a new feature that now allows its user to Bulk Upload jobs via a standard template. The function has been added to the system to help reduce time for our clients ...Fumigation Management and Handling
Freight Tracker offers the capability to manage onsite Fumigation as well as providing a report that also facilitates fumigation at delay locations. This can be used by companies during the high risk seasons for fumigation Like BMSB season and those ...Capacity Management
Capacity Management is a module that can be activated via the FreightTracker Marketplace. The below setup is required before the module can be utilised The Capacity Management feature requires set up for each of the Allocations Screen Tabs where ...Container Allocation - Key Features
Our goal is to bring companies closer to their clients with a variety of alerts and automated communication. With pro-active decision making taking the lead. We build the tools for your teams to provide the best service possible, while significantly ...