Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D93A Messages page.


This message is available for formal trial in the present version for a period of at least twelve months from the date of approval by the UN/ECE/TRADE/WP.4.

Organisations are invited to trial this message and are requested to notify their Rapporteur Team Secretariat of their intention. Comments on the results from the trial should also be forwarded to the Secretariat as soon as they are available. Based on the results of the trials, a UNSM will be issued.

It should be noted that this material is contained in a Trial Directory; however, it may differ from that in the UN Directories (UNTDID) having the same identfying tags. Any differences will be reconciled prior to the message becoming a UNSM.

Message Type:BAPLTE
Contr. Agency:UN

  1. Introduction
  2. Scope
    1. Functional Definition
    2. Field of Application
    3. Principles
  3. References
  4. Message Definition
  5. Message Definition
    1. Data Segment Clarification
    2. Message structure
      1. Branching Diagram
      2. Segment Table
    3. Data Segment Index (Alphabetic Sequence)

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.5, 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

0. Introduction

This specification provides the definition of the Bayplan/Stowage Plan Total Numbers Message (BAPLTE) to be used in Electronic Data Interchange (EDI) between partners involved in Administration, Commerce and Transport.

1. Scope

1.1. Functional Definition

A message to transmit information about the total numbers of equipment and quantity of goods on a 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 BAPLTE 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 center ============|==|=====|===|==6======== center | | | | | | | | | | | | | | | 7 | | | | | 4 | | | | | | | | ================|==|==8==|===|================ | | | | | | | | | | | | | | | | | | | | | stevedore===============|==|==9==|===|=========== stevedore

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


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 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 and total numbers of equipment or packages by location (i.e., port) and:or by type or equipment or packages.
  • The bayplan message BAPLIE must be used to transmit detailed information about equipment, location on the means of transport, goods descriptions and properties of equipment and/or goods.

2. References

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

3. Terms and Definitions

See UNTDID, Part 4, Section 2.5 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 the message. The message type code for the UN Bayplan/Stowage Plan Total Numbers message is BAPLTE. Note: Bayplan/Stowage Plan Total Numbers messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 BAPLTE 0052 D 0054 93A 0051 UN

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-SG3

A group of segments containing information about the total numbers of equipment and/or goods by location.

0130 LOC, Place/location identification

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

0140 GID, Goods item details

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

0150 Segment Group 3: EQD-EQN

A group of segments containing information about the type of equipment and the number of units.

0160 EQD, Equipment details

A segment to identify the type of equipment to which the following totals apply. Only transport equipment size/type coded or plain language is used here further to identify the type of equipment.

0170 EQN, Number of units

A segment to specify the number of equipment units.

0180 UNT, Message trailer

A service segment ending the message giving the total number of segments in the message and the control reference of the message.

4.2. Message Structure

4.2.1. Branching Diagram

4.2.2. 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 ×999 (C)
├─LOC Place/location identification ×1 (M)
├─GID Goods item details ×1 (C)
└─Segment Group 3 ×9999 (C)
──├─EQD Equipment details ×1 (M)
──└─EQN Number of units ×1 (C)
└─UNT Message trailer ×1 (M)

4.3. Data Segment Index (Alphabetic Sequence)

BGM Beginning of message
DTM Date/time/period
EQD Equipment details
EQN Number of units
FTX Free text
GID Goods item details
LOC Place/location identification
NAD Name and address
RFF Reference
TDT Details of transport
UNH Message header
UNT Message trailer

Return to Stylus Studio EDIFACT D93A 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.