In this part, we will discuss the Query operation and along with various query parameter exist in the OData.Basically, Query operation is for getting all the records, which is also known as Feed. For each entity set, there is a method called <entityset name>_GET_ENTITYSET . in the previous part (part Read more…
In Part 3, different artifacts in OData service are covered. In this part, we will check the implementation of the OData service and its Get Operation. As we know all the logic parts of the OData service are to be implemented in the DPC_EXT class. In the DPC_EXT class, there Read more…
As we have already gone through the basics of OData in Part 2 of the series, let’s focus on creating an OData service in the system itself. Let’s begin.To create an OData service/Project, you need to go to the transaction SEGW. or /n/IWBEP/SB. The Transaction will look like below To create a project, click Read more…
Before developing the OData service, let’s check the system configuration and its deployment options. So typically there are two deployment options that are Central Hub Deployment Embedded Deployment Central Hub Deployment OptionThere is basically two systems in the type of deployment option – one is for the Frontend System and Read more…
OData(Open Data Protocol) is a REST-based protocol. A Protocol will be called REST-based if it fits under certain constraints. Below is the list of constraints. Client-Server Architecture – Request from Client to server Statelessness – Meaning Request are not stored in the server Cachebility – Response is cacheable if define as cacheable Read more…