Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D01B Messages page. Container stock report message
0. INTRODUCTIONThis 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. SCOPE1.1. Functional definitionA 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 applicationThe Container stock report message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry. 1.3. PrinciplesBusiness 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 in order to relate to business data contained in the Container acceptance order:
The transport sub-working group (D4) has developed recommendations for a harmonised implementation of this message through its subgroup ITIGG (International Transport Implementation Guidelines Group). Users implementing the message are strongly advised to apply these recommendations, which may be obtained from the D4 secretariat. 2. REFERENCESSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS3.1. Standard terms and definitionsSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Segment clarificationThis section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements. 0010 UNH, Message headerA 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:
0020 BGM, Beginning of messageA segment to indicate the beginning of a message and to transmit the identifying number. 0030 DTM, Date/time/periodA 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 textA segment to specify free form or processable supplementary information, such as: - change information 0050 Segment Group 1: RFF-DTMA group of segments to specify a reference relating to the whole message, and its date and/or time. 0060 RFF, ReferenceA segment to express a reference which applies to the entire message, such as: - reference to previous message 0070 DTM, Date/time/periodA segment to indicate date and/or time related to the reference. 0080 Segment Group 2: NAD-SG3A group of segments to identify a party and/or addresses and related contacts. 0090 NAD, Name and addressA segment to identify the party's name and address, and function, such as: - message recipient - message sender - ordering customer - ordering customer agent 0100 Segment Group 3: CTA-COMA group of segments to identify a contact and its communications related to the party. 0110 CTA, Contact informationA segment to identify a person or department of a message sender and/or message recipient, such as: - information contact 0120 COM, Communication contactA segment to identify a communication number of a person or department to whom communication should be directed. 0130 Segment Group 4: EQD-RFF-DTM-LOC-COD-HAN-EQN-SG5-SG6-SG8-SG10A group of segments to specify containers in stock of the sending party, including relevant details by individual container number or grouped and total by type and size. 0140 EQD, Equipment detailsA segment to specify the prefix and number of the container, its status and a full/empty indication. 0150 RFF, ReferenceA segment to express a reference which applies to the particular container, such as: - container announcement reference number - acceptance order reference 0160 DTM, Date/time/periodA 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). 0170 LOC, Place/location identificationA segment to indicate a port/place according to the corresponding container, such as: - stack position 0180 COD, Component detailsA segment to specify the details of the components of transport equipment. 0190 HAN, Handling instructionsA segment to specify handling instructions related to the container equipment. 0200 EQN, Number of unitsTo specify the number of units of a particular type and size of equipment. 0210 Segment Group 5: DAM-CODA group of segments to specify damage details related to the equipment. 0220 DAM, DamageA segment to specify equipment damages, such as the point of the damage on the equipment, and the type of damage. 0230 COD, Component detailsA segment to specify component details of the damaged equipment. 0240 Segment Group 6: TDT-SG7A group of segments to specify transport details related to the container. 0250 TDT, Details of transportA 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. 0260 Segment Group 7: LOC-DTMA group of segments to specify locations related to the main carriage of the container equipment. 0270 LOC, Place/location identificationA segment to specify a location related to the main carriage of the container such as port of discharge. 0280 DTM, Date/time/periodA segment to specify date(s) and time(s) related to a location. 0290 Segment Group 8: DGS-FTX-MEA-SG9A segment group to identify dangerous goods. 0300 DGS, Dangerous goodsA segment to specify dangerous goods. 0310 FTX, Free textA segment to specify supplementary details regarding the dangerous goods such as the technical name of the dangerous goods etc. 0320 MEA, MeasurementsA segment to specify measurements of the dangerous goods, such as: - net net weight. 0330 Segment Group 9: CTA-COMA segment group to specify contact information including communication details regarding the dangerous goods. 0340 CTA, Contact informationA segment to identify a person or department to be contacted regarding the dangerous goods. 0350 COM, Communication contactA segment to specify communication details of the contact specified in the CTA segment. 0360 Segment Group 10: TMP-RNGA segment group to identify transport related temperature settings. 0370 TMP, TemperatureA segment to specify the type of transport related temperature such as storage, transport or operating temperature and also to optionally specify a single value temperature setting. 0380 RNG, Range detailsA segment to optionally specify the transport related temperature such as a range of values. 0390 CNT, Control totalA segment to specify the number of containers in the message, explicitly given by the sender. 0400 UNT, Message trailerA service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message. 4.2. Segment index (alphabetical sequence by tag)
4.3. Message structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D01B Messages page. |
Site Map | Privacy Policy | Terms of Use | Trademarks |