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: 

NAD+FW+IT03450730100:160:ZZZ'

OR

NAD+FW+03450730100:160:ZZZ'

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!

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: 

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:

FTX+AAA+++FAK OR CARGO  NOS WITH REFERENCE 998740013'

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

FTX+AAA+++'

                                    

Hope these tricks will be useful to you!