Uncover Hidden QM Problems Using Health Checks
- by Doug TenBrock Sr., Senior QM/MM Consultant, Enowa
- January 19, 2011
Save time and money by knowing the health of your Quality Management (QM) module with SAP QM module health checks. By running health check reports, you are able to avoid a costly rework of processes because the close observation of the health of a go-live allows for quick adjustments if needed; roll off consultants, if you are using them, sooner because you have the tools to support a go-live; know the actual health of the modules; and solve issues without outside help.
Quality management (QM) module health checks involve running a set of standard SAP reports that identify if your QM module is operating smoothly. These reports show how well the users understand the processes, how well the master data is set up, if data is being closed out without problems, if processes are falling into the cracks, and if there are trends that should signal warnings.
SAP Quality Management (QM) module health checks act as an important part of successfully running SAP QM. Those of you who are in the middle of QM implementations may start to feel like you finally have what you need to ensure your go-live will be successful, because you are relying on facts, not hope. Those of you who are already live can tell how well your QM module actually runs. In many cases, you can obtain the information you need for the system to start running correctly.
Several years back a client called me in to fix a few problems in QM. The client felt these problems were the only issues at hand and believed the rest of the module was running well. The first thing I did was run the QM daily health check. What I found was that the module was not only running poorly, but was one of the worst QM systems I had seen to date. On top everything looked fine, but underneath they had a mess that could only be seen by the QM module health check reports.
Later I found that the additional troubles that the reports had identified were legitimate. This client needed to fix many more things than what I was called in to handle. It was painful, but if the client had run QM module health check reports during its initial go-live — or at least started the reports after the go-live —the client could have fixed the problems years earlier. Then the client would have obtained true benefits and accurate reporting from the QM over the years.
I discuss the three main types of health checks:
- QM go-live health checks
- QM daily health checks
- QM monthly health checks
Would you like to see this full item?