Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D99A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Bayplan/stowage plan total numbers message

Version:D
Release:99A
Contr. Agency:UN
Revision:5
Date:99-01-14
SOURCE:Western European EDIFACT Board, MD2

CONTENTS
Bayplan/stowage plan total numbers 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:
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 trading 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

The Bayplan/stowage plan total numbers 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 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 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 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, 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 indicates 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 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 element0065BAPLTE
0052D
005499A
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 Segment Group 1: RFF-DTM

A group of segments to specify the document or message to which the current message relates, and related date and time.

0050 RFF, Reference

A segment to identify a reference which applies to the entire message, e.g. reference to previous message.

0060 DTM, Date/time/period

A segment to indicate date and time relating to the reference.

0070 Segment Group 2: NAD-SG3

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

0080 NAD, Name and address

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

0090 Segment Group 3: CTA-COM

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

0100 CTA, Contact information

A segment to identify a person or department within the party.

0110 COM, Communication contact

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

0120 Segment Group 4: TDT-LOC-DTM-RFF-FTX

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

0130 TDT, Details of transport

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

0140 LOC, Place/location identification

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

0150 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.

0160 RFF, Reference

A segment to identify the loading voyage number.

0170 FTX, Free text

A segment to transmit general information about vessel/voyage.

0180 Segment Group 5: LOC-GID-SG6

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

0190 LOC, Place/location identification

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

0200 GID, Goods item details

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

0210 Segment Group 6: EQD-EQN-RFF

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

0220 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.

0230 EQN, Number of units

A segment to specify the number of equipment units.

0240 RFF, Reference

A segment to specify a reference number to equipment.

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

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)
├─Segment Group 1 ×9 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×9 (C)
├─NAD Name and address ×1 (M)
└─Segment Group 3 ×9 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×9 (C)
├─Segment Group 4 ×3 (M)
├─TDT Details of transport ×1 (M)
├─LOC Place/location identification ×2 (M)
├─DTM Date/time/period ×99 (M)
├─RFF Reference ×1 (C)
└─FTX Free text ×1 (C)
├─Segment Group 5 ×999 (C)
├─LOC Place/location identification ×1 (M)
├─GID Goods item details ×1 (C)
└─Segment Group 6 ×9999 (C)
──├─EQD Equipment details ×1 (M)
──├─EQN Number of units ×1 (C)
──└─RFF Reference ×9 (C)
└─UNT Message trailer ×1 (M)

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