Page tree
Skip to end of metadata
Go to start of metadata

Simple example to the topic Ambiguous Join, chapter 'Provider supports Local Groupng'

We use the same query as in Ambiguous Join Example 2 and just add some filter values for the characteristic STPEATTR1. This filter does not cange the query result. We just would like to show that restrictions in queries can lead to additional  characteristics requested by the Analytic Engine.

Query

We use the same query as in Ambiguous Join Example 2 and just add some filter values regarding the characteristic STPEATTR1.

 We run the query in Transaction RSRT and use the button Execute&Debug: 

 In the Trex statement(see SQL / HANA Analytics-API  ) we see that, in addition to the characteristics STPE_CUST(is in the drilldown) and the join field STPEMAT2, the field STPEATTR1 is selected:

 This is onyl necessary since the provider the query is based on has an ambiguous join.

Query Result

Now we remove STPE_CUST from the drilldow

 The Analytc Engine needs the 'filter characteristic' and the join characteristic' selected in oder to guarantee a correct result:

 

 

  • No labels