JBA's MPS/MRP

[Doug333@xxxxxxx]

> Business Information Database
> Product Support Alert
> 
> Date : 26-04-99    Version : 3.5.2b    Number : 258    Issue : 1.0
> 
> 
> Inputs incorrect in MPS plan
> Introduction
> 
> This problem only exists in versions 3.5.2a and 3.5.2b and will occur
> whenever a route is used to derive input quantities, i.e. Suggested Work
> Orders, Planned Work Orders, Suggested Item Schedules and Confirmed Item
> Schedules. 
> 
> MPS incorrectly calculates the quantities required for inputs of route
> derived supplies. This problem manifests itself where the 'Quantity per
> basis' on the Company Profile is set to '2' (Per std lot size). Regardless
> of the parent route lot size,  MPS will always calculate the quantity of
> inputs used based on a lot size of 1. 
> 
> For example, if a parent route lot size is 10 and the input quantity per
> lot is 5, MPS will suggest that, for a planned order of 5, 25 inputs are
> required.  This should of course be 2.5.
> 
> Remedial Action
> 
> This problem has been reported as MP/V3/0478, and has been fixed and
> issued as part of PTF number P#EMV30016.
> 
> 
> 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!
> 
> 
> 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.
> 
> 
> > 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?
> >
> 
+---
| 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.
+---