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

Problem with error message

Former Member
0 Likes
589

Hi Experts,

Im populating an error message in the standard transaction (VA03) to restrict the user from viewing the print preview of the document. The error message works perfectly well in the initial screen of the transaction. But when the same functionality is performed after entering into the document, its getting converted to an Abort message. Using the other message types as I,W,.. does not serve my purpose.

Is it anything to do with the screen number? What could be done to change the message type?

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
517

Hi,

as mentioned earlier the soultion provided is perfect use can use the message "message'' display like 'E'.

since the list or the document is not been generated and their is no screen as such the program goes for an abort status.

but when we have a screen than the Error message triggers the initial screen.

go with the solution provided..

it will work ..

thanks

3 REPLIES 3
Read only

Former Member
0 Likes
517

HI

try below

message s000(00) with 'Message' display like 'E'

hope it works

Thanks!

Read only

Former Member
0 Likes
518

Hi,

as mentioned earlier the soultion provided is perfect use can use the message "message'' display like 'E'.

since the list or the document is not been generated and their is no screen as such the program goes for an abort status.

but when we have a screen than the Error message triggers the initial screen.

go with the solution provided..

it will work ..

thanks

Read only

Former Member
0 Likes
517

Hi,

Thank you for your replies. But i cant check whether your suggestion will work or not because the statement "display like 'E'" is throwing syntax error. In one server its working and in the other its not. Probably due to some difference in the version.

Anyway i solved the issue by keeping an information message instead and cleared the sy-ucomm value after the message.