Frames | No Frames

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

Bayplan/stowage plan occupied and empty locations 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:BAPLIE
Version:D
Release:94A
Contr. Agency:UN
Status:2
Revision:1
Date:94-09-21
SOURCE:Western European EDIFACT Board

CONTENTS
Bayplan/stowage plan occupied and empty locations 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:
D93A, D94A, D94B, 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 Bayplan/stowage plan occupied and empty locations message (BAPLIE) 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 transmit information about equipment and goods on a means of transport, including their location on the means of transport. The message can be exchanged between (liner's) agents, tonnage centers, stevedores and ships masters/operators (see section 1.3 for more details).


1.2. Field of Application

This message may be applied for both national and international trade. It is based on universal practice and is not dependent on the type of business or industry.


1.3. Principles

In the shipping industry the BAPLIE message can be used between partners as indicated below:

ships/liner ============== 1 ============== ships/liner agents =======2===== =====13====== agents | | | | | 3 | | | | | | | | | | I tonnage ==5 ====== | | ======11= tonnage I centre =========|==|=====|===|==6===== centre | | | | | | | | 7 | | | | | 4 | | | | | | | | =============|==|==8==|===|============= | | | | | | | | | | | | | | | | | | | | | | | | | | | | stevedore============|==|==9==|===|======== stevedore

| | | | | | | | | | | | ====10=== ships master/operator ===12===

PORT OF DEPARTURE(PD) NEXT PORT OF CALL(NC)

1) Agent(PD) to agent (NC) 2) Agent(PD) to ships master/operator(PD) 3) Agent(PD) to tonnage centre (PD) 4) Agent(PD) to stevedore (PD) 5) Tonnage centre(PD) to ships master/operator (PD) 6) Tonnage centre(PD) to tonnage centre (NC) 7) Tonnage centre(PD) to stevedore (PD) 8) Stevedore (PD) to tonnage centre (NC) 9) Stevedore (PD) to stevedore (NC) 10) Stevedore (PD) to ships master/operator (PD) 11) Ships master/operator to tonnage centre (NC) 12) Ships master/operator to stevedore (NC) 13) Ships master/operator to agent (NC)

The above gives only one set of communication channels per organisation but in practice there will be a combination of one or more channels per organisation from or to port of departure/next port of call.

  • The message will contain only one vessel/voyage combination, giving details regarding carrier, mode of transport, means of transport, equipment, location on the means of transport, goods descriptions and properties of equipment and/or goods.
  • The message can be used to transmit information about occupied locations on the means of transport, however information about empty locations may be added.
  • The bayplan message BAPLTE must be used to transmit information about total numbers of equipment and quantity of goods on a means of transport.

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 Bayplan/stowage plan occupied and empty locations message is BAPLIE.

Note: Bayplan/stowage plan occupied and empty locations messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065BAPLIE
0052D
005494A
0051UN

0020 BGM, Beginning of message

A segment to indicate the beginning of the message and to transmit function, type and number of the message.

0030 DTM, Date/time/period

A segment to indicate date and time of the preparation of the message.

0040 RFF, Reference

A segment to indicate a message reference number.

0050 NAD, Name and address

A segment to identify the liner service operating or responsible for a particular vessel/voyage.

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

A group of segments identifying the means of transport and related details.

0070 TDT, Details of transport

A segment to identify a means of transport and discharge voyage number.

0080 LOC, Place/location identification

A segment to identify the locations to which the following information applies.

0090 DTM, Date/time/period

A segment to indicate date and time of events in local time, else the time zone specifier is to be used.

0100 RFF, Reference

A segment to identify the loading voyage number.

0110 FTX, Free text

A segment to transmit general information about vessel/voyage.

0120 Segment Group 2: LOC-GID-GDS-FTX-MEA-DIM-TMP-RNG-LOC-RFF-

SG3-SG4 A group of segments containing information about the equipment and/or goods and its stowage location onboard a vessel.

0130 LOC, Place/location identification

A segment to identify locations relevant to the equipment or goods carried.

0140 GID, Goods item details

A segment to identify the number of packages of the goods.

0150 GDS, Nature of cargo

A segment to identify or specify the goods carried.

0160 FTX, Free text

A segment to transmit goods descriptions, additional equipment details or other relevant free text.

0170 MEA, Measurements

A segment specifying physical weights related to an equipment detail or a goods item detail.

0180 DIM, Dimensions

A segment to identify off standard measurements (e.g. overheight, overlength etc.).

0190 TMP, Temperature

A segment to indicate the temperature setting in relation to an equipment detail.

0200 RNG, Range details

A segment to transmit a temperature range in relation to an equipment detail.

0210 LOC, Place/location identification

A segment to identify the locations (ports) to which the given information applies.

0220 RFF, Reference

A segment to give additional information on equipment or goods carried (i.e. equipment expected to be shifted at the next port).

0230 Segment Group 3: EQD-EQA-NAD

A group of segments containing information about the type of equipment.

0240 EQD, Equipment details

A segment to identify a single piece of equipment to which the following information applies. Only transport equipment size/type coded or plain language is used here further to identify the equipment.

0250 EQA, Attached equipment

A segment to identify details of equipment attached to the main piece of equipment.

0260 NAD, Name and address

A segment to identify the owner/operator of a particular piece of equipment.

0270 Segment Group 4: DGS-FTX

A group of segments containing information about dangerous

0280 DGS, Dangerous goods

A segment to identify dangerous goods related to an equipment detail.

0290 FTX, Free text

A segment to give additional information concerning dangerous goods.

0300 UNT, Message trailer

A service segment ending the 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
DGS Dangerous goods
DIM Dimensions
DTM Date/time/period
EQA Attached equipment
EQD Equipment details
FTX Free text
GDS Nature of cargo
GID Goods item details
LOC Place/location identification
MEA Measurements
NAD Name and address
RFF Reference
RNG Range details
TDT Details of transport
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)
├─DTM Date/time/period ×1 (M)
├─RFF Reference ×1 (C)
├─NAD Name and address ×3 (C)
├─Segment Group 1 ×3 (M)
├─TDT Details of transport ×1 (M)
├─LOC Place/location identification ×1 (M)
├─DTM Date/time/period ×99 (M)
├─RFF Reference ×1 (C)
└─FTX Free text ×1 (C)
├─Segment Group 2 ×9999 (C)
├─LOC Place/location identification ×1 (M)
├─GID Goods item details ×1 (C)
├─GDS Nature of cargo ×1 (C)
├─FTX Free text ×9 (C)
├─MEA Measurements ×9 (M)
├─DIM Dimensions ×9 (C)
├─TMP Temperature ×1 (C)
├─RNG Range details ×1 (C)
├─LOC Place/location identification ×9 (C)
├─RFF Reference ×1 (M)
├─Segment Group 3 ×3 (C)
├─EQD Equipment details ×1 (M)
├─EQA Attached equipment ×9 (C)
└─NAD Name and address ×1 (C)
└─Segment Group 4 ×999 (C)
──├─DGS Dangerous goods ×1 (M)
──└─FTX Free text ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D94A 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 Simplify Legacy Data Integration with Stylus Studio XML Enterprise Edition - Free Download!
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-2011 All Rights Reserved.