Home » Categories » Solutions by Business Process » E-Business » XML

Receive and Process Orders

Datafile Software

Receive and Process Orders


Process XML Files IN


This option populates an intermediate database with data from XML order files received. As distributed, this is actually a set of processes that strips out processed orders from the intermediate database, and then adds new order details from the input XML files.

The final process in the queue checks through the new order details in the intermediate database to check for obvious errors, which are then reported in a spooled report. This report should be checked, and suitable corrections made within the system (see below), before passing orders to Datafile. If there are different standards of XML order file, then these must be deconstructed using different XML templates. This can be achieved by creating XML transactions for each standard, and adding these to the queued process.

Pass Orders to Datafile

The second option is the one that physically creates the sales orders in the SOP system from the intermediate database. It is actually a standard SOP batch update option, and that application is used to define the batch update process. An example of a batch update definition is distributed with the XML module.

Note that any order lines reported as containing some errors by the initial XML import process are not be passed to Datafile. If you want to correct errors first (see below) then you must do this before you pass the orders to Datafile. In many cases, however, it may be just as easy to add missing order lines manually to the orders that were transferred.

Re-Validate Orders Received

This option is only required should there be correctable errors in the incoming XML order files. Typical errors are orders for new delivery locations not yet defined in your system, or new product codes that have not yet been added to the XML general lookup database.

If you decide to add the missing data into the lookup database, then this option re-checks the order data in the intermediate order database, and prints a revised report.

Note

Adding or amending missing data in the general lookup file is not in itself sufficient to correct errors found in incoming orders. It is the re-validation process that does this.

Orders Day-Book Print

This merely prints all details from the intermediate orders database that have been added since the last time the day book print is run. It is entirely optional to run this process. If you decide not to use it, then your reseller will remove it from the menu, and amend the original XML process to remove order details immediately once passed to Datafile, rather than leave them until the orders day-book has been printed.
Custom Fields
  • Release ID: Standard
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Credit Control Manager / Additional Options
Viewed 2712 times since Mon, Jun 11, 2012
XML Audit Log
Viewed 1324 times since Thu, Jul 5, 2012
EAN/Locns (Incoming Messages)
Viewed 3594 times since Thu, Jul 5, 2012
EAN/Product Table Update
Viewed 1259 times since Thu, Jul 5, 2012
Markup Rules
Viewed 1272 times since Tue, Jul 10, 2012
Processing Commands
Viewed 1496 times since Mon, Jul 9, 2012
Element Names
Viewed 1282 times since Mon, Jul 9, 2012
Purchase Order Header (POH)
Viewed 3117 times since Tue, Jul 10, 2012
match
Viewed 1297 times since Mon, Jul 9, 2012
Output XML File Questions
Viewed 1438 times since Mon, Jul 9, 2012