input verification while declaration of selection screen

[Former Member]

Hi Friends,

Is there a way to verify the input which the user enters on screen

either declared by parameters or select-options

without below techniques at declaration level itself.

1. Provide user a dropdown list ( no error, no verifcation ).

2. By sending back the user input and do select query and then display type E messages

ex: select f1 from table into wa

where a1 IN s_first and " s_first user input

where a2 IN s_second. " s_second user input

if sy-subrc ne 0

*display error to user

endif.

My basic idea is to avoid database hits i.e., minimise select 's

Edited by: DeepakNandikanti on Dec 1, 2010 10:35 AM

[Former Member]

For Parameters you can use VALUE CHECK extension, if the possible entries are defined in domain.

But for select options, may be the only way to validate is query the table.

[Former Member]

Hi,

You can force entries through F4 Help.

Check this link.

<a href = " target="_blank" >

[Former Member]

Hi Deepak,

As far as my knowledge, that can happen to fields which have Conversion Exits defined at their domain level like PROJ-PSPNR which checks automatically when you enter some data in it. For other types of fields which don't have conversion exits, you have to check on your own.

Thanks & Regards,

Faheem.

[RaymondGiuseppi]

Declare TABLES: sscrfields in your global data, then perform the db-costly check only if sscrfields-ucomm is 'ONLI' or 'PRIN'

AT SELECTION-SCREEN [ON xxx].
  IF sscrfields-ucomm EQ 'ONLI'
  OR sscrfields-ucomm EQ 'PRIN'.
    SELECT ...
  ENDIF.

Regards,

Raymond

[Former Member]

Thank you for your reply,

Could you please elaborate..

[Former Member]

Thanks a lot!! You all have poured in your valuable replies..

I am going through all..