Re: ITH Record Invisible -- BPCS-L

We are on 405 CD.

There is a field in IIM which is used to track the last addition to ITH that drives what shows up on INV300, and there are ways that companies can manage to mess up that tracking, such that you can have transactions that did update inventory, but they not show up on INV300, leading to misunderstanding of reality. This sequence number controls how stuff shows up in INV300, not the actual date time stamps.

When we run INV900 in month end, it gets rid of ancient ITH records for IIM still active. There is a bug at least in 405 CD such that if an Item has been deleted, INV900 ignores any ITH on that item. In some cases we have done an IBM reorg to actually get rid of the deleted IIM records, so ITH and other things containing that item # sit out there to infinity. Along comes scenario where we reassign that item # for some other purpose identity. The "new" item # comes into existence with that IIM field tracking ITH at zero, all those ITH history "valid" for that item, but the sequence #s not valid for today, and new transactions added, which increment the tracking field, but thanks to the appearance of the ancient history, you get a very distorted picture on INV300.

Most of our PR transactions are generated by JIT600 labor reporting. Now there are some circumstances under which we are able to bomb a JIT620 update run, and try to run it again, and in the process we can get MULTIPLE posts of the SAME transaction, multiplied several times thanks to how people try to rerun what bombed. This does show up in INV300, several times, and we have been assuming that it does update inventory, several times.

Inventory transactions can be entered using date of last month. If the General Ledger has been kept open for Accounting adjustments, then it is valid date for other purposes, like it or not, because BPCS is not granular enough to say for what purposes we want to keep some date ranges valid. What this means is that the transaction updates Opening Balance, not current month activity, because it is simulating results of what would have happened had the transaction actually shown up in the month it is dated for. So you see the transaction in INV300 but not the effect of the transaction where you expected to find it. - Al Macintyre http://www.ryze.com/go/Al9Mac Homeland Security latest (public) Bad News http://www.emergencyemail.org/

        We have a case in which a transaction record (PR) exists in the
ITH file but:
1 - It did not update inventory, and

2 - It does not appear in the history in INV300.

Anyone have an idea about what might have caused that?

We're on BPCS 8.0 on an AS400

Dick Bailey