× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: IWI and ILI Imbalances
  • From: Odonnell John CF CH <john.odonnell@xxxxxxxxxx>
  • Date: Thu, 29 Jun 2000 09:24:59 +0200

The TCOM field for the B transaction is populated in INV500, the user can
enter whatever he likes in the comment field and this feeds through to the
TCOM field in ITH.  You can change the comment description in the ITE so
that when the user enters INV500 he may be asked for a "PO Number" but
essentially it is a free field.

Rgards
John O'Donnell

-----Original Message-----
From: klvanhorn@lozier.com [mailto:klvanhorn@lozier.com]
Sent: Wednesday, June 28, 2000 5:37 PM
To: BPCS-L@midrange.com
Subject: RE: IWI and ILI Imbalances


HP/Oracle 6.0.04

We had a similar situation:
We had 2 items on the same day that had no ILI or IWI records.

PR transaction for 4 and 1 respectively

B transaction for  4- and 1- respectively

In both cases the ILI updated correctly but the B transactions did not
update IWI.

Both B transactions had a Transaction Comment in ITH (TCOM) of "VC-5".  This
has no meaning anywhere in our system.  SSA helpline checked with the
programmers and it has no meaning to them.  I queried ITH and this does not
appear anywhere else.  This field is populated by BPCS.

Does this mean anything to anyone?  

Dick do you have anything in this field?

Kent Van Horn
lkvanhorn@huntel.net


        ----------
        From:  Bailey, Dick[SMTP:Dick_Bailey@MCFA.COM]
        Sent:  Tuesday, June 27, 2000 3:28 PM
        To:  'BPCS-L@midrange.com'
        Subject:  RE: IWI and ILI Imbalances

                What we have sounds different - the resulting inventory
balance is
        correct in either ILI or IWI but not both.  Here are two specific
examples:

                #1 - Item G3KFC/3404770, for which no ILI or IWI record
existed on
        6/1, we had:

                PR transaction for a quantity of 1 on 6/13.

                Result was Receipts of 1 in both the IWI and ILI records,
and a
        total of -1 Adjustments in the IWI record. 

                No other transactions prior to this one.  ILI shows one on
hand, IWI
        shows zero.

                #2 - Item 9542703010, for which on 6/1 there were no ILI
records,
        and an IWI record containing zero opening balance, zero adjustments,
zero
        receipts and zero issues.

                On 6/22 we had a B transaction for 2 and a = transaction for
2 (We
        shipped this kit) - and ended up with an ILI record containing
Issues of 2
        and Receipts of 2.  The IWI record, however, had Receipts of 3 and
Issues of
        2.  So ILI showed zero on hand but IWI showed -1. 

                No previous transactions since 3/22.

                Dick


                        -----Original Message-----
                        From:   Lacelle, Marc [mailto:LACELLE@rcmint.ca]
                        Sent:   Tuesday, June 27, 2000 8:32 AM
                        To:     'BPCS-L@midrange.com'
                        Subject:        RE: IWI and ILI Imbalances

                        Hi Ho.

                                How about that INV971D. Kidding.

                                We are also experiencing the same problems.
SSA
        cannot duplicate the
                        problem and this leaves us to fix the problem
ourselves. SSA
        when trying to
                        duplicate the problem probably only generate 10
        transactions. We on the
                        other hand generate about 50,000 transactions of
which 10 or
        so items are
                        affected.
                                
                                We to have noticed the B and T transactions
are
        giving false
                        information. For those who are wondering what we are
talking
        about. This is
                        the situation.

                                In your INV300 you will notice a MTD and a
YTD
        column. These columns
                        are the sum of Issues - Receipts - Adjustments -
Sales for
        the month and
                        year.

                                The B and T transactions:
                                        The "B" transaction will affect the
Issue
        and Sales
                                        The "T" transaction will affect the
        Adjustment

                                For some unknown reason the quantities are
being
        posted in the wrong
                        place. 
                                        Example: A "B" transaction for 20
will post
        against the
                        ADJUSTMENT and SALES. Remember the "B" should affect
the
        ISSUE and the
                        SALES. 

                                What those this do to my inventory Marc, you
ask?
        Nothing. Your
                        inventory is adjusted properly, since the
calculation is
        (Opening + Receipts
                        - Issues  - or + Adjustments). Even  though the
transaction
        was posted
                        incorrectly as an adjustment the calculation for
your on
        hand is correct.

                                I have written a program that fixes the
problem for
        YTD. Since your
                        MTD at the end of each month goes to 0, I never
bothered to
        write on that
                        fixes the MTD.

                                Hopefully Dick, someone else will notice
this and we
        could make a
                        case to SSA. Let's keep in touch on this one.

                        Marc Lacelle
                        Royal Canadian Mint
                         
                        > ----------
                        > From:         Bailey,
Dick[SMTP:Dick_Bailey@MCFA.COM]
                        > Reply To:     BPCS-L@midrange.com
                        > Sent:         Sunday, June 25, 2000 11:36 AM
                        > To:   'BPCS-L@midrange.com'
                        > Subject:      IWI and ILI Imbalances
                        > 
                        > 
                        > 
                        >       Here I am again,  trying to maintain some
faith that
        BPCS on hand
                        > balance programs work - We keep getting
out-of-balance
        conditions between
                        > IWI and ILI MTD adjustment balances during the
month, with
        no apparent
                        > pattern. In this case the IWI record always is
incorrect.
        It is not a new
                        > IWI record, and is not related to a transaction in
which a
        new ILI record
                        > is
                        > created. 
                        > 
                        >       The transactions involved include B and T so
far.
                        > 
                        >       Anybody have a clue what we have to fix??
(And
        please don't tell
                        > me to run a program to re-synch the records; we
know how
        to do that.)
                        > 
                        >       Dick Bailey
                        >       MCFA
                        > +---
                        > | 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
+---
+---
| 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.