ā2013 Jan 16 9:23 PM
Hello Giris,
I have a custom dialog program with some fields on screen. Now when user enters the custom dialog program, the program reads data from custom table and populates the data in those fields.
There are instances when the data in the custom table is bad data (incrrect datatypes). So program gives Dynpro_field_conversion error dump. I don't want this dump to happen but program to catch this error and populate the screen fields with no values.
How can I catch Dynpro_field_conversion error and avoid dump ?
Regards,
TS.
ā2013 Jan 16 11:28 PM
HI T S,
At the INITIALIZATION or Screen Events section, use TRY CATCH ENDTRY Block to catch the error dump, and send a custom message.
ā2013 Jan 16 9:54 PM
ā2013 Jan 16 11:28 PM
HI T S,
At the INITIALIZATION or Screen Events section, use TRY CATCH ENDTRY Block to catch the error dump, and send a custom message.
ā2013 Jan 17 3:21 PM
But whats the system exception that I can use between TRY CATCH ENDTRY during screen initialization so that I can give custom message for DYNPRO_FIELD_CONVERSIOn error.
ā2013 Jan 17 4:12 PM
The exact exception is the one on the dump error, or, you can catch the root exception.
TRY
" your code
CATCH cx_root.
" your error message
ENDTRY.
ā2013 Jan 17 5:53 AM
The elegant way is to map the screen field types with db field types.