ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Suggestions for Updates >> EDI Import Suggestions
http://www.istechforum.com/YaBB.pl?num=1068744718

Message started by kevind on 11/13/03 at 09:31:58

Title: EDI Import Suggestions
Post by kevind on 11/13/03 at 09:31:58

Now that we are importing our Web Orders using the EDI Import function, here are a few suggestions that would smooth out the process:

1. Have an option to delete DBASO.IN when the Import is complete. Allow this new option to be saved with a "Save Settings" button.

2. Allow import to the "Ship Via" field.

3. In addition to importing the Terms Text, look this text up in the terms table and plug in the Terms number. If the imported Terms to not match one from the Terms table, then do what it does now. Alternately, If the Terms Text is a number, then plug this number into the 'Terms Cd' field.

4. In 'Convert EDI to Sales orders', Add the "Save Settings" button. We almost always set the "Keep EDI Order on File" to 'N'. It's current programmed default is 'Y'.

5. When Converting an EDI order to a Sales Order, Report the Sales Order Number created in an information dialog box if only 1 order is converted. Currently, to record the Sales order number, you have to go into SO-A after you have reviewed and converted EDI orders.

Title: Re: EDI Import Suggestions
Post by Lynn_Pantic on 11/13/03 at 12:15:43

All good ideas, in fact the Save Settings button for ED-D Convert to Sales Orders is already done, will be in the next update.

Kevin, do you only take web orders from existing customers? If not, how do you handle new customers. We have an add-on for web catalog/field salesperson order import that is based on the EDI structure but one open issue is how to address orders coming in from new customers.

Title: Re: EDI Import Suggestions
Post by aricon on 11/13/03 at 12:29:15

Wouldn't the best way to handle new customers would be to not make them new at all?

Meaning that you make it a 2 stage process. Stage 1 is registration within the web-store which would generate an import file of their customer information. This could be reviewed, and if approved, imported. If not approved, then no import and they couldn't place orders.

That way you don't change your existing order import functionality/structure.

Just an idea....

Title: Re: EDI Import Suggestions
Post by kevind on 11/13/03 at 13:55:21

Lynn,
The Items that we have for sale online are consumer oriented. We do not currently take orders from our regular customers. Try searching for "86rac" or "brk" on google. Note the sponsored links.

The way we have delt with it is to create a catch all customer called "WEBORDER".

Right now, our web orders are sent to us using FormMail. We have a software package here called "EPS" from Harvey Software ( www.harveysoftware.com ). EPS processes Mail messages and generates a reply email to the customer and prints a sales order here on the same printer that our faxes print on.

In addition, EPS automaticly Exports the order data to a comma seperated file that we process with a JavaScript to create the DBASO.IN file.

From this point, we use the DBA EDI software. The JavaScript is kind of a bridge between the Comma Seperated file and the DBASO.IN file.

Ideally, we want to set up a Miva Merchant Store ( www.miva.com ). This software was recommended to me by a local company that does Web Design and Commercial Graphics ( www.slidearts.com ). I'm just not ready to take the time right now.