|
Not a bad idea; we use triggers for the item master, bill of material and routings and I have to say we've not had performance problems. IBM web site was great. The only "problem" we've had with triggers is that to do backups and re-orgs you have to remove the triggers and add them back. Not a big deal; we just created a CL program to run before and after backup/reorg. -----Original Message----- From: Bielskus, Mindaugas [mailto:Mindaugas@xxxxxxxxx] Sent: Friday, September 12, 2003 9:42 AM To: SSA's BPCS ERP System Subject: RE: Order changes Terri, I have not done this for a BPCS system, but have done something similiar for JDEdwards. Everytime there is a change, add or delete to an order, the program triggers an email to persons affected by this change. So instead of a batch process, it is interactive. Triggers were not used, however it would have been the easy thing to do. At the time, I was afraid of the performance hit on the 400. If the performance problem would have been serious, there would not have been an easy way to adopt a different strategy. If I had to do another program like this, I would try to gauge the performance impact with a throw away program. For a sample trigger program, search the IBM web site, they don't seem very complicated. Mindaugas Bielskus -----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. DISCLAIMER: This e-mail transmission is strictly confidential. If you are not the intended recipient, you must not copy, distribute or take any action in reliance on it. If you have received this e-mail in error, please notify us as soon as possible and delete it. E-mail transmission cannot be guaranteed free from viruses, secure or error free. No liability is accepted by the sender for any loss or damage which may be caused as a result of the transmission of this e-mail. If verification is required, please ask for a hard copy version. _______________________________________________ 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.