cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to trigger Derive method of class CL_RSPLS_CR_EXIT_BASE using Characteristic relation

sagar_ghonge
Discoverer
0 Kudos

Dear All,

We want to derive functional location from maintenance plant & planner group combination and maintenance plant and functional location category “M” combination from functional location master.

Maintenance plant and planner group are input on our variable screen.

To achieve this we have create a copy of class CL_RSPLS_CR_EXIT_BASE as ZTEST_BIIP by defining the base class as super class

We redefine all methods of class CL_RSPLS_CR_EXIT_BASE in class ZTEST_BIIP

We used same class (ZTEST_BIIP) in characteristic relationship(CR) of our cube  and assigned source as maintenance plant, planner group and target as functional location and activate this CR in cube.

In query we have select characteristic relation in filter value selection at query execution setting of functional location.

As per our understanding we have to write code in derive method of Z class 

But when i execute our WAD, i am unable to debug Derive method of class ZTEST_BIIP, rest all methods are getting triggered but derive method is not

Note : we have put external debug

Please help

Regards,

Sagar Ghonge

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Sagar,

in a derivation relations you defne the source and target characteristics. Derivation fills the target characteristics if all source characteristics are filled. Thus derivation is called if the value of the source fields are known and at least one target field is not known. Typical use cases are: the aggregation level contains all source fields and no target fields. Then derivation is called in the delta buffer (InfoCube) or after-image buffer (DSO) to fill the target fields.

Maybe you have all characteristics of the relation in the aggregation level already, then derivation will not be called since all fields are filled already; in this case the CHECK method will be called. 

The DERIVE method will also not be called if one source characteristic is initial, except the flag 'EXCL #' is used.

You also mention the variable screen. Derivation relations have nothing to do with variables and the variable screen. There exists only a special feature to restrict the returned values in the F4 help based on characteristic relationships (but this does only work to restrict values at run time of the query and not in the variable screen).

Regards,

Gregor

sagar_ghonge
Discoverer
0 Kudos

Dear Gregor,

Thank you so much for your reply,

Initially our requirement was to derive functional location (FL) from maintenance plant & planner group combination, And in that case  we were passing maintenance plant & planner group in variable screen & when we execute query in the F4 help of FL we used to get respective FL, we had achieve this through attribute type of characteristic relationship with derivation and was working very fine.

Now our users requirement is to have FL from maintenance plant & planner group combination and maintenance plant & functional location category "M" combination.

Could you please suggest how to achieve this without using customer exit variable for FL???

Regards,

Sagar Ghonge

0 Kudos

Hi Sagar,

it is still not 100% clear whether you use 'derivation' in the context of variables or context of characteristic relationships (fill fields in data records). It seems that you talk about the first case. Here the standard techniques to 'derive' fields from other fields to fill variable values it to use replacement path e.g. based on master data attributes or queries (if the dependencies are not modeled in master data, master data attributes).

Regards,

Gregor

sagar_ghonge
Discoverer
0 Kudos

Dear Gregor,

Please find below 2 cases

1) Initial requirement :

please refer below table, its my functional location master table.

Now in my query i am giving input as maintenance plant, planner group, planning year and planning version.

Now after executing query user will select FL and other require fields and will enter the cost.

initially they want only plant and planner group  combination FL should populate,

means suppose i have given maintenance plant: 100 & planner group MEC as input  from below table 1st  & 3rd row FL will  populate,

we achieved this by selecting FL in source & maintenance plant and planner group in target of attribute type of characterised relationship and it was working fine

Functional location master table

Input (Maintenance plant)Input (planner group)Input (functional location category)Expected Output (Functional location)
100MECECRA-104-104FA42
100ELET-CRA-104-PW2401
100MECM-CRA-106
100INST
-CRA-108

2) Current requirement :

Now my user requirement is they want FL of maintenance plant & planner group combination and also maintenance plant & functional location category "M" FL , where my planner group will be blank .

suppose i pass plant 100 & planner group mec they should get 1,3,5,6th row  FL for selection

can i achieve this through exit class ?? or any other characteristic relation ?????

Functional location master table

Input (Maintenance plant)Input (planner group)Input (functional location category)Expected Output
100MECECRA-104-104FA42
100ELETCRA-104-PW2401
100MECMCRA-106
100INSM-CRA-108
100BLANKM-CRA-109
100BLANKM-CRA-110

Regards,

Sagar Ghonge

Answers (0)