Home » Categories » Solutions by Business Process » Profiler |
Process Received Messages - EDI Order Processing |
Article Number: 1730 | Rating: Unrated | Last Updated: Tue, Jun 20, 2023 at 5:12 PM
|
Datafile Software Process Received Messages - EDI Order Processing This is an automatic 12-step process that deconstructs messages received and creates records in the EDI message file. It creates the three reports described above, which should be scrutinised after the run for any issues raised. You are first asked to say to which printer any output reports should be printed. We recommend that you use the print spooler for this, and determine later whether or not physically to print the reports. Next, a screen message tells you what is about to happen. To proceed, key <Enter>. To abandon the process without processing the EDI messages, key <Escape>. This process first archives any orders that have either been passed to Datafile or that were marked for manual entry to Datafile – whether marked by the validation process or directly by you. It does not process any order records where the EDI message contained any errors of any sort, on the basis that you will correct the errors and re-validate them later. After archiving any processed orders it then deconstructs any EDI messages it finds in the !INTRAY (and that have the correct filenames as defined in the systems constants file — see System Maintenance); prints a summary of the files processed, or a full print of each message (again determined by a systems constants parameter); validates the order records deconstructed; and finally prints all the orders that appear to be OK. Unless the parameters determine that an order can be passed directly to the Datafile Software order processing application, the printed order is clearly marked MANUAL ENTRY. Such orders must be processed by hand. If you chose to spool the printed reports, remember now to look at them and determine if there is any corrective action required, either because EDI files have failed to deconstruct in full, or because there are errors in some messages, or because some orders are marked for manual processing. |
Attachments
There are no attachments for this article.
|
User-Defined Reports - *RECCOUNT Test Condition on $Record Control Block
Viewed 2326 times since Mon, Jun 11, 2012
Profiler - Application Landing Pages
Viewed 721 times since Thu, Jun 18, 2020
System Maintenance - EDI Order Processing
Viewed 1434 times since Thu, Jul 5, 2012
Screen Options - Increment Code within ‘Location’
Viewed 1468 times since Fri, Oct 26, 2012
A1 Background Note on EDI
Viewed 1391 times since Thu, Jul 5, 2012
Print Database Definition
Viewed 1594 times since Fri, Jun 29, 2012
User-Defined Report - Update Report Date to Constants
Viewed 1347 times since Mon, Nov 25, 2013
Chained ProFiler UDR Reports (9905)
Viewed 1417 times since Fri, Jun 29, 2012
R – Rebuild Indexes
Viewed 736 times since Fri, Jun 29, 2012
E – EDI Definitions
Viewed 763 times since Thu, Jun 28, 2012
|