Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error after message display in modulepool

Former Member
0 Likes
673

In the modulepool , after some validation error message is displaying, But while doubleclick/ enter on screen it is going out of transaction to sap initial screen

please let me know if any one can help me in this regard.

Thanks in Advance

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
641

Check if the function type is assigned as 'E' - Exit command for those actions / function codes. In such case the validations will be bypassed.

If not, the message should re-appear even after hitting enter button.

Regards,

Shyam

5 REPLIES 5
Read only

Former Member
0 Likes
642

Check if the function type is assigned as 'E' - Exit command for those actions / function codes. In such case the validations will be bypassed.

If not, the message should re-appear even after hitting enter button.

Regards,

Shyam

Read only

Former Member
0 Likes
641

Hi,

Check the position at which the error message is triggered. Might be you can try calling the status message as error.


MESSAGE s899(v1) DISPLAY LIKE 'E'
                 WITH  msg1
                       msg2
                       msg3
                       msg4.

Regards,

Harish

Read only

Former Member
0 Likes
641

The system behavior after the message depends on the message type and on the place where the message is called. For example - the message type W will behave differently in the PAI module and the START-OF-SELECTION block.

So, in you case it may be the problem with message behavior in the given context.

The details about the messages behavior in various contexts:

[http://help.sap.com/saphelp_46c/helpdata/en/9f/dbaae335c111d1829f0000e829fbfe/content.htm]

Read only

Former Member
0 Likes
641

Hi,

Execute the program using '/h' in debugging mode, then in the debugging mode goto menu Breakpoints->Breakpoint at->Breakpoint at Statement->enter 'message' and press 'Enter'. Now Breakpoint will be set at all messages. Press 'F8' and reach the place where the error message is triggering and do the analysis

Regards

Dande

Read only

0 Likes
641

thanks all for your quick responce ....

@ Harish/Sham : probelm is the error message is called from standerd Function module

@Dande : Even though i am trying in debugger mode it is comming out.