nerdexam
SAP

E_BW4HANA214 · Question #21

You would like to implement a virtual mixed scenario in your SAP BW/4HANA system.Which approach does SAP recommend for this kind of scenario? Note: There are 3 correct answers to this question

The correct answer is B. Generate external SAP HANA views of SAP BW/4HANA Info Providers to consume this SAP C. Load SAP HANA data into SAP BW/4HANA Info Providers based on the Operational Data D. Model a Composite Provider that combines data from multiple SAP BW/4HANA Info Providers and. In SAP BW/4HANA, a virtual mixed scenario combines persistently stored BW/4HANA data with virtually accessed SAP HANA data at query time. Options B, C, and D represent the three SAP-recommended pillars of this pattern: B generates external HANA views from BW/4HANA InfoProviders…

Native SAP HANA Integration

Question

You would like to implement a virtual mixed scenario in your SAP BW/4HANA system.Which approach does SAP recommend for this kind of scenario? Note: There are 3 correct answers to this question

Options

  • AModel a Data Store object (advanced) and use an ABAP CDS View for virtual access.
  • BGenerate external SAP HANA views of SAP BW/4HANA Info Providers to consume this SAP
  • CLoad SAP HANA data into SAP BW/4HANA Info Providers based on the Operational Data
  • DModel a Composite Provider that combines data from multiple SAP BW/4HANA Info Providers and
  • EDefine an Open ODS View that integrates an SAP HANA table into SAP BW/4HANA

How the community answered

(27 responses)
  • A
    11% (3)
  • B
    85% (23)
  • E
    4% (1)

Explanation

In SAP BW/4HANA, a virtual mixed scenario combines persistently stored BW/4HANA data with virtually accessed SAP HANA data at query time. Options B, C, and D represent the three SAP-recommended pillars of this pattern: B generates external HANA views from BW/4HANA InfoProviders so native HANA can consume them; C physically loads HANA data into BW/4HANA InfoProviders via the ODP framework, making it managed BW data; and D uses a CompositeProvider - the core BW/4HANA blending object - to combine persistent InfoProviders with virtual SAP HANA views in a single query layer. Together they cover both directions of data movement and the federation/combination step that defines the "mixed" architecture.

Why A is wrong: A DSO (advanced) paired with an ABAP CDS View is a valid modeling technique, but ABAP CDS Views are primarily an S/4HANA embedded analytics construct - not the SAP-recommended tool for virtual access within a BW/4HANA mixed scenario.

Why E is wrong: An Open ODS View does provide virtual access to HANA tables, but on its own it only creates a pure virtual integration, not a mixed one. It's an ingredient that could feed into a CompositeProvider (D), but it alone does not implement the full mixed scenario.

Memory tip: Think BCD = "Bring, Collect, Design" - Bring BW data out to HANA (generate views), Collect HANA data into BW (ODP load), Design the blend (CompositeProvider). The mixed scenario needs both data directions plus a combiner.

Topics

#virtual mixed scenario#Composite Provider#Open ODS View#External HANA Views

Community Discussion

No community discussion yet for this question.

Full E_BW4HANA214 Practice