Forum Discussion

jothikumar's avatar
jothikumar
New Member
9 years ago

SAP BW Multiprovider Error - Reg.

Hi Power BI Team,

 

We have SAP BW at the backend and trying to create specfic Dashboards in Power BI.


The specific requirement for the client is to design a Power BI Dashboard based on Multiproviders from SAP BW.

1. Able to connect to the SAP BW Infocube in Power BI.

2. But while trying to connect to SAP BW Multiprovider, facing the error as mentioned below:


"SAP Business Warehouse: RfcReceiveEx Failed (RFC_SYS_EXCEPTION): EXception condition "HIERARCHY_NOT_FOUND" raised"


Is there any fix for the issue mentioned? If so please update.


Awaiting your response at the earliest.

 

Regards,

JK.

 

4 Replies

  • v-caliao-msft's avatar
    v-caliao-msft
    Microsoft Employee

    Hi jothikumar,

     

    Is this MultiProvider available for other tool for reporting purposes? After created a multiprovider, we need to activate the MultiProvider and only this activated MultiProvider will be available for reporting and analysis.

     

    Regards,

    Charlie Liao

    • jothikumar's avatar
      jothikumar
      New Member

      Hi Charlie,

       
      At the outset, I thank you for responding to my query swiftly.
       
      Yes, I duly follow the activation process of Multiprovider as stipulated by SAP BW. The same is available for reporting and analysis in other tools. The problem I face is only with Power BI.
       
      And one more observation I wish to bring to your kind attention, SAP BW DSO's are not displayed in the navigation tree.
       
      I would really appreciate if you could help me out of this situation or connect me to the right technical engineer to sort this issue.
       
      Regards,
      - JK.
      • Oihane's avatar
        Oihane
        New Member

        Hi jothikumar

         

        Did you solve the problem. I'm now in the same situation, and i've no idea whats going on.

        I can access cubes and querys, but when I try it with a multicube i get the same error as you.

         

        Regards,

        Oihane