3
Product download is not working after system copy Skip to end of metadata Page restrictions apply Attachments:2 Added by Willie Musa, last edited by Willie Musa on Apr 22, 2013 (view change) show comment Go to start of metadata Purpose This article would give you an overview of how to configure your system after a system copy. Overview After you have done a system copy from production to quality for example, the logical system name in ECC and CRM has been changed back . When you try to replicate the material, you get the following middleware in transaction SMW01. Error in transaction SMW01

Product Download is Not Working After System Copy

Embed Size (px)

Citation preview

Page 1: Product Download is Not Working After System Copy

Product download is not working after system copy

Skip to end of metadata Page restrictions apply Attachments:2 Added by Willie Musa, last edited by Willie Musa on Apr 22, 2013 (view change) show comment

Go to start of metadata

Purpose

This article would give you an overview of how to configure your system after a system copy.

Overview

After you have done a system copy from production to quality for example, the logical system name in ECC and CRM has

been changed

back . When you try to replicate the material, you get the following middleware in transaction SMW01.

Error in transaction SMW01

Page 2: Product Download is Not Working After System Copy

The following error message no. will appears after you click on on a bdoc error.

You might also get the following messages errors

Logical system must not be changed "Message no. COM_PRODUCT713"

Data for set BBPM_PR_GENERAL may only be changed in the original system XXXX "Message no. COM_PRODUCT502"

Validation error occurred: Module COM_PRODUCT_MAT_VALIDATE, BDoc type PRODUCT_MAT "Message no.

SMW3018"

Requirement

If you are uploading the product the main trigger is that the system logical system gets change and the error

COM_PRODUCT713 appears

Here are some recommendations given to solve the issue;

The creation of product data in a CRM/EBP System should not occur by means of a client copy. When you set up a new

CRM/EBP System, the products should be created by means of a download from the connected R/3 Back-end System. If it

is required to make a client copy, for example in the cause of an upgrade test, the R/3 Back-end System must be copied to

the new CRM system landscape as well.In the new CRM system landscape, you must not rename any logical

systems.However, all RFC destinations have to be redefined in such a way that there is no longer a connection to the

original system landscape. If this restriction is too strict, you must not change the logical system directly in table T000, but by

means of transaction BDLS which must run three times in this process:

- in the R/3 Backend: LOGSYS OLTP old -> LOGSYS OLTP new

- in the CRM/EBP System: LOGSYS CRM/EBP old -> LOGSYS CRM/EBP new

- in the CRM/EBP System: LOGSYS OLTP old -> LOGSYS OLTP new

Conclusion

To avoid the error in your system, you have the BDLS order as mentioned above

Page 3: Product Download is Not Working After System Copy

Related document

Additional information can be found in note 418886