Shulou(Shulou.com)06/01 Report--

This article will explain in detail how the implementation of SAP OData service is transferred from the Gateway system to the backend system. The content of the article is of high quality, so the editor shares it for you as a reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Here is the model of the background OData data I studied today and how to consume in IE:

In SPRO:

This model provider class defines all the structure of the LWM_CUSTOMER_BRIEFING model, as well as the interrelationships between the structure.

At present, there is no tool with a graphical interface to do modelling, we can only define the structure of model in the DEFINE of CL_LWM_CB_ADAPTER_MDP. The specific approach is to pre-define the data type of the entity to be used in the background

All the DDIC object used by Customer briefing are put in this package: LWM_CRM_CUSTOMER_BRIEFING

In DEFINE, create entity by ABAP code, tie DDIC object to them, and establish relationships, such as association.

Through URL consume OData service:

On the Gateway system, you will first find the service ID used by internal based on the external name from OData service expose:

Then find the destination of the corresponding CRM system according to service ID:

Directly call CRM a remote function module on the system through RFC:

Set a breakpoint on this FM in CRM and find that the breakpoint has been triggered.

On how the implementation of SAP OData service is transferred from the Gateway system to the backend system to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

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.