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

In the following we discuss a simple example to the topic Ambiguous Join, chapter 'Provider does not support 'Local Grouping'

InfoProvider with two Ambiguous Joins

We extend the HCPR of Ambiguous Join Example 2 by joining another ADSO:

This HCPR does not support Local Grouping(see Ambiguous Join, chapter 'Local Grouping') when there is at least one key figure(requested by the query) where a bad characteristic is also a join field:

  • E.G. key figure 0Quantity
    • for this key figure, STPECNTRY2 is a bad characteristic, at the same time it is also a join field.
    • all bad characteristics for this key figure: STPECNTRY2, STPEATTR2, 0UNIT, STPECNTR3 and STPEDSTR3.

In the BW Modeling Tools of the Hana Studio, the HCPR definition is as follows:

The content of the ADSO STPE_AJ01 is as follows(the content of the other two ADSOs ias as in  Ambiguous Join Example 2):

Query I (No Local Grouping)

The query uses only the key figure 0Quantity and the following (free) characteristics(there are no filters)

For the key figure 0Quatity, local grouping is not supported and hence all join characteristics need to be requested by the Analytic Engine(independent of the navigation state)!

When we take a look at the Technical Information in Transaction RSRT, we can see under 'Non-Visible Drilldown Characteristics' a list of all join characteristics and all mad characteristics which are used in the query:

E.g. STPEDSTR3 is a bad characteristic and used as a free characteristic in the query. If there is a query filter regarding STPEDSTR3, then this InfoObject is also requested from the database(see below)

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 characteristic STPE_CUST, all join fields are requested:

The query result is as expected, see content of ADSOs as shown in Ambiguous Join Example 2:

Even when we remove the STPE_CUST Infoobject from the drilldown, all join fields are still requested:

If we define a filter regarding a mad characteristic, it is added to the Requested Attributes:

Query Result:

Query II (Local Grouping supported) 

This query contains the key figure  STPEQUNT2(see also Ambiguous Join Example 2) which has the following bad characteristics

  • STPE_CUST, 0COUNTRY, STPEATTR1, STPEATTR3, 0UNIT and STPECNTR3, STPEDSTR3

None of theses InfoObjects is a join characteristic. Hence, in this case, Local Grouping is posssible.

The query has the following (free) characteristics(there are no filters):

When we take a look at the Technical Information in Transaction RSRT we therefore can see the following 'Non-Visible Drilldown Characteristics':

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 characteristic STPE_CUST, all join fields are requested:

Query result is the same is in Ambiguous Join Example 2

When STPE_CUST is removed from the drilldown, the join characteristics are not needed any longer(only 0UNIT since 0STPEQUNT2 is a quantity key figure)

 

 

  • No labels