SAP Business Warehouse - Key Figure Multiplied by 100K Based on User Account

[Anonymous]

This doesn't appear to be a Power BI issue but I'm hoping that someone has ran into this issue as I can only recreate this issue with Power BI. We have a BEx query that we are consuming and its basically multiplying the value x 100,000. An example would be a sales order qty of 450 shows up as 450 for all users but 1, that user see's 45,000,000. On that users machine, if I change the database credentials to any other user the value will change from 45M to the correct value of 450 (Within Power BI)

We've tested this on multiple machines with multiple user ID's in order to confirm that its the user's ID and not the version of Power BI, Computer, etc. 

We've looked at the users profile data (SAP GUI) and it matches everyone else's. Also keep in mind when this user runs the BEx query in Analyzer they get they correct value of 450. 

So while I don't believe its a Power BI issue, Power BI is the only place we can recreate the issue and we still can't figure out what could be causing this issue. I'm hoping that someone else has experienced a similiar issue and found a resolution. 

Thanks

[Eric_Zhang]

---

@Anonymous wrote:

This doesn't appear to be a Power BI issue but I'm hoping that someone has ran into this issue as I can only recreate this issue with Power BI. We have a BEx query that we are consuming and its basically multiplying the value x 100,000. An example would be a sales order qty of 450 shows up as 450 for all users but 1, that user see's 45,000,000. On that users machine, if I change the database credentials to any other user the value will change from 45M to the correct value of 450 (Within Power BI)

We've tested this on multiple machines with multiple user ID's in order to confirm that its the user's ID and not the version of Power BI, Computer, etc. 

We've looked at the users profile data (SAP GUI) and it matches everyone else's. Also keep in mind when this user runs the BEx query in Analyzer they get they correct value of 450. 

So while I don't believe its a Power BI issue, Power BI is the only place we can recreate the issue and we still can't figure out what could be causing this issue. I'm hoping that someone else has experienced a similiar issue and found a resolution. 

Thanks

---

@Anonymous

What do you see from the "Source" step? I don't know SAP, is there any profiling/tracing tool that can capture queries underlying sent from Power BI to your SAP Server?

[Anonymous · Accepted solution]

So we finally figured this out. This has to do with SAP authorizations and it was called out in the Power BI SAP docs but I overlooked that. 

This is called out under the troubleshooting section of this page:

https://powerbi.microsoft.com/en-us/documentation/powerbi-desktop-sap-bw-connector/