SAP S/4HANA Administration · Users & Authorizations

Best practice is named superuser copies of SAP*. Why disable SAP* afterward but never delete it?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

Get it on App StoreGet it on Google Play

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Users & Authorizations

You want to enforce an idle-session timeout tonight without a restart. Can rdisp/gui_auto_logout do that, and what does it actually terminate?
You finished editing a role's authorizations in PFCG and clicked Save. A user assigned to it still gets authorization failures. What did you skip?
Why must you copy an SAP standard role into the customer namespace before customizing instead of editing it directly?
You set a login/min_password_lng in an instance profile and RZ10 warns you. Why won't password policy params work there?
In an authorization, a colleague leaves * in a field thinking it means "unset." Why is that dangerous?
A compromised user must be lockable from the child system immediately, but you also want role assignments owned centrally. Which SCUM distribution options give you each?

Start learning today

Free to start — download the app or use it in your browser.

Get it on App StoreGet it on Google Play