Processing Principles

Validation/Update

The EDI module contains programs (both asynchronous and batch) that perform all necessary validation on all inbound EDI transactions.  If the transaction is valid, these programs will also update the necessary files and print a control report detailing the update.  If the transaction is not valid, these programs will print a control report detailing the problems with each transaction.

Exception Handling

Inbound transactions that have an exception condition are maintainable in an online conversation.  Each inbound transaction has its own online exceptions program.  In these programs, you can fix data errors found on the transaction or delete the transaction so that it may be resent by your trading partner.

Deleting Transactions

If you wish to delete an individual transaction, you may do so within its online exception program.  Use the F14 function key to delete the individual transaction.

Batch vs Asynchronous Processing

Inbound EDI transactions can be processed in either of two ways:

Batch                Release the batch job from the EDI menu inbound request option.  Each inbound transaction has an inbound request option.

Asynchronous   Bring up the EDI asynchronous monitor to process all the transactions.

Using either processing method, both the valid transactions report and the error report are created.

Valid Transaction Reports

Once the inbound transactions are processed, a valid transaction report is created.  This report details all the valid transactions processed.

Error Reports

Once the inbound transactions are processed, an error report is created.  A control report is printed detailing all the transactions in error that have been processed.  It categorizes the transactions into three categories¾how many transactions were transmitted, accepted, and rejected.  It shows transaction details as well as error messages.  This report can be used when handling exceptions to identify changes necessary to make the transactions valid.

Release Codes

Release codes govern when each outbound transaction will be processed.  Each transaction has three different release code options:
(I) Immediate Release
(N) Normal End-of-Day
(H) Hold Indefinitely

Document Format Codes

Document format codes govern the type of document to be processed.  Document format codes are defined on Reference File category G61.  They are associated with each outbound EDI transaction.  Possible document format codes are:
(P) Paper copy only
(E) EDI transmission only
(B) Both paper copy and EDI transmission
(N) Neither  (valid for BOL documents only)

Reprinting and Regeneration

In order to reprint or regenerate a document, you must request a reprint for the individual transaction.  The document format code dictates the reprinting/regenerating process.  If the document format code is P (paper copy only) or B (both paper copy and electronic transmission), the document is reprinted.  If the transactions document format code is E (electronic transmission only) or B (both paper copy and electronic transmission, the EDI transaction files are regenerated.

Generation Control Reports

Once the outbound EDI transactions are processed, either through a batch or asynchronous process, a control report is printed detailing how many transactions were transmitted.  Use these reports to verify/monitor your EDI transactions.

Translation Update Programs

These programs update the individual transaction file records, marking them the Translation Status field with a "P" (processed).  They are to be used once the transactions have been successfully translated using a third party translation software package.  If these programs are run before the transactions have been translated, the record(s) will not be transmitted to your trading partner.

Purging

Once the translation update programs have been run (updating the translation status flag on the transaction files to "P"), that transaction file can be purged.  The purge program will only purge records that have a translation date prior to the horizon date and have a "P" in the Translation Status field.