If you intend to reveal your SAP Data (Table or Query Data) to an external environment such as UI5/Fiori or HANA, you must push your data via API. By API, we imply that we might create a provider link utilizing OData which can be accessed via the internet and used to perform CRUD operations. SAP OData behaves similarly to any other ABAP Class in a SAP ABAP environment.By using SEGW transaction, designers can obtain the methodologies of this class. We can start writing the necessary code for manipulating data here, and once we initiate the class, the service link which we generate will function properly.
SAP OData is indeed a standard Web protocol for querying and updating data in SAP using ABAP, utilizing and expanding on Web technologies such as HTTP to provide access to information from a wide range of external applications, platforms, and devices.
Want to Become a Master in SAP Success Factors? Then visit here to learn SAP Success Factors Certification Course from hkrtrainings!
Architecture of SAP Odata:
In this section, we will go over the high-level architecture of SAP OData.
SAP OData has numerous advantages. It not only allows us to expose data, but it also allows customers to access data from any location and device. If there are no OData services, the data will remain on-premise, and if a user needs to access their data, they may have to physically visit the data location, which is inconvenient for the digital world.
Related Articles what is SAP SD !
Using SAP OData provides us with the following benefits:
SAP Odata V2 Version:
OData v2 is a set of new standards that are extensions to SAP OData V1. These are as follows:
SAP Odata V4 version:
OData v4 is the most recent upgrade to the SAP OData services, and it includes some new and some reduced features, such as:
Now we will learn how to perform Odata query and crud operations in Odata.
Now we must learn how to read a table using an OData Query as well as perform operations on that table such as Insert, Update, and Delete. In this article, we will also learn about basic data reading queries.
In the odata there are mainly 3 phases of data transfer. They are:
Data is sent from UI (Client) to OData (Server) in form of query
At OData we receive data from Frontend using data provider (Code implemented in CRUD Operation section)
io_data_provider->read_entry_data(IMPORTING es_data= ls_entity).
After manipulating data, we send information from OData to UI using et entityset or er entity (Code implemented in CRUD Operation section)
Operations in Odata:
SAP ABAP OData provides several methods for performing CRUD operations, which are as follows:
Querying in SAP Odata:
Throughout this section, we will look at all of the queries that can be run while reading data from OData. We learned how to read calls with GET ENTITY and GET ENTITYSET in the preceding section. Sometimes we need to filter out data based on our needs, or get the total number of data counts, or get data in a specific order. All of these SAP OData Queries are explained below:
In this blog post we had discussed the sap odata, sap odata architecture, and how it works to perform various crud operations.Had any doubts please drop them in the comments section.
Batch starts on 10th Jul 2022, Weekend batch
Batch starts on 14th Jul 2022, Weekday batch
Batch starts on 18th Jul 2022, Weekday batch