User Authorities (was Change Management)

Ray,

You mention giving the user profiles AMAPICS as their group profile. Since
XA adopts the AMAPICS authorities when it runs, you do not need to set the
group profile. With AMAPICS as the group profile, the users would have
authority to every XA file. Since you restrict command line access, the
risk is minimized but still there. Best practices would be to remove the
group profile from users.

I enjoy reading all the different ways issues like SOX is being handled.
Keep up the dialog.

Regards,
-Greg

Gregory Novak
Manager North American Technical Services
Momentum Utilities Pty Ltd
(630) 985-1736
gnovak@xxxxxxxxxx
www.jacana.com

Making Information Work for your Business
www.intuator.com



-----Original Message-----
From: Ray Bassett [mailto:rbcb55@xxxxxxxxxxx]
Sent: Thursday, July 24, 2008 12:29 PM
To: mapics-l@xxxxxxxxxxxx
Subject: Re: [MAPICS-L] MAPICS-L Digest, Vol 6, Issue 184

All...
Greg Wenzloff's answer is (in my opinion) the best solution by far. It is
the cleanest and most accurate one. Think aboout it......another thing...WHY
do developers need access to production files??? take away *ALCOBJ from ALL
production objects!! If your going to be operating in a SOX world, then your
going to be utilizing a TEST environment. Developers have access to *ALL in
test, but not in Production!!! Your users should be working with the AMAPICS
as their group profile, with no command line action....after all this, you
s/b able to see the light at the end of the tunnel.....!?!?!? :-)

Ray Bassett
BTR Consultants Inc.
Technology Solution Providers
401.573.2226
BTRCINC@xxxxxxxxxxx