Message type
UN/EDIFACT BAPLTE
Extended bay plan message with additional container data. It is published in 18 directory versions of the UN/EDIFACT standard, each defining its own segment structure.
Open the D02B BAPLTE specification- Message
- BAPLTE
- Directory versions
- 18
- Latest
- D02B
Sending and receiving
Exchange BAPLTE with your trading partners
The specification tells you what a valid BAPLTE looks like. Sending and receiving one means mapping it to the system that holds the data, agreeing the format with each partner, and handling the messages that come back when something is rejected. XEDI does the mapping, validation and transport.
Specifications
BAPLTE in every directory version
A trading partner names both the message and the directory, for example D00A BAPLTE, because the segments differ between versions. Open the one your partner specified.
18 directory versions
- D00A BAPLTE segment structure, data elements and codes for D00A
- D00B BAPLTE segment structure, data elements and codes for D00B
- D01A BAPLTE segment structure, data elements and codes for D01A
- D01B BAPLTE segment structure, data elements and codes for D01B
- D01C BAPLTE segment structure, data elements and codes for D01C
- D02A BAPLTE segment structure, data elements and codes for D02A
- D02B BAPLTE segment structure, data elements and codes for D02B
- D94B BAPLTE segment structure, data elements and codes for D94B
- D95A BAPLTE segment structure, data elements and codes for D95A
- D95B BAPLTE segment structure, data elements and codes for D95B
- D96A BAPLTE segment structure, data elements and codes for D96A
- D96B BAPLTE segment structure, data elements and codes for D96B
- D97A BAPLTE segment structure, data elements and codes for D97A
- D97B BAPLTE segment structure, data elements and codes for D97B
- D98A BAPLTE segment structure, data elements and codes for D98A
- D98B BAPLTE segment structure, data elements and codes for D98B
- D99A BAPLTE segment structure, data elements and codes for D99A
- D99B BAPLTE segment structure, data elements and codes for D99B
Related messages
Messages in the BAP set
UN/EDIFACT groups related documents under a shared three-letter stem. These usually appear together in one trading flow.
Frequently asked questions
What is the BAPLTE message?
Extended bay plan message with additional container data. It is one of the UN/EDIFACT message types, identified by the six-letter name BAPLTE in every directory version that publishes it.
Which directory version of BAPLTE do I need?
The one your trading partner specifies. BAPLTE is published in 18 directory versions and the segment detail differs between them, so a mapping built for one version is not automatically valid for another.
How do I send a BAPLTE message?
Map the data from the system that holds it into the segment structure the agreed directory version defines, then transport it by the route the partner uses, commonly AS2 or SFTP. XEDI handles the mapping, validation and transport, and surfaces the acknowledgements and errors that come back.
Sources and further reading
- GS1 EDI standards GS1 guidance on EDI standards used for supply-chain document exchange.
- UNECE introduction to UN/EDIFACT United Nations guidance on UN/EDIFACT for structured business data exchange.
- X12 EDI standards Official X12 standards body for North American EDI transaction standards.
- OpenPeppol post-award specifications OpenPeppol documentation for e-procurement and e-invoicing specifications.