Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 295 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Maximum order quantity and reorder cycle
MatthewRBritton
Member Posts: 27
Hi all,
In our factory many of our products have a fixed batch/lot size due to processing constraints. For example, a batch may be limited to 100 units. I have set this size up as both the minimum order quantity, maximum order quantity and order multiple. I also have a reordering cycle of 45 days for this item to allow rescheduling within that time to occur.
If I enter a sales order for 300 units, the planning worksheet plans beautifully and suggests 3 production orders of 100 units. If I then create those orders and re-run the regenerative plan, the system suggests that I cancel two production orders, and change the quantity of the third to 300. Is MRP disagreeing with itself?
Microsoft tells me (via our partner/consultants) that I should not use a reorder cycle with the field maximum order quantity (although this is not in the help file). If I remove the re-order cycle and my customer decides to move the sales order a week earlier (as they are apt to do) the planning worksheet will suggest I cancel my production orders and create new ones for the new date rather then re-schedule the existing ones.
Has anyone else come accross this issue? Any suggestions?
Thanks
Matt
In our factory many of our products have a fixed batch/lot size due to processing constraints. For example, a batch may be limited to 100 units. I have set this size up as both the minimum order quantity, maximum order quantity and order multiple. I also have a reordering cycle of 45 days for this item to allow rescheduling within that time to occur.
If I enter a sales order for 300 units, the planning worksheet plans beautifully and suggests 3 production orders of 100 units. If I then create those orders and re-run the regenerative plan, the system suggests that I cancel two production orders, and change the quantity of the third to 300. Is MRP disagreeing with itself?
Microsoft tells me (via our partner/consultants) that I should not use a reorder cycle with the field maximum order quantity (although this is not in the help file). If I remove the re-order cycle and my customer decides to move the sales order a week earlier (as they are apt to do) the planning worksheet will suggest I cancel my production orders and create new ones for the new date rather then re-schedule the existing ones.
Has anyone else come accross this issue? Any suggestions?
Thanks
Matt
0
Answers
In fairness the reorder cycle help states "Note: It is not recommended to use the Reorder Cycle field together with the reordering policy Maximum Qty., and in most cases the reorder cycle will be overruled."
Unfortunately I have had lots of issues with the policy of Maximum Qty. What version are you using?
My re-ording policy is lot-for-lot, which I didn't think would be an issue and I would be happy for the re-order cycle to be overruled in place of the maximum order quantity field. I want the maximum order quantity field to be respected. We are using version 5.0 sp1.
Can you tell me the problems you have seen?
After extensive discussion testing and to-and-fro this issue has been recognised as a bug and a fix will be supplied. At this stage it would appear it is not caused by the base product but by our partners add-on module. I will keep you updated if I hear it is related to the Microsoft product.
Regards
Matt
Just to update on this issue. This is now with MBS for development of a patch, so we can look forward to this being corrected in the near future.
Thanks
Matt
Good news
I am sure I replied to this post with the advice that I had posted many of the issues here and on dynamicsusers.net
There are just many versions and many conditions that caused oddities, were fixed and this broke it in two other places! It is just the one I always used to have the most issues with.