Skip to Content

Cannot activate HANA view query (External SAP HANA view) due to Ambiguities

Dear all,

I have created a Composite Provider in which I have included two aDSOs with Inner Join (n:1). After set "External SAP HANA view" and activating I have received a warning reg. Ambiguities, but it was possible to activate.

After creating a query based on it and trying to set the "External SAP HANA view" flag as well, I receive now an error message after saving: Ambiguities cannot be resolved without the analytic engine. I have read the Online help reg. creating SAP HANA views based on queries esp. the section for supported and unsupported functions, but can not find any hint. Is there something wrong with the Composite Provider Definition?

We are running on BW on HANA 7.5 and I am using BW modelling Tools in Eclipse.

Any idea would be great. Thank you in advance.

Best regards,

Stefanos Leon

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Feb 01 at 10:51 AM

    Hi Stefanos,

    Please read this KBA:

    2372430 - Ambiguous Joins: LISTCUBE may display incorrect values

    Additional information:

    Ambiguities (for example measure multiplication) can occur when accessing the external SAP HANA view. This is consistent with the result of the InfoProvider access in ABAP, for example transaction LISTCUBE, because the BW OLAP engine is only used in the context of a BW Query to handle the ambiguity.

    The external SAP HANA view of a Query using such a CompositeProvider cannot be activated anymore. In contrast to the external SAP HANA view of the CompositeProvider, which is still supported, the result of the external SAP HANA view of such a Query is not consistent with the result of the BW OLAP engine. The HANA engine does not handle ambiguities.

    To be able to activate the external SAP HANA view of such a BW Query, the CompositeProvider definition must be changed that no ambiguities are occuring so the warning message RSQBW143 does not appear anymore when checking the CompositeProvider. This can be achieved by changing the cardinalities in the CompositeProvider definition in order to avoid ambiguity. Changing the cardinalities however can alter the result of the BW OLAP engine, but the result is consistent with the result of the external SAP HANA view.

    Hope it helped.
    Best regards, Andras

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 05 at 10:59 AM

    Hi Andras,

    thanks a lot, your Input was very helpful. I was able to remove the amguous join via "Edit Cardinality". Now I am able to set the "External SAP HANA view" flag and activate the referring query. Best regards, Stefanos

    Add comment
    10|10000 characters needed characters exceeded