‎2009 Feb 10 5:53 PM
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®
‎2009 Feb 10 7:27 PM
Is there a message being produced in a:
process on help-request.Rob
‎2009 Feb 10 6:01 PM
Hi
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
‎2009 Feb 10 6:33 PM
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®
‎2009 Feb 10 6:45 PM
> 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
‎2009 Feb 10 6:52 PM
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®
‎2009 Feb 10 6:07 PM
Hi,
I think it is coming because of some error message...in the AT EXIT-COMMAND module...
Check the module..
Thanks
Naren
‎2009 Feb 10 6:52 PM
Hi,
In the short dump..which line it is showing...that causes the dump...
Thanks
Naren
‎2009 Feb 10 6:59 PM
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®
‎2009 Feb 10 7:14 PM
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
‎2009 Feb 10 7:23 PM
Naren,
Here is the code from PBO of the screen
process before output.
module status.
in Module status
set pf-status sy-dynnr .
a®
‎2009 Feb 10 7:33 PM
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].
‎2009 Feb 10 7:38 PM
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®
‎2009 Feb 10 7:27 PM
Is there a message being produced in a:
process on help-request.Rob
‎2009 Feb 10 7:34 PM
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®
‎2009 Feb 10 7:41 PM
Does your custom dialog screen is being called from the module which could be raised by the Exit Command?
Regards,
Naimesh Patel
‎2009 Feb 10 7:41 PM
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
‎2009 Feb 10 8:55 PM
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®
‎2009 Feb 11 9:25 AM
> 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.