SAP OSS Notes
2021399 SAP OSS Note - CUA: RSLDAPSYNC_USER automatically assigns central system to
SAP OSS Note 2021399 version 0005 contains details of a know issue related to CUA: RSLDAPSYNC_USER automatically assigns central system to . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.
...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.
Note 2021399 Details:
When does this problem occur
You use the report RSLDAPSYNC_USER regularly to create new users in your
ABAP systems from your directory service (LDAP server).
If the connected ABAP system is a Central User Administration (CUA)
central system, the system automatically assigns this central clie
nt to all users created by the report. As a result, the new users can
log onto the CUA central system. Normally, this is not desired,
because a CUA central system usually exists for user administration
purposes only and for this reason only administrators should be ab
le to log on.
Cause of the problem and Pre-requisites
New function as of SAP_BASIS 7.01/7.11
Solution instructions
Implement the attached correction instructions or import the relevant
Support Package.
Caution!
If using the correction instructions, note that the new text symbol is
delivered in English only. The German text can only be delivere
d by means of a Support Package.
Description of problem
Solution instructions
Please import the corrections attached to this OSS note into your SAP system using SNOTE.
You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.
You can also check if a new version of note 2021399 has been released as well as see if the note is valid for your current SAP system landscape.
Check if SAP OSS note 2021399 has already been downloaded and is valid
To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
From here you can just enter the note number 2021399 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.
If note 2021399 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.
Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)