How to transport from Production environement back to Quality

[Former Member]

Hello,

As part of our effort to keep out Development, Quality and Production systems as close to the same as possible we have been UJBR backups of Production and setting them up in Quality and Development.  I recently ran into some errors that have not occurred before and was told by SAP support that the UJBR is not the best way to keep our environments consistent.   Can anyone help on what is the best method to get our production environment back into Dev, Quality or even our Sandbox environments?

Thank you,

Robert

[Former Member · Accepted solution]

Hi,

System copy is more common for this kind of scenarios.

Regards,

Manohar

[Former Member · Accepted solution]

Hello Manohar,

When you say a system copy.  What are you specifically talking about?  Are you talking about a database copy because essentially I have seen a UJBR referred to as a system copy before by some people.

Regards,

Robert

[Former Member · Accepted solution]

No,Not UJBR backup.With UJBR backup you will be taking only BPC Environment data.

But with system copy you will be replicating all the BW related objects(BW (Basic)cubes,Info objects,process chains..etc.)It is Basis team activity.

Thanks,

Manohar

[Former Member · Accepted solution]

Will this type of backup change any of the names and therefore mess up any transport channels going back from Development > Quality > Production?

[Former Member · Accepted solution]

Whatever there in the production will be replicated in other systems.

Limitations:

1.If any modifications/enhancements,saved as local objects in Dev/QA..which are yet to be transported to production..you will miss them.Need to transport before copy.

If is it QA system,again transport which was moved only till need to be imported again.

2.Sandbox and Dev systems may not have enough resources to hold production system.

Regards,

Manohar

[Former Member]

Hi Robert,

I think the main issue is how did it become out of sync in the first place and how do you maintain in sync with DEV - QA - PROD afterwards.

and when you talk about out of sync is it only the reports? or what is it that is out of sync?

master data and transaction data is depends on ECC and BW

BADI is transported via SAP transport

so only the items you can maintain in web admin and excel might be out of sync

Andy

[Former Member]

Hello Robert,

It depends what meaning you put into words "keep ... as close to the same as possible". If you include configuration only, then transport can be the best way. If you include data as well, then system copy or UJBR is better.

Additionally, you can decide between system copy and UJBR depending on how many "out of BPC" objects you use. By "out of BPC" objects I mean BADIs, web dynpro, custom tables etc. because those not coming over with UJBR.

UJBR will keep most of the technical names unchanged if you choose "keep tech names" check box, but some that are not visible in RSA1 can get changed.

With transports I'd suggest go first to Dev and then from Dev to QA.

Regards,

Gersh

[Shrikant_Jadhav]

Hi Robert,

Transport is the best option, if you do system copy you will lose all the track of transport.

Shri