How to drive requirements for a Purchased item from another purchased item?????

Hi all,

I have an issue that I am sure will stump most people but I am hoping that
someone out there has a potential solution. Here is the scenario:

We have ITEMA that is a purchased item. We want to use MRP to drive the
requirements for this item based on Demand (Forecast). The only problem is
that we want the requirements for ITEMA to drive requirements for ITEMB
which is also a purchased product.

The biggest issue, is that I can trick the system in different ways using
planning bills, phantom bills etc etc but they all drive requirements form
ITEMB from the demand for ITEMA and not the Requirements for ITEMA.

EXAMPLE: I have to buy 1 EA per month for the next six months. I currently
have 3 EA's on hand. In order to buy 1 EA of ITEMA, I need to buy 2 EA's of
ITEMB. Since I have 3 EA's of ITEMA on hand, I only need to buy 3 EA's of
ITEMA over the next 6 months, which means I only need to buy 6 EA's of
ITEMB. Using all backdoor approaches, the system continually thinks I need
to buy 12 EA's of ITEMB to meet the demadn of 1 EA per month of ITEMA. It
wuill not look at see that I only need to buy 3 EA of ITEMA so therefore
only buy 6 EA's of ITEMB.

Of course BOMs do not explode down when the parent item is a stocking type =
P. I cannot use stocking type = M as then MRP generates Work Orders which I
do not want.

Any ideas would be greatly appreciated!!!!!

EnterpriseOne XE SP19 Update 6
Intel NT, Oracle 9.0i

Peter J Fourie

Peter,

What do your supply demand rules look like? It sounds like they do not include the on hand quantity in the calculation.

peterfourie <[email protected]> wrote:
Hi all,

I have an issue that I am sure will stump most people but I am hoping that
someone out there has a potential solution. Here is the scenario:

We have ITEMA that is a purchased item. We want to use MRP to drive the
requirements for this item based on Demand (Forecast). The only problem is
that we want the requirements for ITEMA to drive requirements for ITEMB
which is also a purchased product.

The biggest issue, is that I can trick the system in different ways using
planning bills, phantom bills etc etc but they all drive requirements form
ITEMB from the demand for ITEMA and not the Requirements for ITEMA.

EXAMPLE: I have to buy 1 EA per month for the next six months. I currently
have 3 EA's on hand. In order to buy 1 EA of ITEMA, I need to buy 2 EA's of
ITEMB. Since I have 3 EA's of ITEMA on hand, I only need to buy 3 EA's of
ITEMA over the next 6 months, which means I only need to buy 6 EA's of
ITEMB. Using all backdoor approaches, the system continually thinks I need
to buy 12 EA's of ITEMB to meet the demadn of 1 EA per month of ITEMA. It
wuill not look at see that I only need to buy 3 EA of ITEMA so therefore
only buy 6 EA's of ITEMB.

Of course BOMs do not explode down when the parent item is a stocking type =
P. I cannot use stocking type = M as then MRP generates Work Orders which I
do not want.

Any ideas would be greatly appreciated!!!!!

EnterpriseOne XE SP19 Update 6
Intel NT, Oracle 9.0i

Peter J Fourie

Peter,

What is your underlying issue at hand? I don't see how demand for ItemB can be dependent on ItemA, unless ItemB is actually incorporated into ItemA during it's manufacture. If this is the case, that is where the *OP Outside Process functionality kicks in. Are you unaware of the Outside Process (ItemA being an "M", using a work order to generate purchase req/order of ItemA*OP10 to track the commitment and payment for the supplier to take your ItemB and turn it into ItemA) - or are you fully aware of it, but want to stay away from it?

If the latter, I can sympathize, and would also like to know of any creative workaround that someone may have developed... Not so much that *OP is bad, just that it is so different, and outside of the normal MRP view of things.