cancel
Showing results for 
Search instead for 
Did you mean: 

Homogeneous system copy on iseries

Former Member
0 Kudos

Hello All,

We are planning to refresh our R/3 development system (SID: R3D) by doing homogeneous system copy using production data (SID: R3P).

There are couple of open transports in development system and I donu2019t want to overwrite those in the process of system copy.

also I donu2019t want to over write users idu2019s and passwords.

When i goggled, I found a procedure to execute a User Master Export SCC8 (client export) for profile: SAP_USER.

After creating a transport with users master datau2026 should I copy the transport co and data files to some other location, so that it doesn't get over written?

Should i save all CO and data files of transports from u201CR3Du201D into a separate folder and reimport into one by one after reconfiguring TMS?

Is there any procedure to save all variants in the system and apply the same after system copy?

Thanks a lot in advance.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

>> After creating a transport with users master datau2026 should I copy the transport co and data files to some other location, so that it doesn't get over written?

It will not get overwritten on it.

>> Should i save all CO and data files of transports from u201CR3Du201D into a separate folder and reimport into one by one after reconfiguring TMS?

Exported requests will not be overwritten. At the end of the system copy process, you should re-read the transport queue and import these requests into the system

>> Is there any procedure to save all variants in the system and apply the same after system copy?

SAP_UCSV will save "Customizing, User Master Records and User Variants". Please note that if you select this profile, customization data will be exported, as well

Best regards,

Orkun Gedik

Former Member
0 Kudos

Hello rk_007,

but I do not see a real solution for your issues except the users ... SAP_USERS is ok and can be used at any time. All the rest will delete ALL tables and replace it with the copy.

So, when you do a system refresh from R3P to R3D and then replace with SAP_UCSV ALL application data will be deleted ;-((

You cannot conserve open transports as well. You have to close them, and reimport later on again and open new ones for the missing functionality,

So, the process is a bit more complicated in a 2-system landscape as you might think.

Would be a client export of R3P perhaps sufficient ?

The versions of ABAPs are lost as well ... you should backup them before deleting R3D.

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de