Central User Administration

If you have a number of SAP systems in your organization then setting up a Center User
Administration (CUA) can reduce your amount of work whether this is worth doing is down
to how many SAP systems you have and manage! "ost SAP environments wi## consist of a
$%& 'A and Production environment and it can be very tedious (ust to mange these the
users master data is he#d in the CUA and is distributed to the chi#d systems via App#ication
)ink %nab#ing (A)%) techno#ogy!
*o setup a CUA you need to carry out the be#ow steps
+! Create communications users for the CUA and provide them with authorizations
,! $efine and assign #ogica# systems
-! Set up ./C connections between the systems
0! 1enerate a distribution mode# for the CUA
2! Synchronize company addresses and users
3! Customize authorizations for communication users for operation
4! Configure the distribution of user fie#ds (fie#d se#ection)
)ets now go through each step in each (#ogica# system) a user I$ with specia#
authorizations is re5uired for the communication between the systems of the CUA!
+! #og on to the centra# system
,! Create a user I$ CUA (see above for user creation)
-! Se#ect the system user type in the logon tab (see be#ow screenshot)
0! Change the password and save the master record
6ow we wi## setup the authorization for the user I have se#ect the be#ow authorizations a#so
set the va#id date from and to
SAP78C7CUA7S%*UP7C%6*.A)
SAP78C7CUA7C%6*.A)
SAP78C7UCA7S%*UP7C)I%6*
SAP78C7UCA7C)I%6*
6ow you need to repeat the above steps for a## the chi#d systems
6ow we move on to creating and a##ocating #ogica# systems the term system does not refer
to an app#ication server or an instance but instead to #ogica# systems these #ogica# systems
must be defined in the SAP system and are then assigned to a c#ient of a system in the
centra# system a## #ogica# systems taking part in UA must be known we wi## user transaction
code BD54 I have created two #ogica# systems which are the same I$%S server using
c#ients 999 and :99 you then need to do the same on the chi#d systems (you cou#d
transport the configuration)
6e;t we need to assign the #ogica# system to the respective system c#ients using transaction
code SCC4 repeat for the remaining c#ients
6e;t we need to setup the ./C connections between the systems which are re5uired to
e;change data via A)%! A connection must be setup from the centra# system to each of the
chi#d system and from the chi#d system to the centra# system (two way)! <e can use
transaction code SM59 repeat for the chi#d systems
=ou can make sure the connection is working by performing a connection test
6ow we can generate the distribution mode# of the CUA we use transaction code SCUA
enter a name for the CUA (#eft>hand screen) and then enter the systems that you wish to
manage (right>hand screen) you may get permission prob#ems i got a
SCC.71%*7.%)%AS%76. (ust add the re5uired permissions to the user in my case I used
SAP7A))!
?nce you save the configuration a #og is disp#ayed a## green is good
6ow when you go back to the main CUA screen you wi## notice that the CUA is now
configured here you can change the e;isting configuration you can add systems or remove
them
6e;t we wi## synchronize address and users but first we wi## check that a## the detai#s have
been comp#eted we use transaction code SA38 (#eft>hand screenshot) and
report RSADRCK2 which wi## detai# the users with any addresses (right>hand screenshot)
8efore we synchronize we need to create an entry in the tab#e P.167CUS* to a##ow user
groups which are not avai#ab#e in the centra# system to be automatica##y created when users
are copied from the chi#d system without this entry errors wou#d arise when the users are
copied you cou#d create the groups manua##y if you so wish!
6ow #ets synchronize the company addresses and users by using transaction SCUG
high#ight the system that you wish to synchronize and then se#ect eithercompany
addresses or user, a#so notice the message new system not all users were copied we wi##
come back to this #ater
*he #eft>hand screenshot shows the company address synchronization and the right>hand
screenshot shows the users synchronization (ust se#ect the appropriate button to perform
the synchronization
?nce the synchronization has comp#eted you wi## notice at the main SCU1 screen that
the new system not all users were copied has now gone
If you want you can now remove the be#ow authorizations from the cua user for security
SAP78C7CUA7S%*UP7C%6*.A)
SAP78C7CUA7C%6*.A)
SAP78C7UCA7S%*UP7C)I%6*
SAP78C7UCA7C)I%6*
=ou can customize which user fie#ds of the master user record can on#y be changed in the
centra# system we can use transaction code SCUM
Global > *he data can on#y be maintained in the centra# system these are
distributed to the chi#d systems
Local > *he data can on#y be maintained in the #oca# system these are not
distributed in the centra# system or other chi#d systems use this fie#d if you need
different settings for each system
ro!osal > *he data can be changed in both the centra# system and chi#d systems
however the fie#d va#ue is distributed on#y then the user is created in the chi#d
system for the first time! 6o redistribution to the centra# system takes p#ace if the
fie#d va#ue is changed in a chi#d system subse5uent changes in the centra# system
are a#so not transferred to the chi#d systems
Redistrib"tion > *he data can be maintained in both the centra# system and chi#d
systems use this fie#d when the fie#d is identica# in a## systems
#$er%&'ere > *he data can be maintained both in the centra# and in the chi#d
systems this option is on#y avai#ab#e for the initia# password and certain user #ocks! if
a chi#d system is changed this change is not redistributed to the centra# system and
other chi#d systems!