Go Coding

Category: ABAP

ABAP

  • $FILTER in SAP OData

    Preface – This post is part of the SAP ABAP OData Tutorial series.

    In this section, we will learn the concept of the $filter query in SAP OData and its usage.

    Supported System Version

    SAP NetWeaver Gateway Release 2.0 Support Package >=03

    Syntax

    http://<server>:<port>/sap/opu/odata/sap/<service_name>/EntitySet?$filter=ProductId eq ‘HP-101’

    Business Example

    The shopping site, say, Amazon is displaying all the products but you want some specific category to be displayed. So, you will apply filters (select category phones or laptops)  to display the data of your choice.

    Implementation

    In this section, we will implement $filter on our Product Entity Set.

    Step 1: After the creation of the OData service, right Click on Entity Set under Service Implementation, go to ABAP workbench.

    SAP OData Implementation

    Step 2:

    Adjust your code for $filter query.

    $FILTER in SAP OData

    The filter query option is available by accessing the parameter IT_FILTER_SELECT_OPTIONS.

    In the above code, we first retrieved the filter options passed from the frontend by reading IT_FILTER_SELECT_OPTIONS. And then passed the select-option range to BAPI to get the desired filtered output.

    Step 3:

    If we do not pass any filter option, we will get all the products from the system.

    Add $filter query in OData URL and execute the service. You can add one or more filter options.

    Service URL: /sap/opu/odata/sap/ZDEMO_GW_SRV_SRV/ProductsSet?$filter=Name eq ‘Notebook Basic 15.

     

    Operators used with $filter

    Logical Operators

    Logical Operator Description Example
    eq Equal https://<API-Server>/odata/v2/User?$filter=gender eq ‘F’ .
    ne Not Equal hhttps://<API-Server>/odata/v2/User?$filter=place ne ‘’London’
    gt Greater than https://<API-Server>/odata/v2/PicklistLabel?$filter=amount gt 200
    ge Greater than or equal https://<API-Server>/odata/v2/PicklistLabel?$filter=amount ge 200
    lt Less than https://<API-Server>/odata/v2/PicklistLabel?$filter=amount lt 200
    le Less than or equal https://<API-Server>/odata/v2/PicklistLabel?$filter=amount le 200
    and Logical and https://<API-Server>/odata/v2/PicklistLabel?$filter=amount le 200 and amount ge 300
    or Logical or https://<API-Server>/odata/v2/PicklistLabel?$filter=amount le 200 or amount ge 300
    not Logical not https://<API-Server>/odata/v2/PicklistLabel?$filter=amount le 200 not amount ge 300

     

    Arithmetic Operators

    Arithmetic Operator Description Example
    add Addition https://<API-Server>/odata/v2/PicklistLabel?$filter=amount add 5 gt 10
    sub Subtraction https://<API-Server>/odata/v2/PicklistLabel?$filter= amount sub 5 gt 10
    mul Multiplication https://<API-Server>/odata/v2/PicklistLabel?$filter= amount mul 5 gt 10
    div Division https://<API-Server>/odata/v2/PicklistLabel?$filter= amount div 5 gt 10
    mod Modulus https://<API-Server>/odata/v2/PicklistLabel?$filter= amount mod 5 gt 10

     

    Grouping Operators

    Grouping Operator Description Example
    ( ) Precedence grouping https://<API-Server>/odata/v2/PicklistLabel?$filter=(number sub 20) gt 30

     

  • SAP EML (Entity Manipulation Language) in RAP: Guide

    SAP EML (Entity Manipulation Language) in RAP: Guide

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    SAP Entity Manipulation Language (EML) is an ABAP language that is used to control the behavior of business objects in the context of the RESTful Application Programming model (also called SAP ABAP RAP). The business objects developed with the SAP ABAP RAP model can be consumed not only by OData protocol (Web API, Fiori UI) but also in ABAP using EML statements.

    There are two flavors of EML:

    • Standard API: Uses signature of business object entities
    • Generic API: Used for dynamic consumption of the business object

    The Generic API is used for the dynamic integration of business objects into other frameworks, such as the Cloud Data Migration Cockpit. Generic API is not in our scope. We will focus on Standard API’s.

    The Standard API’s are used when target business object is statically specified. It provides READ and MODIFY statements for the access of transactional scenarios of objects and COMMIT access for triggering save sequence. Using these syntaxes we will be able to perform the transactional behavior ( Create, Update, Delete, Actions, Read ) of business objects that are defined in Behaviour Definition.

    SAP EML Scenarios

    The following table gives you an overview of different SAP EML scenarios:

    Scenario Description Relevant EML statements
    Develop(BO with IN LOCAL MODE within its own behaviour pool) In EML develop scenario, when you provide the functionality for your own BO in its own behaviour pool, you use IN LOCAL MODE. It bypasses the access control, authorization control and feature instance control.  You can use it with CRUD and Actions. ·         READ/READ by ASSOCIATION

    ·         CREATE/CREATE BY ASSOCIATION

    ·         UPDATE/UPDATE BY ASSOCIATION

    ·         DELETE/DELETE BY ASSOCIATION

    ·         EXECUTE

    ·         AUGMENTING BY ASSOCIATION
    Consume (BO from other behaviour pool/ released objects) In consume scenario, you can use EML to consume other BO in or released BO’s. Here, you are not allowed to used IN LOCAL MODE. ·         READ/READ by ASSOCIATION

    ·         CREATE/CREATE BY ASSOCIATION

    ·         UPDATE/UPDATE BY ASSOCIATION

    ·         DELETE/DELETE BY ASSOCIATION

    ·         EXECUTE

    ·         GET PERMISSION

    ·         SET LOCK
    Test To test the BO outside of ABAP behaviour pool, you can use EML statements. Here, it is mandatory to add COMMIT statement to end RAP LUW. When in case of implementation inside behaviour pool, save it is done by the framework and we need not to write explicit COMMIT there. ·         READ/READ by ASSOCIATION

    ·         CREATE/CREATE BY ASSOCIATION

    ·         UPDATE/UPDATE BY ASSOCIATION

    ·         DELETE/DELETE BY ASSOCIATION

    ·         EXECUTE

    ·         GET PERMISSION

    ·         SET LOCK

    ·         COMMIT ENTITIES

    ·         ROLLBACK ENTITIES

     

    SAP EML Syntax

    SAP EML syntax has three major sections:

    • READ
    • MODIFY
    • COMMIT

     

    READ syntax

    READ is used to retrieve the data or you can say read the data of the entity. The syntax supports:

    • Read: Read the entity
    • Read by association: Read child entity using parent key

     

    Short syntax – 

    READ ENTITY

 EntityName [FIELDS ( field1 field2 ... ) WITH] | [FROM] it_instance

RESULT et_result

BY \association_name [FIELDS ( field1 field2 ... ) WITH] | [FROM] it_instance_rba

RESULT et_result_rba

LINK et_link_rba

[FAILED ct_failed].

where,

EntityName: specifies the CDS view entity

FIELDS: specifies the direct read for the given fields

RESULT: used to store the retrieved data in variable

LINK: used to store the key pair that is used for read by association operation

Failed: used to store the response about failed retrieve (key-value, fail cause etc)

    Long syntax-

    READ ENTITIES OF RootEntityName

ENTITY entity_1 " entity alias name [FIELDS ( field1 field2 ... ) WITH] | [FROM] it_instance_1

RESULT it_result

BY \association1_name [FIELDS ( field1 field2 ... ) WITH] | [FROM] it_instance_rba

RESULT et_result_rba

LINK et_link_rba

ENTITY entity_2_name " entity alias name [FIELDS ( ......

ENTITY entity_3_name " entity alias name

       ... [FAILED ct_failed].

    The long syntax allows you to club READ operation of multiple entities of Business Object specified by RootEntity name at one go. Also, we can use alias names of entities defined in Behavior Definition.

    Example: 

    READ ENTITIES OF /dmo/i_travel_m

ENTITY travel

FIELDS ( travel_id

  agency_id

                      customer_id

                      booking_fee

                      total_price

                      currency_code )

WITH CORRESPONDING #( keys )

RESULT DATA(ct_read_result)

FAILED DATA(ct_failed)

REPORTED DATA(ct_reported).

    MODIFY syntax

    MODIFY statement is used when we want to perform the change of data in entities. It includes:

    • Create
    • Create by association
    • Update
    • Delete
    • Execute (for Action)

    Short syntax-

    MODIFY ENTITY EntityName

CREATE [FIELDS ( field1 field2 ... ) WITH] | [FROM] it instance_crt

CREATE BY \association_name [FIELDS ( field1 field2 ... ) WITH] | [FROM] it_instance_cba

UPDATE [FIELDS ( field1 field2 ... ) WITH] | [FROM] it_instance_upd

DELETE FROM it_instance_del

EXECUTE action_name FROM it_instance_act

[RESULT et_result_a] [FAILED ct_failed] [MAPPED ct_mapped] [REPORTED ct_reported].

    Long syntax-

    MODIFY ENTITIES OF RootEntityName

ENTITY entity1_name CREATE [FIELDS ( field1 field2 ... ) WITH] | [FROM] it_instance1_crt

CREATE BY \association_name [FIELDS ( field1 field2 ... ) WITH] | [FROM] itinstance1_cba

UPDATE [FIELDS ( field1 field2 ... ) WITH] | [FROM] itinstance1_u

DELETE FROM it_instance1_del

EXECUTE action FROM it_instance1_act

[RESULT et_result]




ENTITY entity2_name

CREATE FROM it_instance2_crt

...




ENTITY entity3_name

... [FAILED ct_failed] [MAPPED ct_mapped] [REPORTED ct_reported].

    The long syntax allows clubbing multiple MODIFY operations of entities specified by RootEntity of the business object. We can specify alias names for entities if they are defined in behaviour definition.

    Example

    MODIFY ENTITIES OF /dmo/i_travel_m

ENTITY travel

CREATE FIELDS ( travel_id

   agency_id

   customer_id

   begin_date

   end_date

   booking_fee

   total_price

   currency_code

   description

   overall_status )

WITH lt_create

MAPPED ct_mapped

FAILED ct_failed

REPORTED ct_reported.

     

    COMMIT syntax

    The COMMIT syntax is used along with the MODIFY statement. As MODIFY statement does not change the data at database level, it is required to call COMMIT after MODIFY to persist the database changes.

    The modify statement set the data to transaction buffer and buffer data gets cleared after the ABAP session is closed. That means we need to trigger save sequence to save the data from the transactional buffer to the database. This trigger is called by executing the COMMIT statement. For save sequence methods you can refer to our previous articles.

     

    Simple syntax-

    COMMIT ENTITIES.

     

    Long syntax-

    COMMIT ENTITIES

   [RESPONSE OF rootentityname1

[FAILED ct_failed]

 [REPORTED ct_reported]]

[RESPONSE OF rootentityname2

[FAILED ct_failed]

[REPORTED ct_reported]].

    Using long syntax we can call COMMIT for multiple entities by explicitly specifying  RootEntity names. Whereas, the simple syntax COMMIT ENTITIES will also work for multiple entities in the same LUW. Here we need to specify the RootEntity name.

  • SAP ABAP RAP CRUD operation

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    To enable the CRUD operations in SAP ABAP RAP managed scenario, you need to enable the transactional behavior in Behavior Definition. There is no need to explicitly implement the CRUD operation in behavior implementation class, the RAP framework itself handles this.

    Steps for enabling CRUD in RAP Managed scenario

    1. Create CDS views
    2. Create Behavior Definition
    3. Enable transactional behavior of Business Object and activate.
    4. Test using EML (Entity Manipulation Language)

    Create CDS views

    Procedure

    1. Right-click on package
    2. Go to New >> Other Repository Objects >> Core Data Services >> Data Definition
    3. Provide the details (Name, Description).
    4. Select Next and provide the Transport Request number.
    5. Select Finish.

    Interface view SAP RAP

    Create Behavior Definition

    Procedure

    1. Right-click on root CDS view
    2. Select New Behavior Definition
    3. Provide the details (Name, Description).
    4. Select Next and provide the Transport Request number.
    5. Select Finish.

    Create Behavior Definition

    Enable transactional behaviour and activate

    Add transactional behaviour in Behavior Definition

    Test using EML

    In Report, implement EML statements to test the CRUD operations

  • OData Development using SAP ABAP RAP

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    In SAP ABAP RESTful Application programming, the business service is RESTful service which is called by end-users/customers. It consists of two parts: Service Definition and service binding. The service binding implements the protocol such as OData and the services to be consumed by customers. In this article we will learn OData development using SAP ABAP RAP.

    Steps for OData development using SAP ABAP RAP

    1. Create Service Definition
    2. Expose Services
    3. Create Service Binding
    4. Select service type as OData while creation. Click Finish.
    5. Activate service

    Create Service Definition

    Right-click on Package >> New >> Other Repositories Objects >> Service Definition.
    Provide the details to create a Service Definition.

    Create Service Definition

    Once the Service Definition is created, expose the required entities and activate it.

    expose the required entities

    Create Service Binding

    Right-click on Package >> New >> Other Repositories Objects >> Service Binding.
    Provide Package details, Name, Description and Service Definition name. Select the Binding Type as ODATA to create OData Service Binding.

    SAP RAP Create Service Binding

    Verify the information and click on activate.

    OData Publish SAP RAP

  • Service Consumption and Web APIs using SAP ABAP RAP

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    In this article, we will see how to create services in SAP RAP (RESTful Application Programming) and consume the same in UI5/Fiori using the given steps:

    1. Create service definition
    2. Expose entities in the Service Definition
    3. Create Service Binding
    4. Publish OData service
    5. Implement OData in UI5/Fiori

    Create Service Definition

    Right-click on Package >> New >> Other Repositories Objects >> Service Definition.
    Provide the details to create a Service Definition.

    SAP RAP Create Service Binding

    Once the Service Definition is created, expose the required entities and activate it.

    expose the required entities

     

    Create Service Binding

    Right-click on Package >> New >> Other Repositories Objects >> Service Binding.
    Provide Package details, Name, Description and Service Definition name. Additionally, select the Binding Type to create Service Binding.

    SAP RAP Create Service Binding

    Verify the information. To expose the service, click on activate.

    You can access the metadata details by following the Service URL provided in Service Binding. To preview the application, click on provided Preview button.

    OData Publish SAP RAP

    How to consume OData create by SAP RAP

    Like any other OData created by CDS or SEGW, the OData of SAP RAP can be used similarly in UI5/Fiori Applications. Read more about OData here.

  • Dealing with Existing Code in SAP RAP

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    This article will provide the step-by-step enabling of existing code in RAP. Using the steps below we will learn “Dealing with Existing Code in SAP RAP”.

    Steps:

    1. Create data model with CDS views
    2. Create Behavior Definition
    3. Add transactional behaviour in Behavior Definition
    4. Create Behavior Pool
    5. Implement transactional behavior of the existing application

    Create data model with CDS views

    Click here to follow step 1

    Create Behavior Definition

    Procedure

    1. Right-click on root CDS view
    2. Select New Behavior Definition
    3. Provide the details (Name, Description).
    4. Select implementation type as unmanaged
    5. Click Next and provide the Transport Request number.
    6. Select Finish.

    Create Behavior Definition SAP RAP

    Add transactional behaviour in Behavior Definition

    Add transactional behavior (Create/Update/Delete/Actions) of business objects.

    Add transactional behaviour in Behavior Definition SAP RAP

    Add transactional behaviour in Behavior Definition ABAP RAP

    Create Behavior Pool

    You can assign any number of behavior pools to behavior definition. Within a single global class, you can implement multiple local classes which defines the transactional behavior of the business object.

     

    Procedure

    Behavior Definition >> Right-click >> select New Behavior Implementation >> Provide details >> Finish

    Splitting implementation into different behavior pools

    Figure 1:Splitting implementation into different behavior pools

     

    Behavior Pool

    Figure 2: Behavior Pool

    When you go to Local Types in Behavior Pool, you can see below local classes.

    local classes in Behavioral Pool

    local implementation classes SAP RAP

    Within these local implementation classes, you can implement the business logic of existing behavior objects and test the end-to-end scenario using EML (Entity Manipulation Language) syntax.

  • Enabling the Transactional Behavior of an App in SAP RAP

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    This article will provide a step-by-step guide to enable the transactional behaviour of an application in SAP RAP.

    1. Create data model with CDS views
    2. Create Behavior Definition
    3. Add transactional behaviour in Behavior Definition
    4. Create OData service
      1. Create a Service Definition
      2. Expose CDS view
      3. Create Service Binding
      4. Publish OData service
    5. Application preview

    Create data model with CDS views

    Procedure

    1. Launch ADT (ABAP Development Tool).
    2. Select package for your development.
    3. Right-click on package and choose NEW > Other Repository Objects > Core Data Services > Data Definition.
    4. Provide the details (Name, Description).
    5. Select Next and provide the Transport Request number.
    6. Select Finish.
    7. Provide the data source name and add the elements in the CDS views.
    8. Provide the root statement to the top node as shown below.
      data model with CDS views
    9. Similarly, create consumption views and add required annotations.

     

    Result Screen

    Interface view SAP RAP

    Figure 1: Interface view

    Consumption view SAP RAP

    Figure 2: Consumption view

    Create Behavior Definition

    Procedure

    1. Right-click on root CDS view
    2. Select New Behavior Definition
    3. Provide the details (Name, Description).
    4. Select Next and provide the Transport Request number.
    5. Select Finish.

    Create Behavior Definition

    Add transactional behaviour in Behavior Definition

    Add transactional behaviour to Behavior Definition as shown below.

    Add transactional behaviour in Behavior Definition

    Create OData service

    a.       Create Service Definition

    Procedure

    1. Right-click on root CDS view
    2. Select New Service Definition
    3. Provide the details (Name, Description).
    4. Select Next and provide the Transport Request number.
    5. Select Finish.

    Create Service Definition

    b.      Expose CDS view

    Expose CDS view

     

    c.       Create Service Binding

    Procedure

    1. Right-click on Service Definition
    2. Select New Service Binding
    3. Provide the details (Name, Description).
    4. Select Next and provide the Transport Request number.
    5. Select Finish.

    SAP RAP Create Service Binding

    d.      Publish OData Service

    Publish OData Service SAP RAP

    Application Preview

    Fiori App SAP RAP

    Fiori Detail Page SAP RAP

     

  • How to create a SAP ABAP RAP Project

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    SAP ABAP RAP provides the intrinsic approach to build SAP Fiori based applications that are optimized for S/4 HANA and can run over on-premise as well as on the cloud. In this article we will learn how to create a SAP ABAP RAP Project.

    Prerequisites

    Before we start with the development of our first project using SAP ABAP RAP, we need a few things ready:

    SAP Cloud Platform ABAP Environment

    You should have access to and an account for SAP Cloud Platform ABAP Environment.

    Development Environment (IDE)

    • Install ABAP Development Toolkit (ADT).

    SAP recommends the latest version of the client installation. The download is available on https://tools.hana.ondemand.com/.

    • Access to and an account for the relevant space in SAP Cloud Platform Cloud Foundry.

    Authorization

    To create development artifacts, you need to have a developer role in the ABAP environment.

    Basic knowledge

    • ABAP Core Data Services (CDS)
    • ABAP Objects
    • ABAP Syntax

    Steps to create a SAP ABAP RAP Project

    1. Create an ABAP CDS View enabled with OData. Follow the steps mentioned here. This ABAP CDS View can be either basic, composite or consumption based upon the use case. The basic view is just a simple view created based upon ABAP table, the composite views are the ones that are created using multiple basic views or existing composite views. The consumption is the one that is consumed by the Fiori Apps (other views too can be consumed, it is created with final annotations such that UI5 has to call just this view and not the others).
    2. The very next thing that we create in ABAP RAP is a behavior definition. You can read the steps here. A behavior definition is an ABAP repository that represents the behavior of business objects in the context of SAP ABAP RAP. This is the place where we define the CRUD operations for the CDS Views.
    3. The last and important step is behavior Implementation. The steps to implement the same is mentioned here. This is the place where business logics are written.

    Thus in above steps we have created an ABAP CDS View, an ABAP OData, behavior definition and behavior Implementation.

    What is SAP RAP

    That’s it, this is how we create a SAP ABAP RAP Project. In our next articles, we will show you the implementation, step by step.

  • Developing Read-Only List Reporting Apps

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    Using persistent data sources, we are going to implement a query for the OData service to get an application with the read-only feature. This OData service will be consumed by the Fiori Element application.

    This article will provide the step-by-step guide to build a read-only list reporting application.

    1. Create data model with CDS views.
    2. Add associations to CDS views for navigation purpose.
    3. Add relevant annotations.
    4. Changing UI field labels and description
    5. Create OData service
      1. Create a Service Definition
      2. Expose CDS views
      3. Create Service Binding
      4. Publish OData service
    6. Application preview

    Create data model with CDS views

    Procedure

    1. Launch ADT (ABAP Development Tool).
    2. Select package for your development.
    3. Right-click on package and choose NEW > Other Repository Objects > Core Data Services > Data Definition.
    4. Provide the details (Name, Description).
      Create data model with CDS views
    5. Select Next and provide the Transport Request number.
    6. Select Finish.

    Result Screen

    An inactive version of the data definition is created. You need to provide the data source name and add the elements in the CDS views. Similarly, create all the required CDS views.

    Generated Template code

    Figure 2: Generated Template code

     

    Add associations to CDS views for navigation purpose

    1. Define association and cardinality
      Define association and cardinality
    2. Define mapping condition
      Define mapping condition
    3. Add association element list in CDS view
      Add association element list in CDS view

    Add relevant annotations

    Add required annotations to fields (see the below figure).

    ABAP CDS Annotation

    Changing UI field labels and description

    UI field labels and description allows you to customize your UI application. You can add text annotation (@ObjectModel.text.association:'<_AssocToTextProvider>’),value help (@Consumption.valueHelpDefinition: [{ entity: { name: ‘<target_view>’ , element: ‘<target_element>’ }}]), search capability ( @Search.searchable: true ) and as many functionality to your field element.

    Changing UI field labels and description

    Create OData service

    a.       Create a service definition

    In service definition, we will expose our data models.

    Procedure

    1. Launch ADT (ABAP Development Tool).
    2. Select package for your development.
    3. Right-click on package and choose NEW > Other Repository Objects > Business Service > Service Definition.
    4. Provide the details (Name, Description).
      Create a service definition
    5. Select Next and provide the Transport Request number.
    6. Select Finish.

     

    b.      Expose CDS views

    In service definition, add the CDS view that you want to expose to UI. You can provide an alias also for the same. Once the CDS views are exposed, activate the service definition.

    Expose CDS views

    c.       Create Service Binding

    In service definition, we will expose our data models.

    Procedure

    1. Launch ADT (ABAP Development Tool).
    2. Select package for your development.
    3. Right-click on the package and choose NEW > Other Repository Objects > Business Service > Service Binding.
    4. Provide the details (Name, Description).
      Create Service Binding
    5. Select Next and provide Transport Request number.
    6. Select Finish.

    When you open the created service binding from editor you can see the below screen. As soon as the service binding is created, it is registered in your local system.

    Activate the service binding

    Activate the service binding and it is ready for consumption.

    d.      Publish OData service

    Once you activate the service binding, the OData service is published and is activated in SAP Gateway. Now it can be consumed by UI5 application.

    Publish OData service

    The service URL on the right side will provide the metadata information of OData service. Preview button will navigate you to the resulting UI service.

    Application preview

    The resulting UI5 application will look like this:

    Application preview

  • Introduction to ABAP CDS Views

    Preface – This post is part of the SAP ABAP RAP series.

    Introduction

    SAP ABAP CDS View is used for defining and consuming semantic data models on standard tables or dictionary views. The abbreviation for CDS is Core Data Services. Although SE11 dictionary view and CDS views both create database views at the backend, the ABAP CDS view supersedes the dictionary view in so many ways.

    Difference between dictionary view and CDS View

    Dictionary View CDS View
    Can be created from SAP GUI or Eclipse. Can only be created from Eclipse or SAP HANA Studio.
    Cannot define Annotations. Annotations are provided to enrich metadata.
    Aggregation is not possible. Can provide Aggregation function.
    Grouping is not possible. Grouping can be provided.
    Join can be used. Join and Union both can be used
      Case Expressions can be used.
      Input parameters can be allowed for filtering data and column calculations
      Operators can be used.

    CDS view Types

    There are three different VDM view types:

    • Basic view
    • Composite view
    • Consumption view

    CDS view Types

    Figure 1: CDS view types

    1.      Basic View

    VDM Basic views are created on the top of DDIC tables or views. It is the only view that interacts directly with the database.

    Annotation: @VDM.Viewtype : #BASIC

    Properties for Basic View:

    1. Basic views can directly access the database tables and other basic views.
    2. They have an association with other basic views.
    3. Free of redundancies.
    4. They expose all business data.

     

    2.      Composite view

    The composite view is created on top of the VDM Basic view. It interacts with Basic views for the result set and does not interact with the database directly.

    Annotation: @VDM.Viewtype : #COMPOSITE

    Properties of Composite View:

    1. They can access other Composite views but not database tables.
    2. They can have an association with other composite views and basic views.
    3. Redundancies might be possible.
    4. They should be reusable.

     

    3.      Consumption view

    The consumption views are built on top of Interface views. By the name Consumption, we can assume that this view is meant to be consumed by SAP UI5 through OData, Analytical queries, Transactional service models.

    Annotation: @VDM.Viewtype : #CONSUMPTION

    How to create CDS views in ADT?

    To create a CDS view follow the below steps:

    1. Navigate to New ABAP Repository.
      New ABAP Repository
    2. Select Data Definition.
      Select Data Definition
    3. Provide Package, Name, Description of CDS view.
    4. Now from the given options, select Define View.
      Define View
    5. Define data source name, SQL view name, required annotations and other properties.
      Define data source name
    6. Define data selection Query.
      Define data selection Query
    7. Save and activate.

    How to view the data from CDS Views?

    1. In the DDL source object, navigate to your CDS view.
    2. Right-click and select OPEN DATA PREVIEW. Also, you can open the CDS view and press F8 to view the data.
    3. The output will show you the retrieved data from CDS View.

    Tutorial Video

    You can watch the video below to learn implementation:

    [embedyt] https://www.youtube.com/watch?v=CwWbauSyD4s[/embedyt]