% Response.CharSet="utf-8" %>
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.
|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:|
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 Container stock report message (COEDOR) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A message to report containers that are in stock of the sending party (i.e., a terminal, depot or container freight station).
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'.
The Container stock report 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.
Business area: Pre- and on-carriage transport of containers/equipment
Sending functions include: Container terminal (seaside), inland terminal (landside), container freight station, container depot
Receiving functions include: Shipping agent, logistic center, freight forwarder
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 stock report message:
A combination of the following data elements can be used to refer to business data contained in the Container announcement 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 Container stock report message is COEDOR.
Note: Container stock report messages conforming to this document must contain the following data in segment UNH, composite S009:
A segment to indicate the beginning of a message and to transmit the identifying number.
A segment to indicate the date and time on which the particular container has been ascertained as being in stock (stock check date/time).
A segment to specify free form or processable supplementary information, such as: - change information
A segment to express a reference which applies to the entire message, such as: - reference to previous message
A group of segments to identify a party and/or addresses and related contacts.
A segment to identify the party's name and address, and function, such as: - message recipient - message sender - ordering customer - ordering customer agent
A segment to identify a person or department of a message sender and/or message recipient, such as: - information contact
A group of segments to specify containers in stock of the sending party, including relevant details.
A segment to specify the prefix and number of the container, its status and a full/empty indication.
A segment to express a reference which applies to the particular container, such as: - container announcement reference number
A segment to indicate the date and time on which the particular container has been ascertained as being in stock (stock check date/time), and to indicate when the container has been delivered at the stock keeper (actual equipment positioning date/time).
A segment to indicate a port/place according to the corresponding container, such as: - stack position
A group of segments to specify damage details related to the equipment.
A segment to specify equipment damages, such as the point of the damage on the equipment, and the type of damage.
A segment to specify component details of the damaged equipment.
A group of segments to specify transport details related to the container.
A segment to indicate information about sea transport related to the container (main carriage transport), such as voyage number/indication sea transport, vessel and carrier/liner service.
A segment to indicate a port/place according to the corresponding container, such as: - place of discharge
A segment to specify the number of containers in the message, explicitly given by the sender.
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|
|NAD||Name and address|
|TDT||Details of transport|
|├─UNH Message header||×1||(M)|
|├─BGM Beginning of message||×1||(M)|
|├─FTX Free text||×9||(C)|
|├─Segment Group 1||×9||(M)|
|│─├─NAD Name and address||×1||(M)|
|│─└─CTA Contact information||×9||(C)|
|├─Segment Group 2||×9999||(M)|
|│─├─EQD Equipment details||×1||(M)|
|│─├─LOC Place/location identification||×9||(C)|
|│─├─Segment Group 3||×9||(C)|
|│─│─└─COD Component details||×1||(C)|
|│─└─Segment Group 4||×1||(C)|
|│───├─TDT Details of transport||×1||(M)|
|│───└─LOC Place/location identification||×9||(C)|
|├─CNT Control total||×1||(M)|
|└─UNT Message trailer||×1||(M)|