Your customer runs SAP BW/4HANA and would like to build an SAP BW Query on top of an existing native SAP HANA Calculation View. The BW Query should make use of an InfoObject which contains a…

Question

Options

• ACreate a CompositeProvider and associate the relevant field of the SAP HANA Calculation View
• BCreate a VirtualProvider and associate all fields of the SAP HANA Calculation View with SAP
• CCreate an external SAP HANA view for the SAP BW/4HANA InfoObject and combine this with the
• DCreate an Analytical Index and associate only the relevant field of the SAP HANA Calculation View

• A
  71% (12)
• B
  6% (1)
• C
  18% (3)
• D
  6% (1)

Explanation

Option A is correct because a CompositeProvider is the purpose-built BW/4HANA modeling object for bridging native SAP HANA Calculation Views with BW semantics - including InfoObjects that carry hierarchies. By associating only the relevant field of the Calculation View with the corresponding InfoObject in the CompositeProvider, you preserve hierarchy functionality while enabling BW Query consumption.

Option B is wrong for two reasons: VirtualProvider is a legacy BW concept not recommended in BW/4HANA, and associating all fields indiscriminately is not a valid or recommended design practice.

Option C is wrong because creating a separate external HANA view as an intermediary adds unnecessary complexity and is not the recommended pattern in BW/4HANA - the CompositeProvider was designed precisely to avoid this kind of workaround.

Option D is wrong because an Analytical Index serves a different purpose (optimizing query performance via search indexes), not as a modeling layer to expose Calculation View data with InfoObject hierarchies in a BW Query.

Memory tip: Think "Composite = Combine BW + HANA." Whenever you need to blend native HANA artifacts (Calculation Views) with BW semantics (InfoObjects, hierarchies, authorizations), the CompositeProvider is always the go-to in BW/4HANA.

No community discussion yet for this question.