|
I agree, let the web interface stand alone, and run it thru as and EDI order and let the EDI system edit and post. That is the way we have implement most web order entry interfaces. cjg -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Stone, Brad V (TC) Sent: Tuesday, February 29, 2000 11:13 AM To: 'MIDRANGE-L@midrange.com' Subject: RE: as400 to WEB order entry From my experience a seperate program would work the best. The screen scrapers tend to hog a lot more cPU than necessary. A simply CGI program to collect the data and do verification can be much more streamlined. The CPU used by screen scrapers adds up exponentially for every user you have using the app. We have an internal EDI system that we use for this. the Web program collects the data and puts it into our internal EDI system. Then from there it's billed. So, we only really have one billing program that reads these EDI files and bills the order, putting the bulk of the processing into one application, making Oe programs simple data collection programs. check out http://www.bvstools.com/erpg.html for a cool book on the subject. ;) Brad > -----Original Message----- > From: JGracetri@aol.com [mailto:JGracetri@aol.com] > Sent: Tuesday, February 29, 2000 8:12 AM > To: MIDRANGE-L@midrange.com > Subject: Re: as400 to WEB order entry > > > We are going to put order entry on the web. We have used a > product to make > our green screens GUI. To do this we use our orginal screen > as the source for > the GUI screen. So when a screen changes we have to go thru > the re-gen > process again. > > Our web users will be our sales force and a few selected customers. > > In house order entry takes many steps and is not real simple. > > The debate is now raging with 6 weeks to go. > > One side says hammer down(as is), the other wants to > streamline order entry > with a seperate program. With just Cust# Item# QTY on the screen. > > I can go either way. > > I would be interested in someone else's experience or if you > know a case > study i can look at. > > thank you jeff g > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.