Adding CR/LF to an EDIFACT message

Everybody who handles EDIFACT messages, at least once in his life, needs to have a closer look at the message/segment contents in order to figure out the reason of a mapping failure: well, it's a dirty job but someone got to do it...

Then things may get harder when message has no CR/LF breaks and your EDIFACT translator has not a built in tool  to make message readable: find out the error becomes a real nightmare !

Well, a reader of  this blog (off course smart people read smart blog :D) has created a web application with the following features: 

1. Adding a CR/LF after every segment ends;
2. Properly numerate every line/segment of the message. 

You can have a look at this new brand project here and maybe, in the future, the developer will also add some extra features, who knows... :)

I have also added the site in the Web Utilities section.

Thank you Nick for sharing your good job !

Carriage Returns (CR) and/or Line Feeds (LF)

All the segments into our INVOIC sample are shown on separate lines. Anyway, in accordance with EDIFACT Syntax Rules, no Carriage Returns (CR) and/or Line Feeds (LF) must be used in a real data transaction.

Here is how our INVOIC sample now looks like:

UNB+UNOA:1+005435656:1+006415160:1+060515:1434+00000000000778'
UNH+00000000000117+INVOIC:D:97B:UN'BGM+380+342459+9'DTM+3:20060515:102'
RFF+ON:521052'NAD+BY+792820524::16++CUMMINS MID-RANGE ENGINE PLANT'NAD+SE+005435656::16++GENERAL WIDGET COMPANY'CUX+1:USD'LIN+1++157870:IN'IMD+F++:::WIDGET'QTY+47:1020:EA'ALI+US'
MOA+203:1202.58'PRI+INV:1.179'LIN+2++157871:IN'IMD+F++:::DIFFERENT WIDGET'
QTY+47:20:EA'ALI+JP'MOA+203:410'PRI+INV:20.5'UNS+S'MOA+39:2137.58'ALC+C+ABG'
MOA+8:525'UNT+23+00000000000117'UNZ+1+00000000000778'