RE: ITH Seq# > 99,999 -- BPCS-L

Several years ago, on a different version of BPCS, we had people who wanted to save history of "C" transactions to infinity, to help research cost change evolution of our raw materials. I modified the INV900 program so that when old history went away, the C transactions got copied to a separate file that was not accessed by INV300, but several other INV programs were cloned so that a variety of reports and inquiries would run with infinite access to the C history.

We also added some new reports by vendor that we purchased from, class of part, etc.

You could do something similar. Where INV900 might not get rid of some transactions until they hit ceiling on TIME period you normally keep transactions, you might look at the sequence number cranked up for some item, and if it is over some number, clear out everything older than a more recent date, for items with such high volumes, copying the info to some other file, that could be linked in some reports. If a report does not use the sequence number, use a logical that links ITH with your overflow file so that people get the benefits of accessing the data, without blowing up INV300.

I not know if related, but we recently plagued with duplicate GLD A/P batch numbers (running out of AP batch #s). I suspect it may be related to how we key in the material - lots of people doing lots of tiny batches, compared to past corporate practices.

In checking the ITH file, we have a new item that processes 32,000
transactions a month. We are in trouble this month when we went over the
99999 limit.
What I am planning on doing is creating a new item number "X", changing the
item number for old item in the ith file to the "X" number for Jan-Mar. Then
using a re-sequence program to re-sequence the old number for the April
records so we can close and buy some time. Long range, I can only think of
expanding the sequence field.
Has anyone done this?  Or any better suggestions?


-----Original Message-----
From: Sally Bosman

Hi,

You have had some very good advice regarding this but please remember, if
you are going to write a program to resequence your ITH file (Tom Sult's
reply), you also need to consider updating the IIM file.

We have software that will archive the ITH (not to YTH) and will resequence
records.  Please contact me offline if you are interested.

Best regards,

Sally

-------------------------------------
Sally Bosman
Director - Small Blue Ltd
Tel:   +44 1737 824246
Fax:  +44 1737 824247
Mob: +44 7767 447107
www.smallblue.co.uk

----- Original Message -----
From: "Syed Arif Inam"

> Hi,
>
> We are facing a problem with ITH Seq# field. Some of high
> transaction items' ITH seq# value has reached greater than
> 99,999 and the system is creating transactions with zero
> seq#. We have to keep 3 years of history and these items
> have reached the limit in less than 3 years.
>
> Has anybody came across this problem?
>
>
> Thanks
>
> Ver 4.05CD
>
> Syed Arif Inam
> Dey, L.P.
> Napa, California

- Al Macintyre BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/ See Al at http://www.ryze.com/go/Al9Mac Emergency notification (homeland, weather, etc.) http://www.emergencyemail.org/ Find BPCS Documentation Suppliers http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html