Re: JBA's MPS/MRP -- SYSTEM21

Sorry for the very late reply and I hope you have this solved already.  We
had the same problem following an upgrade from V2 to V3.5.2b and got JBA
involved.  The bug was confirmed and our local JBA office helped fix it.
Thank heavens for having source code!  Someone at JBA apparently thought no
one used anything but a quantity per of 1.  We had always used 100 as our
"standard lot size" to buy a couple of extra decimal places in the product
structure.  We were finding requirements 100 times higher than expected.
This was finally fixed in less than a day after messing around for weeks
with a variety of people.  This really should be in JBA's knowledge base by
now since we found and fixed this in July of 1999!

Please let me know if I can help further.

Best,

Bruce Stern
sternb@home.com

----- Original Message -----
From: <lorena_frausto@gcamerica.com>
To: <JBAUSERS-L@midrange.com>
Sent: Thursday, October 19, 2000 10:36 AM
Subject: Re: JBA's MPS/MRP



I  checked on this setting and we have it set to '2' already. I was hoping
that was it , but no luck. So there must be a bug in V3.5.2b because this
was not happening when we were running on V.3.5.0. This problem arose when
we went to V3.5.2b.



Thanks for your input!!

Lorena



                    "STANLEY ROCKEY"
                    <srockey@btcgrp.com        To:
<JBAUSERS-L@midrange.com>
                    >                          cc:
                    Sent by:                   Subject:     Re: JBA's
MPS/MRP
                    owner-jbausers-l@mi
                    drange.com


                    10/19/00 10:18 AM
                    Please respond to
                    JBAUSERS-L





There is a setting in the second screen of the Mfg Company Profile called
'Quantity Per Basis' which can be set to:
        1=Per 1, or
        2=Per std lot size
I suspect that the problem is that you have this set to 1, per each, in
which case the component's usage should be 1 and not 1,118.  If you change
this setting to a '2', then MPS should take the 1,118 per of the component
as the required quantity per 1,118 of the parent.

The recent users I have worked with have all used '1' Per Each so, if you
have this field already set to a '2', you have a BUG.


----- Original Message -----
From: <lorena_frausto@gcamerica.com>
To: <JBAUSERS-L@midrange.com>
Sent: Tuesday, October 17, 2000 12:25 PM
Subject: JBA's MPS/MRP


> Hi,
>
> We're using JBA v3.5.2b and we're having a problem with MPS.
>
> The MPS problem that we have is that in order to make one finished good
> item it needs an outrageous amount of its components. In our situation, a
> finished good item that we have, has 4 component items. Its lot size is
> 1,118 and the quantity per for its components is also 1,118. One of those
> component items is also a parent item. This item has lot size of 1,118
and
> its 2 component's quantity per is also 1,118. For every one item that we
> need to make of the finished good item, MPS calculates that it needs
1,118
> each, of its components. When it gets to the level 1 in order to make the
> 1,118 of each of the components; the program calculated that it needs
> 1,249,924 each of level 1 components. This amount is always reflected in
> confirmed work orders. When we review MPS we see that a confirmed work
> order quantity is 1,249,924.
>
>
> Is anyone having the same problem?
>
>
> LorenaF.
>
>



+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---

+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---