Skip to Content
0

NW 7.4 client 066 unable to copy user

Sep 04, 2017 at 09:12 AM

82

avatar image

Hi All,

I want to delete client 066 in our Solman 7.2 system, but when I log on using SAP* I am not authorised to run transaction SCC5. So I thought I'd check the user profiles which shows only S_TOOLS_EX_A & S_USER_ALL. So I thought I'd change it to have SAP_ALL. Only to be greeted with "You are not authorized to assign user group to profiles". So I thought OK I'll create a new user instead.

But complains of "NUMBER_GET_NEXT AENDBELEG INTERVAL_MISSING".
I also can't run SCDN, not authorised.

If I try to copy the SAP* user as another user I get the same error.

You are not authorized to assign user group to profile S_TOOLS_EX_A
You are not authorized to assign user group to profile S_USER_ALL

What can I do about this?

Cheers
Craig

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Prithviraj Rajpurohit Sep 04, 2017 at 09:36 AM
0

Hi Craig,

please go through below mentioned Sap note

https://launchpad.support.sap.com/#/notes/2176524

https://launchpad.support.sap.com/#/notes/1749142

Hope they help.

Regards

Prithviraj.

Show 5 Share
10 |10000 characters needed characters left characters exceeded

Hi Prithviraj,

I was following note 1749142 but the other note doesn't help. I'm in a catch 22 whereby I can't run the transactions I need to delete the client due to the missing authorities. And I can't make the necessary authorities available, again due to the missing authorities.

There must be some way around this situation.

Cheers
Craig

0

Hi Craig,

Below can done as a workaround.

Step 1: Go to directory /usr/sap/trans/bin in OS Level using <SID>adm userid

Step 2: Create file using vi editor with below details $ vi delete_<SID>_<clntno>.ctl

E.g.: $ vi delete_SM1_066.ctl

clientremove

client=066

select *

Step 3: Run R3trans like below R3trans -w delete_<SID>_clntno.log delete_<SID>_<clntno>.ctl

E.g.: R3trans –w delete_SM1_066.log delete_SM1_066.ctl

Step4. You can monitor the log by doing below from OS level

$ tail –f delete_SM1_066.log

Regards,

Prithviraj

0

Hi Prithviraj,

That's perfect and ran successfully. However I am assuming I need to manually cleanup scc4 etc as the entry for 066 still remains.

Cheers
Craig

0

Hi Craig,

Yes, the only task that is pending is to Delete SCC4 entry for 066 client. All Done!!

Regards

Prithviraj.

0

Thanks very much.

0