|
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: | VESDEP |
|---|---|
| Version: | D |
| Release: | 96A |
| Contr. Agency: | UN |
| Status: | 1 |
| Revision: | 1 |
| Date: | 95-11-23 |
| 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 Vessel departure message (VESDEP) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A message from a stevedore to a liner agent informing the latter party of the closing of a vessel's file and giving information on the actual container operations.
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 Vessel departure 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.
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 Vessel departure message:
The ordering customer agent is to supplement the unique identification only when several agents are acting on behalf of the same shipping line for the same voyage number.
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 Vessel departure message is VESDEP.
Note: Vessel departure messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | VESDEP |
| 0052 | D | |
| 0054 | 96A | |
| 0051 | UN |
A segment to indicate the beginning of a message and to transmit identifying number.
A segment to provide a reference relating to the whole message, such as: - reference to previous message
A group of segments to identify a party and related contacts.
A segment to identify a name and address of a party, such as: - message sender - message recipient - ordering customer/principal - ordering customer agent
A segment to identify a person or department for the party, such as: - information contact
A group of segments to specify details of the departing means of transport.
A segment to identify the transport details of the departing vessel.
A segment to identify a relevant reference number, such as: - voyage number
A segment to identify a date and time related to the departure of the means of transport, such as: - actual sailing date/time
A group of segments to specify total numbers.
A segment to specify the actual number of segments in the message and the control reference number of the message.
A segment to provide supplementary information related to the actual number of operations on equipment.
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 | |
| CTA | Contact information | |
| DTM | Date/time/period | |
| FTX | Free text | |
| NAD | Name and address | |
| QTY | Quantity | |
| RFF | Reference | |
| TDT | Details of transport | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─RFF Reference | ×9 | (C) |
| ├─Segment Group 1 | ×9 | (M) |
| │─├─NAD Name and address | ×1 | (M) |
| │─└─CTA Contact information | ×9 | (C) |
| ├─Segment Group 2 | ×1 | (M) |
| │─├─TDT Details of transport | ×1 | (M) |
| │─├─RFF Reference | ×9 | (C) |
| │─└─DTM Date/time/period | ×9 | (C) |
| ├─Segment Group 3 | ×9 | (C) |
| │─├─QTY Quantity | ×1 | (M) |
| │─└─FTX Free text | ×1 | (C) |
| └─UNT Message trailer | ×1 | (M) |