CDS based Analytical oData for Fiori

During my developments I found that analytical oData services (or maybe to be more precise "analytical entitysets" within oData services) are needed quite often but it's not very well documented what options can be used to create them. In most of the official literature you will find oData generated on top of "analytical query" but this option is not supported in Restful ABAP programming model and makes some stuff (like adding additional entitysets in the same service) difficult.

As a first thing let's explain "analytical oData" on a very simple example and probably most common scenario: you have some kind of document item which has for example Supplier, Company Code, Fiscal Year, Amount with Currency code and Quantity with Unit. And you perhaps need to get the "sums" of amounts and quantities on different levels

Fiori Adoptation Project for Extending Standard Fiori Application for onPremise using BAS

Prerequisites:

◉ On BTP: Cloud Connector Connection to Gateway system and Destination 

◉ OnPremise: Activating required standard Fiori Application

Step 1: Open Template Wizard and select the application type as SAP UI5 Adoptation Project.

SAP ABAP RAP: Custom Entities with compositions relationship in a Fiori Elements App

Introduction:

ABAP Restful Application Programming is an efficient and cloud-compatible development model that enables rapid creation of Fiori apps.

This programming model facilitates both Managed and Unmanaged Implementation approaches, although the core data source must originate from a CDS view or a table within the same system in both scenarios. However, the non-key fields can be calculated on the fly using virtual elements.

When retrieving data from a remote source through an API or performing complex calculations, managing CDS view entities becomes challenging. Further complexities arise when compositions  are involved.

ABAP RAP: Side Effects in CDS Behavior Definition and its variants

Introduction

 

​The most awaited feature was released for SAP BTP – ABAP Environment in 2302. It is none other than ‘Side effects in CDS Behavior Definition’.

I have been waiting for this feature and can’t stop myself from trying it. I thought the syntax would be complicated and was surprised when I realized they were so simple and readable.

​​​Side effects are useful in UI scenarios based on draft-enabled BOs to notify a Fiori Elements UI that data changes of defined fields require the recalculation of other data values, permissions or messages.​

How to use Side Effects in ABAP RAP (Restful Application Programming) Model

In this beginner blog post we are going to see how we can use Side Effects in ABAP Restful Application Programming Model.

What is Side Effects:

When user makes a change to a field on UI, and this change effect the content of other field, this behavior is called Side Effect.

Annotation to Implement Side Effects:

Some more annotation properties are available but for this demo we are only using below 2 Annotations properties.

ABAP RAP – Global Authorization

In this beginner blog post we are going to see how we can use Authorizations (Global Authorization) in ABAP Restful Application Programming Model.

What is Authorization in RAP

Authorization control in RAP protects your business object against unauthorized access and operations (Create, Update, Delete). Authorization control is always relevant when the permission to execute an operation depends on the role.

In RAP each read or modify request can be checked via authorization objects against user roles before the request is finally executed.