- A HCPR uses a join condition with one of the following cardinalities: 1:n; n:1; n:m. When you check the data with the help of transaction LISTCUBE, incorrect values are displayed.
- When running transaction LISTCUBE or checking the definition of a HCPR, the warning 'Ambiguities cannot be resolved without the analytic engine' (Message no. RSQBW143) is issued.
- When such a HCPR is used as a source of a DTP, the extracted data is incorrect.
- SAP NetWeaver 7.4
- SAP NetWeaver 7.5
RSQBW 143, RSQBW143, wrong results, COPR, ISET, InfoSet, Additional Grouping before Join, HANA, composite provider, compositeprovider , KBA , wrong values , non unique , list , listcube , hana composite provider , hcpr , hana data preview , incorrect results , cube , composite provider data preview , composite provider , BW-BEX-OT-HCPR , CompositeProvider Query , BW-BEX-OT-OLAP , Analyzing Data , BW-BEX-OT-DBIF , Interface to Database , BW-WHM-DST , Data Staging , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.