|
This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4. Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued. The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags. |
| Message Type: | IFTSTQ |
|---|---|
| Version: | D |
| Release: | 96A |
| Contr. Agency: | UN |
| Status: | 1 |
| Revision: | 2 |
| Date: | 95-11-23 |
| SOURCE: | Joint Transport Group (JM4) |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the International multimodal status request message (IFTSTQ) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A message to request an International multimodal status report message (IFTSTA) in order to provide details relating to transport status and/or a change in the transport status between agreed parties.
The International multimodal status request message may be used for both national and international trade. It is based on universal commercial practice and is not dependent on the type of business or industry.
This message allows for the request of information regarding the status of the physical movement of consignments, goods, or equipment at any point (in time or place) within the full transport chain.
The request for status can be made by either:
APPROACHES a) AND b) MUST NOT BE USED TOGETHER WITHIN ONE IFTSTQ MESSAGE.
Data requirements for tracking equipment, where equipment is not associated with a consignment (such as repair container), are not addressed in this message.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the International multimodal status request message is IFTSTQ.
Note: International multimodal status request messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | IFTSTQ |
| 0052 | D | |
| 0054 | 96A | |
| 0051 | UN |
A segment to indicating the beginning of the message and identifying the consignment for which status is being requested.
A segment indicating the date/time of the message and the dates, times and periods relating to the requested status or events.
A segment identifying a place/location which applies to the consignment such as consignment origin and destination.
A group of segments to specify a reference which applies to the whole message, and its related date and time.
A segment to identify a reference relating to the requested status, e.g. customer reference number. Also a reference to previous message can be given.
A segment to indicate date and time relating to the reference.
A segment identifying conveyance relating to the status or event such as flight, vessel/voyage.
A segment identifying equipment related to the requested status or event such as a container.
A group of segments to specify the parties related to the consignment.
A segment identifying a party to the consignment such as a shipper, consignee, freight forwarder, broker.
A group of segments to indicate contacts related to the party.
A segment to identify a person or department to whom communication should be directed.
A segment to identify a communication number of a department or a person to whom communication should be directed.
A group of segments to provide information about specific consignments, e.g. included in a consolidation.
A segment to indicate a consignment (in a consolidation) using the reference number of its transport document.
A segment to indicate the date/time of the transport document of this consignment and the dates, times and periods relating to the requested status or events.
A segment identifying a place/location which applies to the consignment such as consignment origin and destination.
A segment identifying a reference relating to the requested status, e.g. customer reference number/order.
A segment identifying conveyance relating to the status or event such as flight, vessel/voyage.
A segment identifying equipment related to the requested status or event such as a container.
A group of segments to specify the parties related to this consignment.
A segment identifying a party to the consignment such as a shipper, consignee, freight forwarder, broker.
A group of segments to indicate contacts related to the party.
A segment to identify a person or department to whom communication should be directed.
A segment to identify a communication number of a department or a person to whom communication should be directed.
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
| BGM | Beginning of message | |
| CNI | Consignment information | |
| COM | Communication contact | |
| CTA | Contact information | |
| DTM | Date/time/period | |
| EQD | Equipment details | |
| LOC | Place/location identification | |
| NAD | Name and address | |
| RFF | Reference | |
| TDT | Details of transport | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×9 | (C) |
| ├─LOC Place/location identification | ×99 | (C) |
| ├─Segment Group 1 | ×999 | (C) |
| │─├─RFF Reference | ×1 | (M) |
| │─└─DTM Date/time/period | ×9 | (C) |
| ├─TDT Details of transport | ×99 | (C) |
| ├─EQD Equipment details | ×999 | (C) |
| ├─Segment Group 2 | ×9 | (C) |
| │─├─NAD Name and address | ×1 | (M) |
| │─└─Segment Group 3 | ×9 | (C) |
| │───├─CTA Contact information | ×1 | (M) |
| │───└─COM Communication contact | ×9 | (C) |
| ├─Segment Group 4 | ×999 | (C) |
| │─├─CNI Consignment information | ×1 | (M) |
| │─├─DTM Date/time/period | ×9 | (C) |
| │─├─LOC Place/location identification | ×99 | (C) |
| │─├─RFF Reference | ×99 | (C) |
| │─├─TDT Details of transport | ×99 | (C) |
| │─├─EQD Equipment details | ×99 | (C) |
| │─└─Segment Group 5 | ×9 | (C) |
| │───├─NAD Name and address | ×1 | (M) |
| │───└─Segment Group 6 | ×9 | (C) |
| │─────├─CTA Contact information | ×1 | (M) |
| │─────└─COM Communication contact | ×9 | (C) |
| └─UNT Message trailer | ×1 | (M) |