Remote client copy error

[Former Member]

Hi,

I am trying to copy two clients from source system to target system.

(Both are in ECC 6.0 with same package level).

Having said that, i kicked off SCC9,but it failed with an error.

"Table Not convertible".

There are about 25-30 such entires are listed in the copy log.

I understand that there are some cross client customizing done in source sysem.

But my question is what is the best way to sync up taget system with these cross client customizing in order to avoid these errors in SCC9?

Thanks for your help.

PS:Alternatively,i can do client export /import.Since i can ftp/copy out files

from source system this opetion is ruled out for me.

Ram

[former_member185534]

Hello,

I want to do remote client copy from PRD to DEV system,

But the problem is in my scenario is we have some modules i.e.Transfer pricing..etc are configured in PRD,not in DEV system.

If i do the remote client copy then how the SAP system behaves means the changes which are adopted in PRD server would be reflected in DEV server.

or

Is there any process/method to choose what changes do we want to migrate.

Please reply....!!!

Regards,

JUNAID AHMAD

[former_member182505]

Hi Junaid

This is the tumb rule we should not do client copy from PROD to DEV,

You Version Details will get changed , its not recommended

Thanks

Sadiq

[former_member185534]

Dear Sadiq,

We have 2-system landscape (DEV--->PRD).What will we do in this scenario.

We have some customization like Transfer Pricing...etc in DEV server,which is not in PRD server.

Now i want a copy of PRD in our DEV server.

Then kindly tell me how can we do this..??

Regards,

JUNAID AHMAD

[former_member182505]

Hi Junaid

This is not recommended , but still if you want to do , inform your abap and  functional team about the challenges can be come, and create a new client and do client copy,

Thanks

sadiq

[former_member185534]

Hello Sadiq,

Actually we want to know what challenges do we face when we do client copy in 2-system landscape.

If it is not recommended ,then is there any possibility that we are not able to do the client copy in our SAP system.

Reply........!!!!!!!!!!

Regards,

JUNAID

[former_member182505]

Hi

Program version will change,

Thanks

Sadiq

[Former Member]

Hello Rama,

Run the client copy operation using SCC9 in a test mode and check out its log for the errors / warning that are raised.

Follow SAP note 557132, run report RSCCEXPT and add tablenames that cannot be converted. You can attend to this manually at individual level after the client copy is complete. You can also set parameter IGNORE_CON to ignore errors conversion errors.

Cheers,

Nisch

[Former Member]

Thanks for your info Nisch..

But, i really need those changes in my target system ..

So i thought let me make those changes and kick off the remote client copy.

I know i can copy those changes using transport..but is there any way

i can compare both system using RFC connection and pull the changes thru RFC connection?

Thanks

Ram

[Former Member]

Hi Ram & Nisch,

I am also facing the same problem .Can you tell me how did you resolve this error.

How can we copy the missing tables or changes from source system(PRD) to target system by transport organizer or any other method.

IGNORE_CON will affect the source system?

Pls help me out

[Former Member]

are you telling about abap/ignore_con parameter ?.When I tried to set value 1 to this parameter I was informed by the system "change in abap/ignore_con is not permitted " still do you want to change it.Choose yes or NO

I am expecting your suggestion.

[Former Member]

Hi Feranandez,

You would use the setting IGNORE_CON when you do remote client copy.

When you do SCC9 click on edit --> Expert settings --> then look for IGNORE_CON param.

Make sure this paramater is selected

It woked for me and the client copy was successful.

Hope this reply helps.

Ram

[Former Member]

Since i can not ftp/copy the files from my source system,

i can not go with client export/import method.

Thanks

Ram