What are some of the reasons to choose the CUBE data category instead of DIMENSION data category for an SAP HANA calculation view? (3)

Question

Options

• APersist transactional data
• BCreate restricted columns
• CProvide default time characteristics
• DAggregate measures as a sum
• ECombine master data and transactional data

• A
  71% (20)
• B
  21% (6)
• C
  7% (2)

Explanation

CUBE is the right choice when your calculation view needs to handle fact/transactional data with aggregatable measures. Options A, D, and E all describe CUBE's core strengths: it is purpose-built to persist transactional (fact) data, it enables measures to be aggregated via functions like SUM, and it supports star-schema style joins that blend master data with transactional data in a single view.

B is wrong because creating restricted columns (attribute-level restrictions) is a feature associated with the DIMENSION category, which models master/attribute data - not a reason to choose CUBE over it.

C is wrong because default time characteristics are provided by DIMENSION views (specifically time dimension views), not CUBE views. CUBE consumes those time dimensions; it doesn't generate them.

Memory tip: Think "CUBE = Facts + Figures" - it's for transactional Facts (A), aggregatable Figures/measures (D), and mixing both fact and master data in one place (E). If your view has no measures and is purely descriptive attribute data, that's a DIMENSION.

No community discussion yet for this question.