SAP AS ABAP Administration · Security Audit Log & Central User Administration

You just activated a new SM19 audit profile because a critical incident is unfolding right now, but nothing new is being logged. What did you overlook and how do you make it take effect immediately?

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

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 Security Audit Log & Central User Administration

You are defining the CUA distribution model and list only the child systems as receivers. Why does CUA still not manage users in the central client itself?

In a CUA landscape you maintain a user centrally in SU01. Why is the user's data identical everywhere, yet their roles can differ per child system?

Where should you host the CUA central function, and why is putting it in an existing production client a poor choice?

Your landscape has SAP systems plus a central directory service, and some child systems run older Basis releases. How does the LDAP connector help, and what is its reach compared with plain CUA?

You carefully defined the SM19 filter criteria for a critical user, saved the profile, and activated it — but SM20 still shows nothing for that user. What is the easy-to-miss filter step?

The Security Audit Log has been running for months and no one has touched the log files. Beyond disk space, what operational responsibility is being neglected?

Start learning today

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