CONVT_NO_NUMBER in ALV table when filtering a field with conversion exit

[Former Member]

Hello!

A Z-program is used for table maintenance.

I have a field of type NUMC10 with a conversion exit which displays the field as CHAR17.

As field values are displayed in CHAR17 format, a filter is also applied to the table using value of CHAR17 (for example: equal to "001.2007.10012401" ).

After filtering, we transfer ALV table mode to edit mode, CL_SALV_TABLE=>REFRESH is executed, call hierarchy is like that:

Call Hierarchy
21 FORM         SAPLSLVC_DIALOG                     LSLVC_DIALOGF18   LVC_FILTER_APPLY10
20 FUNCTION     SAPLSLVC_DIALOG                     LSLVC_DIALOGU18   LVC_FILTER_APPLY
19 METHOD       CL_SALV_FULLSCREEN_ADAPTER====CP    CL_SALV_FULLSCREEN_ADAPTER====CM00W    CL_SALV_FULLSCREEN_ADAPTER=>IF_SALV_ADAPTER~APPLY_SERVICES
18 METHOD       CL_SALV_TABLE=================CP    CL_SALV_TABLE=================CM014    CL_SALV_TABLE=>REFRESH

Dump follows at line 713 of LSLVC_DIALOGF18 include of SLVC_DIALOG function group:

if <l_filter> in ls_rsds_frange-selopt_t.

<l_filter> has NUMC10 value here (2110000842), field itself is also described as NUMC, and selection criteria is CHAR17-like (I EQ 001.2007.10012401).

So the program crashes with CONVT_NO_NUMBER.

Notes 1379679, 1519383, 1405506 were applied and that didn't help.

What can be done to fix it?

[PeterJonker]

Maybe if you create a second ranges table where all the values of the select-options have been converted to the internal table format (with conversion exit input) and use that range table in stead on checking <l_filter> will be a possible solution.

[Former Member]

The problem looks like a standard (non-Z) software bug. All the filtering is processed by standard code, and dynamic error also appears in standard SAP function group.

We have NetWeaver 7.00 here, probably some fix is missing.

[PeterJonker]

OK, I didn't realize the error wa thrown in standard code. Then I am out of ideas for now. Sorry.