Old Vens
14th May 2003, 08:16
While executing the batch job "Generate planned MRP orders" we 've got the error message in a logfile : Log_mesg: Fatal error: index -1181 out of dims [1] 3000. After that the job stopped although RDBMS didn't generate any error messages. We had never got this messge before. MRP planning is a thing of great importance so any help appreciated.
Djie-En
14th May 2003, 09:36
Hi,
Are there solutions, which you did imprted last time?
Take a look into the solutions, which objects were imported.
Or do a ttstpsessinfo on the timrp1211(m/s)000 session and
take a look when it was last updated.
GN
Old Vens
20th May 2003, 11:06
Hi Djie-EN,
thanks for the reply. We have IVc4 SP10, difficult to find out the list of solutions needed after that. We have also SP11-12 but didn't install it yet. I guess it concerns only tools but not manufacturing.
ttstpsessinfo analyze seems to be OK. we use standard c4 session. The curious thing is sometimes it works sometimes it doesn't. :)
Djie-En
20th May 2003, 12:23
Hi,
Which version of portingset are you using?
Did you just updated the portingset?
I am asking this because i did ttstpsessinfo on timrp1210m000 and timrp1211s000 on my oper. system (port. 6.1C.06.05) as well on my testsystem (port. 6.1C.06.07), but for both i got an error: "Error in reading sort file record 61 fields scanned, 74 expected". I've just made a case for this problem on B.O.S.
GN
Old Vens
20th May 2003, 12:39
We have even earlier
Portingset : 6.1c.06.01. Trying to update it we've encountered with several erors unfortunately i don't remember which in details. But the strange fact is MRP was OK untill some days ago.
Martin Jung
20th May 2003, 13:23
Hi Old Vens,
we faced a similar problem several months ago. The solution we got from Baan Support was quite simple: increase the Length MRP Time Horizon in Days (default: 2500) to a higher value and the problem should not occur any more.
This was my post in this forum:
http://www.baanboard.com/baanboard/showthread.php?s=&threadid=7105&highlight=MRP
Regards,
Martin
Old Vens
20th May 2003, 14:32
Hi Martin,
Thanks for your help. The point is we do not use RPT items so actively so maybe it is another case. Can you please give some more details concerning increasing the length of MRP time horizon?
Martin Jung
20th May 2003, 14:52
Hi Old Vens,
using RPT-items or not should have no impact on the MRP-run. In our case we could reproduce the problem with RPT-items as well as with a standard item.
The Time Horizon can be changed in the MRP Parameters (timrp0100m000). The online help for this field contains the following hint:
.. you can adapt this to your company's needs, but note that: a too long value results in error messages from the MRP program. A too high value results in unnecessary memory usage..
Hope this helps a little bit more..
Martin
Old Vens
20th May 2003, 15:14
Yes, Martin
I've already found out this quoatation, thank you.
Perhaps indeed out company planning calendar needs some restructruration. we have value of time horizon 6 times less than default. That's because we used another planning method before.
My profile is system administration but wishing to resolve the problem makes me join this process. :)
Old Vens
26th May 2003, 12:50
Yes, indeed after increasing of
Length MRP Time Horizon in Days in MRP parameters the situation became more stable. The time required to fulfil MRP planning became sufficiently shorter. Thanks.