# Receive EDIs via FTP

**URL:** <https://techcommunity.softwareag.com/t/receive-edis-via-ftp/108131>\
**Category:** Forum\
**Tags:** EDI\
**Created:** [March 17, 2004, 1:18pm UTC](https://techcommunity.softwareag.com/t/receive-edis-via-ftp/108131 "2004-03-17T13:18:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![schung888](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@schung888](https://techcommunity.softwareag.com/u/schung888)\
**Post date:** [March 17, 2004, 1:18pm UTC](https://techcommunity.softwareag.com/t/receive-edis-via-ftp/108131/1 "2004-03-17T13:18:27Z")

</div>

Peers

Have a quick question on receiving EDIs file via FTP.

We will have our trading partner to ftp EDI files to our AIX Box.  
To process those EDI files, we will poll (either via File Polling Port  
or a scheduled service) those EDIs file

The question is, what is the pros and cons of

1. submit the polled EDI file to wm.tn.receive (thus will be recognized  
and processed by TN and calling our service based on processing  
rules)

2. directly submit the EDI file to our serivce (which will  
process the envelope, retrieve the transaction set, etc)

I can see the advantage of submitting to wm.tn.receive  
as transactions will be logged in TN (participated in  
conversation as well). But other than this, any other pros and cons (esp regarding Functional Acknowledgement processing

---

<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/receive-edis-via-ftp/108131/2 "2021-04-02T15:05:04Z")

</div>