Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Production order scheduling order
shyamraoo
Member Posts: 38
Hi team,
We noticed that when we would Refresh the PRD, the Backflush would schedule EVERY item to end at the Due date and flow backwards even if they go through the same work center (see two lines below). However our Work Center Capacity is currently set at 1, which to me would mean that it would only be able to process one item at a time and thus the items should be staggered in serial, not stacked in parallel. Would you happen to know why the jobs are scheduling on top of each other even though our Work Center Capacities are set to 1?
One thing I have determined is that the issue seems to be with Items who only have an interaction in a Work Center. If items have a component/sub-component relationship, then they are correctly scheduling the sub-component to be completed before the component can starts its routing (See below, the sub-component ASWP is correctly scheduled before the finished components ASWK & ASWP).
However the ASWK and ASWT are scheduled to start and finish at the same time. They both share the same Work Center, and can be completed in any order, but the Work Center should only be able to do 1 at a time (e.g. Capacity = 1?)
We noticed that when we would Refresh the PRD, the Backflush would schedule EVERY item to end at the Due date and flow backwards even if they go through the same work center (see two lines below). However our Work Center Capacity is currently set at 1, which to me would mean that it would only be able to process one item at a time and thus the items should be staggered in serial, not stacked in parallel. Would you happen to know why the jobs are scheduling on top of each other even though our Work Center Capacities are set to 1?
One thing I have determined is that the issue seems to be with Items who only have an interaction in a Work Center. If items have a component/sub-component relationship, then they are correctly scheduling the sub-component to be completed before the component can starts its routing (See below, the sub-component ASWP is correctly scheduled before the finished components ASWK & ASWP).
However the ASWK and ASWT are scheduled to start and finish at the same time. They both share the same Work Center, and can be completed in any order, but the Work Center should only be able to do 1 at a time (e.g. Capacity = 1?)
Regards,
N.Shyam Kumar
N.Shyam Kumar
0