There are three main pieces of the EDI process: getting your data in, mapping that data from the format it is in to the format you need, and sending the data out. EDI/HQ™ provides tools for data communications as well as mapping.
It is an important part of the development process to plan what communications method(s) you will use, e.g., secure FTP or AS2 or a value-added network (VAN). And where on your storage devices the data files first need to land, then be processed, then be sent to an input folder for the next process. EDI/HQ has functions for STP and Secure STP, file definitions for inputting and outputting files, and processes for, say, moving files or calling an external program if needed.
Equally important is to capture documentation of those processes for use later. It can save time by being able to glance at a data flow document instead of having to “reverse engineer” a process and look at all the pieces that make up that process.
Remember that when you view the transaction log in the EDI/HQ data viewer and it shows a time-stamp for “transaction sent”, it means that the data was written to a file. You still have to check the process(es) that actually communicate that file to its destination. This is where you documentation will pay off with troubleshooting time savings!
1 EDI Source consultants are experienced with just about any communication method you will encounter and can assist you with planning your data flows but also with documenting data flows.