RSA1 Transaction: Work in client 001 only

[Former Member]

Hi All,

I have done NW2004s installation for BW 7.0. Proceeding further, I have done a client copy from 000 to 100 which was successful.

Now in CLient 100, which iam supposed to use for BW, I am unable to run the TCODE RSA1.

Can anyone please let me know the way forward ASAP as it is very urgent.

Thanks and Regards,

Mani

[Former Member · Accepted solution]

Hello Mani,

You need to make client 100 as your default login client. For this change the value of profile paramter login/system_client accordingly in RZ10. Further execute the function module RS_MANDT_UNIQUE_SET in SE37 with value of i_mandt being set to 100 (in general the client where you want to execute this transaction). This is in accordance with OSS note 316923.

Please let us know if this solved the issue for you and <deleted>.

Regards.

Ruchit.

DO NOT ASK FOR POINTS

Edited by: Matt Kangas on Feb 5, 2009 11:11 AM

[Former Member · Accepted solution]

Hi Ruchit,

Your solution worked like a miracle. Our problem got resolved and that saved us before the client.

A Million THANKS for the timely help!!!

Best Regards

Mani

[Former Member · Accepted solution]

hi mani..

this is chaitanya..

your solution is working very good

thanks alot...

-chaitanya

[Former Member · Accepted solution]

sorry...

thanks Ruchit.

thanks alot for your solution...

its working really nice..

-Chaitanya

[Former Member · Accepted solution]

Hi Ruchit,

I had the same problem on SCM and I did what you said. Now this message is gone but I have this one: Logical system name has been changed for this system.

What to do? I want to work in client 100.

Thanks

[Former Member · Accepted solution]

Hello Mona,

This is strange message as it doesnot explain much. However please verify if:

1. A client copy was done on client 100 as target.

2. After client copy a new logical system was created and BDLS transaction executed.

Regards.

Ruchit Khushu

[Former Member · Accepted solution]

Hi,

The client copy was done in 100, from client 000.

When I try to run BDLS, it says that the new logical system name SCMCLNT100 is already assigned to the current client.

Any others ideas?

Thank you very much.

[Former Member · Accepted solution]

Try removing the new logical client definition first and then run BDLS again. It worked for me. Thanks.

Michael

[Former Member · Accepted solution]

Hello All,

Earlier the RSA1 was activated for client 300 on our crm 5.2. after that we changed the client to 500 using SE16 -> Type table RSADMINA / Check Colum BWMANDT -> 500.

But now when we login to client 500 and execute RSA1 it is showing

"

Logical system name has been changed for this system"

In scc4 we have not made any changes. Can you tell what should be done ? in the pop up it is showing following steps

###

Change the name of the logical system (table T000) for client back to SIDCLNT300. This enables you to continue working with the system.

If you really want to change the logical name, than you can, if and when you:

change the system name back to SIDCLNT300,

delete all existing connections between this system and other systems,

delete all transfer structures that still exist, and

do not use ALE or Workflow.

###

Can you guys please give some steps to solve this?

[Former Member · Accepted solution]

Hello All,

Earlier the RSA1 was activated for client 300 on our crm 5.2. after that we changed the client to 500 using SE16 -> Type table RSADMINA / Check Colum BWMANDT -> 500.

But now when we login to client 500 and execute RSA1 it is showing

"

Logical system name has been changed for this system"

In scc4 we have not made any changes. Can you tell what should be done ? in the pop up it is showing following steps when clicked on the question mark that comes with pop up

###

Change the name of the logical system (table T000) for client back to SIDCLNT300. This enables you to continue working with the system.

If you really want to change the logical name, than you can, if and when you:

change the system name back to SIDCLNT300,

delete all existing connections between this system and other systems,

delete all transfer structures that still exist, and

do not use ALE or Workflow.

###

Can you guys please give some steps to solve this?

[Former Member · Accepted solution]

Hi,

Did you manage to solve this problem? I ma having a similar issues. Please Help

KT

[Former Member · Accepted solution]

Hi, Frans

Please Check Note 140276 - Error in source system assigment

[Former Member · Accepted solution]

Very Good Solution

[Former Member · Accepted solution]

Thanks Sahad...for your reply, this helped me.

[former_member199963 · Accepted solution]

Thanks Ruchit,

It worked for me too.

Regards,

Asad

[avi_malamud · Accepted solution]

This solution worked for us as well.

Thanks a lot!!

[Former Member]

In the past few days we have migrated an SCM 7.0 system from Windows to Linux

The migrated data was put in client 001.

We did a client copy using SCCL using the SAP_ALL profile from client 001 to client 510.

The project team went into validate data and received the message: You can only work in client 001.

Can anyone help with steps to correct this for and SCM 7.0/DB2 system running on Linux RHEL 5.5?

Appreciate all the help possible.

Hal

[Former Member]

BW SYSTEM-> SE16-> RSADMINA---> CHANGE --> BWAMNDT --> NEW CLIENT NUMBER.

Thanks

SM

[Former Member]

thanks alot for your solution...

its working really nice..