SMQ1 - RFC destination does not exist

[Former Member]

Hi Folks,

After a system copy from production to QAS the connection between CRM and R/3 stuck.

The CRM team is running some test and the error in the SMQ1 is:

RFC destination does not exist

the process into SMQ1 is pointed to the production RFC.

I have already run the BDLS, created the QAS RFC and fixed SMQS queue.

Does anyone know what else I could do?

BR,

Má

[Former Member · Accepted solution]

Hi,

Please make the changes in BD97, we21 and we20, SMQR and SMqs and BD64.

Manual Configuration

If not all steps are executed successfully, you can perform the relevant step manually. Manual configuration is also necessary after an upgrade.

• Defining Logical Systems (SAP CRM)
• Assigning Logical Systems to a Client (SAP CRM)
• Defining Logical Systems (SAP ECC)
• Assigning Logical Systems to a Client (SAP ECC)
• Creating RFC Users (SAP ECC)
• Creating Logical Systems for SAP CRM (SAP ECC)
• Creating RFC Destinations for the ECC System (SAP CRM)
• Creating RFC Users (SAP CRM)
• Defining Logical Systems for ECC (SAP CRM)
• Connecting SAP CRM (SAP ECC)
• Checking the CRMCONSUM Table (SAP ECC)
• Maintaining the CRMRFCPAR Table (SAP ECC)
• Maintaining the CRMPAROLTP Table (SAP ECC)
• Activating Event Control (SAP ECC)
• Creating RFC Users in Client 000 (SAP CRM)
• Creating RFC Destinations for Replication and Realignment (SAP CRM, Client 000)
• Creating RFC Users in CRM Client (SAP CRM)
• Creating RFC Destinations for Replication and Realignment (SAP CRM, Application Client)

Thanks

Rishi Abrol

[Former Member · Accepted solution]

Tahnk you so much Rishi, your hints really helped me.

[former_member182606]

Hi

After such client copies it is always better to delete the existing Sites in the transaction ( SMOEAC - Administration Console ) and recreate them with their subscriptions.

If any inconsistency is there it will be shown when you try to modify or delete the sites.

These are the 2 table which gets updated while you create New Site or modify existing ones SMOHSITEID and SMOF_ERPSH.

After the client copy these table are likely to be corrupted. Check for any inconsistency in this table.

In my case ECC quality site id (GUID) was replaced with Production Site id (GUID) In above tables   after the client copy from Production to quality.

Regards,

Chella.

[former_member215981]

Hello,

Please double click the RFC destination in SMQ1, it it exist, you will get the RFC destination screen, if not,

obvioursly,if you create it accordingly.

Best Regards,

Yong Luo

[Former Member]

Hi Marilia,

              Can you please check in SM59 for the RFC destination which is showing in SMQ1 and which is pointing to Production System , please delete that destination and create a new one pointing to QAS.

              Can you please post the screenshot of SMQ1 and SM59

Thanks and Regards,

Kunal Gahlot

[Former Member]

Hi,

After the system copy from Production to QAS the RFC of Production system will be copied to QAS,

RFC for QAS will not exist

Have you taken the export of RFC of QAS before doing system copy as a pre steps

If yes , you can import those RFC into QAS

Make sure you have done all the Post steps

Also you need to run secstore for this to maintain the password of RFC

Thanks & regards

Amit