What to check
Access through an external HANA view involves a database identity and authorization context that must be checked separately from a BW frontend session. An insufficient-privilege message can include a diagnostic identifier useful to the HANA administrator. A successful test with a powerful technical user does not validate the intended user's access.
Troubleshooting steps
- Capture the full error, diagnostic identifier if supplied, view name, connection, effective HANA user, and failure time.
- Have the HANA and BW security owners inspect the relevant privilege diagnostics, user mapping, and supported generated authorization setup.
- Correct the specific approved assignment or generation issue using release-appropriate procedures, then retest with the original user and expected data restrictions.
Confirm the result
Verify both allowed and prohibited selections. Avoid broad grants, unrestricted analytical access, or manual edits to generated authorization artifacts as a shortcut.
References
The SAP KBA link provides a public symptom preview; its full resolution requires SAP Support access. These diagnostic steps are independent guidance. Check the installed release before applying a correction.