|
Hi, >To play this game we hardwired a new file with the information we needed to one of the >ord7xx green screen program. Every add created a new record; changes were captured and >the whole issue of shuffling the line was to write out a negative of the before image >and a positive of the after image (reverse for credits that would impact sales) and let >a batch program net them out. Our ORD7XX programs are only slightly modified, and I would rather leave it alone, But the your approach gives me something to think about. Thanks! <===================================================> Terri Harteau **************** "There's no point in being grown up if you can't be childish sometimes." - Dr. Who **************** "Steve Segerstrom" To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx> <SSegerstrom@inte cc: rmatic.com> Subject: RE: Order changes Sent by: bpcs-l-bounces@mi drange.com 09/12/2003 09:18 AM Please respond to "SSA's BPCS ERP System" We have had a similar requirement. Version 6.0.04 heavily modified. We track incoming orders and what we do is reduce orders if an order was deleted; add the orders taken for the day, net with certain credit types. To play this game we hardwired a new file with the information we needed to one of the ord7xx green screen program. Every add created a new record; changes were captured and the whole issue of shuffling the line was to write out a negative of the before image and a positive of the after image (reverse for credits that would impact sales) and let a batch program net them out. I can give you more info offline if you are interested. Steve Intermatic Inc (815) 675-7469 -----Original Message----- From: THarteau@xxxxxxxxxxxxxxxxxx [mailto:THarteau@xxxxxxxxxxxxxxxxxx] Sent: Friday, September 12, 2003 7:53 AM To: SSA's BPCS ERP System Subject: Order changes Hi, I am on V6.02. We have a program that prints any new orders taken out the previous day and also any changes made to existing orders. It is a batch program that compares entry date and last maintained date to a record in a work file. If it is different, there has been a change (in item number, quantity, price, salesperson or customer). The programs were written when we first got BPCS many, many years ago. It was maintained to keep working, but has some serious holes. I need to rewrite it without the holes. Some of the problems are: the work file is keyed by order #, line # (the item number can and does change), but we have had users resequence the order, We have had lines deleted, and L01 was used, so it was never reduced, and several unexplained things where it just did not update correctly. Does anyone have any ideas on how to track the changes? I'm not looking for any product to purchase, it is home grown and needs to stay that way. I am just starting to look at different ways to do it, and thought I would see if anyone else is already doing something similar. <===================================================> Terri Harteau **************** "There's no point in being grown up if you can't be childish sometimes." - Dr. Who **************** _______________________________________________ This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/bpcs-l or email: BPCS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. _______________________________________________ This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/bpcs-l or email: BPCS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l.
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.