Refreshing your Development System

[Former Member]

This may be in the wrong forum, but I was having a problem classifying this.

<b>Does anyone refresh their R/3 Development system from Production (Data, Repository, and Customization)?</b> In my 9 years of experience, we never did, but at my current company, we are being convinced that the refreshing of the Development system is necessary for 2 reasons: 1)The configuration in the Dev System does not reflect production and is corrupt, 2)The development system does not have adequate test data. We are currently on 4.6C with a Unix/Oracle platform.

[ingrid_ney]

Did you have any success with this refresh? We are thinking of doing a database refresh of development to Production.

[markus_doehr2]

> Did you have any success with this refresh? We are thinking of doing a database refresh of development to Production.

You certainly mean from production, don't you?

We do this once a year saving the variants of the programs. Apart from that it's a lot of manual work - but it's technically possible.

Markus

[Former Member]

Hi,

Refresh is a part of SAP activity, its recommended by SAP that every 3 month System Refresh must be carried out.

Please refer the below link it may throw some light on the topics.

http://www.sap-img.com/bc049.htm

Thanks

Ahamed

[Former Member]

Hello Jhonathan,

If do you need the stable configuration from production system, its is possible using a export-import client or a remote client copy. This can apply for independent repository objects (reports, dictionary objects).

If do you need fresh data, its more complicated because do you need a homogeneous copy using any way (db backup/restore, R3copy, copy of file system), change the SID of the system and voila, but this is very expensive on resources (disk) and administration resources (you). In the market exists several tools for make a reduced client copies like SAP TDMS or Infomation (former Gamma Technologies) Infoshuttle.

Kind Regads,

Carlos

[Former Member]

Here's an old article that might help on this issue: [ BASIS ADMINISTRATION Safeguarding the version database during a refresh of the development system|http://searchsap.techtarget.com/tip/0,289483,sid21_gci1176707,00.html]

And a note about the transporting of versions: [130906 - How can versions be transported?|https://service.sap.com/sap/support/notes/130906]

Hope that information is helpful.

J. Haynes

MindWorks

[Former Member]

Hi Jonathan,

Yes we did it once...

We included version table export prior to restore ...and import them after restore..

Thats the only change in steps...