System Maintenance - EDI Order Processing

A number of options are offered here:

¨Global trading partner table update. This process runs through your sales ledger accounts file looking for those that contain an EAN or other location reference, and then either updates or creates new entries in the table. It does in fact recreate the EAN location codes in the global lookup file, although it leaves intact your own location codes (see below).

You are asked to name a printer at the start of this run, but no report is in fact printed. An initial screen allows you the option to <Enter> to continue or <Escape> without further processing.

¨Maintain trading partner table. This allows you manually to maintain entries in the trading partner table – you can create a new entry, for example, without having to update the lot from the sales ledger.

¨Global bar-code table update. This process runs through your stock or product file looking for those entries that contain an EAN or other product code reference, and then either updates or creates new entries in the table.

You are asked to name a printer at the start of this run, but no report is in fact printed. An initial screen allows you the option to <Enter> to continue or <Escape> without further processing.

¨Maintain bar-code table. This allows you manually to maintain entries in the bar-code table. If you want a warning printed if a product is ordered, enter Y<Enter> to the question To warn if product is ordered mark "Y" here.

¨Maintain ANA standard code value list. Use this to maintain the Tradacoms ANA code tables, including any action codes determined for your system.

¨Purge orders from EDI archive file. This allows you to drop off very old archive records – for example, those more than a year old. Give the date prior to which all orders should be dropped. We recommend that you keep orders on file for at least three months after they have been fully fulfilled.

¨Print an EDI file. This is a useful diagnostic tool that prints an EDI message file a segment per line, duplicating the print that the deconstruction process creates — see Appendix A1 for an example of this report. Enter the full pathname for the file in question. Note that new orders are generally put into the !INTRAY folder, and that EDI message files successfully deconstructed are copied into the !PROCSSD folder.

¨System constants maintenance. The main parameters needed by the system include the name of the input message file folder, and whether or not to print the EDI message itself during the deconstruction process.

Directory for input EDI files !INTRAY\*.*

Enter the pathname for the folder into which you will put all EDI files ready for the deconstruction process.

Print EDI files unravelled? Y

Reply Y <Enter> here if you want the full segment-per-line print of EDI message files deconstructed, or N to omit this. Any errors discovered are still printed if you reply N here.

If you elect notto print the message structure, it still produces a report of any errors encountered.

Print DNA segments in orders? (1/0 for Y/N)

Enter a value of "1” here if you want to print on the order documents the details from the DNA segment. Leave it at "0” to omit printing this.

Print DNB segments in orders? (1/0 for Y/N)

Enter a value of "1” here if you want to print on the order documents the details from the DNB segment. Leave it at "0” to omit printing this.