topic Re: authorization object per systems in Application Development and Automation Discussions

authorization object per systems

Former Member — Sun, 11 Jan 2009 09:55:55 GMT

HI,

1. There is different authorization object in different systems (like R3 BW CRM) .

2. When we get R3 system we get out of the box authorization object and roles like for admin ...

or we have to build it?

Regards

Re: authorization object per systems

Former Member — Sun, 11 Jan 2009 10:00:38 GMT

1) Some yes, some no.

2) Some yes, mostly no.

Re: authorization object per systems

Former Member — Sun, 11 Jan 2009 10:04:49 GMT

HI Julius,

Thanks,

maybe you can give a little bit detail about it or reference that can help for my questions .

Regards

Re: authorization object per systems

Former Member — Sun, 11 Jan 2009 10:16:34 GMT

The Netweaver "Basis" AS ABAP for example has it's objects, regardless of which components are installed. E.g. S_DEVELOP, S_DATASET, S_RFC, etc etc etc. See the BC* classes.

The application components also have their own objects (assigned to the packages of those components).

SAP does provide some roles as templates and profiles to get you started if you have nothing else (E.g. the SAP* roles and SAP_ALL profile), as well as portal roles for which you need to build the backend authorization for, as well as nothing other than the SU24 check proposals from which you need to building your own role from scratch depending on your business process design (choice of transaction).

In some cases, absolutely nothing is delivered except the coding. Those are the real buggers.

Cheers,

Julius