Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D95B Messages page.
UN/EDIFACT
DRAFT RECOMMENDATION

Forwarding and transport schedule and availability information message

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:IFTSAI
Version:D
Release:95B
Contr. Agency:UN
Status:1
Revision:1
Date:95-07-07
SOURCE:Western European EDIFACT Board

CONTENTS
Forwarding and transport schedule and availability information message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. 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:
D93A, 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 Forwarding and transport schedule and availability information message (IFTSAI) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

The function of this message is to request transport schedule or availability information and to answer to such a request.


1.2. Field of Application

This message may be applied for both national and international trade. It is based on universal practice and is not dependent on the type of business or industry.


1.3. Principles

This message may be used:

  1. to request operating means of transportation for a specific routing. Certain specific research criteria such as date/time of operation and type of transport desired may be precised to limit the volume of information requested.
  2. to answer to such a request furnishing a list of operating means of transport in accordance with the selection criteria. Such answer may comprise direct and/or combinations of means of transport.
  3. to request means of transport on which space is available for a specific routing. Certain specific research criteria like date/time of operation, type of transport and space desired may be precised to limit the volume of information requested.
  4. to answer to such request furnishing a list of available means of transport in accordance with the selection criteria. Such an answer may comprise direct and/or combinations of means of transport.

2. REFERENCES

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


3. 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 Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.

0010 | UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Forwarding and transport schedule and availability information message is IFTSAI.

Note: Forwarding and transport schedule and availability information messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065IFTSAI
0052D
005495B
0051UN

0020 BGM, Beginning of message

A segment to indicate the type and function of the message and to transmit the identifying number.

0030 DTM, Date/time/period

A segment to indicate date(s) and time(s) applying to the whole message.

0040 FTX, Free text

A segment to specify free form or processable supplementary information. In computer-to-computer exchanges free form text will normally require the receiver to process this segment manually.

0050 RFF, Reference

A segment to express a reference which applies to the entire message.

0060 Segment Group 1: LOC-DTM

A group of segments to identify the routing and date of the schedule or availability information.

0070 LOC, Place/location identification

A segment to identify a location, e.g. place of departure/arrival.

0080 DTM, Date/time/period

A segment to indicate date(s) and time(s) related to the location.

0090 Segment Group 2: EQD-EQN-MEA-DIM-FTX

A group of segments to define requested or available equipment.

0100 EQD, Equipment details

A segment to specify requested or available equipment and equipment size and type.

0110 EQN, Number of units

A segment to specify the number of requested or available pieces of equipment.

0120 MEA, Measurements

A segment to specify measurements, other than dimensions, associated with equipment, in terms of capacity.

0130 DIM, Dimensions

A segment to specify dimensions applicable to equipment.

0140 FTX, Free text

A segment to specify free form or processable supplementary information associated with the equipment.

0150 Segment Group 3: TDT-DTM-TSR-FTX-EQD-QTY-MEA-SG4

A group of segments to specify the schedule or availability selection criteria and to detail the schedule or availability information being provided.

0160 TDT, Details of transport

A segment to indicate information related to the mode and means of transport, eg. specific conveyance/carrier.

0170 DTM, Date/time/period

A segment to indicate date(s) and time(s), e.g. earliest departure date/time, latest arrival date/time.

0180 TSR, Transport service requirements

A segment to identify contract, conditions of carriage, services and priority requirements.

0190 FTX, Free text

A segment to specify free form or processable supplementary information related to the means of transport.

0200 EQD, Equipment details

A segment to identify the equipment requested/available.

0210 QTY, Quantity

A segment to indicate a quantity, e.g. number of intermediate stops.

0220 MEA, Measurements

A segment to indicate weight and/or volume selection criteria, e.g. minimum weight.

0230 Segment Group 4: LOC-DTM

A group of segments to identify the routing(s) and indicate corresponding date(s) and time(s).

0240 LOC, Place/location identification

A segment to identify a location, e.g. place of departure/arrival.

0250 DTM, Date/time/period

A segment to indicate date(s) and time(s) related to the location, e.g. date/time of scheduled departure/arrival.

0260 Segment Group 5: NAD-LOC-SG6

A group of segments to indicate all parties involved in the transaction and relevant locations, contacts and communication channels.

0270 NAD, Name and address

A segment to identify the party's name, address and function.

0280 LOC, Place/location identification

A segment to identify a place/location/sub-location and where relevant the function. The present location must be associated with the relevant party.

0290 Segment Group 6: CTA-COM

A group of segments to identify a contact and its communication channels, related to the party.

0300 CTA, Contact information

A segment to identify a person or department within a party.

0310 COM, Communication contact

A segment to identify the communication numbers of person or department to whom communication should be directed.

0320 Segment Group 7: GID-HAN-FTX-SG8-SG9-SG10-SG11

A group of segments to describe the goods items for which schedule or availability is requested/provided.

0330 GID, Goods item details

A segment to identify the goods item. A goods item can be identified by up to three levels of packaging within this segment.

0340 HAN, Handling instructions

A segment to specify handling instructions relating to the goods item.

0350 FTX, Free text

A segment to specify free form or processable information relating to the goods item.

0360 Segment Group 8: GDS-FTX

A group of segments to identify and describe the goods.

0370 GDS, Nature of cargo

A segment to describe the nature of cargo.

0380 FTX, Free text

A segment to describe the goods in free form.

0390 Segment Group 9: MEA-EQN

A group of segments to specify measurements applicable to the goods item.

0400 MEA, Measurements

A segment to specify measurements, other than dimensions, applicable to the goods item.

0410 EQN, Number of units

A segment to specify the number of equipment units to which the measurement applies.

0420 Segment Group 10: DIM-EQN

A group of segments to specify dimensions applicable to the goods item.

0430 DIM, Dimensions

A segment to specify dimensions applicable to the goods item.

0440 EQN, Number of units

A segment to specify the number of equipment units to which the given dimensions apply.

0450 Segment Group 11: DGS-FTX

A group of segments to specify dangerous goods details related to the goods item.

0460 DGS, Dangerous goods

A segment to specify the class of dangerous goods, packing group, etc.

0470 FTX, Free text

A segment to specify the dangerous goods technical name and any other additional dangerous goods information.

0480 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
COM Communication contact
CTA Contact information
DGS Dangerous goods
DIM Dimensions
DTM Date/time/period
EQD Equipment details
EQN Number of units
FTX Free text
GDS Nature of cargo
GID Goods item details
HAN Handling instructions
LOC Place/location identification
MEA Measurements
NAD Name and address
QTY Quantity
RFF Reference
TDT Details of transport
TSR Transport service requirements
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)
├─FTX Free text ×99 (C)
├─RFF Reference ×9 (C)
├─Segment Group 1 ×9 (C)
├─LOC Place/location identification ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×9 (C)
├─EQD Equipment details ×1 (M)
├─EQN Number of units ×9 (C)
├─MEA Measurements ×9 (C)
├─DIM Dimensions ×9 (C)
└─FTX Free text ×9 (C)
├─Segment Group 3 ×999 (C)
├─TDT Details of transport ×1 (M)
├─DTM Date/time/period ×9 (C)
├─TSR Transport service requirements ×9 (C)
├─FTX Free text ×9 (C)
├─EQD Equipment details ×99 (C)
├─QTY Quantity ×9 (C)
├─MEA Measurements ×9 (C)
└─Segment Group 4 ×99 (C)
──├─LOC Place/location identification ×1 (M)
──└─DTM Date/time/period ×9 (C)
├─Segment Group 5 ×9 (C)
├─NAD Name and address ×1 (M)
├─LOC Place/location identification ×9 (C)
└─Segment Group 6 ×9 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×9 (C)
├─Segment Group 7 ×9 (C)
├─GID Goods item details ×1 (M)
├─HAN Handling instructions ×9 (C)
├─FTX Free text ×9 (C)
├─Segment Group 8 ×9 (C)
├─GDS Nature of cargo ×1 (M)
└─FTX Free text ×9 (C)
├─Segment Group 9 ×9 (C)
├─MEA Measurements ×1 (M)
└─EQN Number of units ×9 (C)
├─Segment Group 10 ×9 (C)
├─DIM Dimensions ×1 (M)
└─EQN Number of units ×9 (C)
└─Segment Group 11 ×9 (C)
──├─DGS Dangerous goods ×1 (M)
──└─FTX Free text ×9 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D95B 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.