Hello everyone,

Our MRP process is crashing giving the following error message.

Planning horizon of 3000 days exceeded for Item xyz; please increase parameter.

Why shall we increase at this time the "Length MRP Time Horizon in Days" ( we have it to 2000 since 1999) at this point in time?

We've been running MRP for over 7 years and never had this error.

I'll appreciate any help and thanks in advance.

Carlos

Hi Cherokee,

Horizon of 2000 days seems quite ok.

What parameters are used?
for the item: orderquantity, leadtime, first allowed orderdate
MRP: no of orders per day ?

Sounds like a combination of small orderquantity, 1 order per day and a huge demand don't fit in 2000 days.......

Instead of enlarging the horizon I would think that the item properties are off

The other area to check for the item would be in its routing if it is a manufactured item. Check the run time etc. are not strangely large.

Hi

Check your patch level or if a patch or service pack has been applied recently. I know Guido Meijers, previously of Baan PMG/PEG did a patch around this issue which may have changed the behavior from what you are use to. The other suggestions were also good because an item/routing my also be out of range.

Hello again,

I found that the EOQ is set to 1 and Minimum Order Qty is 95. EOQ field help reads that EOC should be >= Min Ord. Qty. Baan gives a warning but lets save the item with this settings. Also I noticed that we've been having this always, we have over 6000 items with this type of set up.

This item is purchase Item and has no routing.

We have not added any patch lately. I think this problem is related to data.

Also, it is the second time this happen to us. Coincidently, three weeks ago, people here started to use MPS for certain Items ( before we had not MPS items). I wonder if this could cause this problem or has something to do with it.

Carlos

Hello everyone,

After further investigation this is what I have found.

If I have a MRP firm-planned order with not dates, No Fix Order Date, No Fixed Delivery Date, before I run MRP engine (Plan Order Date and Plan Delivery Date must be calulated by BaaN). When the MRP engine runs, BaaN creates an internal date table starting on the earliest date which is 0, caused by the order with no dates up to 3000 days. So 3000 days are created and overflown the planning horizon but it isn't even close to today's date. This only happen while generating the Reschedule Messages. So BaaN aborts and finishes the MRP engine process.

It also creates Plan MRP Inventory transactions for the item in question with no transaction dates in table tirmp010! This is not good!

The tisfc.dll0200.backward(....) function returns 0 as plan.stdt if input dates to this function are 0 from the MRP Plan Order.

Does anyone know if this is a bug? Or why BaaN let you save a MRP firm-plan order with none of these dates, if can cause this problem?


while not abort.mrp and date.table(max.stoc.table.i) < timrp010.date
increase.max.stock.table.index.o2b1a1()
if not abort.mrp then
date.table(max.stoc.table.i) = startdate
endif
startdate = startdate + 1
endwhile
....

function increase.max.stock.table.index.o2b1a1()
{
max.stoc.table.i = max.stoc.table.i + 1
if max.stoc.table.i > max.horiz.table.i then
abort.transaction()
display.item.llcd()
if tccom.dll0200.server.running() then
error.message = sprintf$(strip$(text.tab(1,1)),
max.horiz.table.i, cmrp.item)
print.error.message()
else
| Internal MRP table overflow for item %s; MRP process
| aborted
mess("timrp12103",1, max.horiz.table.i, cmrp.item)
| Planning horizon of %d days exceeded for item %s.
| Increase the parameter
endif
abort.mrp = true
endif
}


Thanks in advance.


Carlos
:eek:

Indeed there is a solution for this problem...(Planning horizon of 3000 days exceeded for item...)

SolutionID
117837


Thanks and hope this help someone else

Carlos
:cool:

Hi

Check your patch level or if a patch or service pack has been applied recently. I know Guido Meijers, previously of Baan PMG/PEG did a patch around this issue which may have changed the behavior from what you are use to. The other suggestions were also good because an item/routing my also be out of range.


Yes Tim, I did a fix on the horizon when MPS items where involved which have a different planhorizon then the predefinied MRP horizon.......but I guess Carloss has found that patch ;)