You might be faced with the task to create a really comprehensive user listing for an SAP system with several productive clients – even including 000 and 066.
This is usually a boring task, as you have to log in to every client… gather the list… proceed to the next client… and so on…
Apart from dying of boredom, you might run into the problem of not having access to all clients (e.g. 066). 😕
Write a report like this:
REPORT. TABLES: usr02. SELECT * FROM usr02 CLIENT SPECIFIED ORDER BY mandt. WRITE: / usr02-mandt, usr02-bname. ENDSELECT.
Pro: Easy, simple, fast.
Con: Has to be transported, protected… and using “CLIENT SPECIFIED” is considered “bad code” by many companies! So you might get problems during transport.
Use the report RSUVM005, which is intended for system measurement: it gives you a list of (almost!) all users on the clients you specify on the selection screen.
Still, the list is missing a few users, because SAP quite rightly considers them irrelevant for licensing — they are automatically filtered out by the report (or more specifically: by the function module SLIM_EXCLUDE_USER):
|SAP client||Excluded user|
|( all other clients )||ALEREMOTE|
To get the comprehensive user listing, we just need a cross-client selection for those excluded user names in addition.
Fortunately, you can simply achieve this via tcode SM21 and (mis-)use the “User” field to check for the existence of the missing users on other clients.
Now you can compile the cross-client user listing from within one client… 😎
Have I got it correctly: SM21 user field give the same results as RSUVM005 + excluded users?
Correct – RSUVM005 also uses CLIENT SPECIFIED… so you can remove the value from the Client selection to get a similar result.
Have you tried transaction UASE16N where you can switch on/off the cross client flag?
yep, I did… but for some time it’s not usable anymore: “Program is obsolete. Use transaction SE16 instead.”
-> SAP note 1473881