In this exercise we will learn how to combine HANA native artifacts, like calculation views, with SAP Cloud Application Programming Model (CAP).
Perform all the steps in 👉 tutorial: Create Calculation View and Expose via CAP (SAP HANA Cloud)
You've now experienced Calculation View development in the Business Application Studio. For some of you this might have been a big change from HANA Studio. For others coming from SAP Web IDE, the difference isn't really all that great.
But perhaps more importantly you now know how to create a CAP proxy entity to import an existing database artifact into CAP (and therefore also use it in the service layer). This can be done for database tables that weren't modeled in CAP or that come from another schema/container as well as SQL Views.
-
This was a very basic Calculation View and perhaps everyone in the room is already familiar with Calculation Views; but if new to the topic -- what is a Calculation View and how is it different from a SQL View?
-
Why did we change from a namespace to a context in steps three?
-
What is
@cds.persistence.existsdoing? -
What is
@cds.persistence.calcviewdoing?
- CAP - Using Native SAP HANA Artifacts
- SAP HANA Cloud, SAP HANA Database Modeling Guide for SAP Business Application Studio
- hana-cli inspectView
Continue to 👉 Exercise 7 - Create HANA Stored Procedure and Expose as CAP Service Function (SAP HANA Cloud)