Re: Seq# in ITH corrupted

Chronological is not always obvious. To the casual user, the data is in
date sequence, in which time is in ITH but not in INV300.

ITH in INV300 is in sequence of when the transactions actually posted.

It is possible for some transactions to post showing a date other than the
date the transactions were actually posted.

There are screens where user can key in date to be used. This defaults to
"today date" which can be session date ... for example, a work station is
signed on Monday, left signed on overnight, used on Friday. The session
date is still Monday, the date the session started. Some programs can use
the system date, which is the correct date, unless someone has been mucking
in system parameters, which can have major negative complications.

-
Al Mac
-----Original Message-----
From: bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of Don
Cavaiani
Sent: Thursday, February 18, 2010 1:57 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Seq# in ITH corrupted


I forget how important you have said it is to have the ITH seq # correct??

I have managed to 'corrupt' the sequence # of several ITH records for given
part numbers!

Looking at ITH history chronologically, seq# is working, then randomly
reverts back to some already used sequence numbers (probably due to a
program mod of mine), then straightens itself out after that. I don't think
the SEQ# in IIM ever got corrupted, just certain transactions in the ITH
file ??? Other than viewing the ITH transaction which are not "out of
chronological sequence" because of the corruption, can anything more major
happen?

TIA
Don F. Cavaiani
IT Manager
Amerequip Corp.
920-894-7063

"It's amazing what you can accomplish if you don't care who gets the
credit." Harry S. Truman