<% Response.CharSet="utf-8" %> UN/EDIFACT D97A Message VESDEP - Vessel departure message Return to Stylus Studio EDIFACT D97A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Vessel departure message

Version:D
Release:97A
Contr. Agency:UN
Revision:2
Date:96-12-13
SOURCE:Joint Transport Group (JM4)

CONTENTS
Vessel departure message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard 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 Vessel departure message (VESDEP) 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 from a stevedore to a liner agent or from a liner agent to a local authority (e.g. port authority) to inform the latter party of the departure of a vessel and giving information on the actual container or cargo 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'.


1.2. Field of Application

The Vessel departure 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. Principles

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.


2. REFERENCES

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard 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 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 Vessel departure message is VESDEP.

Note: Vessel departure messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065VESDEP
0052D
005497A
0051UN

0020 BGM, Beginning of message

A segment to indicate the beginning of a message and to transmit identifying number.

0030 DTM, Date/time/period

A segment to indicate a date and/or time applying to the whole message, such as date and time of document or message issue.

0040 FTX, Free text

A segment to specify free format supplementary information: - change information - additional remarks

0050 Segment Group 1: RFF-DTM

A group of segments to specify a reference relating to the whole message, and its date and/or time.

0060 RFF, Reference

A segment to provide a reference relating to the whole message, such as: - reference to previous message

0070 DTM, Date/time/period

A segment to indicate date and/or time related to the reference.

0080 Segment Group 2: NAD-SG3

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

0090 NAD, Name and address

A segment to identify a name and address of a party, such as: - message sender - message recipient - ordering customer/principal - ordering customer agent

0100 Segment Group 3: CTA-COM

A group of segments to identify a contact and its communications related to the party.

0110 CTA, Contact information

A segment to identify a person or department for the party, such as: - information contact

0120 COM, Communication contact

A segment to identify a communication number of a person or department to whom communication should be directed.

0130 Segment Group 4: TDT-RFF-LOC-DTM-MEA

A group of segments to specify details of the departing means of transport.

0140 TDT, Details of transport

A segment to identify the transport details of the departing vessel, such as voyage number or an indication of the transport method.

0150 RFF, Reference

A segment to identify a relevant reference number, such as: - voyage number

0160 LOC, Place/location identification

A segment to specify a place or port of call of the means of transport or conveyance, such as: - Maritime Mobile Ship Identifier (MMSI number)

0170 DTM, Date/time/period

A segment to identify a date and time related to the departure of the means of transport, such as: - actual sailing date/time

0180 MEA, Measurements

A segment to specify a measurement related to the means of transport, such as: - gross tonnage (of the vessel)

0190 Segment Group 5: QTY-FTX

A group of segments to specify total numbers.

0200 QTY, Quantity

A segment to specify the actual number of segments in the message and the control reference number of the message.

0210 FTX, Free text

A segment to provide supplementary information related to the actual number of operations on equipment.

0220 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
COM Communication contact
CTA Contact information
DTM Date/time/period
FTX Free text
LOC Place/location identification
MEA Measurements
NAD Name and address
QTY Quantity
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 ×9 (C)
├─FTX Free text ×9 (C)
├─Segment Group 1 ×9 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×9 (M)
├─NAD Name and address ×1 (M)
└─Segment Group 3 ×9 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×9 (C)
├─Segment Group 4 ×1 (M)
├─TDT Details of transport ×1 (M)
├─RFF Reference ×9 (C)
├─LOC Place/location identification ×9 (C)
├─DTM Date/time/period ×9 (C)
└─MEA Measurements ×9 (C)
├─Segment Group 5 ×9 (C)
├─QTY Quantity ×1 (M)
└─FTX Free text ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D97A Messages page.