CDS – nocin.eu

CAP

[CAP] Fiori Elements – Add i18n label for bound action

October 8, 2025 October 24, 2025

It took me some time to figure out, how I can provide a label for an action parameter.

I try to separate all my translations in label.cds file. This means, the annotations are not placed where the entities or actions are defined. If you have the action definition and the label annotations in one file, you could simply do the following for an action:

trip-service.cds

    entity Trip as projection on db.Trip
        actions {
            action approval();
            action rejection(reason: String @title: '{i18n>reason});
        };

But if you separate both, you need to access somehow the defined action to add the annotation. Following a short snippet, how it works. The important part is, that you have to write a complete new annotation block for your actions.

trip-service.cds without label

service tripService @(requires: 'authenticated-user') {

    entity Trip as projection on db.Trip
        actions {
            action approval();
            action rejection(reason: String);
        };

}

label.cds

using my.namespace as db from '../db/index';
using tripService from '../srv/trip-service';

annotate db.Trip with @title: '{i18n>trips}' {
    description   @title      : '{i18n>description}';
    status        @title      : '{i18n>status}';
    // etc.
}

// solution
annotate tripService.Trip actions {
    rejection(reason @titlel: '{i18n>reason}' )
}

CAP

[CAP] Select exists

March 25, 2024 March 25, 2024

So far I have not found a better/shorter way to check if a table entry exists than the following:

let exists = await SELECT(1).from(Books,201)
return (exists .length > 0) ? true : false

Found here: https://cap.cloud.sap/docs/node.js/cds-tx#cds-tx-ctx-fn

CAP

[CAP] Get ID for newly created entry in a table defined with aspect cuid

October 18, 2022 May 9, 2023

https://cap.cloud.sap/docs/cds/common#aspect-cuid

https://cap.cloud.sap/docs/node.js/databases#insertresult-beta

const result = await INSERT(payload).into(table)
const newEntries = [...result]

console.log("New ID: " + newEntries[0].ID)

SAP Cloud Platform ABAP Environment

[ABAP Env] Create Data Model & OData Service

March 27, 2020 March 28, 2020

Recently I worked through the tutorial on creating a travel bookings app in the SAP Cloud Platform ABAP Environment.

Find a good introduction and overview on this topic here: Getting Started with ABAP in the Cloud – Part I
And the travel bookings app tutorial here: Getting Started with ABAP in the Cloud – Part II

These are my notes on the steps needed to create the data model and publish it as oData service.

#	Layer	Nomenclature	Description
1	Database Table	ZTABLE	Place your raw data first
2	Data Definition (Interface View)	ZI_	Relation between different tables (e.g. currency or text table)
3	Projection View (Consumption View)	ZC_	Configure the UI depending on your scenario. Use different projection views for different usages of the same interface view and the same physical table.
4	Service Definition	ZSD_	Expose the projection view (and underlying associations like currency, country…) as service
5	Service Binding	ZSB_	How to we want to make the service available? Defines the binding type (OData V2 / OData V4) Activate it with the “Activate” Button within the editor window. Select the Entity and hit “Preview…” to see whtat we defined in our projection view.

If you’ve done this, you are able to view the data in a generated Fiori Elements app. But if you also want to create, edit, delete data, you’ll have to add some behavior functionality.

6	Behavior Definition on Data Definition	ZI_	Created on top of the Data Definition. Will get the same name es the Data Definition. Implementation Type: Managed Defines the operations create, delete, edit.
7	Behavior Implementation on Definition View	ZBP_I_	The code for the behavior… For the travel app tutorial, some logic for a generated unique key and field validation. The class inherits from cl_abap_behavior_handler.
8	Behavior Definition on Projection View	ZC_	Created on top of the Projection View. Will get the same name es the Projection View. Defines the operations create, delete, edit.