Stock Requisition schedule

sabzam

Dear All,

I need to schedule the purchasing as follows.

Let's say that i purchase item x on the following dates:

1/03
1/06
1/09
1/12

I may opt to make more orders but only if enough requests are available so as to satisfy the minimum requirements.

Is this possible?

MarkHamblin

It depends a bit on what you mean by "schedule", and whether you're using 2013 or not. 2013 adds a number of additional planning parameters and make this scenario easier. I'll assume you're in 2009 (same concepts apply in 2013, but you have better control).

In 2009, the field you'll want to play with is "Reorder Cycle" - NAV will combine demand for the period specified in this field. So if you enter "3D" here, NAV will combine the demand for 3 days based on the order date you run the worksheet for. You would still need to run the worksheet manually or create a batch job to do it, but you will get an order suggestion scheduled for every 3 days. If your date format in your example is day/month, then of course enter "3M" here for the same result - one order every 3 months.

One very important note though: in 2009, when NAV combines demand, it sets the order date for the supply based on the last demand date instead of the first (this is bad design). So if you have a 3M reorder cycle, and you need items for customers on Jan 1 and on March 1, NAV will create the PO to supply for March 1.

You also need to decide which reordering policy you're going to use. If you're ordering every 3 days, I'm guessing these are high volume, short lead time items. Lot-for-lot is probably your best choice in this scenario, since it won't artificially inflate your inventory without demand. However, in 2009, lot for lot does not respect order modifiers, making it less useful (see post and comments at http://blogs.msdn.com/b/nav/archive/2011/11/15/order-modifiers-and-exceptions.aspx). If you want to use lot-for-lot, there is some code I can provide to allow it to respect order modifiers.

- Mark

Andwian

MarkHamblin wrote:

It depends a bit on what you mean by "schedule", and whether you're using 2013 or not. 2013 adds a number of additional planning parameters and make this scenario easier. I'll assume you're in 2009 (same concepts apply in 2013, but you have better control).

In 2009, the field you'll want to play with is "Reorder Cycle" - NAV will combine demand for the period specified in this field. So if you enter "3D" here, NAV will combine the demand for 3 days based on the order date you run the worksheet for. You would still need to run the worksheet manually or create a batch job to do it, but you will get an order suggestion scheduled for every 3 days. If your date format in your example is day/month, then of course enter "3M" here for the same result - one order every 3 months.

One very important note though: in 2009, when NAV combines demand, it sets the order date for the supply based on the last demand date instead of the first (this is bad design). So if you have a 3M reorder cycle, and you need items for customers on Jan 1 and on March 1, NAV will create the PO to supply for March 1.

You also need to decide which reordering policy you're going to use. If you're ordering every 3 days, I'm guessing these are high volume, short lead time items. Lot-for-lot is probably your best choice in this scenario, since it won't artificially inflate your inventory without demand. However, in 2009, lot for lot does not respect order modifiers, making it less useful (see post and comments at http://blogs.msdn.com/b/nav/archive/2011/11/15/order-modifiers-and-exceptions.aspx). If you want to use lot-for-lot, there is some code I can provide to allow it to respect order modifiers.

- Mark

What a great and thorough explanation! Thanks Mark!