|
Hi Ho. Problem 2: You will notice in INV500D2 screen a transaction date(it's about 3/4 down the page). This Date is the system date or the (TTDTE) found in the ITH data file. When users are asked to post transactions they are also capable to change this system date. This date, if changed will become the transaction date in the ITH data file. So for example: We are Jan 01/2000 and I am posting a transaction to increase product X. I make a mistake and change the system date to Jan 01/1990 or even Jan 01/2001. The transaction will go through. You can verify if transactions are properly dated in your system by writing a simple SQL statement. From a command line: STRSQL enter SELECT * FROM ITH WHERE TPROD = 'XXXXXXXXXXX' enter XXXXXXXX is the item number. Now, look at the 5th column and verify if the dates are sorted properly(smallest date first) with the sequence numbers (3rd column). If you find a date that is improperly sequenced in this list, you have people changing or overriding system dates when posting transactions. SOLUTION: I hope you have AS/SET ADK. You will need to mod the following programs. INV500D2, INV510D, PUR550D1. These programs have system dates that can be overridden. Send me a line if that is the situation. Problem 3: Reorg programs. Yes you are correct in saying that the ILI and IWI are not identical. You will need to run INV970 and INV972 (IN THIS ORDER) right after month end. Please note (I MEAN RIGHT AFTER MONTH END). Don't ever run this at any other time. I hope this helps Marc Lacelle Royal Canadian Mint lacelle@rcmint.ca > ---------- > From: Bailey, Dick[SMTP:Dick_Bailey@MCFA.COM] > Reply To: BPCS-L@MIDRANGE.COM > Sent: Sunday, May 21, 2000 1:27 PM > To: 'BPCS-L@MIDRANGE.COM' > Subject: RE: Erroneous Balances in ILI/IWI > > > Thanks to great help, I now have determined that an incorrect > inventory balance is created for a Kit whenever the Kit is shipped and the > location selected for the resulting B and = transactions is one for which > no > record exists in ILI. A new ILI record is created and the BPCS program > brings into the new ILI record the sum of 1)the issues FROM THE PREVIOUS > ILI > RECORD processed and 2)the issue quantity of the B transaction. > > So now I have about one hundred balances to correct. > > HOWEVER - I still have two other problems with erroneous ILI > balances, some of which are not related to Kit transactions. > > Problem Two is: the mystical appearance of an ILI record for an > item number several months after the last transaction for the item. > Example: > > One item was built on a shop order in December 1999, and shipped the > same month. No transaction was processed for it after December. In > February, > an ILI record appeared for a quantity of 1 and this added into the on-hand > balance (probably at month-end). The location selected was the location > from > which it had been shipped. This would not have noticed if it hadn't been > for a forklift truck, our primary product. > > Problem Three is: The total of ILI on hand quantities does not equal > the on hand in the IWI file. It is definitely true that the original Kit > problem one generates some of these imbalances - during the month in which > they occur. Then at the end of the month, IWI gets synchronized with ILI > (to > the incorrect ILI balance). However, this is only one source of this > problem. I have seen many references here to having to run a > synchronization > program - and we have run it too, but, as the Kit situation proves, the > result is wrong. > > Does anyone have some other sources of (or solutions to) Problems > Two and Three? > > Dick Bailey > MCFA > > > > -----Original Message----- > From: Bailey, Dick [mailto:Dick_Bailey@MCFA.com] > Sent: Friday, May 19, 2000 9:25 AM > To: BPCS-L@MIDRANGE.COM > Subject: Erroneous Opening Balances in ILI > > > > We're on 6.1 BPCS - and are finding this problem. > Can anybody help > us figure out what to do? > > At the end of each month after running the month end > summarizing of > inventory balances, we see erroneous opening balances. For > example, on a > part that had no inventory (ILI) records on 1/1, and had > only these > transactions during January: > > B transaction -1 from location P04E > = transaction +1 to location P04E > B transaction -1 from location PICK > = transaction +1 to location PICK > > on 2/1 we got ILI records like these: > > Location P04E -98 > Location PICK -194 > > Most of the cases we have identified so far are associated > with allocated > kit transactions like these, but there others that have > taken place when > there is no intervening transaction at all. > > Dick Bailey > MCFA, Inc > > +--- > | This is the BPCS Users Mailing List! > | To submit a new message, send your mail to > BPCS-L@midrange.com. > | To subscribe to this list send email to > BPCS-L-SUB@midrange.com. > | To unsubscribe from this list send email to > BPCS-L-UNSUB@midrange.com. > | Questions should be directed to the list owner: > dasmussen@aol.com > +--- > +--- > | This is the BPCS Users Mailing List! > | To submit a new message, send your mail to BPCS-L@midrange.com. > | To subscribe to this list send email to BPCS-L-SUB@midrange.com. > | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. > | Questions should be directed to the list owner: dasmussen@aol.com > +--- > +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.