Friday, November 18, 2016

How to Fix MRP ExceptionsReveal

By Mike Hayes Read the full article at "Have you ever been told to do one thing and know you should do the exact opposite? It happens to me all the time. Being a consultant, I travel incessantly – new airports, new cities, new addresses and different rental cars. Every week, I have to figure out how to connect my phone via Bluetooth to a different car model (I need to start traveling with a millennial) so I know where to go. 
 In addition to that is Google. Now don’t get me wrong; I love my cell phone and Google maps, but I grew up with a father who had an innate ability to know where to turn. Now I am the father, and I believe I should have the same intrinsic ability when it comes to direction. That ability has been relegated obsolete due to that lady with an English accent directing me from my phone. Nearly every week she tells me to turn left when I know I need to turn right. More oftentimes than not, though, she’s correct. 
 Interestingly enough, supply chain planners using standard SAP exception monitoring are challenged by a similar internal battle — not which way to turn, but deciphering the exception message presented in the Stock Requirements List or the MRP List. The exception message presented indicates one course of action when the planner intrinsically knows he/she may need to take another. In these cases, however, the planner seems to be correct more times than not. 

 Re-prioritizing MRP Exception Messages 

Let me explain. In SAP, an MRP element may have up to two exception messages. One is presented in the initial display, and the second, if generated, has to be sought out. SAP has grouped and prioritized exception messages. Forty-something messages divided unequally into eight groups. Independent of those groups, SAP has assigned a priority for each message. The priority determines what order messages are presented. Higher priority messages are presented before those of lower priority." Read the full article, by Mike Hayes, at