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 - Remove a system

former_member759680
Contributor
0 Kudos

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.

4 REPLIES 4

Bernhard_SAP
Employee
Employee
0 Kudos

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

Former Member
0 Kudos

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

0 Kudos

...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

Former Member
0 Kudos

>

> 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