Skip to Content
0
Former Member
Apr 19, 2010 at 07:01 AM

A customer exit variable unexpected behavior

45 Views

Hi,

I have a variable on 0calmonth. The variable is to behave such a way that it should be available for the user to input, but its optional. There is a customer exit behind this variable, which will validate if the user entered anything in the variable, if its blank, the customer exit fills in some value.

High - sydatum

low - 19000101

I have written the code in cmod

when'ZIC_CALMTH'.

IF i_step = 3. "validation

If l_s_range-high eq space and l_s_range-low eq space.

l_s_range-high = sy-datum+0(6).

l_s_range-low = '190001'.

l_s_range-opt = 'EQ'.

l_s_range-sign = 'I'.

endif.

APPEND l_s_range TO e_t_range.

ENDIF.

This is not working. The customer exit it not accepting this and the report runs without any inputs for the variable. When debugged, I found below response from system

The Can be changed in query navigation property has been set for variable ZIC_CALMTH, characteristic 0CALMONTH. However, the variable is used in the query in such a way, that the system is unable to apply this change-option.

This can, for example, occur under the following conditions:

Characteristic 0CALMONTH is filtered by additional restrictions (the restrictions must be joined using an OR-connection)

A second characteristic, which is restricted by a variable, is compounded to charcteristic 0CALMONTH.

Variable ZIC_CALMTH is a hierarchy node variable, but the hierarchy has not been determined uniquely.

A variable can be changed during query navigation only if it is used exclusively in a drilldown-characteristic, and there are no further restrictions to the characteristic other than this variable. There must be no additional characteristics with variables compounded to the characteristic you are working with. For variables for hierarchy nodes, the hierarchy must be determined uniquely and agree with the set display hierarchy.

The variable works if I remove the checkbox from "ready for input"

Appreciate inputs