MRP Action proposals and hierarchy

Hi @majose 

thankyou for your priority list and explanation of each message, a structured approach is something we at looking to implement in order to improve the MRP data and reduce the number of Action messages generated. 

you suggested letting the manufacturing planners go through their MRP action messages first to let them take action. is there a logical approach they should take such as start at the top of a structure (sales part) and work they way down the structure?

kind regards

Jamie 

Hi Jamie,

Let say there is quite of few Remove Orders messages on sales parts and their immediate sub-assemblies, but then at level 5 or 6, the buyers are struggling with a lot of Late Order messages, then the approach could be like:

Run Selective MRP by low level code. And for example if you think it is a good idea to run MRP for low level code 0 to 2 in one go, you can specify it like this: 0..2

Note the dots

And then you can work through the action messages according to my prioritized list above, and take actions upon them. (In this example we will cancel a few shop orders coz they are not needed anymore)

Then you perhaps run a full site MRP

Or

a Selective MRP for levels: 3..10

(in this example many of the Late Orders will not exist because they were induced by shop orders downstream, which now are canceled)

I think it is a little bit of balance act for you

Lots of MRP jobs to manage and think about. BUT an MRP plan in very good shape

VERSUS

A single site MRP with MRP messages that are probably not aligned when you consider the complete BOM

Where is the golden mean for you?

-Mats

Hi @majose 

our current situation look s a little like this.

We run MRP once a week and it generates 37,500 Action messages, break down below

• 22,891 No Demand Exists
• 5,645   Not Buildable
• 414      Late Order
• 743      Early Order
• 399      Remove Order
• 595      Supply is Past Due
• 577      Plan Supply is Past Due
• 103      Planned Supply start date is past due
• 3,299   Demand is Past Due
• 2,834   Other

this is a combination of manufacturing and purchasing MRP action messages at all level codes and site wide, we have a team of 3 production planners and 3 buyers. Currently we are only actioning a small fraction of action messages, for example this week only 117 MRP action proposals got actioned. 

would you suggest we take the approach you suggested before and start by filtering out ‘Part  Type’ Manufactured , ‘Level Code’ 0..2 and work our way down the priority list of MRP action proposals. Re-Run MRP and then let the buyers use the MRP APW to action the Purchasing and Purchase (raw) messages?

regards

Jamie 

Sounds like a good plan Jamie   See how it works for you. But the fact that you initiated this discussion in your company shows you are taking this seriously - well trained users in this area is the key to success.

And when it comes to Early Order, you know MRP wants everything to be Just In Time, but in real life you might want to level your production. So as long as you know what you are doing, you can live with quite a few Early Order messages.

I think it would be good if you spend a little bit of time on why you get that many ‘Not Buildable’ messages.

When it comes to all those No Demand Exists… all customers are getting tons of this message. Perhaps an action point here is to change Part Status to “Demands Not Allowed” for some of your spare parts from the 1970ties if you know what I mean.

Future glory ahead

-Mats

@majose thanks for your help and suggestions, I will start to implement this approach right away to create an structured process for handling MRP action messages.

I'm sure I will come across situations I am not failure with and hope you can share some off your vast knowledge in the future.

Kind regards

Jamie