Question:
Hi,
I am currently building a new role in BW for report and query viewing and I get an error while trying to open a query saying "no authorisation for info providor xxx". Does anyone know if there is a new auth object the 7.0 needs to access workbooks or querys or what object might be missing from my role?
Thanks,
TMH
Answer:
Have you tried running transaction /nSU53 immediately afterwards? Then post the result here.....
_________________
We were somewhere around Barstow on the edge of the desert....
Answer:
SU53 in BEX?
Answer:
No Su53 is not available in BEX, but you should get an autorisation error pop up and when you click on the error a detailed error screen will pop up, this will exactly show what went wrong.
Answer:
No luck so far, the expanded message does not show what auth object failed. I just tells that an authorasation has failed.
Thanks,
TMH
Answer:
Nevertheless you should still be able to check the SU53 for the user concerned by logging on to the system through the gui. The SU53 should still be recorded in the event of an auth fail.
If that doesn't work you could perform a system trace in ST01 selecting authorisations only and filtering by user. Don't forget to switch off the trace afterwards.
MB
_________________
We were somewhere around Barstow on the edge of the desert....
Answer:
Just remember that ST01 does not always provide you with the full picture. If you have created custom authorization objects against infoproviders you need to enable the trace in RSSM too (think that is the one).
Answer:
Hello Markcus,
The authorizations in 7.0 have changed dramatically. SAP has come out with the new Analysis Authorizations where you can limit queries by the characteristic rather than the whole cube.
The new object that controls these authorizations is "S_RS_AUTH". The transaction used for maintaining the new authorizations is RSECADMIN. (You can also set up a user to trace with this transaction and view the su53-like results).
Hope this helps!