Re: Missing Requirements

Another thing you might check is the planning date from
MRP120, if you use that or leave MRP500 MRP600 date blank
(better check F1 help on what going on with that), and
whether the due dates of any components of FPO's are "past
due" from perspective of planning date or system date.

We do not use FPO's ... instead we release SO's & PO's which
serve similar function.

Let's suppose you enter an FPO due in a few days, which has
components with lead times that are not zero days (some of
our raw materials have several weeks lead time), then you do
an MRP regen using system date as planning date. I do not
believe MRP is able to properly plan components whose need is
past due at time of MRP first recognition.

SFC350 is one way to access cumulative lead time.

However, if you crank planning date back to several months
ago, and do the regen, then MRP "picks up" requirements for
whatever compoenents, then you can do the regen with a
contemporary planning date, and MRP will not lose what was
picked up.

If you don't want to do this, another way of exploring this
reality is via the simulation MPS menu SSAK02

We get same phenomena on new parts that might get started
with an effectivity date of when they got entered to our
system, then an order goes in asking for the parts
immediately, but some of the components may not have been
date effectivity a few days ago, because this is a new part
that just got keyed in. So MRP does not plan those
components.

Sometimes we get customer orders where they need the product
almost immediately, but our cumulative lead time days is
quite long by comparison. We are supposed to cover this
using minimum balances.

I'm throwing out what I think are "obvious" thoughts based on
the kind of stuff we have managed to mess up with MRP, that
could go wrong for someone else. I hope this think-through,
of things worth checking, is not a waste of your time.
-
Al Macintyre
BPCS 405 CD Computer Janitor