TN: EANCOM 96A DESADV validations

, ,
1

Hello,

I�m receiving EDI messages via TN, more specific EANCOM 96A DESADV messages.
I installed the EDI document type and now have a dictionary and a flat file in the wMEDIforTN package. I also created a document type from the flat file.
The convention/agreement between supplier and customer in our case are far more rigid than the EANCOM standard. How should I implement these new specifications (for example length, dependencies and format)?

  • Should I adapt the dictionary?
  • Should I adapt the Flat file?
  • Should I adapt the document type that I created from the flat file?
  • Should I implement all validation after TN, in the Integration Server?

Thanks a lot for your comments!

Claire