Power BI: Can't determine relationships between the fields while consuming SAP Analytical CDS Query

Hi Everyone,

I am trying to consume an SAP S/4HANA Analytical CDS Query in Power BI Desktop using the SAP BW Application Server Connector (DirectQuery).

Environment:
- Power BI Desktop, connecting via SAP Business Warehouse Application Server connector
- Data source: SAP ABAP CDS Analytics Query view (Analytics Cube-based)
- Model mode: DirectQuery

Issue:

We're consuming an SAP CDS Analytics Query view in Power BI via the SAP BW connector. Several fields from this single CDS view import correctly as flat columns in one table, but two specific fields (Status Text and Status Description, etc.) each get split into their own separate table, with a "Level 01" hierarchy sub-item under each (e.g. "Status Text" table -> "Status Text Level 01").

Because these come in as separate tables instead of columns in the same table, Power BI throws:

"Can't determine relationships between the fields"

whenever we try to use both fields together in a visual.

Additional context:
- The underlying characteristic (Object Status) is derived from a status-tracking logic where one object can have multiple status rows (active/inactive flags), resolved via a join to a status text table.
- Other fields in the same CDS view (Plant, Order Type, Order Number, etc.), which are simple single-valued attributes, come through fine as flat columns with no splitting — only the status-related fields split into "Level 01" tables.

What I've tried:
- Attempted to manually create a relationship in Power BI's Manage Relationships between the "Level 01" columns of the two split tables — as soon as a second field from a different "Level 01" table is added to a visual, Power BI still shows "Can't determine relationships between the fields," even after the manual relationship is created
- Testing with a separate, simple CDS view (basic 2-table join, no status fields) — this loads fine as one flat table, suggesting the issue is specific to hierarchy/multi-valued characteristics being split by the connector

Screenshot 1: Status Text and Status Description are loaded as two separate tables, each with a "Level 01" sub-column, instead of coming through as flat columns in the same table

Screenshot 2: Error shown when trying to use both fields together in the same visual — "Can't determine relationships between the fields."

Question:
Is this "Level 01" splitting expected behavior of the BW connector for hierarchy-enabled/status characteristics? Since manually relating the split tables doesn't resolve the relationship error either, is there a way to force these fields to load as flat attributes instead (a connector setting or a CDS-level annotation), rather than having them split into separate hierarchy tables in the first place?