topic Re: Dump dynpro_msg_in_help in Application Development and Automation Discussions

Dump dynpro_msg_in_help

former_member194669 — Tue, 10 Feb 2009 17:53:17 GMT

All,

I am getting a short dump in one of production systems as DYNPRO_MSG_IN_HELP

Screen: Illegal message

This is coming from one of custom dialog program. This is not getting in all the time,.

Currently i could NOT able recreate the same dump again. and user who created this is in other geographical location

Any info on this ?


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

a®

Re: Dump dynpro_msg_in_help

Former Member — Tue, 10 Feb 2009 18:01:46 GMT

It seems the program called a message in a routine defined for the EXIT-COMMAND event.

Check if there's a message statament in the module for the EXIT-COMMAND

Max

Re: Dump dynpro_msg_in_help

Former Member — Tue, 10 Feb 2009 18:07:10 GMT

Hi,

I think it is coming because of some error message...in the AT EXIT-COMMAND module...

Check the module..

Thanks

Naren

Re: Dump dynpro_msg_in_help

former_member194669 — Tue, 10 Feb 2009 18:33:22 GMT

Mar/Naren,

I check the exit_command module , there is no message statement mentioned


process after input.
  module common_exit at exit-command.
  chain.
    field: yshdrt-docdes,
           yshdr-doccat,
           yshdr-labor,
           yshdr-oruser.
    module validate_200.
  endchain.
  module user_command_ok_code.

and in module common_exit


module common_exit input.
  case ok_code.
    when c_back.
      leave to screen 0.
    when c_exit.
      leave to screen 0.
    when c_cncl.
      leave to screen 0.
  endcase.

endmodule.

a®

Re: Dump dynpro_msg_in_help

former_member156446 — Tue, 10 Feb 2009 18:45:34 GMT


> module common_exit input.
>   case ok_code.
>     when c_back.
>       leave to screen 0.
>     when c_exit.
>       leave to screen 0.
>     when c_cncl.
>       leave to screen 0.
>   endcase.

looks like when Other step is causing this dump

Re: Dump dynpro_msg_in_help

former_member194669 — Tue, 10 Feb 2009 18:52:14 GMT

J@Y

I checked GUI STATUS for the screen 200 Only Function Type "E" is mentioned for the following OKCODES ie BACK EXIT CNCL, and for all other GUI statuses it was blank (Normal Application Function)

So if any function codes other than BACK EXIT CNCL is pressed the control will not come into moduel common_exit here

a®

Re: Dump dynpro_msg_in_help

Former Member — Tue, 10 Feb 2009 18:52:52 GMT

Hi,

In the short dump..which line it is showing...that causes the dump...

Thanks

Naren

Re: Dump dynpro_msg_in_help

former_member194669 — Tue, 10 Feb 2009 18:59:32 GMT

Naren,

Cursor is NOT pointing any code in the dump (ie in the portion of source code extract of dump)

that's what i confused

a®

Re: Dump dynpro_msg_in_help

Former Member — Tue, 10 Feb 2009 19:14:50 GMT

hm...it's a tricky one...can you post the code of your PBO event...

also are you clearing the ok_code variable..at end of the PBO section...

Thanks

Naren

Re: Dump dynpro_msg_in_help

former_member194669 — Tue, 10 Feb 2009 19:23:06 GMT

Naren,

Here is the code from PBO of the screen


process before output.
  module status.

in Module status


  set pf-status sy-dynnr .

a®

Re: Dump dynpro_msg_in_help

Former Member — Tue, 10 Feb 2009 19:27:11 GMT

Is there a message being produced in a:

process on help-request.

Rob

Re: Dump dynpro_msg_in_help

amit_khare — Tue, 10 Feb 2009 19:33:44 GMT

I think you might have cheked, but still if not check the code as per this SAP [Help|http://www.sapnet.ru/abap_docu/ABAPMESSAGE.htm].

Re: Dump dynpro_msg_in_help

former_member194669 — Tue, 10 Feb 2009 19:34:03 GMT

Rob,

The flow logic is very simple



process before output.
  module status.

process after input.
  module common_exit at exit-command.
  chain.
    field: yshdrt-docdes,
           yshdr-doccat,
           yshdr-labor,
           yshdr-oruser.
    module validate_200.
  endchain.
  module user_command_ok_code.

a®

Re: Dump dynpro_msg_in_help

former_member194669 — Tue, 10 Feb 2009 19:38:32 GMT

Amit,

I have already checked this documentation

The program terminates with a runtime error DYNPRO_MSG_IN_HELP. While F1 and F4

are processed, the system cannot send error messages or warnings.

I tried to press F1 & F4 in the screen, but could not recreate the dumpt

a®

Re: Dump dynpro_msg_in_help

naimesh_patel — Tue, 10 Feb 2009 19:41:08 GMT

Does your custom dialog screen is being called from the module which could be raised by the Exit Command?

Regards,

Naimesh Patel

Re: Dump dynpro_msg_in_help

Former Member — Tue, 10 Feb 2009 19:41:48 GMT

Well, it seems to be dumping at a MESSAGE statement, so put a break-point at the statment MESSAGE and see if you can duplicate the error.

Rob

Re: Dump dynpro_msg_in_help

former_member194669 — Tue, 10 Feb 2009 20:55:32 GMT

I find the issue will be that

The field LABOR in the screen defined have search help , some developer puts a ERROR MESSAGE inside search help exit.

Thanks for your repsonse.

a®

Re: Dump dynpro_msg_in_help

Former Member — Wed, 11 Feb 2009 09:25:50 GMT


> some developer puts a ERROR MESSAGE inside search help exit.

Hmmm...Yes, it happens sometimes when we have to wash the dishes for some other Developer's efforts.

Although, I used-to cross-check before starting any devolopement/Enhacement for standard functionality To make sure if any other Custom Code or Messages includes by some one?

Here is another(Silly one) fact which i faced a while age =>

Cross-check would save your lot of efforts.

Julius helped me lot in above thread.

Cheers,

Amit.