Skip to Content
Aug 14, 2008 at 07:46 PM

Select-options are not destroyed while calling view of used component popup


Hi Friends ,

I'm facing a unique problem. I'm calling a view of a component within another component. the view that I'm calling has some select-options. When I close the popup window ( using close 'X' of popup ) and then try to reopen the popup system give me a dump. I debugged and found that select-options are not destroyed by system and once it tries to create the select-options again it dumps because they are already there.

This is the source code extract of that dump for your reference .

1 method if_wd_select_options~add_selection_field.


3 data:

4 lr_table_descr type ref to cl_abap_tabledescr,

5 lr_struct_descr type ref to cl_abap_structdescr,

6 lr_value_field_descr type ref to cl_abap_elemdescr,

7 added_field like line of mt_added_fields,

8 dfies type dfies,

9 description type string,

10 complex_restrictions type if_wd_select_options=>t_complex_restrictions.


12 field-symbols:

13 <it_result> type index table.


15 * check of someone wants to add a field that already exists

16 read table mt_fields

17 with key m_id = i_id

18 transporting no fields.

19 if sy-subrc = 0.

20 * might be deleted - recreating a field with different setting is of course allowed

21 read table mt_all_removed_fields

22 with key table_line = i_id

23 transporting no fields.

24 if sy-subrc <> 0.

>>> message x000(00).

26 endif.


28 * remove the existing field in order to avoid duplicates

29 delete table mt_fields with table key m_id = i_id.

30 endif.

I've already tried using REMOVE_ALL_SEL_SCREEN_ITEMS( ) method of interface IF_WD_SELECT_OPTIONS before creating new elements ( select-options ). If any one can help me in this It would really help and I'll appreciate it.

Thanks in advance,