Q
Problem solve Get help with specific problems with your technologies, process and projects.

Overwriting dev environment for CRM; what to watch out for

A SearchSAP.com reader asks for pointers on what to watch for when overwriting a CRM environment to correct inconsistencies.

I have three systems (BW, CRM, R3). The company wants to overwrite the Dev environment for CRM from Prod because of inconsistencies/bad practices.

Apart from losing all change history, is there anything else to worry about?

Would there be a need to refresh all three Dev environments (CRM, BW, R3) or could CRM be done by itself?

Some additional steps are needed when copying a CRM system, such as the renaming of the logical system name via transaction BDLS, the changing of the RFC connections to the back-end system. The best source of information is the Best Practice Guide for Solution Management 'mySAP CRM System Landscape Copy'. The guide is available via the Solution Manager. If there is no guide for your specific product/release combination, use the latest guide. It will nevertheless contain valuable information for your system copy.
This was last published in February 2007

Dig Deeper on SAP implementation and upgrades

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close