Wednesday, December 21, 2016

S_RFC_ADM.... the auth check we all love to hate

So many times since SAP decided to create the S_RFC_ADM, but also choose not to include it in the S_A.SYSTEM role, I have hated having to do usually BI data source stuff. So often I have to re-create an RFC destination, and in so many source systems I just dont have a role that contains the ability to create an RFC destination.
Ofcourse I can wait a week or two for the auth guy to make me one. But often times the users dont really sympathize with my plight when I tell them how hard it is to get access.
So my little workaround: In most systems there is an authorization to maintain archivelink. I ask for that instead. It's usually much simpler to get a default auth, than to have a custom one created.

the auth in question is S_AL_ALL. and it contains "just" the ability to maintain RFC destinations, and archivelink destinations. Perfect for my needs.