|
Greg, IF you do not have any modified or custom programs, removing AMAPICS group from your users profiles should not cause any problems. Your MAPICS programs and files should be correct as they were installed via MAPICS procedures (but you should check this out). A few of the MAPICS programs are owned by QSECOFR, but 99% should be owned by AMAPICS. In fact I just displayed all the program objects to a file and all but 2 are owned by AMAPICS. The MAPICS command in QGPL should have *use for public. That is how users get into MAPICS with no authority, then the cross applcation security you grant inside MAPICS takes over. If you do have a lot of custom, trigger, or modified MAPICS programs, you can create user modified option(s) (1 for ownership, 1 to use *owner authority) and with a subsetted list in wrkobjpdm change ownership, etc. in mass. If you need to change many programs and/or files, be sure to test your user modified option on one or two before applying to all. After you get the authority in place, you can remove the AMAPICS group profile from the user profiles. (a program can be written to do this, too, if you have many users). And of course you should do one or two manually first and let those users test before removing all... 14 years of loose security could have some gotchas. Do you have a test environment? -----Original Message----- From: mapics-l-bounces@xxxxxxxxxxxx Behalf Of Greg Wenzloff Sent: Thursday, December 30, 2004 8:03 AM To: 'MAPICS ERP System Discussion' Subject: RE: MAPICS - need info on the AMAPICS user profile Thanks Ann, Michael, and Ted for your suggestions on how to correct our problem. Dave and Kevin: You put a lot of energy into your replies but no suggestions on what to do about it. Once MAPICS is tightened down, what is a good technique that allows Query to be used against MAPICS file? Any other methods for securing MAPICS? Greg
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.