The TDT segment carries transport and carrier information. Element 2 is the shipment reference number. Element 3 is the transport mode code (10=maritime, 20=rail, 30=road, 40=air). Element 5 is a composite identifying the carrier (name and code). Used in ORDERS for requested transport and in DESADV for actual carrier details.
TDTHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
TDT+20+TRUCK-REF-01+30++VANS:::FAST_FREIGHT_PTY_LTD'Transport Information
| 1 | Transport stage | 20Main carriage |
| 2 | Conveyance reference | TRUCK-REF-01 |
| 3 | Mode | 30 |
| 5.1 | Carrier: ID | VANS |
| 5.4 | Carrier: Name | FAST_FREIGHT_PTY_LTD |
Not mapped in this demo. In production CleanEDI maps it into your contract, or keeps it in the raw archive.
Elements are separated by + and their parts by :. Positions match the explainer, so 2.3 is the third part of the second element.
| Position | Element | Parts |
|---|---|---|
| 1 | Transport stage | 1.1 Code |
| 2 | Conveyance reference | Single value |
| 3 | Mode | Single value |
| 4 | Means | Single value |
| 5 | Carrier | 5.1 ID, 5.2 Code list, 5.3 Agency, 5.4 Name |
| Code | Meaning |
|---|---|
10 | Pre-carriage |
20 | Main carriage |
30 | On-carriage |
Common EANCOM and UN/EDIFACT values. Your trading partner's implementation guide is the final word on which codes they send.
Have a real message with TDT in it? The explainer breaks down every segment and runs in your browser.
Explain my message