topic Re: Catching error Dynpro_field_conversion to avoid dump.... in Application Development and Automation Discussions

Catching error Dynpro_field_conversion to avoid dump....

Former Member — Wed, 16 Jan 2013 21:23:08 GMT

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.

Re: Catching error Dynpro_field_conversion to avoid dump....

Former Member — Wed, 16 Jan 2013 21:54:21 GMT

When you say bad data is the values with negative sign?

Re: Catching error Dynpro_field_conversion to avoid dump....

Former Member — Wed, 16 Jan 2013 23:28:08 GMT

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.

Re: Catching error Dynpro_field_conversion to avoid dump....

kesavadas_thekkillath — Thu, 17 Jan 2013 05:53:28 GMT

The elegant way is to map the screen field types with db field types.

Re: Catching error Dynpro_field_conversion to avoid dump....

Former Member — Thu, 17 Jan 2013 15:21:59 GMT

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.

Re: Catching error Dynpro_field_conversion to avoid dump....

Former Member — Thu, 17 Jan 2013 16:12:04 GMT

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.