Logical system on source has changed after client copy

[Former Member]

Hi,

we faced a strange situation on our ERP system. We performed a client copy from 100 to 210, after the client copy finished we saw the logical systems at SCC4 has changed at the 100, it change to SIDCLNT210. The original was SIDCLNT100. And the target has been changed to SIDCLNT210 as well. My question is: why the Logical System changed at the source client? I think it is not the normal behavior of the client copy method.

We faced the same situation at an another system at an another customer.

Our systems is a NW7.40 ECC6 EHP7 at latest SP level.

[JPReyes · Accepted solution]

Hi Andras,

No its not normal, sounds to me like someone executed BDLS and replace all entries of SIDCLNT100 with SIDCLNT210 perhaps...

BDLS has two options one for System Copies and one for Client copies which excludes Client independent tables.

Regards, Juan

[Former Member · Accepted solution]

Hi Juan,

in the source client there is no any "footprint" of any bdls, only the system name changed in table T000. It is easy to change it back to original in SCC4, but it is not so clear why the client copy change it automatically after it finished. In tha past we did not see this.

Regards,

Andras

[JPReyes · Accepted solution]

Hi Andras,

Any information on the last changed field on SCC4?,

Also, BDLS could have been executed in the target client.

Regards, Juan

[Former Member · Accepted solution]

Hi Juan,

in the last change "field" has my user, because I performed the client copy and the date is the finish date/time of the client copy.

Regards,

Andras

[Former Member · Accepted solution]

Hi.

If someone run the BDLS, you can see that in the Job logs.

Regards.

Osvaldo Ferreira

[Former Member · Accepted solution]

Hi,

there were no any bdls on the source client, as I mentioned only the T000 table changed.

Regards,

Andras

[JPReyes · Accepted solution]

Hi Andras,

T000 is a client-independent table, it is not modified in anyway by the client copy process (which by nature only copy the client-dependent data), IMHO if this wasn't done manually you have a very weird bug on your system. Open an OSS message.

Regards, Juan

[Former Member · Accepted solution]

Hi Andras,

Please go through below sapnote  that fits the scenario. if applicable implement it.

2246015 - BDLS: Incorrect conversion of client table T000

Regards,

Prithviraj.

[shirley_wang2012 · Accepted solution]

Hi Andras,

To avoid the issue, you should apply the note 2246015 which is mentioned by Prithviraj.

To resolve the existing issue, you only need to go to SCC4 to change the logical system name back.

Best regards,

Shirley Wang

[Former Member · Accepted solution]

Hi,

this note solved our problem. Thank you!

Regards,

Andras

[Former Member]

check T-code " BDLSS " (two s)

And then click the log button. It will give you information from which system you have copied and if you have done a convertion of naming.

If you have. use BDLS to reconvert the names back to whatever you desire.