You switch on the "External SAP HANA view flag in the settings for a Data Store object (advanced) and activate it. Which authorizations are used when you consume the SAP HANA view directly for…

Question

Options

• AThe existing Data Store object (advanced) analysis authorizations in SAP BW/HANA.
• BThe existing Data Store object (advanced) object authorizations in SAP BW/4HANA.
• CThe generated privileges in SAP HANA
• DThe generated authorizations for the HDI container access in SAP HANA

• A
  14% (8)
• B
  3% (2)
• C
  78% (45)
• D
  5% (3)

Explanation

When the External SAP HANA view flag is activated on a DSO (advanced), SAP BW/4HANA generates a native SAP HANA view along with corresponding generated SAP HANA privileges for that view. Since consumption happens directly in HANA - bypassing the BW stack entirely - it is these HANA-layer privileges that govern access, not any BW authorization objects.

Why the distractors are wrong:

• A is wrong because BW analysis authorizations (InfoObject-based) only apply when data is consumed through the BW reporting path, not via a direct HANA view.
• B is wrong because object authorizations in BW/4HANA control who can manage (transport, activate) the DSO itself, not who can read data through a HANA view.
• D is wrong because HDI (HANA Deployment Infrastructure) containers are a separate deployment mechanism used for CDS/XSA artifacts - the External HANA view is generated directly into the HANA catalog, not deployed via HDI.

Memory tip: Anchor it to the word External - the moment you go external (outside BW), you've crossed into SAP HANA's jurisdiction, so HANA's own generated privileges are what matter. "External = HANA privileges."

No community discussion yet for this question.