web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Production Order route operation

(0) ShareShare
ReportReport
Posted on by

Dear All,

Hi, once again came into the problem where i am have a simple and complex route scenario.

1) having product with 6 Operation which should be move sequential way means first operation finished then 2nd operation get started till that system should not allowed to start next operation.

10 --> 20 --> 30 --> 40 --> 50 --> 60

2) having complex routes where first 2 operation parallel and 3 operation and then 3 operation parallel then 7 then 8.

10 -->                               --> 40

--> 30                 -- > 50                --> 70  --> 80     

20 -->                               --> 60     

there is no control in production module if the operation is completed or not system allowing to register the FG which is wrong and system should not allowed this. even i hide the option accept error but still i am in trouble due to registration of product.

*This post is locked for comments

I have the same question (0)
  • Brandon Wiese Profile Picture
    17,788 on at

    The system does not enforce reporting in the way you have described it "should".  There are plenty of reasons to allow for loose reporting the way AX does.  The most common is simply out-of-sequence reporting, where you cannot depend upon data to be entered in AX in a timely fashion or in the exact sequence it occurred in the real world.  By analogy, you might argue that it should not be possible to ship a sales order unless its production order has been reported, but there are plenty of legitimate scenarios where a sales order packing slip might drive the inventory negative and the reporting of the production order occurs later.  You could enforce your requirement with a simple modification of AX.

    Regarding parallel operations, that's probably best handled by secondary operations in AX.  For example, operation 10 would have a primary and secondary 1 operation (20 in your example).  Operation 40 would have a primary, secondary 1, and secondary 2.  Secondary operations are scheduled in parallel by design I believe.  Perhaps this does not meet your requirement, but is it an option that you may not yet have considered.

  • Community Member Profile Picture
    on at

    Sorry but i saw and remember there was something to do in AX 2009 to enforce the user to finish the previous operation first then can start new one. right now i don't have 2009 so not able to see what was the setup.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans