Question Re: insufficient privilege: search table error: Authorization failed in Calculation Engine. in Technology Q&A

insufficient privilege: search table error: Authorization failed in Calculation Engine.

Former Member — Mon, 02 Nov 2020 06:43:40 GMT

Hi ,

We have created a source system (ODP - SAP HANA Information Views) in quality BW system(7.5 on HANA).

And when we execute the infopackage to read the data from HANA view as a source through the ODP source system, it always throws error:

insufficient privilege: search table error: [2950] exception 306003: Authorization failed in Calculation Engine. User is not authorized to 'SELECT'

We are aware that what privileges to be assigned and we are able to run in dev system.
We also tried to trace the user authorization but no log generated.

Here is the Flow:

1:Created RFC HANA_XYZ

2:Maintained user, which also has corresponding DB user (with the same user view can be executed in the HANA studio)

3:Maintained the source system

4:Tested the connection

5: After TR transport all the Data sources replicated successfully.

6: When execute the infopackage, it throws error.

am I missing any configuration?

Regards

Re: insufficient privilege: search table error: Authorization failed in Calculation Engine.

Tommaso — Wed, 01 Sep 2021 15:23:07 GMT

Hi,

Did you find a solution? Can you share it?

I'm facing the exact same problem.

Re: insufficient privilege: search table error: Authorization failed in Calculation Engine.

yoona_kim — Wed, 29 Sep 2021 15:52:39 GMT

Hi.

I am also facing the same issue.

Could you share how to solve it?

Thank you.

Re: insufficient privilege: search table error: Authorization failed in Calculation Engine.

Tommaso — Wed, 29 Sep 2021 16:08:42 GMT

Hi all,

We found a solution to our problem. We realize that the user connecting to the database was incorrect.

We identified it with the SQL statement CURRENT_USER but realize we should have checked the SESSION_USER. I'm still not sure about the difference and, in other system we worked on, the two were the same user, but not in this scenario.

Once we gave the correct role to the user the issue was resolved.

Hope this helps!