RE: ITH transactions of the type #

["Chick Doe" <Cdoe@xxxxxxxxxxxxxxxxxxxxxx>]

we have run into several of the problems mentioned with duplicate sequence 
numbers. as such we have written an rpg program and we resequence the ITH 
sequence number and update the IIM TSEQ field each evening. the reason for 
having to do this is that the bpcs configurator product has a very nasty habit 
of deleting (inactivating) an item master record and then creating a new copy 
of that item master. when it does the new record is formatted with a zero in 
the TSEQ field. thus any new ITH transactions for that item start over again 
with duplicate seq numbers. by resequencing the ITH file each evening we avoid 
the various problems that have been mentioned as a result of having duplicate 
seq numbers in the ITH file.

>>> LACELLE@rcmint.ca 03/29 5:53 AM >>>
Hi Ho again.

        Still raining. Can't complain

        You are correct Les in saying that if sequence numbers are
duplicated in the ITH file, the  INV903D will loop. On top of that, when
running INV903D with duplicates the system will actually create blank
sequence numbers. This is getting complicated. The only work around is
saying no to purging ITH records when submitting INV903D. I also wrote a
program to re-align the ITH sequence numbers. 

        From what I can see, the problem causing this is any program writing
to the ITH file (re:INV550, INV500, PUR550 etc.). The user can change the
transaction date (sysdate). If a transaction is entered today with a date,
lets say two years ago(by mistake of course), the INV903 program will purge
this transaction even though it transpired in the previous month. The
transaction disappears and reconciling becomes quite difficult. I have made
all dates in these programs non-updateable(is this a word). 

        One more thing(this is getting to long for me). You mention TSEQ
(IIM) with ITSEQ (ITH). You are forgetting the old HPC file. What's the HPC
file, commodity codes. If you re-sequence the ITH file and update the IIM
sequence number you cant do this with the HPC file since it has no sequence
numbers. You must take that in consideration when writing the program that
will update the sequence numbers.   

         

> ----------
> From:         Lacelle, Marc[SMTP:LACELLE@rcmint.ca] 
> Reply To:     BPCS-L@midrange.com 
> Sent:         Friday, March 24, 2000 12:02 PM
> To:   'BPCS-L@midrange.com' 
> Subject:      RE: ITH transactions of the type #
> 
> Hi Ho.
> 
>       Version 6.02 gives you the option of deleting ITH records when
> running INV903(month end). You can set number of retention days for your
> ITH
> file through SYS800 then Transaction History System Parameters(SYS824D). 
> 
>       Those transaction types "#" don't do a thing. They are added to the
> ITH file when you add or manualy update a cost using CST100.
> 
>       My suggestion to you. NEVER DELETE ITH RECORDS. 
> 
> > ----------
> > From:       Warren, Rick[SMTP:RWarren@burco.com] 
> > Reply To:   BPCS-L@midrange.com 
> > Sent:       Friday, March 24, 2000 9:51 AM
> > To:         'BPCS-L@midrange.com' 
> > Subject:    ITH transactions of the type #
> > 
> > 
> > We are AS/400 6.02 MM on OS/400 V4R4.
> > 
> > We have looked at the description for the # transaction type and noticed
> > it
> > says "Cost Adjustment from CST/ACP".  Our finance department ignores
> these
> > transactions when they post to the general ledger so we are wondering if
> > we
> > could delete them from the ITH.
> > 
> > Does anyone know if deleting them would create any problems?
> > +---
> > | 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 
+---
+---
| 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
+---