Frames | No Frames

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

Container discharge/loading 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:COPRAR
Version:D
Release:95B
Contr. Agency:UN
Status:1
Revision:1
Date:95-07-07
SOURCE:Joint Transport Group (JM4)

CONTENTS
Container discharge/loading 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 discharge/loading order message (COPRAR) 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 order to the container terminal that the containers specified have to be discharged from a seagoing vessel or have to be loaded into a seagoing vessel.

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 discharge/loading 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: Loading and discharging of containers/equipment

Sending functions include: Ship's agent, Liner agent

Receiving functions include: Container terminal, Stevedore

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 discharge/loading order message:

  • The message contents can be uniquely identified by a combination of the following data elements:
  • ordering customer, coded (NAD)
  • ordering customer agent, coded (NAD)
  • container discharge/loading order reference (RFF)

The ordering customer agent, coded is needed to supplement the unique identification only in the following situation: the agent acts on behalf of several ordering customers issuing the same range of reference numbers for each customer. E.g., the ship's agent acts on behalf of several shipping lines issuing for each shipping line the same range of numbers.

  • A message contains information on only one visit/conveyance of a seagoing container vessel either arriving or departing.
  • A message contains an order for either discharging or loading containers from or into the seagoing container vessel. One order message does not necessarily cover all containers to be loaded/discharged.
  • An indicator for the equipment status may be completed on container level (EQD-segment), e.g., import, export, transhipment, shifter.
  • One shipping line can be specified on message level.
  • The sea-going container vessel and sea voyage number can be specified on message level.
  • For each container its cell position on board the container vessel and its port of discharge can be given.
  • For each container dangerous goods information can be specified.
  • If the container prefix and number is not known (in the loading order message), a supplementary container reference number (Container sequence number) is used to identify a container group in the message to be able to refer to this information of the container(s) in the loading report message.
  • In case of a loading order an equipment guideline can be specified in the message in order to load (empty) containers that cannot be identified by their full prefix and serial numbers. In case of a guideline a combination of size and type and/or a certain range of equipment serial numbers (container prefix and numbers) can be given for a group of one or several containers.
  • 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 discharge/loading order message is COPRAR.

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

Data element0065COPRAR
0052D
005495B
0051UN

0020 BGM, Beginning of message

A segment to indicate the beginning of a message and to transmit identifying number and the further specification of the message type (in data element 1001: Document/message name, coded), such as Loading order, Discharge order.

0030 FTX, Free text

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

0040 RFF, Reference

A segment to express a reference which applies to the entire message, such as: - container discharge/loading order reference - reference to previous message

0050 Segment Group 1: TDT-RFF-LOC-DTM-FTX

A group of segments to indicate the main carriage means of transport.

0060 TDT, Details of transport

A segment identifying the voyage of the vessel relevant to the message (main transport).

0070 RFF, Reference

A segment identifying a relevant reference number, such as: - shipping - syndicate - marketing organization - conference code

0080 LOC, Place/location identification

A segment to identify a location related to the means of transport, such as: - place of departure/arrival (terminal within the port)

0090 DTM, Date/time/period

A segment identifying a date/time related to the arrival or departure of the vessel, such as: - estimated date/time of arrival/departure

0100 FTX, Free text

A segment giving supplementary information related to the vessel, such as: - transport details remarks

0110 Segment Group 2: NAD-CTA

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

0120 NAD, Name and address

A segment to identify the party's name, address, and function, and other addresses, such as: - message recipient - message sender - ordering customer - ordering customer agent

0130 CTA, Contact information

A segment to identify a person or department of a message sender and/or message recipient, such as: - information contact

0140 Segment Group 3: EQD-RFF-EQN-TMD-DTM-LOC-MEA-DIM-TMP-RNG-SEL-

FTX-DGS-EQA-SG4-NAD A group of segments to specify containers or groups of containers (in case of guidelines) that are either to be loaded or to be discharged.

0150 EQD, Equipment details

A segment identifying a container, container size/type. The equipment status may be e.g. import, export, transhipment, shifter.

0160 RFF, Reference

A segment identifying a relevant reference number, such as: - container sequence number - upper equipment serial number of range - lower equipment serial number of range

0170 EQN, Number of units

A segment to specify the number of containers in one guideline that meets the same equipment details information.

0180 TMD, Transport movement details

A segment to indicate a Full Container Load (FCL) or a Less than Full Container Load (LCL).

0190 DTM, Date/time/period

A segment to identify a date/time related to the equipment, such as: - actual arrival/departure date/time - CSC expiration date (International Convention for Safe Containers)

0200 LOC, Place/location identification

A segment to identify a location or country related to the equipment, such as: - stowage cell - (final) place/port of discharge - transhipment place - place of delivery - country of origin/destination

0210 MEA, Measurements

A segment specifying a physical measurement related to the equipment, such as: - gross weight

0220 DIM, Dimensions

A segment specifying physical dimensions related to the equipment, such as: - gross dimensions - off standard dimension general - off standard dimension left - off standard dimension right - off standard dimension back - off standard dimension front

0230 TMP, Temperature

A segment which identifies the transport temperature setting of the container.

0240 RNG, Range details

A segment to specify the transport temperature range setting of the container.

0250 SEL, Seal number

A segment identifying a seal number related to the equipment.

0260 FTX, Free text

A segment to specify supplementary information related to the equipment, such as: - blockade reason - government inspection service - container loading remarks - container remarks - container order information - additional remarks concerning the container - container safety convention plate - continuous examination program (ACEP)

0270 DGS, Dangerous goods

A segment to identify the UN-number and the class of the dangerous goods loaded in the container.

0280 EQA, Attached equipment

A segment to identify clip-on units, such as: - generator sets

0290 Segment Group 4: TDT-RFF-LOC-DTM

A group of segments to specify the planned on-carriage details in case this message is a discharge order message.

0300 TDT, Details of transport

A segment identifying the on-carriage transport details of the mode, means of transport by which the container will depart after being discharged.

0310 RFF, Reference

A segment identifying a relevant reference number, such as: - shipping line - syndicate - marketing organization - conference code

0320 LOC, Place/location identification

A segment identifying locations related to the transport details, such as: - place of departure

0330 DTM, Date/time/period

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

0340 NAD, Name and address

A segment to specify a related address or party, such as: - container operator

0350 CNT, Control total

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

0360 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
DGS Dangerous goods
DIM Dimensions
DTM Date/time/period
EQA Attached equipment
EQD Equipment details
EQN Number of units
FTX Free text
LOC Place/location identification
MEA Measurements
NAD Name and address
RFF Reference
RNG Range details
SEL Seal number
TDT Details of transport
TMD Transport movement details
TMP Temperature
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)
├─FTX Free text ×9 (C)
├─RFF Reference ×9 (M)
├─Segment Group 1 ×1 (M)
├─TDT Details of transport ×1 (M)
├─RFF Reference ×9 (C)
├─LOC Place/location identification ×9 (C)
├─DTM Date/time/period ×9 (C)
└─FTX Free text ×9 (C)
├─Segment Group 2 ×9 (M)
├─NAD Name and address ×1 (M)
└─CTA Contact information ×9 (C)
├─Segment Group 3 ×9999 (M)
├─EQD Equipment details ×1 (M)
├─RFF Reference ×9 (C)
├─EQN Number of units ×1 (C)
├─TMD Transport movement details ×9 (C)
├─DTM Date/time/period ×9 (C)
├─LOC Place/location identification ×9 (C)
├─MEA Measurements ×9 (C)
├─DIM Dimensions ×9 (C)
├─TMP Temperature ×9 (C)
├─RNG Range details ×9 (C)
├─SEL Seal number ×9 (C)
├─FTX Free text ×9 (C)
├─DGS Dangerous goods ×9 (C)
├─EQA Attached equipment ×9 (C)
├─Segment Group 4 ×1 (C)
├─TDT Details of transport ×1 (M)
├─RFF Reference ×9 (C)
├─LOC Place/location identification ×9 (C)
└─DTM Date/time/period ×9 (C)
└─NAD Name and address ×1 (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.