In the context of SAP BW/4HANA, what is the primary purpose of embedding Core Data Services (CDS) views? Please choose the correct answer.

Question

Options

• ATo enable transactional processing
• BTo facilitate agile data modeling
• CTo provide native HANA data access
• DTo replace the BEx Query functionality

• A
  2% (1)
• B
  89% (57)
• C
  6% (4)
• D
  3% (2)

Explanation

Embedding CDS views in SAP BW/4HANA is primarily about agile data modeling because CDS views enable a code-first, declarative approach to building analytical models directly in the HANA layer - allowing modelers to iterate rapidly, reuse models across scenarios, and align data structures with business needs without the rigidity of traditional BW InfoProviders.

Why the distractors are wrong:

• A (transactional processing): BW/4HANA is purely an analytical/data warehousing platform - CDS views are read-optimized and have no role in transactional CRUD operations.
• C (native HANA data access): While CDS views do run natively on HANA, that's a characteristic, not their purpose within BW/4HANA. Native HANA access is better associated with features like Smart Data Access or Open ODS Views.
• D (replace BEx Query): CDS views operate at the data modeling layer, not the query/reporting layer. BEx Query functionality remains a separate concern handled by the OLAP engine.

Memory tip: Link CDS → Agile by thinking "CDS = Change Data Swiftly" - the whole point is the flexibility to model and remodel quickly, which is the essence of agile data modeling.

No community discussion yet for this question.