Characteristic relationship with Exit class is not applied correctly

Question

We are using a characteristic relationship (with derivation) type Exit class. For that we have created class ZCL_RSPLS_ARTICLE_FROM_PLMOD as a copy of the standard class CL_RSPLS_CR_EXIT_BASE.
Target and source characteristics are members of the aggregation level.
We want to generate a list of valid combinations of characteristics planning models and articles which should be planned in the planning query.
For that we are using the method IF_RSPLS_CR_METHODS~CREATE:
Source is characteristic Model ZMATMOD and we determine in the exit class all active articles ZMATART.
We get a list of active (planning relevant) models and articles in our exit class (table e_th_chas).
--> For instance 6 combinations
Until here everything works fine.
The problem is that in the query 8 combinations are displayed.
We have no idea why more than the generated combinations are displayed.
One reason could be that the characteristic article ZMATART is an attribute from characteristic model ZMATMOD.
So from a master data point of view 8 combinations would be relevant.
But we use the exit class in order to reduce the number of combinations to planning relevant items.
If we use the method IF_RSPLS_CR_METHODS~CHECK we could flag the 2 combinations which are not planning relevant to not valid.
But these are then displayed in the query. 6 combinations in change mode; 2 combinations in display mode. This would not help us.
We would like to see only the planning relevant combinations  6 combinations
Can anyone please help me urgently?
Best regards
Martin

Answer 1

Hi,
set a break-point in the factory method get_instance to check whether the class is called. In the planning modeler make sure that you  use an external break-point.
Or use rsrt an change a cell value: Derivation is called in the delta buffer to derive from the fields contained in the aggregation level. So check also that the source fields are contained in the aggregation level or can be derived via a a chain of derivations.
Also make sure that all source fields have to be non-initial. The system will not call derivation for initial source fields since in this case there is not unique target, cf. http://help.sap.com/saphelp_nw70/helpdata/en/43/1c3d0f31b70701e10000000a422035/frameset.htm
Remark: The attached document of note 994853 is about the disaggregation feature but it also contains a section about the characteristic relationships. Observe also that the template exit classes are documented in SE24.
Regards,
Gregor