Forum Discussion

AparnaJ's avatar
AparnaJ
Helper I
1 year ago
Solved

Direct Query to SAP BW

Hello, We have a use case where we are connecting to SAP BW via direct query. We see few values coming in as compounded into Power BI, ([0FISCYEAR].[MC2025] instead of just 2025). Can you guide us i...
  • pankajnamekar25's avatar
    1 year ago

    Hello AparnaJ 

     

    When connecting Power BI to SAP BW via DirectQuery, compounded key values like [0FISCYEAR].[MC2025] appear because SAP BW uses compounding keys. To get cleaner values like 2025, select the display text fields (e.g., 0FISCYEAR__TXT) during the initial connection. Power BI doesn’t allow switching between key and text fields in DirectQuery mode after import.

    If a text version isn’t available, you can create a calculated column using string functions like RIGHT, but this can degrade performance in DirectQuery. The recommended solution is to request your SAP BW team to expose display fields in the InfoProvider or query.

    For better performance, consider importing small dimension tables (like fiscal year) while keeping larger fact tables in DirectQuery. This hybrid approach allows cleaner slicers and avoids excessive visual-level calculations.

     

    Thanks

     Pankaj Namekar | LinkedIn

    If this solution helps, please accept it and give a kudos (Like), it would be greatly appreciated.