Re: Interesting MRP situation.....Solution revealed

[Zzbpcs@xxxxxxx]

--
[ Picked text/plain from multipart/alternative ]
Both Mac & Ruben offered plausible solutions....

But the answer to our specific puzzler was:

The Purchased Item that was showing unexpected De-expedite Messages
was coded as an MPS Item ( IMRP field = "M" ).
It had many parents, some of which were NOT coded as MPS Items.
MPS generation runs first for only MPS items; found some demand for this
purchased item & created a Planned order for this item ....All Is Well.
Then MRP generation runs for all items ( MPS items and non-MPS items);
it finds some more demand for the Item in question, also finds an existing
Planned Order and suggests rescheduling that planned order.
Solution?
An MPS item should NOT have any parents, grandparents...that are NOT also MPS
Items.
Or another way to say it.... low level items probably ought to be MRP Items
not MPS Items.
In our case, someone used the  "handy copy feature" in creating a new item
number but copied an inappropriate item number.






In a message dated 1/22/02 11:18:18 AM Eastern Standard Time, Zzbpcs@aol.com
writes:



> We had an interesting question from a Buyer recently
> that took quite a while to understand & explain:
> A purchased Item had a new Planned Order WITH an Expedite message.
> We reran the MRP job, looked at this item (actually, a few items)
> and saw a new Planned Order with an Expedite Message.
> We were surprised because the MRP jobs first remove any planned orders
> and then regenerates planned orders as needed.
> Why would it plan an order on the wrong date AND suggest a reschedule date?
> We did solve this "problem"
> but I will send the answer tomorrow
> so you can enjoy the 'puzzle' before I give you the answer....
> Consider this the equivalent to the "Car Talk Puzzler".......
>
>
>









Peace,
Jim