EDI Processing Overview

 

The EDI processing processes are run automatically from the Jobber Process (“Jobber”) on a periodic basis to process inbound and outbound transactions.  The Jobber is a StreamV VDF application that runs on a PC or Terminal Server Session to run repetitive un-supervised tasks.

The processing of transactions is a four-step process, these steps are

1.  If you are using the CovalentWorks B2B EDI Exchange to transport your EDI transactions they gather, or receive, inbound ANSI X12, or AS2 EDI transactions from your trading partners.  They translate them to XML and map them to Cove’s standard XML format.  The Jobber connects to the CovalentWorks FTP site periodically and downloads the contents of the “Inbox “ to an EDI inbound directory on your system, and deletes the files at CovalentWorks (who maintains an archive).  If you are not using CovalentWorks then you are responsible to get properly formatted XML files into the inbound directory. 

2.  The system scans the inbound EDI directories for new inbound transactions (xml files) to process. Each transaction is in a separate XML file. Each file must have the extension .XML  As it finds each XML file it opens it and checks what type of transaction it is.  The transaction is then processed by the appropriate EDI transaction object.

3.  Then the Jobber asks each of the EDI transaction object to check if there are any outbound transactions to create.  If there are, the EDI transaction objects create the outbound transactions in the outbound transaction folders, which are in the format: …\EDICVOUT\TradingPartnerName_XXX (where XXX is the transaction number).

4.  Then the Jobber uploads the contents of the outbound transaction folders to the same named folders at CovalentWorks and moves XML files sent to the appropriate archive directories.  CovalentWorks then converts the files from XML to ANSI X12 format specific to your trading partners and delivers them to your trading partners.

As inbound and outbound transactions are processed the system writes a history of the transactions, their status and any errors to a file (Longcode).  This information is displayed, and errors corrected, using the EDI Dashboard.  When the Jobber detects and EDI error it will send an email to the EDI Administrator.

 

 

More:

EDI Startup Checklist