| Learn 3PL Dynamics

#Transsmart (nShift) integration

Introduction

With the nShift Transsmart Platform integration, the WMS/TMS software is connected to carriers like DHL, UPS, TNT and DPD.

Setup

Mapping for Shipping Agents

Transsmart requires Shipping Agent code with a max length of 3 chars. You can either set ShippingAgent.Code to 3 chars, or set a Mapping (Type: Transport, Code: TRANSSMARTSHIP).

Mapping for Handling Unit Types (types of handling units)

Transsmart Setup defines Handling Unit Types with certain codes. This requires to setup 3PL Dynamics with the same coding, although you might need to have a more detailed distinction in your WMS/TMS. For Transsmart/Couriers PALLET might be sufficient, while you need to distinct EURO or BLOK in 3PL Dynamics.

You can set specific Transsmart Codes to your Handling Unit Types by introducing a Mapping (Type: Transport, SourceNo: TRANSSMART). It is allowed to have several Handling Unit Types with the same mapping code (e.g. both EURO and BLOK can be mapped to PALLET).

Mapping for Units of Measure

Transsmart Setup defines Units of Measure with certain codes. This requires to setup 3PL Dynamics with the same coding, although you might need to have a more detailed distinction in your WMS/TMS. For Transsmart/Couriers BOX might be sufficient, while you need to distinct BOX10, BOX20 and BOX30 in 3PL Dynamics.

You can set specific Transsmart Codes to your Units of Measure by introducing a Mapping (Type: Transport, SourceNo: TRANSSMART). It is allowed to have several Units of Measure with the same mapping code (e.g. both BOX10 and BOX30 can be mapped to BOX).

Setup with Conditions

Several options to send information to Transsmart, are enabled to be setup by using Conditions.

For example the referencenumber of the Shipment. In Transsmart messages, it is called TSREF. It has to be a unique value, and preferably implemented for an actual reference. A reference that suits you, your process and your customer's information. Instead of forcing the use of a particular field on the DocumentHeader, the Transsmart Setup provides you with the possibility to setup the Condition TSREF to refer to a data field of the Shipment Document. Examples given: Document Number or External Document Number.

Read more about the 3PL Conditions Framework: Learn page about Conditions.

More in-depth information about this setup is here: Transsmart - setup with Conditions

Generic MessageTypes

Setup by Initialize function is recommended, messagetypes come with Codeunit 11173011.

On POST message (function 100) the following MessageSubTypes are currently supported:

BOOK: doBooking, need to execute getDocs to receive Labels
PRINT: doBooking and get labels in return (recommended)
RATES

On GET message (funtions 200) the following MessageSubTypes are currently supported:

DOCS: get labels
STATUS: get Status
SHIPMENT: get shipment information (to be used in case of printing directly)
PROFILES: get Shipping Agents from Transsmart configuration, Shipping Agent Services (serviceLevel and serviceLevelOther) included