Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

CUA User distribution/ transfer Problem

Former Member
0 Kudos

Hi,

We have configured CUA and also configured LDAP on the same server. Now the problem is I have already synced AD user to CUA central system. I could transfer the child system users to central CUA system with SCUG transaction. But after finishing total configuration now I want to transfer/ distribute all central CUA users to child systems. How could I transfer all the users at a time? is there any report to transfer/distribute all users once? or I have to transfer individual users from su01 assigning the child logical name in the system entry of SU01 tabs?

Any suggestions please?

Thanks,

Ajay.

1 ACCEPTED SOLUTION

Bernhard_SAP
Employee
Employee
0 Kudos

....so you mean, you want to have all users exisitng in all child systems?

With SCUG you have already created the correct assignements to child systems.....

Nevertheeless there is a report rsccusnd (note #574094).

b.rgds, Bernhard

16 REPLIES 16

Bernhard_SAP
Employee
Employee
0 Kudos

....so you mean, you want to have all users exisitng in all child systems?

With SCUG you have already created the correct assignements to child systems.....

Nevertheeless there is a report rsccusnd (note #574094).

b.rgds, Bernhard

0 Kudos

Hi Bernhard,

I have tried with that report RSCCUSND in SE38 but unable to distribute the users. When I have checked the logs in SCUL I am getting receiving system as the same central system name and all users are in green. When I didnt mention any user range I can see only users exist in the child system under SCUL after I run the report.

I want to let you know one more thing that during the CUA configuration after creating RFCs, users and roles when I start SCUA transaction, to add child under receiving systems when I press F4 it is showing only the central system Logical name not child systems. When I manually enter child logical name it has given error like "entry does not exist in TBDLS table". So to get this resolved I have manually defined logical system name of child client in BD54 under central system also. Then I have added under receiving systems.

When I add individual users in CUA able to get in child but not all users with report RSCCUSND. Please suggest.

Thanks,

Ajay.

0 Kudos

Looks like CUA has not been created properly. Can you still see a "Create" button in su01 of child systems? Please make sure that you read the troubleshooting part of CUA pdf. After successful addition of client you need to save the CUA model to distribute to the child systems.

After that, import /distrubute company codes and users in transaction SCUG. Now you can see all the user's in CUA Master with respective child systems in systems tab. Perform text comparison as well in roles tab.

Coming to Synchorinization distrubution, if the user detail gets updated in CUA , idocs will be automatically triggered and distributed to respective child systems. No actions need to be done specifically.

Regards,

Gowrinadh

0 Kudos

Hi Gowrinath,

I think CUA is fine or I dont know but the "create" option is disabled in the child systems. I have searched the troubleshooting PDF but couldn't find solution in that. I have synchronized both company addresses and users in SCUG from child to central.

But for individual users CUA working fine and able to get that users in child but not all users at the same time. Please suggest.

Thanks,

Ajay.

0 Kudos

Hello,

so now I understand, that there exist users, which have only an assignement to the central system itself (SU01->tab 'Systems') and you want these users to exist also in your child system.... Correct?

If so, use SU10 to add the child system to that users (for instance select that users by target system attribute) by adding the chidl systems name on the 'Systems'-tab of SU10. Then save. Users will be created in the child system then. You need to check the log of SU10 and SCUL after that mass distribution, as idocs might get stuck in the child system because of limited ressources in the child....). Propably transfer only small packages of users at the same time, for instance 50 users per run....

b.rgds, Bernhard

0 Kudos

Hi Bernhard,

Thanks a lot for your solution. Exactly the same I was asking about.

I have tested the same with 10 users of central system and able to get successfully in child now with SU10. But whats wrong with that report when I run?. Is there any fault in my configuration? As I told above during addition of receiving systems in SCUA why didnt I get child logical system when I press F4? I am still not getting the receiving systems when I press F4 where ever applicable only getting central system. (It should come automatically when I create RFC in central system correct? means internally it should register in TBDLS table right?)

One more Question as of CUA guide when I assign limited roles to communication users as

On Central - SAP_BC_USR_CUA_SETUP_CENTRAL

SAP_BC_USR_CUA_CENTRAL

On child - SAP_BC_USR_CUA_SETUP_CLIENT

SAP_BC_USR_CUA_CLIENT

I am not able to get users in child with the above roles in child system. When I assign SAP_ALL profile to the comm. user in the child then when I create user in central getting in child but not with mentioned roles. why?

Please explain.

Thanks,

Ajay.

0 Kudos

Hello,

rsccusnd distributes of course only to that systems, to which the user is assigned already. So if a user does not have the assignement to child system X, nothing is distributed for this user to system X.....

>As I told above during addition of receiving systems in SCUA why didnt I get child logical system when I press F4? I am still not getting the receiving systems when I press F4 where ever applicable only getting central system. (It should come automatically when I create RFC in central system correct? means internally it should register in TBDLS table right?)

Regarding this you need to knwo, that CUA is based on ALE. Therefore you need to configer that layer correctly. Teh easiest way not to forget a step is to follow exactly the cookbook 'Central User Administration (AS ABAP) at:

service.sap.com/security->Security->Media Library->Literature: page 8 ff.

>One more Question as of CUA guide when I assign limited roles to communication users as On Central - >SAP_BC_USR_CUA_SETUP_CENTRAL

>SAP_BC_USR_CUA_CENTRAL

>On child - SAP_BC_USR_CUA_SETUP_CLIENT

>SAP_BC_USR_CUA_CLIENT

>I am not able to get users in child with the above roles in child system. When I assign SAP_ALL profile to the comm. user in >the child then when I create user in central getting in child but not with mentioned roles. why?<

Possible cause: profiles not generated for that roles. Did you check that already? Advisable is to copy that sap roles first and then update them and generate the profile(s). if the problem persists afterwards, turn on the authority-trace in the child system with filter to the rfc-user and then create/change a user again for that system. In the trace result you will find, what was missing. Then update your role copies....

b.rgds,

Bernhard

Edited by: Bernhard Hochreiter on May 6, 2010 11:33 AM

0 Kudos

Hi Bernhard,

Thanks for clearing me about the report RSCCUSND. As you mentioned I have gone through CUA cook book page 8. There he has mentioned like create/ define all Logical system names of central and all child names in the central system then transport them to all child systems. or We can also create/ define in each individual system. With this I have a question does "create in all individual systems" means that we have to create all systems Logical names (central and child's) in every system? or just one logical name for that system itself? I have created like in BD54 in child - SIDCLNT<child client> and In central - SIDCLNT<central client>. Only one name for each client is that correct? or I have to create in child- SIDCLNT<child client>, SIDCLNT<central client>

and in central - SIDCLNT<child client>, SIDCLNT<central client> ?

And about roles I have not yet activated the trace but yesterday I have also tested giving full authorizations in the role mean all *s in the authorizations for the role and generated profile but it still it didn't work. When I assign sap_all profile to the user then it worked. Any way I will activate trace and let you know the problem.

Thanks,

Ajay.

Former Member
0 Kudos

Use SCUA and click select system and transfer user from child system to CUA.

Clear SCUL after transfering users.

<nonsense_striked_through_by_mod>

Edited by: Bernhard Hochreiter on May 6, 2010 7:35 AM

0 Kudos

propably you meant SCUG instead.

But if you would read this whole thread, you'll find, that the steps proposed by you have already been performed. thoughts?

b.rgds, Bernhard

Former Member
0 Kudos

Ajay,

You must set up a logical client in both the parent and the child for each system. Since they are client independent, you only need to set up one logical client per system.

0 Kudos

Hi MIke,

Suppose Child SID - CID and parent (central) SID - PID.

So In child system logical name CIDCLNT<client no> is enough. PIDCLNT<client no> is not required to create/ define.

Similarly in Central system only PIDCLNT<client no> is enough CIDCLNT<client no> is not required to be created/ defined.

Am I correct? I did the same but in transaction SCUA. Under receiving systems its not showing client logical name if press F4. If enter directly giving error like "entry does not exist in TBDLS table".

Thanks,

Ajay.

0 Kudos

Hi,

the central system needs to know all its 'childs'. so you need to define all the childs in the central system.... The error message you got gave you that information (indirectly...).

b.rgds, Bernhard

0 Kudos

Hi Bernhard,

Thanks for confirming. That was my doubt. What about in child systems?I think don't require all systems information. correct?

Thanks,

Ajay.

0 Kudos

Hi Ajay,

Let me try to clear your doubt. In child system logical entry of parent system PIDCLNT<client no> is not required. But in parent system entry of logical system of all child system is mandatory in BD54 otherwise SCUA will not recognize the child system.

After this save your entry of child system in SCUA.

Additionaly you have to make the entry of logical system in scc4 for all respective systems. RFC name and Logical system name should be same like PIDCLNT<client no> in BD54 and in RFC.

Check and let me know in case still you face any error.

Cheers

0 Kudos

Hi Connecpk,

Thank you for explaining. Now It is clear to me. I have later created child logical name also in the central system and that then recognized the child but it is not showing in F4 browse of options where child entry is to be entered but I can manually enter the name. Anyway my CUA set up is working fine now. I have a small issue with limited role to communication users that I have posted in Security group with another thread

Thanks,

Ajay.