Frames | No Frames

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

Container special handling order 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:COHAOR
Version:D
Release:95B
Contr. Agency:UN
Status:1
Revision:1
Date:95-07-07
SOURCE:Joint Transport Group (JM4)

CONTENTS
Container special handling order 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:
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 Container special handling order message (COHAOR) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

Order to perform a specified special handling and/or service on containers.

This message is part of a total set of container-related messages. These messages serve to facilitate the intermodal handling of containers by streamlining the information exchange. The business scenario for the container messages is clarified in a separate document, called: 'Guide to the scenario of EDIFACT container messages'.


1.2. Field of Application

The Container special handling order 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.


1.3. Principles

Business area: Pre- and on-carriage transport of containers/equipment

Sending functions include: Shipping agent, Logistic center, Freight forwarder

Receiving functions include: Container terminal, Container depot, Inland terminal, Container freight station

In the context of the 'Guide to the scenario of EDIFACT container messages' (as referred to at the start of section 1) the following guidelines, rules and functionality apply to this Container special handling order message:

  • The message contents can be uniquely identified by a combination of the following data elements:
  • message sender (NAD)
  • ordering customer (NAD)
  • work order reference (RFF)
  • A combination of the following data elements can be used in order to relate to business data contained in other container-related messages: container prefix and number (EQD)
  • In one message special handling orders for several containers can be specified.
  • The ultimate execution date and time of the special handling order can be included.
  • For each container the sea-going vessel, sea voyage number can be given.
  • The special handling orders are to be coded, completed with comments, if any.

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 Container special handling order message is COHAOR.

Note: Container special handling order messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065COHAOR
0052D
005495B
0051UN

0020 BGM, Beginning of message

A segment to indicate the beginning of a message and to transmit identifying number.

0030 DTM, Date/time/period

A segment to indicate a date and time applying to the whole message, such as: - ultimate execution date/time

0040 FTX, Free text

A segment to specify free form or processable supplementary information, such as: - change information

0050 Segment Group 1: RFF-DTM

A group of segments containing a reference and constants which apply to the entire message.

0060 RFF, Reference

A segment to express a reference which applies to the entire message, such as: - reference to previous message - work order reference number

0070 DTM, Date/time/period

A segment to indicate a date and time relating to the reference, such as: - order date/time (work order)

0080 Segment Group 2: NAD-CTA

A group of segments to identify a party and related contacts.

0090 NAD, Name and address

A segment to identify the party's name, address, and function, such as: - message recipient - message sender - ordering customer (if different from message sender)

0100 CTA, Contact information

A segment to identify a person or department for the party, such as: - information contact

0110 Segment Group 3: EQD-RFF-DTM-LOC-FTX-GOR-HAN-SG4-SG5

A group of segments to specify containers in which goods are transported.

0120 EQD, Equipment details

A segment to specify container prefix and number.

0130 RFF, Reference

A segment to provide a reference specific to the equipment, such as: - inspection number

0140 DTM, Date/time/period

A segment to provide a date and time relating to the equipment, such as: - inspection date/time - release date/time

0150 LOC, Place/location identification

A segment to provide a location relating to the equipment, such as: - place of inspection

0160 FTX, Free text

A segment to specify processable supplementary information associated with the container, such as: - description work item equipment (on terminal, depot or freight station)

0170 GOR, Governmental requirements

A segment to specify a governmental requirement relating to the equipment, such as: - government procedure to be conducted

0180 HAN, Handling instructions

A segment to specify a handling instruction relating to the equipment, such as: - put aside for cleaning - put aside for Customs examination

0190 Segment Group 4: TDT-LOC-DTM

A group of segments to specify related transport details for the equipment.

0200 TDT, Details of transport

A segment to specify main carriage transport details.

0210 LOC, Place/location identification

A segment to specify a location associated with the transport details, such as: - place of departure - place of arrival

0220 DTM, Date/time/period

A segment to specify a date/time relating to the transport details, such as arrival or departure date/time.

0230 Segment Group 5: NAD-CTA

A group of segments to identify different parties/places related to the equipment.

0240 NAD, Name and address

A segment to specify a related addres or party.

0250 CTA, Contact information

A segment to identify a person or department for the specified party.

0260 CNT, Control total

A segment to specify the number of containers in the message, explicitly given by the sender.

0270 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
CNT Control total
CTA Contact information
DTM Date/time/period
EQD Equipment details
FTX Free text
GOR Governmental requirements
HAN Handling instructions
LOC Place/location identification
NAD Name and address
RFF Reference
TDT Details of transport
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 ×9 (C)
├─Segment Group 1 ×9 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×9 (M)
├─NAD Name and address ×1 (M)
└─CTA Contact information ×9 (C)
├─Segment Group 3 ×999 (M)
├─EQD Equipment details ×1 (M)
├─RFF Reference ×9 (C)
├─DTM Date/time/period ×9 (C)
├─LOC Place/location identification ×9 (C)
├─FTX Free text ×9 (C)
├─GOR Governmental requirements ×9 (C)
├─HAN Handling instructions ×9 (C)
├─Segment Group 4 ×9 (C)
├─TDT Details of transport ×1 (M)
├─LOC Place/location identification ×9 (C)
└─DTM Date/time/period ×9 (C)
└─Segment Group 5 ×9 (C)
──├─NAD Name and address ×1 (M)
──└─CTA Contact information ×9 (C)
├─CNT Control total ×1 (M)
└─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.