In this exercise we will further combine SAP HANA Cloud native artifacts with the SAP Cloud Application Programming Model (CAP), and expose SQLScript procedures as service functions.
Perform all the steps in 👉 tutorial: Create HANA Stored Procedure and Expose as CAP Service Function (SAP HANA Cloud)
The goals of this exercise are vary similar to the previous one. Import and Expose an existing database artifact via CAP. But there are some major differences here for Stored Procedures. Unlike views they aren't exposed as entities but as functions or actions.
-
What's
SQLSCRIPT_SYNC? -
Why did we have to redeploy to the HANA Database after adding the Calculation View to the CAP service but didn't need to do the same when adding the Stored Procedure?
-
What's the difference between a function and an action?
-
Why did we use module CAP (https://cap.cloud.sap/docs/releases/archive/2022/mar22#driver-agnostic-results-for-stored-procedures) instead of
hdbdirectly to call the Stored Procedure? You can read more about it here.
- CAP - Using Native SAP HANA Artifacts
- SAP HANA Cloud, SAP HANA SQLScript Reference
- hdb module
- sap-hdb-promisfied module
Continue to 👉 Exercise 8 - Deploy CAP with SAP HANA Cloud project as MTA