06-13-2014 8:09 AM
Hi,
I have a requirement to raise error in Screen(Module Pool) and again allow user to stay in the same screen.But if i raise error then it is throwing user directly out of transaction.
For example,if we see in VL02N we will get error while providing serial number during picking or packing but it will still allow user to stay in the same screen.But in my case i have customized VL02N and i am not able to raise error in the same way as it is throwing me out of transaction.
Is there any transaction to maintain Eror type based on application or is there any way to handle this as an exception at screen level.?
Please find attahement for the same.
Regards,
Venu
06-13-2014 8:54 AM
Hi,
Are u talking about a standard program or z program?
If you wrote a Message of Type 'E' in the PBO of Screen, it will terminate the screen with a popup error message.
If it is a standard screen then the functional people may know to change the type of message in configuration.
Regards
Sreekanth
06-13-2014 9:06 AM
Hi,
I think you need to give next screen number same as the screen number in which you are working.
06-13-2014 9:19 AM
some message types will behave differently in a dialog transaction...there is a lot of info in the help on this
however, try using the addition
DISPLAY LIKE of the statement MESSAGE.
so, for example,
message 'my message' type 'S' display like 'E'.
try some different variants of the example above to give you the behaviour that fits best