Skip to Content

SAP QM scenario for Water Testing

Mar 08, 2017 at 04:29 AM


avatar image

Hi QM Gurus,

I am currently working on a POC to implement SAP QM in water utility company.

I will briefly explain the scenario and challenges:


The client has multiple sites where they store water and regularly draws water samples and send it to third party lab for tests like pH value, Turbidity etc. and receives back test result.

The test results are checked against predefined parameters for e.g.

pH value is checked in the scale range of 5 to 10. They break the pH values into four different upper and lower limit so that different department should work in case of out of spec limit.


Lower Limit upper Limit

6.3 7.7

6 8

5 9

4 10

Configuration and master data:

I have created

1. the sites as functional location

2. created charac as pH_Test

3. created MIC using reference charac function

4. created Sampling procedure with sample size as 1

5. Created General maintenance task list and assigned inspection point 310(functional location)

6. Created PM06 order.


While doing result recording I am only seeing only one specification not all defined in MIC.

As far as I know we can't see 1st/ 2nd lower and upper spec(not sure, though).

Please help finding out where I am wrong.



10 |10000 characters needed characters left characters exceeded

I believe that is standard behavior. If you look at the F1 Help on the 1st/2nd lower and upper spec fields it says "The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic."

* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Craig S Mar 08, 2017 at 07:38 PM

I think to resolve your problem you need to use at least four characteristics, possibly 5 if you want to.

MIC A = recorded pH - 0.0 - 14.0

MIC B = recorded pH - 6.3 - 7.7

MIC C = recorded pH - 6.0 - 8.0

MIC D = recorded pH - 5.0 - 9.0

MIC E = recorded pH - 4.0 - 10.0

Characteristics B,C,D,E are calculated characteristics. MIC A is where you record the test result. MIC's B,C,D,E all use the same formula, "CO0010" where 0010 is the characteristis sort number used for MIC A. That way, the result is enterred once, but checked agains the 4 specs maintained in Chara B,C,D, E.

You could get fancy and create an out-of-spec, (OOS), quality notification for each OOS result and have the notification automatically routed to the correct department that needs to now do work as a result of the OOS result.


Show 3 Share
10 |10000 characters needed characters left characters exceeded

Thanks Craig for your prompt answer and sorry to reply late!

I tried executing the scenario given below. I have few more questions

After entering the value for the first mic, I am supposed to calculate rest of the MICs. Also, It opens defect notification screen 5 times.

The Client wants to enter a value once, let's say if they are entering value 6.7 it should automatically trigger notification and email to the partner defined for MIC2 having range 6.3 to 7.7.

They want two type of notification

1. If value is in range it should trigger normal notification to the normal users

2. If the value is out of spec, it should check lower and upper for the specific value and trigger to the defined partner (For e.g. value 6.5, it should trigger notification to the respective users responsible for MIIC2(6.3 - 7.7)

I know it is not standard but can you help me in identifying exit or workflow




If your calculated characteristics are done correctly you should only have to enter the value once. For the first characteristic. You do have to lock and save it. Once locked and saved the others MIC's should calculate.

For your two type of notifications it depends on how you want to communicate to users. SAP provides an example follow-up action for your UD that will email users if an inspection fails. You could copy this and modify it to notify the users when the lot passes. This would probably be the primary and only choice really if everything passes. For notification when something fails, you could also include logic in it to determine who to email in the event a paticualr characteristic fails. You'd probably have to create a Ztable to hold info on who to email for which MIC failures. Or if you some way already in SAP that you group your users you might be able to leverage that. This would simply send emails. For an inspection fully passing, this might be all that is needed. For rejects you may need more

For rejections, you can try to set the calculated characteristics as conditional characteristics as well. That is, it is only done if another characteristic passes or fails. Put the characteristics in order from widest spec to tightest.

MIC A = recorded pH - 4.0 - 10.0

MIC B = recorded pH - 5.0 - 9.0

MIC C = recorded pH - 6.0 - 8.0

MIC D = recorded pH - 6.3 - 7.7

Mic A is alwasy done and is required.

Mic B is only done if A passes

Mic C is only done if B passes

Mic D is only done if C passes.

This ensure that you'll only have one rejected in a given inspection lot.

As soon as one fails, that MIC creates a quality notification. Assign a different severity level to each of the characteristics. (A1,A2,A3,A4) Then develop a resposne profile for each severity. (RA, RB, RC, RD). The response profile can then determine how quickly the notification has to be acted on. And it shoud be able to assign tasks to it and a coordinator to it to start the notification. The notification can then be used to track all actions taken by the users.



Thanks Craig for the detailed explanation.

I think this resolves my query.