Container stock report 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: | COEDOR |
|---|---|
| Version: | D |
| Release: | 95A |
| Contr. Agency: | UN |
| Status: | 1 |
| Revision: | 1 |
| Date: | 95-01-06 |
| 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 |
0. INTRODUCTION
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.
1. SCOPE
1.1. Functional Definition
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'.
1.2. Field of Application
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.
1.3. Principles
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:
- The message contents can be uniquely identified by a combination of the following data elements:
A combination of the following data elements can be used to refer to business data contained in the Container announcement message:
- ordering customer, coded (NAD)
- ordering customer agent, coded (NAD)
- container announcement reference (EQD/RFF)
- The message can be sent on a regular basis; e.g. once or twice per day.
- One message may contain several containers identified by their prefix and serial number.
- For each container its stack position can be given, including the date and time of its checking by the stock reporter, and the date/time on which the container was delivered at the stock keeper's place.
- Also the transport status (= export, import, transhipment or continental), full/empty indication and the condition (damage) of the container can be specified.
- Depending on the transport status of the container additional information on the container can be given, such as carrier agent's reference, (seagoing) vessel, (sea) voyage number/indication and port of discharge.
- Goods item details cannot be completed.
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 stock report message is COEDOR.
Note: Container stock report messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | COEDOR |
| 0052 | D | |
| 0054 | 95A | |
| 0051 | UN |
0020 BGM, Beginning of message
A segment to indicate the beginning of a message and to transmit the identifying number.
0030 DTM, Date/time/period
A segment to indicate the date and time on which the particular container has been ascertained as being in stock (stock check date/time).
0040 FTX, Free text
A segment to specify free form or processable supplementary information, such as: - change information
0050 RFF, Reference
A segment to express a reference which applies to the entire message, such as: - reference to previous message
0060 Segment Group 1: NAD-CTA
A group of segments to identify a party and/or addresses and related contacts.
0070 NAD, Name and address
A segment to identify the party's name and address, and function, such as: - message recipient - message sender - ordering customer - ordering customer agent
0080 CTA, Contact information
A segment to identify a person or department of a message sender and/or message recipient, such as: - information contact
0090 Segment Group 2: EQD-RFF-DTM-LOC-SG3-SG4
A group of segments to specify containers in stock of the sending party, including relevant details.
0100 EQD, Equipment details
A segment to specify the prefix and number of the container, its status and a full/empty indication.
0110 RFF, Reference
A segment to express a reference which applies to the particular container, such as: - container announcement reference number
0120 DTM, Date/time/period
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).
0130 LOC, Place/location identification
A segment to indicate a port/place according to the corresponding container, such as: - stack position
0140 Segment Group 3: DAM-COD
A group of segments to specify damage details related to the equipment.
0150 DAM, Damage
A segment to specify equipment damages, such as the point of the damage on the equipment, and the type of damage.
0160 COD, Component details
A segment to specify component details of the damaged equipment.
0170 Segment Group 4: TDT-LOC
A group of segments to specify transport details related to the container.
0180 TDT, Details of transport
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.
0190 LOC, Place/location identification
A segment to indicate a port/place according to the corresponding container, such as: - place of discharge
0200 CNT, Control total
A segment to specify the number of containers in the message, explicitly given by the sender.
0210 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 | |
 |
COD | Component details |
| CTA | Contact information | |
|
DAM | Damage |
| DTM | Date/time/period | |
| EQD | Equipment details | |
| FTX | Free text | |
| 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 | ×1 | (M) |
| ├─FTX Free text | ×9 | (C) |
| ├─RFF Reference | ×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) |
| │─├─RFF Reference | ×9 | (C) |
| │─├─DTM Date/time/period | ×9 | (C) |
| │─├─LOC Place/location identification | ×9 | (C) |
| │─├─Segment Group 3 | ×9 | (C) |
| │─│─├─DAM Damage | ×1 | (M) |
| │─│─└─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) |
Return to EDIFACT D95A Messages page.