BAPLTE — EDIFACT Bayplan / Stowage Plan Total Numbers Message (D.97A)

The BAPLTE message is the aggregated complement to BAPLIE: rather than listing every container, it conveys totals per cell, per weight category and per package type on board a vessel. It progressively faded after D.02B in favour of BAPLIE alone, but remains indexed in the earlier directories. This page summarises the segment structure as published by UN/CEFACT for directory D.97A.

Purpose

The BAPLTE message is the aggregated complement to BAPLIE: rather than listing every container, it conveys totals per cell, per weight category and per package type on board a vessel. It progressively faded after D.02B in favour of BAPLIE alone, but remains indexed in the earlier directories.

This page focuses on the structure published by UN/CEFACT for directory D.97A. The segments listed, their status (M / C), position and repetition factor are extracted from the official file baplte_c.htm hosted on service.unece.org.

Segment structure

The BAPLTE D.97A message has 0 header entries, 0 detail entries and 0 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.

Header

No segment in this section.

Detail

No segment in this section.

Summary

No segment in this section.

Changes vs D.96A

Top-level differences between D.96A and D.97A for the BAPLTE message (segments directly inside header / detail / summary, ignoring nested groups). The comparison is indicative: a given tag may have evolved inside nested groups without showing up in this synthesis.

Segments removed vs D.96A

• UNH in the header section — present in D.96A but missing in D.97A at the same level.
• BGM in the header section — present in D.96A but missing in D.97A at the same level.
• DTM in the header section — present in D.96A but missing in D.97A at the same level.
• RFF in the header section — present in D.96A but missing in D.97A at the same level.
• NAD in the header section — present in D.96A but missing in D.97A at the same level.
• TDT in the header section — present in D.96A but missing in D.97A at the same level.
• LOC in the header section — present in D.96A but missing in D.97A at the same level.
• FTX in the header section — present in D.96A but missing in D.97A at the same level.
• GID in the header section — present in D.96A but missing in D.97A at the same level.
• EQD in the header section — present in D.96A but missing in D.97A at the same level.
• EQN in the header section — present in D.96A but missing in D.97A at the same level.
• UNT in the header section — present in D.96A but missing in D.97A at the same level.

Structural example

Minimal example of an BAPLTE D.97A message with mandatory segments only. The goal is to show the exact version declared in UNH (BAPLTE:D:97A:UN) — not to replicate a full business case (see the BAPLTE D.96A page for an annotated example).

UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL097001'
UNH+1+BAPLTE:D:97A:UN'
BGM+244+BAPLTE-2026-MSC1234+9'
DTM+137:202605141430:203'
TDT+20+MSC1234W+1++MSC::ZZZ+++9301234:103:::MSC OSCAR'
LOC+5+FRLEH::6'
LOC+147+0010186::ZZZ'
EQA+TC+45G1'
CNT+16:48'
MEA+AAE+G+KGM:1176000'
UNT+9+1'
UNZ+1+CTRL097001'

Common errors

• Misaligned UNH tokens — The UNH+...+BAPLTE:D:97A:UN token must reflect exactly the directory in use — a mismatch between the UNH release and the release agreed with the partner is rejected by every strict validator.
• Wrong UNT segment count — The value after UNT+ must include UNH and UNT themselves. By far the most common sender-side error, regardless of the directory in use.
• Stale code lists — Between D.96A and D.97A, several code lists received new qualifiers (DTM status, RFF qualifier, NAD codes…). Reusing an older directory’s code tables triggers warnings or even rejections depending on the partner’s strict-conformance mode.

Related messages

Other versions of this message available on ediverse.io: BAPLTE D.96A, BAPLTE D.01B, BAPLTE D.99B, BAPLTE D.00B, BAPLTE D.02B.

← All EDIFACT versions