Modeling
HANA modeling means building reusable views, especially calculation views, that shape and combine data for consumption by applications and analytics. Modeling is how you turn raw tables into meaningful, high-performance information on HANA.
Models are consumed by Fiori/analytics via OData, by reporting tools (SAC), and by ABAP.
- Rather than querying raw tables directly, you build views that join, filter, aggregate and enrich data, then applications and…
- Good models are layered and reusable, base views close to tables, composite views on top, so logic is defined once and reused.
- Calculation views: the current, flexible standard (graphical or SQLScript).
- Watch out: Querying raw tables instead of reusable views.
What modeling is
Rather than querying raw tables directly, you build views that join, filter, aggregate and enrich data, then applications and reports consume the views. On HANA the modern modeling artifact is the calculation view (and, in the ABAP world, CDS views), designed to run efficiently in the HANA engine.
Types of views (historical to modern)
- Calculation views: the current, flexible standard (graphical or SQLScript).
- (Legacy) Attribute & analytic views: older types now unified into calculation views.
- CDS views (ABAP): the SAP-application modeling layer, executed on HANA.
Modeling principles
Good models are layered and reusable, base views close to tables, composite views on top, so logic is defined once and reused. Push filtering and aggregation as low as possible, and design for the consumption pattern (transactional lookup vs analytical aggregation).
Consumption
Models are consumed by Fiori/analytics via OData, by reporting tools (SAC), and by ABAP. In S/4HANA, CDS is the primary modeling layer for application data, while native calculation views serve broader HANA use cases.
Common pitfalls
- Querying raw tables instead of reusable views.
- Monolithic views instead of layered, reusable ones.
- Aggregating late instead of pushing it down.