Block Processing of Characteristics when the value is out of spec

[Former Member]

Hi All,

Could you please tell me what do I need to set up in order to get an error message when the value entered for a characteristic is out of the specification limits?

So far I am only getting warning messages when setting "Plausibility" and "Tolerance" limits, and that is not what I am aiming to, I really need a hard block and I am trying to find a solution through SAP standard before putting programming in place.

Thanks in advance for your cooperation.

[busyaban7 · Accepted solution]

Hi Carolina,

Please note that blocking the standard SAP message QE 405 to "Error" may not fix your issue at all, and I presume there will be more downstream impact if we even try to implement such change, as correctly suggested by Anand.

You can try implementing some SCREEN EXITS, which may fix your issue.

Not sure, but you can try the two exits QEEM0011 and QEEM0029 if they somewhat helps you.

Thanks,

Arijit

[Former Member]

Dear all,

Thanks for your reply. I am completely aware of the importance of capturing values out of spec, and we do for all the calculated characteristics as per business requirement. However for the entries of characteristics that provide the sample weight, those canNOT be outside certain limits due to Industry specifications.

We undoubtedly need to be able to avoid typos for those specific characteristics, as the technicians just skip warning messages even when they are told not to do it.

As my initial query has been responded, in regard with an standard solution for a hard block, I will follow then Arijit suggestion.

Thank you all for your inputs, I really appreciate all your help.

[anand_rao3]

Not feasible in standard as per my knowledge! But don't you think by putting such lock you are going to stop capturing non conformity at all? Or there is no scope entering values outside tolerance limit even the inspector finds it? Is that really justifiable in daily business situations to always capture ok results despite of not ok values?  What would you do if you want to capture values which are just outside the tolerance?

Anand

[Former Member]

Hi Anand,

Thanks for your reply. What we are trying to avoid is typos, E.g. there is a characteristic for sample size (100g~) the set up for that characteristic is as follow:

Target Value: 100

Lower spec. lmt: 95

Upper Limit:110

LoPlausibility limit:90

UpPlausibility limit:120

If the user enter any value over 110 e.g. 1058 instead of 105.8 the system only shows warning message Message no. QE405.

We really need to put a hard lock to stop the user saving the inspection with a typo, The user should be able to correct it and then continue processing.

[Martin_H]

I tend to agree with Anand here. If you implement a hard lock then you would not be able to enter a value like 112.

A warning message in its origin is exactly what is adequate here: the user should check if the value entered is really correct or not.

Regards

MH