Re: ITH Seq# > 99,999 -- BPCS-L

The last transaction sequence number is stored in the IIM.

During the month end inventory close the sequence number in the ITH is reset
and the IIM is updated with the last sequence.  This is done to ensure data
integrity says SSA.  Duplicate sequence numbers for an item will cause a
looping problem with INV300, at least in 6.10.

During the cycle count selection process the sequence number of the last
transaction is written to the ILI record that is selected for cycle count.
This becomes the bookmark for the cycle count.

Increasing the field size is not a bad idea.  You will need to address the
cycle count area as well as the ITH, YTH, and IIM.

If you are not using cycle counting, as I have not in some accounts, may I
suggest that you create a logical over the ITH by item, descending date and
time, sequence number and use that logical in the INV300.  This will produce
the same inquiry results as the existing INV300 logic.  Also remove the
resequencing of the ITH sequence number in the month end inventory close,
which will drastically decrease the run time.


----- Original Message -----
From: "Robert Write" <robertwrite@xxxxxxxxxxx>
To: "'SSA's BPCS ERP System'" <bpcs-l@xxxxxxxxxxxx>
Sent: Sunday, April 20, 2003 10:27 PM
Subject: RE: ITH Seq# > 99,999


> The majority of the transactions are issues and receipts. W e are a
> process company that uses container control. Yes this is a manufactured
item
> and about the third level in the bill of material.
>
> Please keep the ideas coming.
>
> My main question is "has anybody expanded this field?"
>
>
> -----Original Message-----
> From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
> Behalf Of Lisa.Abney@xxxxxxxxxxxxxxxxx
> Sent: Sunday, April 20, 2003 7:57 PM
> To: SSA's BPCS ERP System
> Subject: RE: ITH Seq# > 99,999
>
>
> Do you use this same item at multiple facilities?  If so, would it be
> possible to use one item number at one facility, and another at the other?
> When we do something like this, we use a very simple variation (like
adding
> an "A" to the end of the first item number), so it's easy to recognize the
> item.  We also give them a common drawing/formula number, which makes
> searches for total usage, etc., easier.  Another possibility (and I guess
> I'm making an assumption that this is a material you're using in
> manufacturing, not something you're selling) would be to use one item
> number in one group of bill of materials, and a second item in another
> group.
>
> 32,000 transactions for one item in one month is a huge amount.  What kind
> of transactions are these?
>
>
>
>
>
>                     "Robert Write"
>
>                     <robertwrite@xxxx        To:     "'SSA's BPCS ERP
> System'"
>                     ail.com>                 <bpcs-l@xxxxxxxxxxxx>
>
>                     Sent by:                 cc:
>
>                     bpcs-l-bounces@xx        Subject:     RE: ITH Seq# >
> 99,999
>                     drange.com
>
>
>
>
>
>                     04/18/2003 01:06
>
>                     PM
>
>                     Please respond to
>
>                     "SSA's BPCS ERP
>
>                     System"
>
>
>
>
>
>
>
>
>
> In checking the ITH file, we have a new item that processes 32,000
> transactions a month. We are in trouble this month when we went over the
> 99999 limit.
> What I am planning on doing is creating a new item number "X", changing
the
> item number for old item in the ith file to the "X" number for Jan-Mar.
> Then
> using a re-sequence program to re-sequence the old number for the April
> records so we can close and buy some time. Long range, I can only think of
> expanding the sequence field.
> Has anyone done this?  Or any better suggestions?
>
>
> -----Original Message-----
> From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
> Behalf Of Sally Bosman
> Sent: Thursday, April 17, 2003 3:26 AM
> To: SSA's BPCS ERP System
> Subject: Re: ITH Seq# > 99,999
>
> Hi,
>
> You have had some very good advice regarding this but please remember, if
> you are going to write a program to resequence your ITH file (Tom Sult's
> reply), you also need to consider updating the IIM file.
>
> We have software that will archive the ITH (not to YTH) and will
resequence
> records.  Please contact me offline if you are interested.
>
> Best regards,
>
> Sally
>
> -------------------------------------
> Sally Bosman
> Director - Small Blue Ltd
> Tel:   +44 1737 824246
> Fax:  +44 1737 824247
> Mob: +44 7767 447107
> www.smallblue.co.uk
>
> ----- Original Message -----
> From: "Syed Arif Inam" <arifinam@xxxxxxxxx>
> To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
> Sent: Wednesday, April 16, 2003 7:28 PM
> Subject: ITH Seq# > 99,999
>
>
> > Hi,
> >
> > We are facing a problem with ITH Seq# field. Some of high
> > transaction items' ITH seq# value has reached greater than
> > 99,999 and the system is creating transactions with zero
> > seq#. We have to keep 3 years of history and these items
> > have reached the limit in less than 3 years.
> >
> > Has anybody came across this problem?
> >
> >
> > Thanks
> >
> > Ver 4.05CD
> >
> > Syed Arif Inam
> > Dey, L.P.
> > Napa, California
> >
> > __________________________________________________
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo
> > http://search.yahoo.com
> > _______________________________________________
> > This is the SSA's BPCS ERP System (BPCS-L) mailing list
> > To post a message email: BPCS-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo.cgi/bpcs-l
> > or email: BPCS-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/bpcs-l.
> >
>
>
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
>
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
>
>
>
>
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
>
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>