Microsoft Dynamics AX (Archived)

Master planning, demand forecast and customer sellable days

(0) Share

Report

Posted on by Maja RB

265

Hi,

I am testing the master planning functionality, with demand forecast, while taking into account item shelf life.

The scenario is the following:

- There is a demand forecast line for item-customer combination with requirement date 1st of December 2015, 3.000 pieces.

- There is a sales order for the customer with requirement date 16th of November 2015.

- There is on-hand inventory of 50.000 pieces that expires on 26th of December

- the customer has a setting for sellable days for that item: 90 days.

- the item has shelf life 270 days.

After running master planning, AX correctly proposes that the SO should be covered with a new batch order (the item is a production item), because the on-hand inventory doesn't satisfy the sellable days criterion.

However, the demand forecast line is covered with the on-hand inventory.

Is this a bug, or is there a logical explanation?

Thanks,

Maja

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (0)

Suggested answer

Yohann Rolland Axcible 3,111 on at

Like (0)

Report

Hi,

What you are saying is the master plan has not take into account the forecast?

Have you run a Gross requirement and the a net requirement ?

Gross requirement takes into account forecast , net requirement take into account inbounds and outbounds and could ignore or take into account the forecast.

From the net forecast master plan, you have to link it with the gross requirement plan (in the forecast part).

Was this reply helpful? Yes No
Maja RB 265 on at

Like (0)

Report

Hi Yohann,

MRP did take demand forecast into account. However, it did not take into account customer sellable days (the demand forecast line was specified per item and per customer).

MRP proposed to use on-hand inventory to satisfy the demand, which to me doesn't seem right. The requirement date on the demand forecast is 1st of December 2015. For that customer sellable days are set to 90 days. So, the expiry date for on-hand inventory that could satisfy the demand should be 29th of 2016 or later (1st of December 2015 plus 90 days). On-hand inventory has expiry date 26th of December, so that is not ok for the said demand.

"Consider shelf life" in MRP parameters is set. Is there any other setting that I'm not aware of?

Thanks,

Maja

Was this reply helpful? Yes No
Yohann Rolland Axcible 3,111 on at

Like (0)

Report

your item model group should be setup with the FEFO date controlled for your item, is it correctly setup?

Was this reply helpful? Yes No
Maja RB 265 on at

Like (0)

Report

Yes, I have FEFO date controlled checked on the item model group.

MRP works fine with SO, it takes the dates into account, so something IS set right :)

However, with demand forecast it doesn't.

Was this reply helpful? Yes No
Suggested answer

jac_rod 39 Moderator on at

Like (0)

Report

Hey Maja,

I haven't personally seen this behavior, but there's a similar issue logged in LCS.

fix.lcs.dynamics.com/.../NotFixed;qc=56d898f8a3ff20085fbdc450285cff99ebfbe8b80c02e8a37dedf3fe0a8b9a01

It's possible that the problem you're seeing is caused by the same issue. If so, it looks like it's a known bug and has no fix planned.

-Jake

Was this reply helpful? Yes No
Maja RB 265 on at

Like (0)

Report

Hi Jake,

thanks for the answer, it seems to be the same issue.

I am really disappointed that there is no fix planned, cause without it "sellable days" is just another feature that looks nice on paper but is only partially implemented.

Thanks again,

Maja

Was this reply helpful? Yes No
jac_rod 39 Moderator on at

Like (0)

Report

Yeah, I hate when "we know something doesn't work, but we're not going to fix it" is the answer.

Was this reply helpful? Yes No
Guy Terry 28,924 Moderator on at

Like (0)

Report

In my experience, 'Microsoft has evaluated this issue, and will not be issuing a fix at this time' is also used when there is no bug. It could be that the person who logged that incident was doing something wrong, or they were expecting the system to do something it is not designed to do.

In the case of the latter, I have also seen that one incident could be closed as 'will not be issuing a fix', and a new incident opened to request a change to the design.

What I am saying is, we don't know the details of that incident, and we can't be sure that there is a bona fide bug which MS are refusing to fix!

Was this reply helpful? Yes No
jac_rod 39 Moderator on at

Like (0)

Report

Hey Guy,

Yeah. I agree with you. I've seen that as well. If that were the case, though, it'd be nice if they explained it a bit instead of just saying "Microsoft will not be issuing a fix at this time".

If it's a piece of functionality that's intended and just not being used correctly, I've seen the comment "Microsoft has evaluated this issue, and has determined that this functionality is working as designed." If that's the case, they'll sometimes include an explanation or link to references, as well.

Was this reply helpful? Yes No
Maja RB 265 on at

Like (0)

Report

If it's not a bug, I'm more than happy to admit that my setup is flawed :)

I really need that functionality to work, so if someone knows how to make it work (presuming that it's not a bug), please let me know.

Thanks,

Maja

Was this reply helpful? Yes No