MRP - make to stock to supply orders

Yahoo Archive
1
I've never tried it (and have no idea if it works as advertised), but it sounds like using a suitably large "Days Supply" value should give you single larger qty unfirmed jobs (or PO suggestions) to cover multiple days worth of requirements.

I would also think just specifying an logical (for each Part's typical usage patterns) Min and Multi order qty would do the same.

This works for us (404A.) We also then Lock Job Qty's so MRP doesn't pester us with counterintuitive pull in and reduce or push out and increase messages (which tend to 'churn' day to day back and forth as new requirements are entered and old requirements are fulfilled or change dated.

Rob Brown



--- On Wed, 4/23/08, vandertop26 <josh_vtop@...> wrote:

From: vandertop26 <josh_vtop@...>
Subject: [Vantage] MRP - make to stock to supply orders
To: vantage@yahoogroups.com
Date: Wednesday, April 23, 2008, 10:32 AM






We make all of our parts to stock and then ship from stock. We build
to stock based on sales orders. MRP does not combine quantities in a
single job suggestion for the same part on different releases with
different dates on the same sales order (or different sales orders).

We have tried using the planning time fence to combine these
requirements with no success (obviously the release due dates are
closer than the time fence setting).

We are testing 8.03.404A and using 8.03.305 and have the same problem
in both versions.

Any suggestions?
















____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
2
We make all of our parts to stock and then ship from stock. We build
to stock based on sales orders. MRP does not combine quantities in a
single job suggestion for the same part on different releases with
different dates on the same sales order (or different sales orders).

We have tried using the planning time fence to combine these
requirements with no success (obviously the release due dates are
closer than the time fence setting).

We are testing 8.03.404A and using 8.03.305 and have the same problem
in both versions.

Any suggestions?
3
Have you tried using Days of Supply on the part record? This is what it is used for so you are not planning discreetly

vandertop26 <josh_vtop@...> wrote: We make all of our parts to stock and then ship from stock. We build
to stock based on sales orders. MRP does not combine quantities in a
single job suggestion for the same part on different releases with
different dates on the same sales order (or different sales orders).

We have tried using the planning time fence to combine these
requirements with no success (obviously the release due dates are
closer than the time fence setting).

We are testing 8.03.404A and using 8.03.305 and have the same problem
in both versions.

Any suggestions?






---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

[Non-text portions of this message have been removed]
4
Have you tried using Days of Supply on the part record? This is what it is used for so you are not planning discreetly

vandertop26 <josh_vtop@...> wrote: We make all of our parts to stock and then ship from stock. We build
to stock based on sales orders. MRP does not combine quantities in a
single job suggestion for the same part on different releases with
different dates on the same sales order (or different sales orders).

We have tried using the planning time fence to combine these
requirements with no success (obviously the release due dates are
closer than the time fence setting).

We are testing 8.03.404A and using 8.03.305 and have the same problem
in both versions.

Any suggestions?






---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

[Non-text portions of this message have been removed]
5
> We make all of our parts to stock and then ship from stock. We build
> to stock based on sales orders. MRP does not combine quantities in a
> single job suggestion for the same part on different releases with
> different dates on the same sales order (or different sales orders).
>
> We have tried using the planning time fence to combine these
> requirements with no success (obviously the release due dates are
> closer than the time fence setting).
>
> We are testing 8.03.404A and using 8.03.305 and have the same problem
> in both versions.

I think what you're looking for is the "Number of Days Supply" field (although
I think of it as the "Number of Days Demand" field). When MRP finds demand for
the part, it will look ahead this number of days and combine all demands into
one. So if you make this part every week, set your Number of Days Supply to 7.
MRP will combine the next 7 days worth of demand into one requirement (and
then modify it by min lot, multiple, etc.).

Mark W.
6
We have not tried that...we will give it a shot. TIA

--- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@...> wrote:
>
> > We make all of our parts to stock and then ship from stock. We build
> > to stock based on sales orders. MRP does not combine quantities in a
> > single job suggestion for the same part on different releases with
> > different dates on the same sales order (or different sales orders).
> >
> > We have tried using the planning time fence to combine these
> > requirements with no success (obviously the release due dates are
> > closer than the time fence setting).
> >
> > We are testing 8.03.404A and using 8.03.305 and have the same problem
> > in both versions.
>
> I think what you're looking for is the "Number of Days Supply" field
(although
> I think of it as the "Number of Days Demand" field). When MRP finds
demand for
> the part, it will look ahead this number of days and combine all
demands into
> one. So if you make this part every week, set your Number of Days
Supply to 7.
> MRP will combine the next 7 days worth of demand into one
requirement (and
> then modify it by min lot, multiple, etc.).
>
> Mark W.
>