Type I and W messages ignored in user-exit code

[AndySiviter]

Hi all, very sorry if this has been answered elsewhere, I did try several keyword searches without success.

My problem is that when putting addition validation into PO creation (ME21N) the conditions causing error (Type E) messages all work fine, but the one occasion where I just need a warning message (Type W) the message does not appear.

Following the code in debug, the logic is fine, and the step by step reaches the message line, but just skips over it and does nothing.
If I change the type to I the same thing happens.
If I change it to an E like the others I created, then it works, but stops the execution, as would be expected.

The user exit is triggered by either the SAVE or CHECK actions.

Is there some settign perhaps that causes lower severity codes to be ignored under some circumstances?
I am most puzzled and hope someone will be able to help.

Many thanks for reading this,
regards,
Andy

[Grogan]

What user exit are you using ?

[Rich]

Check out the methods POST and CHECK in Badi ME_PROCESS_PO_CUST. Generate your messages using the macro MMPUR_MESSAGE_FORCED. If you want to fail the P/O set CH_FAILED to 'X'.

[riffraff]

We are encountering the same issue in a user exit (ZXQEEU06) called from EXIT_SAPLQEEM_006 which is part of results recording in QE51N for inspection lots in quality management. Is there a similar workaround that is not specific to PO processing that could be used elsewhere in SAP?