10-16-2008 7:47 AM
Hello,
We have a system(SID - DXA) that we wish to remove from CUA.
The problem is -
DXA was copied from DXB (Source-DXB, Target - DXA)
They are from totally diffrent landscapes.
DXB was part of a CUA config. It was a child system there.
Now, we are not able to create Users in DXA in this new landscape, because it is still part of that CUA, or atleast that's what the system thinks.
Could you please help me remove DXA from this imaginary CUA.
Thanks.
10-16-2008 11:16 AM
Hi,
report RSDELCUA shall do.
Use the option 'Invalid Contents in CUA Tables', or 'Complete CUA' in DXA.
Make sure, that you delete the invalid (old) model in bd64 too. Remove invalid WE20 (Partnertype LS) - settings.
b.rgds,
Bernhard
10-16-2008 11:22 AM
Hi Gautam,
Im sure others will advise how to technically convince the system it sno longer in a CUA environment, but basically you will always have problems when copying a CUA linked client.
Technical solution above already ! But still :-
You would be better off (if the system copying time is not large), starting again and contacting the Basis / Security admin of DXB, and get it "unhooked" from CUA, copy it, and confirm back to them so they can "rehook" it back into CUA. hooking and unhooking is not an onerous activity and wouldnt stop the DXB users from being able to work in there - our Basis team does it for us, and it will save you a lot of problems with users, parameters, configs, idocs etc in your new system DXA, and would solve your problem of user creation and modification issues.
We have made this standard practice for client copying in our organisation, as most client copies are taken from CUA hooked clients. It will save you a lot of pain to adopt this approach formally, it has us.
Good Luck
Cheers
Steve
Edited by: Steve Bodell on Oct 16, 2008 12:22 PM
10-16-2008 11:34 AM
...and one of the most important steps after the CC is to adapt the logical system name to the new one. this is often forgotten and causes in the new CUA someunexpected behaviour...
b.rgds, Bernhard
10-16-2008 4:27 PM
>
> Hello,
>
> We have a system(SID - DXA) that we wish to remove from CUA.
>
> The problem is -
> DXA was copied from DXB (Source-DXB, Target - DXA)
> They are from totally diffrent landscapes.
>
> DXB was part of a CUA config. It was a child system there.
>
> Now, we are not able to create Users in DXA in this new landscape, because it is still part of that CUA, or atleast that's what the system thinks.
>
> Could you please help me remove DXA from this imaginary CUA.
>
> Thanks.
Two important items to accomplish your goal.
1. Make sure (SID -DXA) has no reference FROM the (Source-DXB Parent CUA).
Execute Tcodes from the Parent CAU of Source DXB: (SE38->RSDELCUA & BD64->Central User Administration).
2. Make sure (Source-DXB Parent CUA) has no reference from (SID -DXA)
Execute Tcodes from the Child (SID - DXA): (SE38->RSDELCUA & BD64->Centrql User Administration).
Good Luck!
Edited by: John Navarro on Oct 16, 2008 6:07 PM
Clarifying Response