cancel
Showing results for 
Search instead for 
Did you mean: 

managed System Setup - Update roles -CUA

former_member204080
Active Contributor
0 Kudos

Hi All,

Hi Team,

We keep hitting the following error message in our solman production system when doing managed

system configuration to update roles from to any other managed systems from solman_setup


We have  implemented  OSS note 2056893 - SAP

Roles Not Copied to the Customer Namespace and Not Assigned To Users .

but we still have the issue.

We have CUA implimented in our solman system

Has any seen this issue and is there any separate procedure on how to update roles from solman to CUA managed systems

Regards,

Murali

Accepted Solutions (0)

Answers (1)

Answers (1)

divyanshu_srivastava3
Active Contributor
0 Kudos

Why don't you remove CUA from affected managed system while performing this step and latch again once this step is done ?

What is your system SP level ?

If note "2056893 - SAP Roles Not Copied to the Customer Namespace and Not Assigned To Users" is not helping, raise this with SAP.

Anyways, can you share complete logs on the error that you are getting and the places where are halted ?

Regards,

former_member204080
Active Contributor
0 Kudos

Hi Srivatsava,

Thanks for your reply

Yes we can try that but we would like to see if there is any different approach/option for performing role updates to CUA managed systems.The  security roles are getting updated very frequently by SAP and so there will be need to do frequent updates in managed system as well.

So there will be multiple times when we need to disconnect and connect back to CUA

1830640 - Authorizations for SAP Solution Manager RFC users as of SP09

We have few production systems which are not part of CUA there we are able to successfully update the roles from solution manager

We are facing issue in third step of managed system configuration ->Maintain RFC

When we select the option update roles and execute it gives this error

No additional error comes

Regards,

Murali

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Murlali,

Thanks for the update.

I would suggest you to check this with SAP as this incident was corrected with the above note.

Might be something is missed or still needs some correction.

BTW, have you applied the central correction and latest version of this SAP note ?

Regards,