process a large number of sales orders each day?
receive orders from multiple sources like customer emails, files, EDI, your website, Salesforce.com?
have orders with lots of line items?
If so, your customer service staff likely spends a great deal of their day processing orders and getting them into QAD. You’ll want to watch this webinar where we’re joined by David McCloskey from Kauffman Engineering.
Find out how you can manage sales order entry and upload to QAD without implementing costly transformation interfaces. We will show you just how fast, easy and smooth your order entry process can be and David will share how Kauffman Engineering reduced their processing time and increased their productivity.
We do have a version of the Multi SO Data Loader which allows the user to create a new Ship-to that is not already existing in QAD.
We are looking into ways to convert FAX orders to QAD.
There are a couple of options: 1) Check with your customer to see if they can email you orders in one of these formats rather than faxing them to you: Text, XML, CSV or MS Excel. For your customer, it would likely take the same effort as faxing the orders, but for you it would take significantly less time to import into QAD. 2) If #1 is not an option, you can use OCR software to convert fax images to CSV format files which you can then process with the Data Loader.
This looks like it is only for discrete orders. What about scheduled orders and schedule line item updates and additions?
We have a separate Data Loader to handle Schedule orders. You can find out more about it here.
Is the process configurable if our validation rules are different than standard QAD?
Yes, we use standard QAD validation rules in our generic version, but will always work with each client to add or modify to match their validation logic and conditions.
What is the underlying mechanism used to communicate with QAD both for validation and the actual load (CIM, QXtend, etc)?
For validation, we use some standard QAD validation programs and include files, and we also code some additional validations ourselves. We load the data using redirection (like a CIM, not like QXtend), we write the input file for the screen and call the QAD program for the screen. We then read the screen output to see if any errors occurred during the upload. If there are any errors, the load terminates and no data gets uploaded. The user is notified of the error(s) with a description of the problem so they can fix it and upload the data again. You can find out more about how Data Loaders work here.
Does this Data Loader integrate with EDI?
The Loader does not integrate with EDI per se, but it has ‘Open File’ functionality. As EDI files are text files, we can parse them provided we have the specification, and import the data into the Data Loader, where it can be reviewed before uploading to QAD.
Join our mailing list to stay informed about our webinars
