Saturday, 2 May 2020

BAPLIE and flat rack bundle

Sometimes, the gap between MIGs and reality is definitely huge.

A good example comes from BAPLIE and flat rack bundle: here below, the correct way to report a bundle of flat in BAPLIE version 3. 

Sample comes from SMDG MIG which is available on the SMDG site or here.

Friday, 27 September 2019

Standardization problems

Standardization is definitely a complicated process: tons of MIGs are available on the web but end users always find the way to create unpredictable variables to prevent a correct data processing.  

Recently, I'm struggling with an issue about the VAT number of freight forwarders/custom brokers reported into COREOR D00B: apparently, it's unclear if the nation code has to be included, as NAD02, in NAD segment when reporting the VAT number

In terms of message structure, that's the issue: 




Value reported in NAD02, is the target value to transcoding hence the prefix 'IT' makes a big difference when applying the mapping rules and the translation rules.

I'm quite interested in collecting feed-back about this topic: in case you are experiencing the same issue in your EDI environment, you can drop a comment here!

Sunday, 2 June 2019

TPFREP pool results

Time ago a run a pool about TPFREP potential receivers: finally, here below the results that I'm glad to share with you: 

Saturday, 18 May 2019

Tricks when debugging an EDI transaction

Sometimes you might need to debug some EDI transactions and the lack of CR/LF can be an issue. I found out that Notepad++ can easly fix this issue:

But that's just the tip of the iceberg! I have developed a bunch of macros that can be used in a wide range of scenarios and that's a small sample: due to some internal procedures, I needed to remove the goods description into BAPLIE file but did not have the chance to edit related mapping rule. Goods description is stored in Segment Group 5 as FTX04:


Applying the following criteria, in conjunction with CR/LF, will purge unwanted information and will change segment as follow: 


Hope these tricks will be useful to you!

Wednesday, 25 October 2017

My best free tool for BAPLIE

In this post, I will review my best BAPLIE free tools available on the internet.

1. BAPLIE Viewer

It's a great and reliable tool developed many many years ago.
I know for sure that several small Terminals have used the BAPLIE Viewer as standard and unique ship planning program which may confuse you unless you never gave it a try.
BAPLIE Viewer has tons of functionalities; here below some of them: 

Files exported by the prgram:
  • CSV comma separated
  • TXT text files TAB delimited
  • DBF, dBase IV file
  • Microsoft Excel using preset template or to new worksheet
  • Clipboard copy of data
Reports genrated:
  • Container list, filtered and sorted
  • IMDG list; list of dangerous cargo, filtered by port of discharge or displayed as transit cargo
  • Reefer list; list of reefer containers; filtered by port of discharge and status (all, dry, live and empty reefer containers)
  • Cargo summary; summary of all cargo on board by port of discharge
  • Container data; selected container data from BAPLIE file
  • Break bulk; summary of all break bulk cargo from BAPLIE file
  • Suez canal report (cargo summary)
  • Stack weight summary separate for deck and hold; 20FT, 40FT or mixed stowage
  • OOG (Out of Gauge) containers summary with particular dimensions
  • Container remarks; Handling instructions, Special instructions, Container remark, Description of goods, General information's
Statistics created: 
  • General statistics; selection of different statistics per container type, operator, owner, etc...
  • Tonnage sheet; break down of cargo by units and weight, operator, owner, container size, load and discharge port
  • IMDG cargo summary; summary of dangerous cargo by class; port of discharge, container size, deck or hold
  • Container type summary; different container types filtered by line operator
  • Transversal weight distribution; weights and horizontal moments, calculation of cargo induced ship list
  • Load port summary by operator; break down of cargo on board by operator, loading and discharge port
Additional tools and options:
  • Decode and display content of BAPLIE file header
  • Removal of line feeds and unprintable characters from BAPLIE file
  • Create query to extract data from file
  • BAPLIE file analysis; checking for different errors in BAPLIE file and/or stowage
  • Bay view; graphical display of cargo stowage with different coloring filters
  • Cargo plan; graphical display of cargo plan with different coloring filters
  • ISO container types decoder
  • ISO port codes; 8283 ports, automatically decoded for Baplie viewer, but can be used as separate routine
  • Container Id check digit calculation
BAPLIE 1.5, 2.07, 2.1, 3.0

Tons of statistical reports;
Handy data export tool in several formats (including the Plan Master format).
Bay plan and letter plan printing;

Not updated since 2005;
Does not validate message;
Does not support VGM.

2. EDIFACT Viewer

It's a great tool which supports not only BAPLIE but also several UN/EDIFACT messages.
Here the full list of supported messages. 
The EDIFACT Viewer allows to export messages in csv and html files plus has a very intuitive GUI to menage the contents of your files.

All BAPLIE versions; 

Easy to use; 
Solid message translation/acknowledgment; 
Support to VGM; 
Also tested on several Linux distros with Wine.

The last updated version was released in 2010;
Does not validate message.

3. SVM BAPLIE Viewer

It's a very recent development which requires java in order to run on your pc.

SVM BAPLIE Viewer also validates the file and lets you know if there are any incorrect or missing segments which may prevent the file from being read and converted.
SVM BAPLIE Viewer allows to create customized data export templates which include the count function: template then can be saved on your pc and used as soon as you need it. 


Customized template to export data;
Allow to handle data in pivot table style;
Support to VGM.

Requires an old and unsafe java version (Java JRE 1.6).

Wednesday, 8 March 2017

EDI translator enquiry

I would be glad to gather info and suggestions about EDI translator tools with the below functionalities: 

  1. Graphical mapping from CSV to EDIFACT and vice versa; 
  2. Code conversion maintenance through local tables; 
  3. Batch send/receipt with support to SMTP/FTP/SFTP services. 
Please, do not sponsor any external EDI service: I'm not interested in that and all subsequent posts will be deleted.

You can share your proposals here or also sending an email to:

Friday, 25 November 2016


One the funniest consequences of the SOLAS is that some customers started to report decimal values into segment MEA as MEA03:

Assuming that some hectograms may be relevant while stowing a container onto vessel, it's important to remember that, in all the MIG, MEA03 has the below characteristics:

The code n..18 means that this piece of data is a numerical data type with a a maximum length of 18 numbers and 0 number of decimals.

In a nutshell: reporting decimal numbers into MEA03, it should not be considered a good practice.

Edit - 28/11/2016
I have done some extra checks about this topic and it seems that decimal dots are allowed in case of data element with the following characteristics: n..18.

The below information comes from UNECE web page:

10.1 Decimal Mark
The ISO representation for decimal mark is the comma ( , ) but point on the line ( . ) is allowed. See ISO 31/0-1981. Both these characters are part of the Level A and B sets in
clause 5 and both alternatives are allowed. When the Service string advice, UNA, is used, its third character specifies the one character used in the interchange to represent decimal mark and thus overrides the above alternative use. The decimal mark shall not be counted as a character of the value when computing the maximum field length of a data element. However, allowance has to be made for the character in transmission and reception. When a decimal mark is transmitted, there shall be at least one digit before and after the decimal mark. For values represented by integers only, neither decimal mark nor decimal zeroes are used unless there is a need to indicate the degree of precision. 
Preferred  0,5 and 2 and 2,0
Allowed    0.5 and 2 and 2.0
Not allowed:  ,5 or .5 or 2, or 2.

10.2 Triad Separator
Triad separators shall not be used in interchange. 
Allowed: 2500000
Not allowed: 2,500,000 or 2.500.000 or 2 500 000