Microsoft Dynamics AX (Archived)

Production Order Planned Ended for 4 months ahead

(0) Share

Report

Posted on by benjamin84

2,075

Dear All,

Anyone ever experience this case ?

some of my production order, for some operation number, for example oper 40, has ended at februari 6th, but at oper 50, its has started and ended date at June 23th,

please help , from where I should start to check this un-normal scheduling.

is there any form /report to view delayed purchased material/ lacking of man power for oper 50.

Please help.

THank you

7028.Production-Route.png

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Weaveriski 23,620 Moderator on at

Like (0)

Report

I presume you are finite scheduling. I remember this being an early issue (with AX2012 which was an issue with AX2009) where it tried to find the best approach within the way it scheduled the resources and planned the gaps to utilise the resources but it always drove people mad. I thought they solved this with a CU, but I have never tested it since.

Was this reply helpful? Yes No
benjamin84 2,075 on at

Like (0)

Report

Hi Steven,

so its system Bug ?

but I had previous production order that already scheduled. for example ( 2018-49), my problem production order is 2018-50.

I tried at test environment, I resetted status for 2018-49 to estimated, so the resource is available/free. then I did scheduling again for 2018-50, but its still has end date for operation 50 at june.

its seem like its not working calenday/available resource problem.

at explosion form, tab critical on hand issue , we have some item with delayed days.

it is the root-cause ?

if yes, wasn't, if I reset status 49 to estimated, its mean the raw material will be allocated/used for 50 right ?

please help.

Thank you

Was this reply helpful? Yes No
Weaveriski 23,620 Moderator on at

Like (0)

Report

If you look at the delayed item

1. Is it linked from the BOM to the routing operation?

2. When is it due in.

Delayed items would cause this.

So would finite scheduuling depending upon your version. If you are not finite it is stock availability. You could reset 49 but ultimately planning looks at dates, I would remove 49 completely or set the due date to next year.

Previous production orders are different, you need to assess each one.

No it is not a system bug. The finite issue was by design to limit scheduling over multiple resources, they changed this approach mid way through AX2012.

Was this reply helpful? Yes No
benjamin84 2,075 on at

Like (0)

Report

Hi Steven,

thank you for your help.

Thank you

Was this reply helpful? Yes No
Weaveriski 23,620 Moderator on at

Like (0)

Report

Hi Benjamin

Did any of this resolve the issue or is it still an issue?

Was this reply helpful? Yes No
benjamin84 2,075 on at

Like (0)

Report

Hi Steven,

its still issue,

right now I escalated this to my senior for depth analysis.

Thank you for your help.

Was this reply helpful? Yes No
Verified answer

benjamin84 2,075 on at

Like (0)

Report

Hi Steven,

After checked by our senior user, found out that we must use scheduling direction : backward from dateline or forward from previous job.

Thank you for your help.

Appreciate

Was this reply helpful? Yes No

Community site session details

Production Order Planned Ended for 4 months ahead

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates

Community site session details

Production Order Planned Ended for 4 months ahead

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates