Use HTTP PUT, PATCH and MERGE request to consume SAP ABAP OData service modification operation implementation and its differences Trial version

As mentioned in the introductory article SAP OData Development Tutorial - From Getting Started to Upgrading (including SEGW, RAP and CDP) , SAP OData service development, technically speaking, can be divided into three categories. Therefore, this tutorial is also divided into three parts, which will be introduced separately. This article is the article directory for this tutorial.

About the Author

Jerry Wang, joined the SAP Chengdu Research Institute after graduating from the University of Electronic Science and Technology of China with a master's degree in computer science in 2007. Jerry is a SAP Community Mentor and a SAP China Technology Ambassador. In his 15-year career in SAP standard product development, Jerry has participated in the research and development of standard products such as SAP Business ByDesign, SAP CRM, SAP Cloud for Customer, SAP S/4HANA, and SAP Commerce Cloud (e-commerce cloud).

Jerry has in-depth research on the development, testing, publishing, deployment, testing of SAP OData services, as well as the behind-the-scenes technical implementation details and usage scenarios of OData services based on various SAP technologies.

Development tutorial based on SEGW - Gateway Service Builder

• 1. Create a SAP OData project in the SAP ABAP transaction code SEGW
• 2. Configure and test the OData service created by the transaction code SEGW in the SAP ABAP system
• 3. How to use the SAP ABAP OData service diagnostic tool/IWFND/ERROR_LOG
• 4. Implementation Guide for GET_ENTITYSET Method of SAP ABAP OData Service Data Provider Class
• 5. How does the SAP ABAP OData service support the $filter operation
• 6. Use Postman tool to efficiently manage and test SAP ABAP OData service
• 7. How does the SAP ABAP OData service support the $orderby (sort) operation
• 8. How does the SAP ABAP OData service support the Create operation
• 9. How does the SAP ABAP OData service support the Delete operation
• 10. How does the SAP ABAP OData service support the update (Update) operation
• 11. Use HTTP PUT, PATCH and MERGE request to consume SAP ABAP OData service modification operation implementation and its differences
• More articles are being written, so stay tuned

Develop OData services using the Restful ABAP Programming model (RAP for short)

• Currently writing, stay tuned

Develop OData services using the SAP Cloud Application Programming programming model

• Currently writing, stay tuned

  Preamble

This article describes how the server-side ABAP implementation details differ when the SAP ABAP OData service is triggered by three different types of requests: HTTP PUT, PATCH and MERGE.

In the previous step of this tutorial, 10. How the SAP ABAP OData Service Supports the Update Operation , we introduced how to use the HTTP PATCH request to consume the OData service we developed for SAP Book Management to trigger the modification operation of the book inventory field stock_number.

At the end of the previous step, we left a suspense: the modification operation triggered in the SAP ABAP Gateway Client, in addition to the type of HTTP PATCH, there are also PUT and MERGE options. So what happens if I choose to use PUT or MERGE?

This article will introduce in detail the implementation details and differences of triggering SAP ABAP OData service update requests through HTTP PUT / MERGE / PATCH request types.