[415] in SAPr3-news

home help back first fref pref prev next nref lref last post

Re: Authority objects and transactions

daemon@ATHENA.MIT.EDU (Scott Barden)
Tue Jul 25 18:07:46 1995

To: sapr3-news@MIT.EDU
Date: 25 Jul 1995 21:39:46 GMT
From: Scott Barden <100632.1334@CompuServe.COM>

I think we are sometimes too hard on SAP.  I mean how can we 
expect SAP to deliver the R/3 system with the security system 
already set up, they have no idea on your companies structure, 
decentralised or centralised management, cost centre hierarchies 
etc.  All they can do is to provide guides like the 
pre-configured profiles.

I will admit that they could provide clearer pointers to the 
authorisation objects that each transaction uses.

As for the trace being time consuming (which is true) I still 
believe that this would be quicker than running SU53, when done 
with a user with full security.  Why?  Because one trace will 
pick up all the auth. objects tested to complete some transaction 
whereas (if I interpret correctly) SU53 should only give you the 
one auth. object which failed the authorisation check, fine if 
there's only one object in the transaction (yeah right!).

Regards, Scott Barden.

home help back first fref pref prev next nref lref last post