DYNPRO_MSG_IN_HELP dump in user exit

[Former Member]

Hallo gays,

program finish with short dump when i click exit button in case i have wron data in one mandatory field.

IF NOT <ln_anla>-lifnr IS INITIAL.

IF NOT <ln_anlz> IS ASSIGNED.

ASSIGN (c_anlz) TO <ln_anlz>.

ENDIF.

CHECK <ln_anlz> IS ASSIGNED.

SELECT SINGLE kostl INTO zkostl FROM zaa_ccvend_map

WHERE bukrs = <ln_anla>-bukrs AND lifnr = <ln_anla>-lifnr.

IF sy-subrc = 0.

IF <ln_anlz>-kostl NE zkostl.

<ln_anlz>-kostl = zkostl.

PERFORM anlz_bearb(saplaist).

ENDIF.

ELSE.

MESSAGE e005(zaa) WITH <ln_anla>-lifnr. HERE IS SHORT DUMP!!!

• Error message

ENDIF.

ELSE. "LIFNR is initial

[Former Member]

Hallo gays,

program finish with short dump when i click exit button in case i have wron data in one mandatory field.

IF NOT <ln_anla>-lifnr IS INITIAL.

IF NOT <ln_anlz> IS ASSIGNED.

ASSIGN (c_anlz) TO <ln_anlz>.

ENDIF.

CHECK <ln_anlz> IS ASSIGNED.

SELECT SINGLE kostl INTO zkostl FROM zaa_ccvend_map

WHERE bukrs = <ln_anla>-bukrs AND lifnr = <ln_anla>-lifnr.

IF sy-subrc = 0.

IF <ln_anlz>-kostl NE zkostl.

<ln_anlz>-kostl = zkostl.

PERFORM anlz_bearb(saplaist).

ENDIF.

ELSE.

MESSAGE e005(zaa) WITH <ln_anla>-lifnr. HERE IS SHORT DUMP!!!

• Error message

ENDIF.

ELSE. "LIFNR is initial

[b_deterd2]

Hi,

It is not always allowed to raise an error like this in a user exit. Which exit are you using?

Is there an exception you can raise in the exit (RAISE command) ?

regards,

bert

[Former Member]

Can u pl. check whether ur exit is calling from POH event or when u r pressing F4 help ? As the error name suggests 'DYNPRO_MSG_IN_HELP', it can be the possibility that due to F4 help ur exit is triggering and as within F4 help we cannot give error message that's why it is giving u this dump. If I am correct then pl. replace this error message by success(S) or by information (I) message to avoid this prob.

[Former Member]

Thanks for suggestions,

i use function module EXIT_SAPLAIST_003. The dump isn't getting when i use F4.It is getting when i use exit button.But only in case when i reseived first error message.

[Former Member]

I think ur exit EXIT_SAPLAIST_003 is calling from a module with addition AT EXIT-COMMAND like

MODULE USER_COMMAND_9001 AT EXIT-COMMAND. And in this module u cannot use error message. I u use error message then u will get the same dump. I have developed a small prog. and here is dump that I am getting:

Runtime Errors         DYNPRO_MSG_IN_HELP
Date and Time          16.01.2009 10:41:34



 Short text
     Screen: Illegal message



 What happened?
     The current screen processing action was terminated since a situation
     occurred where the application could not continue.
     This is probably due to an error in the ABAP program or in the current
     screen.


 Error analysis
     The program attempted to issue a " " message during  "Exit Command"  processing.
     This is an illegal operation.
     The program was terminated.

     Screen name.............. "SAPMZAPP"
     Screen number............ 9001



 Trigger Location of Runtime Error
     Program                                 SAPMZAPP
     Include                                 MZAPP_USER_COMMAND_9001I01
     Row                                     11

Pl. check whether u r getting the same message in Error analysis section or not.

[Former Member]

yes i received the same short dump - how you solve the problem?

[Former Member]

Pl. use information message or success message instead of error message.

[Former Member]

Hi,

Give an Information message and exit.

santhosh

[Former Member]

Information message and exit solve the problem.Thanks!

[Former Member]

If you really want to stop, you can use message type A.Then will no dump and no go ahead.