Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D99A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

International multimodal status request message

Version:D
Release:99A
Contr. Agency:UN
Revision:3
Date:99-01-14
SOURCE:Joint Transport Group (JM4)

CONTENTS
International multimodal status request message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Data segment clarification
    2. Data segment index (alphabetical sequence)
    3. Message structure
      1. Segment table

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

0. INTRODUCTION

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.


1. SCOPE


1.1. Functional Definition

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.


1.2. Field of Application

The International multimodal status request message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.


1.3. Principles

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:

  1. using the top level segments to request information about one or a number of consignments relating to a point or period of time, location(s), party related reference(s) and party(s), means of transport(s) and equipment(s).
  2. using the CNI segment group and making reference to a unique consignment reference number per consignment and indicating, if necessary, the criteria (date(s), location(s), etc.) for which the status is requested.

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.


2. REFERENCES

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.


4. MESSAGE DEFINITION


4.1. Data Segment Clarification

This section should be read in conjunction with the Segment Table which indicates mandatory, conditional and repeating requirements.

0010 UNH, Message header

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 element0065IFTSTQ
0052D
005499A
0051UN

0020 BGM, Beginning of message

A segment to indicating the beginning of the message and identifying the consignment for which status is being requested.

0030 DTM, Date/time/period

A segment indicating the date/time of the message and the dates, times and periods relating to the requested status or events.

0040 LOC, Place/location identification

A segment identifying a place/location which applies to the consignment such as consignment origin and destination.

0050 Segment Group 1: RFF-DTM

A group of segments to specify a reference which applies to the whole message, and its related date and time.

0060 RFF, Reference

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.

0070 DTM, Date/time/period

A segment to indicate date and time relating to the reference.

0080 TDT, Details of transport

A segment identifying conveyance relating to the status or event such as flight, vessel/voyage.

0090 EQD, Equipment details

A segment identifying equipment related to the requested status or event such as a container.

0100 Segment Group 2: NAD-SG3

A group of segments to specify the parties related to the consignment.

0110 NAD, Name and address

A segment identifying a party to the consignment such as a shipper, consignee, freight forwarder, broker.

0120 Segment Group 3: CTA-COM

A group of segments to indicate contacts related to the party.

0130 CTA, Contact information

A segment to identify a person or department to whom communication should be directed.

0140 COM, Communication contact

A segment to identify a communication number of a department or a person to whom communication should be directed.

0150 Segment Group 4: CNI-DTM-LOC-RFF-TDT-SG5-SG6

A group of segments to provide information about specific consignments, e.g. included in a consolidation.

0160 CNI, Consignment information

A segment to indicate a consignment (in a consolidation) using the reference number of its transport document.

0170 DTM, Date/time/period

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.

0180 LOC, Place/location identification

A segment identifying a place/location which applies to the consignment such as consignment origin and destination.

0190 RFF, Reference

A segment identifying a reference relating to the requested status, e.g. customer reference number/order.

0200 TDT, Details of transport

A segment identifying conveyance relating to the status or event such as flight, vessel/voyage.

0210 Segment Group 5: EQD-TPL

A group of segments to identify equipment and eventually the means of transport in which it is placed.

0220 EQD, Equipment details

A segment identifying equipment related to the requested status or event such as a container.

0230 TPL, Transport placement

A segment to identify a means of transport (e.g. train) to which the equipment is linked.

0240 Segment Group 6: NAD-SG7-SG8

A group of segments to specify the parties related to this consignment.

0250 NAD, Name and address

A segment identifying a party to the consignment such as a shipper, consignee, freight forwarder, broker.

0260 Segment Group 7: GID-FTX-SGP

A group of segments to specify a goods item, necessary in cases where the request concerns only part of the consignment.

0270 GID, Goods item details

A segment to provide details of a goods item as part of a consignment.

0280 FTX, Free text

A segment to describe the goods item.

0290 SGP, Split goods placement

A segment to identify equipment in which goods are transported.

0300 Segment Group 8: CTA-COM

A group of segments to indicate contacts related to the party.

0310 CTA, Contact information

A segment to identify a person or department to whom communication should be directed.

0320 COM, Communication contact

A segment to identify a communication number of a department or a person to whom communication should be directed.

0330 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.


4.2. Data segment index (Alphabetical sequence by tag)

BGM Beginning of message
CNI Consignment information
COM Communication contact
CTA Contact information
DTM Date/time/period
EQD Equipment details
FTX Free text
GID Goods item details
LOC Place/location identification
NAD Name and address
RFF Reference
SGP Split goods placement
TDT Details of transport
TPL Transport placement
UNH Message header
UNT Message trailer

4.3. Message structure


4.3.1. Segment table

├─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)
├─Segment Group 5 ×99 (C)
├─EQD Equipment details ×1 (M)
└─TPL Transport placement ×9 (C)
└─Segment Group 6 ×9 (C)
──├─NAD Name and address ×1 (M)
──├─Segment Group 7 ×99 (C)
──├─GID Goods item details ×1 (M)
──├─FTX Free text ×1 (C)
──└─SGP Split goods placement ×99 (C)
──└─Segment Group 8 ×9 (C)
────├─CTA Contact information ×1 (M)
────└─COM Communication contact ×9 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D99A Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.