ODATA topics necessary for SAP Ui5 / FIORI

 

  • The main purpose of OData services is to implement ‘Database Functionalities’.

Types of OData services :-

  1. ODATA ABAP Service :- Interact with backend system of ( SAP ECC/CRM/SRM/SCM )
  2. ODATA HANA Service :- Interact with backend system ( SAP HANA ).
  3. ODATA External Services :- Interacts with backend system ( Non SAP system ).

ODATA ABAP Service :-

  • These OData services are mainly executed under SAP NetWeaver gateway component with database operations ( Select, Insert, Delete, Update ).
  • SAP NetWeaver gateway support two formats mainly
    1. XML format
    2. JSON format ( preferred because it is a light wight format )
  • From frontend if we indicate format with xml then SAP NetWeaver gateway component will hold the data under entity set in XML format.

Suppose, we have this employee Data

1001 Vijay 34

XML format



JSON Format



Advantages of OData Services :-

  • OData services are independent of frontend, these can be accessed in various front end apps like SAP Ui5 or FIORI, .NET, PHP etc.
  • OData services are reusable.
  • OData ABAP services will be developed under SEGW transaction code.
  • SEGW :- SAP NetWeaver gateway service builder tool.

Properties of OData service :-

  • Every OData service project contains mainly
    1. Data Model
    2. Service Implementation
    3. Runtime Artifacts
    4. Service Maintenance

1. Data Model :-

1. Entity Type :-

  • It is an option to maintain the collection of fields with data type and length.

2. Entity Type :-

  • Entity Type is similar to structure in normal ABAP.

3. Entity :-

  • Entity is an option to hold a single record at a time.
  • Entity is similar to work area in normal ABAP.

4. Entity Set :-

  • Entity Set is an option to hold the collection of records.
  • Entity Set is similar to internal table in normal ABAP.

5. Association :-

  • Association is the relationship between two entity types.

6. Association Set :-

  • Association is a relationship between two entity sets.

Note :-

  • Under single ODATA project we can have n number of entity type and entity sets.

2. Service Implementation :-

  • It mainly contains CRUD Methods.

    


3. Runtime Artifacts :-

  • Runtime artifacts mainly contains runtime classes ( which are auto generated ).

1. _MPC → Model Provider Class

2. _MPC_EXT → Model Provider Extension Class

3. _DPC → Data Provide Class

4. _DPC_EXT → Data Provider Extension Class

5. _SRV → Registered Service

6. _MDL → Registered Model

4. Service Maintenance :-

  • Error Log → To trace / find out error
  • Gateway Client :- Temporary screen to test ODATA service functionality.

Comments

Post a Comment

Popular posts from this blog

Understanding Different Types of SAP Function Modules: Normal, RFC, and Update

Image
  1. Normal/Regular Function Module :- It can be called inside the system. Here Pass by value + Pass by reference both is fine. 2. RFC Function Modules :- You can call from same system or from another possible. In RFC function module you can only have pass by value. In the same system if you are going to add the DESTINATION NONE’ while calling the RFC then it’ll be called in separate session. 3. UPDATE Function Modules :- This is generally used to update the database record. Update Function Module can be called from the same system. ( Background RFC / trfc / grfc ) This is used to achieve generally the SAP LUW. Some time we use from performance perspective also. When COMMIT WORK gets executed then Update starts getting executed. Important Questions on Update Function Modules :- When Update function Module gets Triggered ? ON COMMIT WORK IF a update function module gets failed, under which transaction we can see that ? OR What is the T-Code for moni
Read more

Unlocking SAP ABAP Secrets: Interactive Classical Reports with GET CURSOR, At User Command, and a Comparison of HIDE Statements

Image
 Welcome back everyone, We were discussing about the interactive classical reports, so let’s continue it. Interactive Classical Reports- GET CURSOR :- In Interactive Classical Reports, GET CURSOR statement is used to create secondary list according to cursor position. The parameter FIELD provides the name of an output field. The parameter VALUE provide the output value. Syntax : GET CURSOR FIELD <lv_field> VALUE <lv_value>. In the above syntax - the field name and field value will be returned in to variables lv_field and lv_value respectively. Requirement :- If you remember, In our last two blog, We have been displaying the order header table in a basic list and order item table in the secondary list. We have used SY-LISEL and HIDE statements to achieve the requirement. Now, we have to use the get CURSOR to achieve the same to same requirement. Code :- ************************************************************* *Start of Program *Declaring Strcutrure
Read more

Mastering ABAP: A Step-by-Step Guide to Function Modules and Groups for Modularized Programming

Image
  Function Modules :- It is a modularization technique. The transaction code to create a function module is SE37. To create a function module, we need to create a function group. Function Group :- Function group is a container for the function modules. The transaction code to create a function group is SE80. A function group can store up to 99 function modules. Requirement :- let’s create a function module for sum of two numbers. 1. Creation of function group :- Step 1 :- Go to SE80 transaction code → Object Navigator. Step 2 :- From the drop down select function group. Step 3 :- Give a name of function group. Step 4 :- press enter. Step 5 :- Click on yes a popup screen will appear. Step 6 :- Give short description → press enter → Assign package and transaction request and press enter. Step 7 :- Right click on function group and click on activate to activate the function group. Step 8 :- You will see two includes, will be added after ac
Read more