Central User Administration(CUA) Configuration | SAP Blogs

WRITTEN BY: supportmymoto.com STAFF

Notice: I’ve lately configured Central Consumer Administration (CUA) in considered one of our buyer’s panorama, so I’m scripting this weblog publish, so viewers can get the fast overview of Central Consumer Administration configuration.

Introduction to Central Consumer Administration (CUA) in SAP

Central Consumer Administration is a characteristic in SAP that helps to streamline a number of customers account administration on completely different purchasers in a multi SAP programs surroundings. This characteristic is laudable when comparable person accounts are created and managed on a number of purchasers. Consumer administration is centrally carried out from the central system (shopper with CUA). Different purchasers which are been managed by the central system are termed little one purchasers. From the foregoing, it may be mentioned that the central system acts just like the “father or mother shopper”. The advantage of CUA lies within the risk to limit person’ entry to particular purchasers within the a number of SAP system surroundings. The system makes use of Software Hyperlink Enabling (ALE) to alternate grasp information throughout the purchasers. ALE is a know-how that permits distributed and asynchronous enterprise processing.

Why do we’d like CUA?

CUA or central use administration is definitely configured to save lots of the cash and useful resource to handle massive and comparable person exist in lots of system within the panorama. This instrument assist us to handle all of the person grasp document centrally from on shopper of the system.

  • Advanced system landscapes
  • Guide Upkeep of person data in all of the obtainable programs
  • Tedious Administrative activity
  • Advanced administrative job could result in Safety issues

Advantages of Central Consumer Administration

  • When you configure CUA customers can solely be created or deleted within the central system.
  • Consumer attributes will be maintained solely domestically, solely centrally, or each centrally and domestically
  • Due to this fact, the required roles and authorizations should exist in lively kind in all little one programs.
  • Because of this every person solely needs to be administered as soon as centrally, which supplies the administration a a lot clearer overview of all customers and authorizations.

Steps by Step Course of: Few Factors

  1. We want a SAP Panorama/single system with a number of purchasers
  2. The administrator ought to have entry to SAP and tcodes SU01, BD54, BD64, SCC4, SCUA, SCUM, SM59
  3. We do must create system customers in central system and little one programs
  4. Create RFC connections between programs
  5. Create logical system
  6. Assign logical system to corresponding purchasers
  7. Create mannequin view
  8. Add BAPI to mannequin view
  9. Generate associate profiles and distribute mannequin view
  10. Create CUA and distribution mannequin
  11. Preserve parameters between central and little one programs
See also  Switch Framework – A simple demo on creation and usage of a custom switch



First, we would wish two shopper of programs for the configuration.

For instance, I’m hereby taking a system ECC with two shopper: 800 (Central shopper); 820 (Little one System)

1.)  Create system person:

These system customers required for RFC configuration between two purchasers. These RFC are being required to switch the information right here. We do must create following within the respective purchasers with the below-defined roles:

Consumer 1:    800 Consumer, it is a central system: CUA_ECC800
Consumer 2:    820 Consumer, it is a little one system: CUA_ECC820

Notice: Each customers are created as “Service person” kind.

Above are the usernames created in shopper 800 and 820 respectively with beneath roles.
Consumer CUA_ECC800 with beneath roles (roles within the central system)

Consumer CUA_ECC820 with beneath roles (roles within the little one system)


2.) Create RFC connections between programs:

1.Go to SM59 t-code and choose ABAP connections
2.Click on “Create” button or press F8
3.Enter the RFC connection identify(ie.ECCCLNT800&ECCCLNT820) and select connection kind as 3 which implies ABAP connections
4.Enter the outline of the RFC like “RFC connection for CUA” and save
5.Now Enter the Goal Host as system identify(Laptop identify) of the ECC system or enter the IP tackle of the system and system variety of ECC(like 00)
6.All of the above settings should be carried out on “Technical Settings” tab
7.Subsequent go to “Logon & Safety” tab
8.Enter the Consumer variety of the goal shopper ECC system i.e.
9.Additionally enter the username and password which is created in ECC goal shopper  in preliminary stage
10.Language is elective and equally Unicode possibility in Unicode tab
11.You’ll be able to choose “Unicode” possibility if goal system is Unicode system or depart it
12.Now save the settings and you’ll be prompted “Connection might be used for Distant logon”
13.Click on “OK” and Click on “Connection Check” or Ctrl+F3

See also  CVS Break Policy (All You Need To Know)

RFC from 820 to 800

RFC from 800 to 820

3.) Create logical system: 

It’s essential create logical system for every shopper/ system and ensure it shouldn’t defer from RFC connections respectively

Go to BD54 t-code and setup logical programs.

 4.) Assign logical system to corresponding purchasers:

Go to t-code SCC4 and assign the logical programs to every shopper/system respectively

5.) Create mannequin view:

This steps have to be carried out within the Central system.

  1. Login to the central shopper of the system
  2. Go to transaction BD64 and click on on change button.

6.) Add BAPI to mannequin view:

Choose the mannequin view and click on “Add BAPI”.

 7.) Generate associate profiles and distribute Mannequin View:

We’re carried out with mannequin view creation and BAPI. Now we have to generate associate profiles go to Setting and click on generate associate profiles

Come again to the BD64 display, choose the mannequin view, and go to Edit ModelView –> choose Distribute. This may distribute your mannequin view to little one programs and you’re going to get message like beneath


So now, we’re carried out with mannequin view creation and distribution.


Set up:

8.) Create CUA and distribution mannequin:

Go to t-code SCUA and create distribution mannequin. Enter the mannequin view identify which is created in BD64 earlier and click on create button as proven in beneath determine.


Now you’re going to get a display like beneath and choose the kid programs within the pop up display

As soon as you chose the system identify and click on save.You’ll get a display as beneath if you’re carried out the whole lot accurately, which implies your CUA configuration is finished efficiently.


9.) Preserve parameter between central and little one programs:

As soon as we’re good with CUA configuration there are parameter setup must be carried out from central system like which all are maintained in central and little one programs

See also  Nexus 5X Rooting

Go to SCUM tcode and click on to alter mode for parameter upkeep

It provides you with broad concept about what are the parameters needs to be maintained centrally and which will be maintained little one system in addition to globally.

Ex. Position addition needs to be carried out from central system and password reset and defaults will be maintained from each centrally and native.


Run the RSADRCK2 report back to sync-up the corporate tackle.


/nscum : Confirm the customers in central person

SU01: Confirm the person is included in programs.


To alter the person password from CUA system and to little one programs.

Please use “change password” for world password reset, if we use “Logon information” password reset, it’s going to solely reset in CUA.


We will solely assign the roles in CUA to little one programs, Click on on “Textual content Comparability” to sync-up the roles data to CUA system.

Notice: We will solely assign the roles to little one system and Roles can’t be editable from CUA.

Choose the all of the CUA programs to obtain the roles data, So CUA can assign the roles to customers.


Extra data to test the distribution logs from CUA.

Execute the RSUSRLOG and supply the person identify to view the log.

To Sync-up firm identify between programs, Please Run the RSADRCK2 report.

As well as, if determined to delete the kid system from CUA, Please run the RSDELCUA and we20/bd64 cleanup is required.



That is the whole technique of configuration have been we now have learnt methods to configure CUA and handle the customers from centrally. Be at liberty to publish any feedback or queries associated to this matter.


Reference hyperlinks.



NOTE : Please do not copy - https://supportmymoto.com

Leave a Reply