972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Transport

BAPLIE Bayplan/stowage plan occupied and empty locations

The UN/EDIFACT message that transmits the equipment and goods on a means of transport, typically a container vessel, with their locations.

Sent by
Vessel operator, carrier or terminal
Received by
Terminal at the next port, carrier or vessel planner
Standard
UN/EDIFACT · Batch message
X12 equivalent
324 Vessel Stow Plan (Ocean)

What is the EDIFACT BAPLIE message?

BAPLIE is the UN/EDIFACT bayplan/stowage plan occupied and empty locations message. The directory defines it as a message to transmit information about equipment, mostly containers, and goods on a means of transport, typically a container vessel, including their location on board.

BAPLIE is the global standard for container vessel stowage data. After each port the stowage plan is sent to the next port's terminal and to planners, who use container positions, weights, ports of discharge and dangerous goods details to plan operations and check stability. SMDG publishes widely used implementation guides.

How the EDIFACT BAPLIE message worksDiagram of the UN/EDIFACT BAPLIE Bayplan/stowage plan occupied and empty locations message. Vessel operator, carrier or terminal sends it to terminal at the next port, carrier or vessel planner. It usually follows MOVINS. It is usually followed by COPRAR. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG4 loop with TDT (Transport information) and UNS (Section control). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT BAPLIE message worksBayplan/stowage plan occupied and empty locations: who sends it, where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSMOVINSStowage instructionBAPLIESENDERVessel operator,carrier or terminalRECEIVERTerminal at the nextport, carrier or vesselplannerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOPRARContainerdischarge/loadingorder2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage BAPLIEUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG4 · repeats up to 9TDTTransport informationUNSSection control+ 4 conditional groups, starting with:RFFNADLOCBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for BAPLIE. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT BAPLIE message worksDiagram of the UN/EDIFACT BAPLIE Bayplan/stowage plan occupied and empty locations message. Vessel operator, carrier or terminal sends it to terminal at the next port, carrier or vessel planner. It usually follows MOVINS. It is usually followed by COPRAR. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG4 loop with TDT (Transport information) and UNS (Section control). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT BAPLIEmessage worksBayplan/stowage plan occupied and emptylocations: who sends it, where it fits and whatthe directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSMOVINSStowage instructionBAPLIESENDERVessel operator,carrier orterminalRECEIVERTerminal at thenext port,carrier or vesselplannerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOPRARContainer discharge/loading order2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message BAPLIE (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG4 · repeats upto 9TDTTransport informationUNSSection control+ 4 conditional groups, starting with:RFFNADLOCBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for BAPLIE.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends BAPLIE, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around BAPLIE and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Sending the departure bayplan to the next port
  • Sharing positions of reefer and dangerous goods containers
  • Supporting vessel stability and lashing calculations

Where it fits in the message flow

Usually follows MOVINS Stowage instruction
This message BAPLIE Bayplan/stowage plan occupied and empty locations
Usually followed by COPRAR Container discharge/loading order

Structure

Mandatory segments in BAPLIE (directory D.21A)

In UN/EDIFACT directory D.21A, the BAPLIE message has 43 segment positions arranged in 12 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • SG4 (TDT)
  • UNS
  • UNT

Practical example

BAPLIE in practice

A container vessel departs Singapore for Colombo. The terminal sends the carrier and the Colombo terminal a BAPLIE listing every container on board with its bay, row and tier, weight, port of discharge, reefer settings and dangerous goods details. Colombo's planners prepare the discharge and loading sequence before arrival.

Implementation

Implementation considerations for BAPLIE

  • Follow the SMDG implementation guide version agreed with partners.
  • Validate container numbers, weights and positions.
  • Include complete dangerous goods data for segregation checks.
  • Send the plan promptly after the vessel departs.

How ECOM helps

Automate BAPLIE with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related transport messages

All 36 transport messages

Need help with BAPLIE?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us