|
Had same problem but it was due to a conversion issue. Converted from an HP to AS/400 mgraziano@badgermeter.com -----Original Message----- From: Wolf, Roger [mailto:Roger.Wolf@garmin.com] Sent: Wednesday, September 30, 1998 7:07 AM To: 'BPCS-L@midrange.com' Subject: RE: Interesting Problem We have ran into a problem with the ITH sequence being set wrong. This has effected only 19 items. I am exploring the possibility that INV900 has set the sequence wrong or that one of the program that writes ITH records set it wrong. Has anyone once ran into a problem similar to this? I do have a program that will set these sequences right but am trying to find the cause. We have relative few ITH transaction for these items say 500-1000 ITH records. -----Original Message----- From: Lisa Abney [SMTP:abney@iquest.net] Sent: Wednesday, September 30, 1998 3:01 AM To: BPCS-L@midrange.com Subject: Re: Interesting Problem We have a similar problem, and have solve it with a summary file. We have our ITH file set to 365 days, then summarize to a file that stores info by item, transaction type, facility, etc., with 24 buckets for each item. This lets us see, for example, the CI transactions at a particular facility for a specific item for each of the past 24 months, although not the individual transactions. A similar summary file for as many monthly buckets as you might need might be helpful for you. At 10:46 AM 9/29/98 -0400, you wrote: > > > >We have several items that are high volumn sales items. We have a need to >keep our history of these transactions (ITH) for a year if not longer. It >seems that in the ITH file, there is a sequence number that is created and >added to the file for each transaction. Well, SSA only programmed the >sequence number to go to 99999. Well if you keep the history file without >purging and it is a high volumn item, the sequence number will run out and >it will cause the system to stop logging the inventory transactions in the >ITH file. > >I thought I would post this to for warn user of the possiblity of this >occurring at your locations. > >Thank you > >Joe Royer > > >+--- >| 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.