Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Switching Backend System

Hello everybody

We've setup SRM 4.0 with SRM Server 5.0 SP08 and CCM 2.0 SP03 on a development/customizing machine called DIM. We connected it to temporary devel./customizing SAP R/3 4.7 backend system called RIS.

Why a temporary devel./customizing backend system? Well, that's a complete other story...

However, we now have to change this connection to the definitive devel./customizing SAP R/3 4.7 backend system.

The problem / question is: after having changed all customizing settings (changed logical and/or RFC destinations everywhere) we are able to replicate DNL_CUST_BASIS3, DNL_CUST_PROD0 but not DNL_CUST_PROD1 from the new backend system.

In R3AM1 it hangs with a yellow status, in SMQ2 it stays in the inbound queue with an error message ":COM_PRODUCT_CUSTMSG:028 R3PRODHIER RISCLNT200".

RISCLNT200 is the logical system name of the old backend system.

Is this error message araising because we already replicated from this (old) backend system? Does anybody out there know this issue? Anyone having a solution to it?

Other question:

Is it somehow possible to wipe out all repliacated data (hierarchies, categories, material, ...) from an SRM server instance without having to reinstall everything from scratch? We're still on development/customizing level and not in production yet!

Thanks in advance for some help. Would be happy to reward with points!


EDIT: looking at COMM_HIERARCHY I can see that the product categories were replicated. Any ideas, why I get above error in the inbound queue SMQ2 then?

Message was edited by: Renaud Desarzens

Former Member

Hi Renaud,

for R3MATCLASS: if you also unassign the existing hierarchy from purchasing application, the system will create a new one instead of updating existing one.

Hope you won't have the same control on hierarchy ID as for R3PRODHIER.

Else, you will have to delete old hierarchies and their categories: use report COM_HIERARCHY_DELETE_SINGLE:

- non executable in a productive client

- must register the deletion in table comc_pr_tool_reg

This should solve your issue.



0 View this answer in context

Helpful Answer

Not what you were looking for? View more on this topic or Ask a question