zafar karnalkar

🚀 New Section Added!
Learn how to Create RFC-based Web Services and Service Consumer Proxies in SAP using SOAP. This is a valuable addition for real-world SAP integration scenarios!

📚 Already enrolled in my course? Just log in and start learning!
👉 www.udemy.com/course/sap-abap-basics/?referralcode…

#SAP #ABAP #WebServices #SOAP #Udemy #RFC #SAPIntegration

3 weeks ago | [YT] | 2

zafar karnalkar

WhatsApp API Integration with SAP (Outbound Messaging)

Enroll with free coupon code in the course link below :

www.udemy.com/course/whatsapp-business-api-integra…

3 months ago | [YT] | 2

zafar karnalkar

Mastering SAP UI5 - For beginners Free course by Chitra

www.zktutorials.com/courses/SAP-UI5-walkthrough-tu…

5 months ago | [YT] | 1

zafar karnalkar

Hi All, I have one freelancing project on SAP CPI, short project of 10 to 15 days, If you have experience in SAP CPI with consuming REST API RSA based encryption, kindly share your resume on zafar.karnalkar@gmail.com

9 months ago | [YT] | 2

zafar karnalkar

Free Udemy Course ( Coupon in URL ) SAP ABAP On HANA + Workflow By Shivam Chauhan

www.udemy.com/course/sap-abap-on-hana-j/?couponCod…

1 year ago | [YT] | 4

zafar karnalkar

ABAP Job for Fresher Pune

www.linkedin.com/posts/bijayasap_sapjobs-abapjobs-…

1 year ago | [YT] | 7

zafar karnalkar

Free Practice Test - ABAP On Cloud Practice Test

www.zktutorials.com/courses/Abap-on-Cloud-Certific…

1 year ago | [YT] | 4

zafar karnalkar

"Which object do you work with the most in your projects?"

1 year ago | [YT] | 7

zafar karnalkar

SAP OData Service: Which of following query option can be used to limit the size of the result set by limiting the number of columns?

1 year ago | [YT] | 4

zafar karnalkar

OData Service: Put, Patch and Merge

In SAP OData services, PUT, PATCH, and MERGE are HTTP methods used to update resources, but they have different purposes and behaviors:

PUT:

Purpose: Replaces an existing resource entirely.

Behavior: When you send a PUT request, you must provide a complete representation of the resource. The existing resource is entirely overwritten with the data in the PUT request.

Use Case: Suitable when you want to completely replace a resource or ensure the resource has specific state with all fields provided.

Example: Updating an entire customer record with all fields, including those that might not have changed.

PATCH:

Purpose: Partially updates an existing resource.

Behavior: With a PATCH request, you send only the fields that need to be updated. The server applies the changes to the resource without altering other fields that are not provided in the request.

Use Case: Useful for making small changes to a resource without sending the entire resource data. It reduces the amount of data sent over the network.

Example: Updating just the email address of a customer without needing to send the entire customer data.

MERGE:

Purpose: Also partially updates an existing resource, similar to PATCH.

Behavior: Like PATCH, the MERGE method updates only the specified fields of a resource. The key difference is more historical and nuanced, depending on the implementation by the server. In the context of SAP OData, MERGE behaves very similarly to PATCH.

Use Case: Historically, it was used by some systems to differentiate partial updates. However, in modern implementations, PATCH is more commonly used.

Example: Updating only specific attributes of an employee record, such as their job title or department.

Summary

PUT is for full resource replacement.

PATCH is for partial updates with a focus on minimal data transfer.

MERGE is also for partial updates, often similar to PATCH, but is less commonly used in modern practices.

When designing or using SAP OData services, it's essential to understand the intended behavior of these methods to ensure correct data handling and efficient network usage.

1 year ago | [YT] | 7