I am having a problem using on hand inventory as safety stock. So, even if I have more inventory on hand than the minimum stock key, a replenishment order is created.
The "Fulfill minimum" key is set as "Today" but as I get it, if I have enough inventory I should not have an order to replenish the safety stock today.
Negative days are set as zero and positive days are 365.
Thank you all.
If I've understood you right if I set Fulfill minimum as "Today" the replenishment order will be placed on 16th because there is when the actual requirement exists. But if I do this the safety stock requirement and therefore the planned order is placed today. Below is placed the picture for better understanding.
As I said, my wish is to have the replenishment order on 3/13 because that day the stock will fall below the safety stock, but AX is placing the safety stock requirement today.
Is that a bug? Or I am missing some system customization?
Chan I hope I have answered you as well.
Thank you both.
I have done the test you proposed (if I understood it right) and here are the results. The MRP still working the same way:
The safety stock is being defined as the minimum key, I'm not using the safety stock journal.
If it is not a bug then I don't know where the configuration mistake could be.
Here is the test with a new item. It works exactly the same way as before:
But as before, the results are the same if I just have 20 units on hand:
The problem appears when there is some forecast and stock falls below minimum stock:
This is the configuration for the test and the coverage code is Min/Max:
1. With production order:
Action messages are telling me to cancel the planned order and increase the quantity of the production order.
2. With on hand inventory:
Action messages are telling me to decrease the quantity of the planned order.
I want the order to be placed the 3/6 because that day the stock will fall below the minimum stock.
I hope this was the test that you wanted to see.
Hi Chan, I've just set my settings with EN-GB lenguaje, I review the enums for the (ReqTrans).RefType that you pointed out. "Planned works order" is a valid label, there is no customization there.
Nacho... the finished product you are using, are you creating it from scratch inside AX with native functionality? Are you using any customization or import tool to create the item?
As long as I know this is not a CatchWeight item:
Dimension group are the following:
Static plan has the following configuration:
And the planning table is empty because I'm not using it:
Thank you very much,
Sorry, I thought you meant explicitly Static Plan. I am using the Dynamic Plan:
This is the configuration for the Dimension Group SiteWH:
Tell me if you want to see anything else.
This is the dimension group:
Anything happens if I uncheck finite capacity.
I don't think the issue is about when the MRP generates the planned order but when the MRP does generate the requirement of the safety stock:
But after all this time I'm not sure about anything.
Here's the picture of the same scenario without minimum stock:
On the following picture it can be read that Fulfill minimum just should act when Min/Max coverage key is active (so maybe that it act when Period key is active is a bug) and I understand that Today's date generates today the requirement (it's not said with these exact words):
Thank you Steve for everything.
Fulfil minimum shouldn't be relevant but if I modify this option the safety stock requirement and therefore the planned order for its replenishment will change its date (or maybe I am understanding everything wrong).
The configuration is the same I've been using until now but I am going to change just the Fulfill minimum key.
Today's date (the safety stock requirement is created today):
First issue (the safety stock requirement is created the day of the first issue):
Coverage time fence (the safety stock requirement is created at the end of the planning time fence):
As I've said before all this pictures are using the same configuration with coverage key Period and I've just changed the Fulfill minimum key:
That's why I say that Fulfill minimum shouldn't be affecting my scenario but it seems that it is doing it.