|
>From Al Macintyre 405 CD on AS/436 V4R3 BPCS V4 security has some holes. We are a multi-faciilty company in which some users are authorized to do a wide range of transactions at the facility at which they are based, and are authorized to LOOK at data in other facilities but not update anything there. We have not figured out how to enforce that, but we can query on the user-id within inventory history ... running a total only number of transactions by user by facility each month, to catch any no-nos, after the fact. Al ... We have a very similar setup ... 4.0.5 (nonCD), with 9 manufacturing facilities across the country, all operating out of the same environment. We use a warehouse name the same as the facility name for our "primary" warehouse at each facility. As we can set security at the warehouse level, and because most "stuff" happens at the warehouse level, we think we are secure against users at one facility changing data at another facility. Your comments about the V4 security makes me wonder ... where do you see the holes? +--- | 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.