diff options
Diffstat (limited to 'specification/references/D96A/messages/iftsai_d.txt')
-rw-r--r-- | specification/references/D96A/messages/iftsai_d.txt | 413 |
1 files changed, 413 insertions, 0 deletions
diff --git a/specification/references/D96A/messages/iftsai_d.txt b/specification/references/D96A/messages/iftsai_d.txt new file mode 100644 index 0000000..105c15e --- /dev/null +++ b/specification/references/D96A/messages/iftsai_d.txt | |||
@@ -0,0 +1,413 @@ | |||
1 | UN/EDIFACT | ||
2 | |||
3 | DRAFT RECOMMENDATION | ||
4 | |||
5 | Forwarding and transport schedule and availability information message | ||
6 | |||
7 | |||
8 | |||
9 | |||
10 | |||
11 | ---------------------------------------------------------------------- | ||
12 | This message is available for formal trial for at least six months | ||
13 | from the date of approval by UN/ECE/TRADE/WP.4. | ||
14 | |||
15 | Organisations are invited to trial this message. Comments on the | ||
16 | results from the trial should be forwarded to their Rapporteur's Team | ||
17 | Secretariat as soon as they are available. Based on the results of the | ||
18 | trials, a UNSM may be issued. | ||
19 | |||
20 | The segments, composite data elements, data elements and codes for | ||
21 | use in the trial of this message are contained in the Draft directory. | ||
22 | However, this information may differ from that in the Standard | ||
23 | directory (UNTDID), even for material having the same identifying | ||
24 | tags. | ||
25 | ---------------------------------------------------------------------- | ||
26 | |||
27 | |||
28 | |||
29 | |||
30 | |||
31 | |||
32 | |||
33 | |||
34 | Message Type : IFTSAI | ||
35 | Version : D | ||
36 | Release : 96A | ||
37 | Contr. Agency: UN | ||
38 | Status : 1 | ||
39 | Revision : 2 | ||
40 | Date : 95-11-23 | ||
41 | |||
42 | |||
43 | |||
44 | |||
45 | |||
46 | |||
47 | SOURCE: Western European EDIFACT Board | ||
48 | |||
49 | |||
50 | |||
51 | CONTENTS | ||
52 | |||
53 | Forwarding and transport schedule and availability information message | ||
54 | |||
55 | |||
56 | |||
57 | 0. INTRODUCTION | ||
58 | |||
59 | |||
60 | 1. SCOPE | ||
61 | |||
62 | 1.1 Functional definition | ||
63 | |||
64 | 1.2 Field of application | ||
65 | |||
66 | 1.3 Principles | ||
67 | |||
68 | 2. REFERENCES | ||
69 | |||
70 | 3. TERMS AND DEFINITIONS | ||
71 | |||
72 | 4. MESSAGE DEFINITION | ||
73 | |||
74 | 4.1 Data segment clarification | ||
75 | |||
76 | 4.2 Data segment index (alphabetical sequence) | ||
77 | |||
78 | 4.3 Message structure | ||
79 | |||
80 | 4.3.1 Segment table | ||
81 | |||
82 | |||
83 | |||
84 | |||
85 | |||
86 | |||
87 | |||
88 | |||
89 | |||
90 | |||
91 | |||
92 | ---------------------------------------------------------------------- | ||
93 | For general information on UN standard message types see UN Trade Data | ||
94 | Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM | ||
95 | General Introduction | ||
96 | ---------------------------------------------------------------------- | ||
97 | |||
98 | |||
99 | |||
100 | 0. INTRODUCTION | ||
101 | |||
102 | This specification provides the definition of the Forwarding | ||
103 | and transport schedule and availability information message | ||
104 | (IFTSAI) to be used in Electronic Data Interchange (EDI) | ||
105 | between trading partners involved in administration, commerce | ||
106 | and transport. | ||
107 | |||
108 | 1. SCOPE | ||
109 | |||
110 | 1.1 Functional Definition | ||
111 | |||
112 | The function of this message is to request transport schedule | ||
113 | or availability information and to answer to such a request. | ||
114 | |||
115 | 1.2 Field of Application | ||
116 | |||
117 | This message may be applied for both national and international | ||
118 | trade. It is based on universal practice and is not dependent | ||
119 | on the type of business or industry. | ||
120 | |||
121 | 1.3 Principles | ||
122 | |||
123 | This message may be used: | ||
124 | |||
125 | a) to request operating means of transportation for a specific | ||
126 | routing. Certain specific research criteria such as date/time | ||
127 | of operation and type of transport desired may be precised to | ||
128 | limit the volume of information requested. | ||
129 | |||
130 | b) to answer to such a request furnishing a list of operating | ||
131 | means of transport in accordance with the selection criteria. | ||
132 | Such answer may comprise direct and/or combinations of means of | ||
133 | transport. | ||
134 | |||
135 | c) to request means of transport on which space is available | ||
136 | for a specific routing. Certain specific research criteria like | ||
137 | date/time of operation, type of transport and space desired may | ||
138 | be precised to limit the volume of information requested. | ||
139 | |||
140 | d) to answer to such request furnishing a list of available | ||
141 | means of transport in accordance with the selection criteria. | ||
142 | Such an answer may comprise direct and/or combinations of means | ||
143 | of transport. | ||
144 | |||
145 | 2. REFERENCES | ||
146 | |||
147 | See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General | ||
148 | Introduction, Section 1. | ||
149 | |||
150 | 3. TERMS AND DEFINITIONS | ||
151 | |||
152 | See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General | ||
153 | Introduction, Section 2. | ||
154 | |||
155 | 4. MESSAGE DEFINITION | ||
156 | |||
157 | 4.1 Data Segment Clarification | ||
158 | |||
159 | This section should be read in conjunction with the Branching | ||
160 | Diagram and the Segment Table which indicate mandatory, | ||
161 | conditional and repeating requirements. | ||
162 | |||
163 | 0010 | UNH, Message header | ||
164 | A service segment starting and uniquely identifying a message. | ||
165 | The message type code for the Forwarding and transport schedule | ||
166 | and availability information message is IFTSAI. | ||
167 | |||
168 | Note: Forwarding and transport schedule and availability | ||
169 | information messages conforming to this document must contain | ||
170 | the following data in segment UNH, composite S009: | ||
171 | |||
172 | Data element 0065 IFTSAI | ||
173 | 0052 D | ||
174 | 0054 96A | ||
175 | 0051 UN | ||
176 | |||
177 | 0020 BGM, Beginning of message | ||
178 | A segment to indicate the type and function of the message and | ||
179 | to transmit the identifying number. | ||
180 | |||
181 | 0030 DTM, Date/time/period | ||
182 | A segment to indicate date(s) and time(s) applying to the whole | ||
183 | message. | ||
184 | |||
185 | 0040 FTX, Free text | ||
186 | A segment to specify free form or processable supplementary | ||
187 | information. In computer-to-computer exchanges free form text | ||
188 | will normally require the receiver to process this segment | ||
189 | manually. | ||
190 | |||
191 | |||
192 | 0050 + Segment group 1: RFF-DTM | ||
193 | A group of segments to specify the document or message to which | ||
194 | the current message relates, and related date and time. | ||
195 | |||
196 | 0060 | RFF, Reference | ||
197 | A segment to identify a reference which applies to the | ||
198 | entire message, e.g. reference to previous message. | ||
199 | |||
200 | 0070 + DTM, Date/time/period | ||
201 | A segment to indicate date and time relating to the | ||
202 | reference. | ||
203 | |||
204 | |||
205 | 0080 Segment group 2: LOC-DTM | ||
206 | A group of segments to identify the routing and date of the | ||
207 | schedule or availability information. | ||
208 | |||
209 | 0090 LOC, Place/location identification | ||
210 | A segment to identify a location, e.g. place of | ||
211 | departure/arrival. | ||
212 | |||
213 | 0100 DTM, Date/time/period | ||
214 | A segment to indicate date(s) and time(s) related to the | ||
215 | location. | ||
216 | |||
217 | |||
218 | 0110 Segment group 3: EQD-EQN-MEA-DIM-FTX | ||
219 | A group of segments to define requested or available equipment. | ||
220 | |||
221 | 0120 EQD, Equipment details | ||
222 | A segment to specify requested or available equipment and | ||
223 | equipment size and type. | ||
224 | |||
225 | 0130 EQN, Number of units | ||
226 | A segment to specify the number of requested or available | ||
227 | pieces of equipment. | ||
228 | |||
229 | 0140 MEA, Measurements | ||
230 | A segment to specify measurements, other than dimensions, | ||
231 | associated with equipment, in terms of capacity. | ||
232 | |||
233 | 0150 DIM, Dimensions | ||
234 | A segment to specify dimensions applicable to equipment. | ||
235 | |||
236 | 0160 FTX, Free text | ||
237 | A segment to specify free form or processable supplementary | ||
238 | information associated with the equipment. | ||
239 | |||
240 | |||
241 | 0170 Segment group 4: TDT-DTM-TSR-FTX-EQD-QTY-MEA-SG5 | ||
242 | A group of segments to specify the schedule or availability | ||
243 | selection criteria and to detail the schedule or availability | ||
244 | information being provided. | ||
245 | |||
246 | 0180 TDT, Details of transport | ||
247 | A segment to indicate information related to the mode and | ||
248 | means of transport, eg. specific conveyance/carrier. | ||
249 | |||
250 | 0190 DTM, Date/time/period | ||
251 | A segment to indicate date(s) and time(s), e.g. earliest | ||
252 | departure date/time, latest arrival date/time. | ||
253 | |||
254 | 0200 TSR, Transport service requirements | ||
255 | A segment to identify contract, conditions of carriage, | ||
256 | services and priority requirements. | ||
257 | |||
258 | 0210 FTX, Free text | ||
259 | A segment to specify free form or processable supplementary | ||
260 | information related to the means of transport. | ||
261 | |||
262 | 0220 EQD, Equipment details | ||
263 | A segment to identify the equipment requested/available. | ||
264 | |||
265 | 0230 QTY, Quantity | ||
266 | A segment to indicate a quantity, e.g. number of | ||
267 | intermediate stops. | ||
268 | |||
269 | 0240 MEA, Measurements | ||
270 | A segment to indicate weight and/or volume selection | ||
271 | criteria, e.g. minimum weight. | ||
272 | |||
273 | |||
274 | 0250 Segment group 5: LOC-DTM | ||
275 | A group of segments to identify the routing(s) and indicate | ||
276 | corresponding date(s) and time(s). | ||
277 | |||
278 | 0260 LOC, Place/location identification | ||
279 | A segment to identify a location, e.g. place of | ||
280 | departure/arrival. | ||
281 | |||
282 | 0270 DTM, Date/time/period | ||
283 | A segment to indicate date(s) and time(s) related to the | ||
284 | location, e.g. date/time of scheduled departure/arrival. | ||
285 | |||
286 | |||
287 | 0280 Segment group 6: NAD-LOC-SG7 | ||
288 | A group of segments to indicate all parties involved in the | ||
289 | transaction and relevant locations, contacts and communication | ||
290 | channels. | ||
291 | |||
292 | 0290 NAD, Name and address | ||
293 | A segment to identify the party's name, address and | ||
294 | function. | ||
295 | |||
296 | 0300 LOC, Place/location identification | ||
297 | A segment to identify a place/location/sub-location and | ||
298 | where relevant the function. The present location must be | ||
299 | associated with the relevant party. | ||
300 | |||
301 | |||
302 | 0310 Segment group 7: CTA-COM | ||
303 | A group of segments to identify a contact and its | ||
304 | communication channels, related to the party. | ||
305 | |||
306 | 0320 CTA, Contact information | ||
307 | A segment to identify a person or department within a | ||
308 | party. | ||
309 | |||
310 | 0330 COM, Communication contact | ||
311 | A segment to identify the communication numbers of person | ||
312 | or department to whom communication should be directed. | ||
313 | |||
314 | |||
315 | 0340 Segment group 8: GID-HAN-FTX-SG9-SG10-SG11-SG12 | ||
316 | A group of segments to describe the goods items for which | ||
317 | schedule or availability is requested/provided. | ||
318 | |||
319 | 0350 GID, Goods item details | ||
320 | A segment to identify the goods item. A goods item can be | ||
321 | identified by up to three levels of packaging within this | ||
322 | segment. | ||
323 | |||
324 | 0360 HAN, Handling instructions | ||
325 | A segment to specify handling instructions relating to the | ||
326 | goods item. | ||
327 | |||
328 | 0370 FTX, Free text | ||
329 | A segment to specify free form or processable information | ||
330 | relating to the goods item. | ||
331 | |||
332 | |||
333 | 0380 Segment group 9: GDS-FTX | ||
334 | A group of segments to identify and describe the goods. | ||
335 | |||
336 | 0390 GDS, Nature of cargo | ||
337 | A segment to describe the nature of cargo. | ||
338 | |||
339 | 0400 FTX, Free text | ||
340 | A segment to describe the goods in free form. | ||
341 | |||
342 | |||
343 | 0410 Segment group 10: MEA-EQN | ||
344 | A group of segments to specify measurements applicable to | ||
345 | the goods item. | ||
346 | |||
347 | 0420 MEA, Measurements | ||
348 | A segment to specify measurements, other than dimensions, | ||
349 | applicable to the goods item. | ||
350 | |||
351 | 0430 EQN, Number of units | ||
352 | A segment to specify the number of equipment units to | ||
353 | which the measurement applies. | ||
354 | |||
355 | |||
356 | 0440 Segment group 11: DIM-EQN | ||
357 | A group of segments to specify dimensions applicable to the | ||
358 | goods item. | ||
359 | |||
360 | 0450 DIM, Dimensions | ||
361 | A segment to specify dimensions applicable to the goods | ||
362 | item. | ||
363 | |||
364 | 0460 EQN, Number of units | ||
365 | A segment to specify the number of equipment units to | ||
366 | which the given dimensions apply. | ||
367 | |||
368 | |||
369 | 0470 Segment group 12: DGS-FTX | ||
370 | A group of segments to specify dangerous goods details | ||
371 | related to the goods item. | ||
372 | |||
373 | 0480 DGS, Dangerous goods | ||
374 | A segment to specify the class of dangerous goods, | ||
375 | packing group, etc. | ||
376 | |||
377 | 0490 FTX, Free text | ||
378 | A segment to specify the dangerous goods technical name | ||
379 | and any other additional dangerous goods information. | ||
380 | |||
381 | 0500 UNT, Message trailer | ||
382 | A service segment ending a message, giving the total number of | ||
383 | segments in the message and the control reference number of the | ||
384 | message. | ||
385 | |||
386 | 4.2 Data segment index (Alphabetical sequence by tag) | ||
387 | |||
388 | BGM Beginning of message | ||
389 | COM Communication contact | ||
390 | CTA Contact information | ||
391 | DGS Dangerous goods | ||
392 | DIM Dimensions | ||
393 | DTM Date/time/period | ||
394 | EQD Equipment details | ||
395 | EQN Number of units | ||
396 | FTX Free text | ||
397 | GDS Nature of cargo | ||
398 | GID Goods item details | ||
399 | HAN Handling instructions | ||
400 | LOC Place/location identification | ||
401 | MEA Measurements | ||
402 | NAD Name and address | ||
403 | QTY Quantity | ||
404 | RFF Reference | ||
405 | TDT Details of transport | ||
406 | TSR Transport service requirements | ||
407 | UNH Message header | ||
408 | UNT Message trailer | ||
409 | |||
410 | 4.3 Message structure | ||
411 | |||
412 | See summary file | ||
413 | |||