Create Database Artifacts Using Core Data Services (CDS) for SAP HANA Cloud

The SAP Cloud Application Programming model utilizes core data services to define artifacts in the database module. Because this model is meant to be database-agnostic – i.e., work with any database – it does not allow you to leverage features that are specific to SAP HANA Cloud. For this reason, you will also create two tables that do not require any advanced data types.

1. In the db folder, right mouse click and choose New File

   

2. Use the following name:

   Name

   Copy

   interactions.cds
   

   

3. Use the following content in this new file:

   CAP CDS

   Copy

   namespace app.interactions;
   
   using {
       Country,
       Currency,
       cuid,
       managed
   } from '@sap/cds/common';
   
   type BusinessKey : String(10);
   type Price       : Decimal(10, 2);
   type Text        : String(1024);
   
   entity Headers : cuid, managed {
       items   : Composition of many Items
                     on items.interaction = $self;
       partner : BusinessKey;
       country : Country;
   };
   
   entity Items : cuid {
       interaction : Association to Headers;
       text        : localized Text;
       date        : DateTime;
       @Semantics.amount.currencyCode: 'currency'
       price       : Price;
       currency    : Currency;
   };
   

   What is going on?

   You are declaring two entities with relationships between each other. The design-time artifacts declared in this file will be converted to run-time, physical artifacts in the database. In this example, the entities will become tables.

4. We are using a reusable set of content (lists of countries, currencies, etc) provided by SAP in the above model. We also have to add this dependency to our project. From the command line issue the following command to do so:

   shell

   Copy

   npm add @sap/cds-common-content --save
   

1. In the srv (**not src!**) folder create another file and name it interaction_srv.cds

   Name

   Copy

   interaction_srv.cds
   

   

2. Use the following content in this new file:

   CAP CDS

   Copy

   using app.interactions from '../db/interactions';
   using {sap} from '@sap/cds-common-content';
   
   service CatalogService {
   
       @odata.draft.enabled: true
       entity Interactions_Header as projection on interactions.Headers;
   
       entity Interactions_Items  as projection on interactions.Items;
   
       @readonly
       entity Languages           as projection on sap.common.Languages;
   }
   

3. Save all.

   What is going on?

   You are declaring services to expose the database entities you declared in the previous step.

4. From the terminal issue the command: cds build --production

   shell

   Copy

   cds build --production
   

   

5. Look into the console to see the progress. You can scroll up and see what has been built

   

1. If you pay attention to the build log in the console, you will see the CDS artifacts were converted to hdbtable and hdbview artifacts. You will find those artifacts in a new folder under /gen/db/src called gen.

   

2. You will now deploy those objects into the HANA Database creating tables and views. We will use the SAP HANA Projects view to do this. Please expand this view and you will see the following:

   

3. We need to bind our project to a Database Connection and HDI container instance. Press the bind icon to being the process.

   

4. If you receive either of these two following warning dialogs, please just choose Continue (nothing will be deleted because we are create a new HDI Container Instance) and Enable (automatic undeploy is quite helpful during the development process for the reasons described in this dialog)

   
   

5. The bind process will start a wizard where you will be prompted for values via the command pallet at the top of the SAP Business Application Studio screen. You might be asked to confirm your Cloud Foundry endpoint and credentials depending upon how long it has been since you last login.

   

6. Your first choice will be for the binding option. Choose Bind to an HDI container.

   

7. You might be presented with options for existing service instances (if you’ve completed other tutorials or have performed other HANA development). But for this exercise we want to choose Create a new service instance

   

8. To make subsequent steps easier, shorten the generated name to MyHANAApp-dev + a group number or your initials if you are doing this tutorial as part of a group workshop/shared environment. This makes sure that everything remains unique per participant. Remember the value you used here and adjust the name in the subsequent steps. The remaining screenshots will always just show the base name.

   

9. It will take a minute or two for the service to be created in HANA. A progress bar will be shown in the message dialog

   

10. Sometimes the binding step fails due to a timing issue. If so simply repeat the binding but this time do not create a new container name but select the existing HDI container that has been created from the previous attempt MyHANAApp-dev

11. Upon completion, the Database Connections will now show the service bound to the instance the wizard just created.

    

12. We are now ready to deploy the development content into the database. Before you go ahead, we recommend that you increase the default number of scrollback lines in the integrated terminal, if you’re using a Dev Space in SAP Business Application Studio. This is because there are many lines of log output about to be generated and you will want to see them all. So use menu path File -> Preferences -> Settings and search for the “Terminal › Integrated: Scrollback” setting. Set the value to 10000. Now, once you’ve done that, you’re ready to deploy. Press the Deploy button (which looks like a rocket) at the db folder level in the SAP HANA Projects view.

    

13. Scroll up to in the console to see what the build process has done.

What is going on?

CDS stands for Core Data Services. This is an infrastructure that allows you to create persistency and services using a declarative language. Notice how you are using the same syntax to define both the persistency and the services.
 
You can find more information on CDS in the help

You defined a CDS artifact, this is an abstraction, a design-time declaration of the entities to be represented in a database and the services to expose them.
 

The original .cds file was translated into hdbtable, which is the SQLDDL syntax specific to SAP HANA when you saved all of the files.
 

These hdbtable files were then translated into runtime objects such as tables in the HANA database.

If you checked the services in your space, you would see the service for your HDI container.

You can find a similar example and further context on Core Data and Services in this explanatory video

You can now check the generated tables and views in the Database Explorer.

1. In the SAP HANA Projects view, press the Open HDI Container button

   

2. The Database Explorer will open in a new browser tab and automatically select the database entry for your project’s HDI container.

3. Once open, navigate to the Tables section and click on the Header table.

   

4. Note the name of the table matches the generated hdbtable artifacts. You will also see the physical schema managed by the HDI container.

   Unless a name is specified during deployment, HDI containers are automatically created with names relative to the project and user generating them. This allows developers to work on different versions of the same HDI container at the same time.
   

   

1. Download the header file and the items file and the texts file into your local file system.

2. Right-click again on the header table and choose Import Data.

   

3. Choose Import Data and press Step 2

   

4. Choose Local for the Import Data From: option. Browse for the Header file and click Step 3.

   

5. Keep the default import target and click Step 4.

   

6. Keep the default table mapping and press Step 5.

   

7. Keep the default error handling and press Review

   

8. Choose Import into Database.

   

9. You will see confirmation that 4 records have imported successfully.

   

10. Repeat the process with the app.interactions-Items.csv and app.interactions-Items.texts.csv files into the ITEMS and ITEMS_TEXTS tables.

    1

    

1. You can now check the data loaded into the tables. Right-click on the Items table and click Generate Select Statement.

   

2. Add the following WHERE clause to the SELECT statement and execute it to complete the validation below.

   SQL

   Copy

   where "TEXT"  like '%happy%';