|
Blogs by

Dilip Kumar KrishnaDeo Pandey

Overview In this blog, we try to consume a REST-Services in an OData-Service. Here we use GET operation of OData-Service and while consuming the REST-Service, we use HTTP-Method as POST to send request message and

Overview Main objective of this blog is to put different oData Service blogs (of mine) at one place with respect to their business case summary. And to put brief info of different terms used in

Overview In this blog, we will consume a oData Service of (below type) in Fiori-App using Eclipse: which, in a single call, returns multiple output table records in respective separate EntitySet structures. Here we perform a

Overview In this blog, we will come to know, how we can get multiple table output in a single oData Service call. This blogs is a business case example of parent blog: SAP (Fiori) OData

Overview In this blog, we consume a oData Service in Fiori-App using Eclipse. This oData Service is to perform Create operation (oDataModel.Create). i.e. with this oData Service, we post multiple table as input and in

Overview In this blog, we will come to know, how we can post multiple table input to oData Service that is nothing but a case of single header table and multiple-item table input to oData

Overview: Here we will see Using SAP-PI UDF (Java), we consume SharePoint REST to write a File into SharePoint. A business requirement, where employee’s pending item counts need to be updated in SharePoint in file

Overview: A business scenario in which IDoc is to be sent from SAP-ECC to Non-SAP System via SAP-PO (SAP Process Orchestration 7.5 Single Stack). Here, in this blog, we focus on how IDoc is been

Overview: Here we will see A business requirement, where employee’s pending item counts need to be updated in SharePoint. Here we focus on ‘Batch Update‘ of items in SharePoint at a time. In this blog,

Overview: Here we will see A business requirement, where employee’s pending item counts need to be updated in SharePoint. Here we focus on bulk Insert of items in SharePoint at a time. In this blog,