Recently received a friend’s consultation:
As a third-party external SaaS provider, what versions of SAP do you need to know if you want to integrate with customers using SAP system? And common docking technology, language, mode, protocol, precautions?
First of all, the scope of this problem is indeed relatively large. With the transformation of sap to the cloud in recent years and the acquisition of cloud products from many companies, SAP’s product line is no longer mainly composed of products based on ABAP technology stack as at the beginning of this century.
We can first divide SAP products into on premises and cloud based products according to the deployment mode.
- On premises: SAP ERP, SAP Business Suite (such as SAP CRM), SAP s / 4hana on premises version, SAP Commerce on premises, etc
- Cloud: SAP Business bydesign, SAP cloud for customer, SAP field service management, SAP commerce cloud, etc.
No matter what type, the integration of third-party applications with SAP, in the final analysis, is to call the API provided by SAP system, add, delete, modify and query SAP data model, and execute some transactions on SAP system. For example, call the order creation API of SAP system, generate a new order, return it to the third-party application, and then trigger the approval workflow in the third-party application. The workflow is executed in the sap background, and the execution result is returned to the third-party application.
If a third-party application is integrated with SAP products based on ABAP technology stack, such as SAP ERP and SAP CRM, the integration can be completed by consuming SAP system RFC (remote function call). This integration method is relatively old and mature. Search directly on Baidu according to the keyword “SAP RFC”, and you can find many technical articles.
Of course, either on premises or cloud products, another way is to integrate through APIs. The specific idea is to call the standard API exposed by SAP system through HTTP protocol in a third party. If the sap standard API cannot meet your actual needs, you can create a new API through secondary development in SAP on premises products; For SAP cloud products, the secondary development is less flexible than on premises, but you can still develop APIs to meet your actual needs through the secondary development tools provided by SAP cloud products, and then call them by a third party.
Here are some articles I have written about SAP API calls.
- Complete collection of SAP API development methods: This paper introduces the development methods of APIs in various SAP systems, which are exposed through WebService, OData and other carriers, and then can be consumed through various programming languages.
- SAP FSM learning notes (I): using API to consume FSM data: a practical example of how to consume the API of SAP field service management
- Official account of SAP system and WeChat integrated series three: after WeChat users pay attention to the public number, automatically create customer master data in SAP C4C system.: how to call SAP C4C system customer master data creation API
- Nine series of tutorial SAP system and WeChat: how to automatically transfer WeChat users to WeChat official account to SAP C4C system: how to call the sap C4C system API to store the message text sent by a third party on the sap C4C system
- How to consume the order service of SAP commerce cloud by API: order in SAP commerce cloud system using API
- SAP OData Programming Guide: how to develop OData services in various SAP systems
How to view the SAP system standard API?
Suppose we want to find the standard API of SAP cloud for customer under the sap customer experience product line. In the product list on the left, find SAP customer experience:
Select SAP cloud for customer:
Here you can see a list of all available APIs:
Select any one to enter the details page, and you can see the API interface parameter description, calling method, etc.
More Jerry’s original articles are: “Wang Zixi”: