CMP Problem prevents Pushdown
The sample query is defined on a HCPR based on two ADSOs. The query contains a formula with exception aggregation MAX regarding the characteristic GLPET. As explained in 2400004, if the reference characteristic has a CMP problem(see note 1045683), the exception aggregation cannot be executed in Hana. We use transaction RSOHCPR to check the definition of the HCPR regarding the CMP problem and then analyze to sample queries regarding a pushdown. This can easily be done with the help of transaction RSRT(see How to check why exception aggregation is not pushed down to HANA DB).
Characteristic GLPET is compounded with GLNAME:
The characteristic GLPET is only mapped with the corresponding Infoobject from the partprovider GLADSOCMP. However, the 'compounding father' GLNAME is mapped with both partproviders. Hnece, according to note 1045683, the characteristic GLPET has the so called CMP problem.
In transaction RSOHCPR(besides the BW Modeling Tools) you can check the definition of an HCPR
In the log the warning 'CMP problem occured....' is displayed as expected:
We use the 'Execute&Explain' function in RSRT in order to get the log displayed(see How to check why exception aggregation is not pushed down to HANA DB):
So, for this query it is not possible to execute the exception aggregation in Hana. The reason is the CMP problem of the reference characteristic GLPET(see also 2400004).
The CMP problem always refers to a characteristic and a partprovider. In our case the text of the warning is "CMP Problem occured in characteristic GLPET for InfoProvider GLADSOCM2". Hence, we can expect that this CMP problem is only relevant when this partpovider GLADSOCM2 is accessed. Therefore(for testing purpose), we create a copy of the query I and set the filter 0INFOROV=GLADSOCMP.
In the log we can see that a pushdown was carried out for this query II: