Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.

Reply
POSPOS
Post Partisan
Post Partisan

Fields show as key instead of text when using direct connectivity mode with SAP BW

Hi,

I am connecting to SAP BW BEX query in Power BI using direct mode. 

When I pull fiscal year field , it shows as key instead of text. 

POSPOS_0-1748703958760.png

Properties for this field in backend bex is  set to TEXT.

POSPOS_1-1748704050063.png

 

Can someone please suggest on how to show this as text in Power BI . What settings/workaround can be done to show this as below.

2008

2009

2010.....

 

Thank you.

 

,,

1 ACCEPTED SOLUTION
v-tsaipranay
Community Support
Community Support

Hi @POSPOS ,

Thank you for reaching out to Microsoft fabric community forum.

 

Based on your scenario, this behavior is a known limitation when using DirectQuery with SAP BW in Power BI. Even when the BEx query is configured to display text, Power BI may still default to showing the key, as it may not retrieve the associated metadata for text representations in DirectQuery mode.

 

Please follow the recommended Actions which heps you relsove the issue:

  • In your BEx query, explicitly include the text field (not just rely on default display settings). Power BI is more likely to recognize it as a separate field.
  • Alternatively, create a formula variable in BEx that combines key and text into a single display field (e.g., Key - Text).
  • If you're able to validate via RSRT, confirm that the query returns the correct display values outside Power BI.

For reference, here’s Microsoft documentation outlining these limitations: DirectQuery and SAP BW in Power BI

 

Hope this helps. Please reach out for further assistance.

If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.

 

Thank you.

View solution in original post

3 REPLIES 3
v-tsaipranay
Community Support
Community Support

Hi @POSPOS ,

Thank you for reaching out to Microsoft fabric community forum.

 

Based on your scenario, this behavior is a known limitation when using DirectQuery with SAP BW in Power BI. Even when the BEx query is configured to display text, Power BI may still default to showing the key, as it may not retrieve the associated metadata for text representations in DirectQuery mode.

 

Please follow the recommended Actions which heps you relsove the issue:

  • In your BEx query, explicitly include the text field (not just rely on default display settings). Power BI is more likely to recognize it as a separate field.
  • Alternatively, create a formula variable in BEx that combines key and text into a single display field (e.g., Key - Text).
  • If you're able to validate via RSRT, confirm that the query returns the correct display values outside Power BI.

For reference, here’s Microsoft documentation outlining these limitations: DirectQuery and SAP BW in Power BI

 

Hope this helps. Please reach out for further assistance.

If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.

 

Thank you.

POSPOS
Post Partisan
Post Partisan

@burakkaragoz  - Thank for your reponse.

1.Check the InfoObject settings in SAP BW - InfoObject has TEXT as default setting.

POSPOS_0-1748782061982.png

2. Use the “Display As” option in Power BI - "Display As"  did not show any additional fields for TEXTS.
3.Try importing instead of DirectQuery (if possible) - Our requirement is to use direct query due to large volume of data.
4.Check for composite keys - There is no option to use calculated column or bring in a look up table when using direct query mode.

Thank you

burakkaragoz
Community Champion
Community Champion

Hi @POSPOS ,

 

This is a common issue when connecting Power BI to SAP BW using DirectQuery. Even if the field is set to display TEXT in the BEx query, Power BI often defaults to showing the KEY instead.

Here are a few things you can try:

  1. Check the InfoObject settings in SAP BW
    Make sure the characteristic (like Fiscal Year) has both Key and Text maintained and that the Text is marked as default display in the BEx query.

  2. Use the “Display As” option in Power BI
    In the Fields pane, right-click the field and check if there's a “Display As” option. Sometimes Power BI allows switching between key and text if both are available.

  3. Try importing instead of DirectQuery (if possible)
    When using Import mode, Power BI is more flexible in how it handles key-text pairs. If performance allows, try switching to Import just to test if the text shows correctly.

  4. Check for composite keys
    If the field is part of a compound key (like M/C/2010), Power BI might not resolve the text properly. You might need to create a calculated column or use a lookup table to map keys to text manually.

Let me know if you're using a specific connector (like SAP BW Connector vs. SAP HANA) or if you can share the structure of the InfoObject.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.