|
Al, This may not help since you mention that people are checking ORD300 to see if the order is already entered, BUT, you may want to add some code into ORD500. We did it this way: Call a program at order -entry- that checks to see if the PO entered already exists for this customer (we require a PO on every order). If it does already exist, shoot the user over to the appropriate ORD300 screen. This allows them the opportunity to see if they are entering a duplicate. We occasionally have encountered duplicated ECH records. It's been rare, so I am letting it ride, I just delete one of them. Bill MacWheel99@aol.com wrote: > > What causes duplicates? > > This has come up several times in BPCS_L discussion of MRP performance > challenges. > > We recently had apparent duplicates for one customer order on ORD300 --- the > ORD500 review was fine, but when we inquired into it, each requirement line > was duplicated except the second appearance was blank for location --- after +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.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.