What are valid reasons to generate external SAP HANA Views for SAP BW/4HANA objects? Note: There are 2 correct answers to this question

Question

Options

• ATo leverage the SAP BW Analytic Manager to process BW Queries.
• BTo access data in the COLD tier of SAP BW/4HANA Data Tiering Optimization (DTO)
• CTo consume SAP BW/4HANA data and manage access with native SAP HANA concepts
• DTo apply SAP HANA transformational logic instead of SAP BW/4HANA logic.

• A
  4% (2)
• B
  2% (1)
• C
  94% (45)

Explanation

Generating external SAP HANA Views for BW/4HANA objects serves two key purposes: C allows non-BW tools (like SAP Analytics Cloud, third-party BI, or native HANA clients) to consume BW data while controlling access through HANA's own security model (roles, privileges), bypassing BW's authorization layer - ideal for HANA-native consumers. D is correct because external views expose data at the HANA layer, where HANA Calculation Views and other native transformational logic can be applied directly, rather than routing all logic through BW's transformation engine.

A is wrong because the Analytic Manager is precisely what processes BW Queries without needing external views - BW Queries already work natively through the BW stack. B is wrong because accessing the COLD tier (nearline storage in DTO) doesn't require generating external HANA views; DTO access is governed by BW's own nearline storage interface, not HANA view generation.

Memory tip: Think of external HANA views as "escaping the BW bubble" - you generate them when you want to either consume BW data with HANA-native tools (C) or process that data with HANA-native logic (D). If the action stays inside BW's own stack, external views aren't needed.

No community discussion yet for this question.