Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to solve the problems encountered in the construction of SAP CRM middleware system

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to solve the problems encountered in the construction of SAP CRM middleware system". In daily operation, I believe that many people have doubts about how to solve the problems encountered in the construction of SAP CRM middleware system. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful for you to answer the doubts of "how to solve the problems encountered in the construction of SAP CRM middleware system". Next, please follow the editor to study!

I encountered a problem before. The response from ERP QV5 to CRM X3D did not come back because there was no configuration of X3D in the CRMRFAPCR table on the ERP side, and a new configuration information was added:

OBJNAME = MATERIAL & & DOWNLOAD = R, which gives priority to the more Specific to X3D one.

Re-execute, and Request can return to the CRM side, but there are still errors:

Debug found it because the source system configured on CRM does not match the system from Download, which is in the CRMMLSGUID table on the CRM side:

You can see that the original X3D system is QI3, and there are several systems in the SITE found with T-CODE SMOEAC:

I thought QI3 was already used by X3C, and the SM59 connection test from X3D to QI3 failed, so I found a new QV5 that looks good, and now it seems to be coming back.

There are two ways you can think of:

X3D continues to use QV5, add QV5 configuration as workaround in the CRMMLSGUID table of X3D, and delete it after testing.

X3D with QI3, report to IT TICKET to establish a two-way RFC connection to X3D/QI3, and configure the information back to X3D in QI3's CRMRFAPCR table. Considering that X3C has been tested on QI3, you may need to use different test Client to avoid conflicts.

At this point, the study on "how to solve the problems encountered in the construction of SAP CRM middleware system" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report