Dear All, I don’t really understand about manufacturing manual especially relates to reordering policy I selected that is maximum inventory and fixed reorder quantity. I would like to ask your help in solving the problem I face. I tried this following manufacturing scenario based on reordering policy= a. Maximum Inventory item A = parent item (production order) consists of item B = 1 pcs and item C = 1 pcs manufacturing policy = Make-To-Stock inventory = 100 pcs Maximum Inventory = 500 pcs Reorder point = 500 pcs reoder cycle = 1W LEad time = 2D item B & C = purchase item manufacturing policy = Make-To-Stock inventory = 200 pcs Maximum Inventory = 500 pcs Reorder point = 500 pcs reoder cycle = 3D LEad time = 2D b. Fixed reorder qty item A = parent item (production order) consists of item B = 1 pcs and item C = 1 pcs manufacturing policy = Make-To-Stock inventory = 100 pcs Reorder Qty = 500 pcs Reorder point = 500 pcs reoder cycle = 1W LEad time = 2D item B & C = purchase item manufacturing policy = Make-To-Stock inventory = 200 pcs Reorder Qty = 500 pcs Reorder point = 500 pcs reoder cycle = 3D LEad time = 2D for case a & b, I create sales order for item A with qty 450 pcs with order date is 040406 and request delivery date is 041506, I use planning worksheet (to calculate MPS & MRP), the results areas follows: case a. : order proposal for Item A : 350 pcs order proposal for item B : 150 pcs order proposal for item C : 150 pcs case b : order proposal for Item A : 350 pcs order proposal for item B : 150 pcs order proposal for item C : 150 pcs The things that I don’t understand why results are the same for both and what will be the different then ? I am thankful for your attention. Rgds, Mark
Hi Mark What are you trying to achieve? You have configured the scenarios to be the same. With Maximum once the reorder point is reached it will order the maximum quantity, with fixed reorder when the reorder point is reached it will suggest the reorder quantity. You have these set to 500, so the results will be the same. Due to the issues surrounding Maximum reordering policy if you have any choice, go fixed reorder.
which version are you using? 4.0 sp1 with reorder point is a mess. [B)]
The fixed reorder policy, or the calcualtions involving the reorder point? Would you care to elaborate?
just try the scenario b form mark’s example. (but you can also try on item 1000 in demo db) Run regenerative calculation for item A. Carry out action message. Run calculation again. … it loops and never stop to suggest you new actions, same problem also when you use Maximum Quantity (in that case suggestions are different in quantity and/or due date) in my test: FIRST RUN: create order qty 500 due date 05/04 create order qty 500 due date 15/04 SECOND RUN: cancel order on due date 05/04 reprogram order 15/04 to 14/04 create new order on 15/04 THIRD RUN: create order due date 05/04 cancel order 14/04 cancel order 15/04 FOURTH RUN: cancel order due date 05/04 create order 14/04 create order 15/04 Then it loops 3th, 4th run. In my humble opinion the error is in the new function SuggestSupplyForROPDemand of codeunit 99000854 where there is a mess in using of Temporary and Local variables SupplyInvProfile and DummySupplyInvProfile. (I miss Navision 2.60 [V] [^])
Dear all, Tks a lot for your prompt reply and I am sorry that I forget to tell about location set up. I didn’t set location in components at location field on manufacturing set up but I set location blue and use it as filter when calculate MPS/MRP, and the result is what I have written but when I set components at location for example blue, meanwhile I create two SO with two locations (blue and red), the purchased item will be concentrated in the blue but Production Order locations separated. the blue and the red production orders’ production journal automatically consumed the components in red when posting. It’s a miracle. I don’t use transfer order. If I set nothing for location, the planning parameters I set is work, so I think nav. 4.sp1 is not a mess. I just wonder why the parameter is not work when I use filter field i.e. blue location when calculating MRP/MPS in planning worksheet and emptying components at location field. rgds, Mark
Hi Mark The componenets at location field gives navision a base setting for the planning parameters of a main location when SKU’s are not used. It should never be left blank as Navision simply does not like it. I cannot remember all the implications from this setting, but if you set the production order to be created at GREEN, and your components at location is set to BLUE, then Navision will try to consume the components at the BLUE location. This is different to the location filter on the run, this looks at demand in the area and also plans for replenishment, so you could potentially miss demand on a separate location (I think I am not checking this as I write!).
Dear Steven, Thanks a lot for your prompt reply, I am really indebeted to you, I mean every questions I send you will give the answers asap and although I don’t know yet but it is a hint and could be the correct answers and I think you could be the VMVP (very most valuable professional), I am not kidding but it’s from my heart. Also for others are the same, they give a good answer too. Indeed my questions are very many but you never bore to reply. I hope I can receive the good conclusion or answers then. rgds, Mark