# TN EDI Documents

**URL:** <https://techcommunity.softwareag.com/t/tn-edi-documents/108370>\
**Category:** Forum\
**Tags:** EDI\
**Created:** [July 10, 2003, 3:33pm UTC](https://techcommunity.softwareag.com/t/tn-edi-documents/108370 "2003-07-10T15:33:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![claire](https://avatars.discourse-cdn.com/v4/letter/c/f6c823/32.png) [@claire](https://techcommunity.softwareag.com/u/claire)\
**Post date:** [July 10, 2003, 3:33pm UTC](https://techcommunity.softwareag.com/t/tn-edi-documents/108370/1 "2003-07-10T15:33:01Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:05pm UTC](https://techcommunity.softwareag.com/t/tn-edi-documents/108370/2 "2021-04-02T15:05:12Z")

</div>