I am using NAV 5.0 and setting up our stock levels for items we keep in our warehouse (on hand).
I am using Reorder Policy = Fixed Reorder Qty and have set Reorder Points and Reorder Quantity.
Each time I run the Requisition Worksheet - Calculate Plan and then Carry Out Action Message I get more PO’s for the same items as the last batch. It appears that the system is not considering the OPEN PO’s that are already created. Can someone tell me why?
Kevin
The issue is not really clear. Are you running the requisition worksheet, then creating a purchase order, then running it again and same demand is being planned for? Not sure what you mean when you say you get more PO’s for the same items as the last batch.
Have you had any modifications done?
Are you changing the purchase orders after the initial creation? Any SKU’s in use, transfer orders going out, mixed location planning issues or forecasts being planned for?
Is it never ending?
I suggest you concentrate on one item in test, load some demand and then plan, make the purchase order, check the demand and supply is balanced and then run the worksheet again.
Purchase Orders are Released or Open?
I have tried this both ways with PO’s open and released
First, let me say that we are not live on the system yet, so there are no orders being created yet. With all items set to Fixed Reorder Qty as the planning method, I run the Requisition Worksheet with no filters and get all of the items that meet the requierment (on hand qty is below the reorder point) and then carry out the action message to create and print new PO’s. After I created the PO’s, I release them. Then if I run the Calcuate Plan again, I get the same PO’s to create again. I appears that the system does not consider the open PO’s in the planning.
Kevin
Actually, and why it should? You haven’t completed the normal workflow, system can’t guess what you are intended to do with these PO “blueprints” - you might have even already deleted them. The same happens, say, when you run Suggest Payments, leave created lines in Journal without any processing and run Suggest Payments again - new lines will be added again.
When you go live and process your POs normally, you shouldn’t expect any problems.
OK - thanks for the response, but I am confused. The only thing missing from my process is to receive the goods - but I may need to issue more PO’s before that happens. Why does the system not consider the newly created PO’s? Must I do something to make the system see them? What “normal workflow” are you talking about?
Kevin
I believe Modris is reading this as though you are leaving them in the worksheet, rather than converting them.
You have not answered the questions in my earlier post. My basic starting point would be to keep it simple, and then see if it is really neverending. Are you changing “anything” on the created PO?
In real life you will run Requsition when you really intend to order something - in other words, its a helper tool for you to create POs quicqly & for the right items/amounts. Actually you can see in Req.Wksh. what is is all about your Item - have you tried Line / Item Availability by… ?
In the form that opens only few colums are visible by default - unhide those you are interested in, and there is col Qty On Purch.Order. Remember, its a tool ONLY, you decide whether to order or not, and when. (In most cases users create POs with suggested items/qty, of course.)
That guy who implements ideal Demand Planning, will move BGates from his 1st place in the list [:)]
I can confirm this does not happen on standard UK version 5
I created a new item with fixed reorder point and set the reorder point at 10 and the reorder quantity at 20. I loaded a sales order for 5, I ran the worksheet for this item and it suggested I purchase 20, I carried out the action messages. An open purchase order was created. I ran the worksheet again and nothing came up.
I ran the worksheet for today out until the end of the year with no forecast included.
I would suggest your issue is with one of my earlier questions, you are either altering the created purchase order in some manner, or you have a modification in this area, either planning or purchase order creation.
I am creating the PO, printing it and then releasing it. There are no modifications to our system. There is mo demand created, but running the req worksheet again suggests the exact same suggested PO. I am limiting the planning to one item and that item has a reorder point, reorder quantity and minimum order qty. Everything is in one location and no other activity is present on our system. I simply seems that the planning system does NOT take into consideration and open PO’s. Is there a setting for that?
Kevin
There is no setting for ignoring PO’s.
Can you try this on Cronus with one new item?
Can you verify it is the same report being run and the version of it to pull in the requirements?
I cannot suggest anything else except contacting your partner or Microsoft. This is not stadnard behaviour and I cannot reproduce it so would suggest it is not in the base code.
I also did a quick test and I hasn’t able to simulate your error. Can you dive detailed steps you are doing? Can you simulate error in a Cronus Database?
Kevin I assume you are using the US version, and I agree with “Adam”, this is not behaving normally. Are you sure that the system is not modified.
One other thing, Requsition process does not care if an order is relassed or not. It should but it doesn’t, so that is not the issue here.
OK - I am now thinking that the dates in the option tab of the Calculate Plan must be the problem. If I set the order date to today and the Ending Date to 12/31/08 and the exclude forecast Before 03/04/08 - I get different results than if I leave all the dates defaulted to today. Can someone suggest what dates to use here?
Thanks!
The order date is the date that will appear on the created orders.
The ending date is how far into the future you plan.
The exclude forecast before date only applies forecast figures after this date.
If you set them all to the same date you still should not get duplicated purchase orders unless you set the order date into the future and the ending date to today.
David you can call me whatever you like [:D]
As for suggested dates it depends slightly
Order Date I would have as today.
Ending Date will depend upon your open order book forward window and the forecast settings.
The Exclude date will depend upon how you are forecasting, but exclude before the current day would be a start depending upon when you are entering forecast dates!
if you are not specifying safety lead times, it can be today
Thanks to everyone who posted a reply. I am told by Archerpoint that this is a bug in version 5.0.
Thanks!