Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D95B Messages page. Vessel departure message
0. INTRODUCTIONThis 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. SCOPE1.1. Functional DefinitionA 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'. 1.2. Field of ApplicationThe 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. 1.3. PrinciplesIn 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. REFERENCESSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONSSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Data Segment ClarificationThis section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements. 0010 | UNH, Message headerA 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:
0020 BGM, Beginning of messageA segment to indicate the beginning of a message and to transmit identifying number. 0030 RFF, ReferenceA segment to provide a reference relating to the whole message, such as: - reference to previous message 0040 Segment Group 1: NAD-CTAA group of segments to identify a party and related contacts. 0050 NAD, Name and addressA segment to identify a name and address of a party, such as: - message sender - message recipient - ordering customer/principal - ordering customer agent 0060 CTA, Contact informationA segment to identify a person or department for the party, such as: - information contact 0070 Segment Group 2: TDT-RFF-DTMA group of segments to specify details of the departing means of transport. 0080 TDT, Details of transportA segment to identify the transport details of the departing vessel. 0090 RFF, ReferenceA segment to identify a relevant reference number, such as: - voyage number 0100 DTM, Date/time/periodA segment to identify a date and time related to the departure of the means of transport, such as: - actual sailing date/time 0110 Segment Group 3: QTY-FTXA group of segments to specify total numbers. 0120 QTY, QuantityA segment to specify the actual number of segments in the message and the control reference number of the message. 0130 FTX, Free textA segment to provide supplementary information related to the actual number of operations on equipment. 0140 UNT, Message trailerA 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)
4.3. Message structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D95B Messages page. |
Site Map | Privacy Policy | Terms of Use | Trademarks |