Forum Discussion
Helper ISAP BW Connector do not work with June update
Hello. I just tried July update and the problem is still not corrected. :(
GregoryDF, saguado, Mgfjd123, MatheusLPS
I m not from SAP background and do not understand the need for this parameter [ScaleMeasures=false] when connecting to Bex query as in
let
Source = SapBusinessWarehouse.Cubes(<server ip>, <system number>, <port number>, [ScaleMeasures=false]),Try removing it and see if scheduling works. It seemed to work for me.
- nikil
Resolver I
I removed ScaleMeasures=false and I am able to schedule refresh as well. I am not sure what ScaleMeasures does ?
:( It's still not working on my side.
In fact, it was working fine before the july update of the gateway and only PBI desktop was unable to update my SAP BW data.
About that, I checked with the SAP team here and it's caused by lack of authorizations on some tables. Below is the list Microsoft gave me:
RSTHIERNODE: only used when there are hierarchy node variables
• RSZGLOBV: only used when there are characteristic or hierarchy node variables
• RSDCHABAS: only used when there are characteristic or hierarchy node variables, and only if RSZGLOBV had values
• RSHIEDIR: only used when there are hierarchy node variables that point to external hierarchies (very unlikely)SAP security team is currently upgrading my security rights so it's not yet solved for me, but at least one of the admin tried to access the same tables as me with the July update of PBI Desktop and he was able to do it properly.
Hope it helps :)
Hello. Just an update to say that the problem is now solved for us, with the proposed solution (adding authorizations from BW security to the 4 tables to our roles).
Now it's working fine either in Desktop or Service.
And also, we had the problem with digits not loading properly, it can be set up in SAP Logon with transaction SU3 under number formating.
:) Now the last thing is that's it's very slow, but at least it's working :)
Yes even I noticed this thing. Quite strange, isn't it?
