Skip to Content

Client independent data copy from Test system to Dev

Dear all,

Had you ever did client copy of only client and cross-client customizing from Test/PRD to Dev system?(without application data)

My functional consultants want to have same customiing settings in DEV like in Test/Pod, they suggest to do client copy. There're 4 clients in my DEV.

According SAP note 24853 - "C-INFO: Client copy, functionality" Client-independent customizing must only be copied to create a new system. Client-independent data and thus all clients in the target system are affected by this and can be destroyed!

What will happen in my Dev if i start client copy with profile SAP_EXPC Customizing Including Cross-Client Customizing)?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Apr 27, 2017 at 05:55 AM

    Hi Albert,

    Hi, according to the following link, the remote client copy option SAP_RMPC (formally SAP_EXPC), will copy SAP_CUSV with cross-client customizing, SAP_CUSV means SAP_CUST with variants, so the final data will be:

    Client-specific and cross-client customizing including authorization profile, variants are copied. The application data is deleted, the user data is retained.

    https://help.sap.com/saphelp_nw70/helpdata/en/99/0a2a887e2511d2a6250000e82deaaa/content.htm

    Regards,

    Michael

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 28, 2017 at 05:42 PM

    Hi,

    In general PRD runs with single client, if you want to copy customizing data from PRD/TST to any DEV client then SAP_CUST is the right profile to use. It copies the entire customizing data of source client to target client without disturbing other clients.

    Regards,

    Harish Karra

    Add comment
    10|10000 characters needed characters exceeded

  • May 08, 2017 at 06:06 PM

    Albert,

    You are correct to be concerned about performing a Remote Client Copy into your DEV system that uses any profile that includes cross-client customizing. That has a high potential to disrupt your "golden" DEV client.

    In theory, customizing settings, both cross-client and client-dependent, should be the same between DEV and PRD (except for work in progress), assuming you've properly managed transports throughout your landscape. If your consultants are asking for this, it indicates they suspect that either there are transports that were deleted before release in DEV without first undoing the changes within them, or there were customizing settings made directly in PRD without being transported.

    In general, I would advise against anything that overwrites any data in your DEVC client and/or cross-client information in your entire DEV system. Doing so would indicate you have given up your DEV system as a lost cause and are starting over, in which case perhaps a regular System Copy would be more efficient (it should be possible to export your version history prior to overwriting the system, then re-importing it afterwards, though this is not something I have done myself).

    Bear in mind that remote client copies can be somewhat inefficient and take a long time, and that your source client (i.e., PRD) is impacted while the copy is underway -- you have to lock out access to the system for users and stop all scheduled jobs, or you risk creating an inconsistency in your copy. I would suggest that it would make more sense to refresh a QAS system via system copy (using database backup/restore, for instance) first, then practice or perform your client copy using that QAS system as a source. This should minimize the impact on productive operations.

    Cheers,
    Matt

    Add comment
    10|10000 characters needed characters exceeded