MRP Planned Order Due Date

The short answer to the specific problem is you have released the item that
placed the requirement on the child item.  By doing this you have indicated
to MRP it must get the child created ASAP.  The earliest it can be created
is the date the Parent is due since the requirement is now "pas due" from a
lead-time perspective.  I would be surprised if you didn't see the child on
an MRP exception report indicating an "Expedite" condition.
Martin Foglesong
Senior Technology Consultant
Verona, Inc.
PO Box 4094
Lancaster, PA 17604-4094
Phone: (717) 664-4292
Fax: (888) 256-3772
Mobile: (717) 951-8230
mfoglesong@xxxxxxxxxxxxxx


-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx]On
Behalf Of bpcs-l-request@xxxxxxxxxxxx
Sent: Tuesday, January 13, 2004 1:00 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: BPCS-L Digest, Vol 2, Issue 5

Send BPCS-L mailing list submissions to
        bpcs-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help' to
        bpcs-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        bpcs-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of BPCS-L digest..."


Today's Topics:

   1. MRP RELEASE DATE FOR SMALL PARTS Before and After Release of
      Parent (Judi Svoboda)
   2. Re: MRP RELEASE DATE FOR SMALL PARTS Before and After Release
      of Parent (Alister Wm Macintyre)
   3. Horizon Date Question (Richards, Mark)


----------------------------------------------------------------------

message: 1
date: Mon, 12 Jan 2004 15:54:34 -0600
from: "Judi Svoboda" <Judis@xxxxxxxxxxxxxxxx>
subject: MRP RELEASE DATE FOR SMALL PARTS Before and After Release of
        Parent

Hi to All    Using BPCS 405CD.     Have a question concerning MRP due date
of child part planned order before parent planned order is released  and MRP
due date of child part planned order after parent order  is released. Child
part planned order  has due date of one day before parent, when parent is a
planned order. If the parent gets released before the child part is
released, after MRP has run the child part planned order part due date
changes to the start date of parent

.  Why does the  due date for the child change to one day later after the
parent is released?  The start date for the parent is the same when the
parent is a planned order and when it is a released order. But, now instead
of the due date for child part planned order being day before the parent
start date, the due date of child part planned order is day of parent start
date.  Why does the due date for the child part say the day before the start
date of the parent before the release of the parent order and day of the
start date of parent after the release of the parent order?   Would
appreciate any help.

Judi Svoboda
Ridewell Corp



------------------------------

message: 2
date: Mon, 12 Jan 2004 19:08:43 -0600
from: Alister Wm Macintyre <macwheel99@xxxxxxxxxxx>
subject: Re: MRP RELEASE DATE FOR SMALL PARTS Before and After Release
        of Parent

Hi

We also 405 CD
MRP is one of the more complex applications - very easy to get confused.

Rules of thumb & some talking points:
    * MRP planned due dates constantly fluctuate, but typically due date
that people obey is due date in the released order ... purchase order, shop
order, inter-facility resupply order.
    * Parent needs drive Children.
    * Does not matter when Child released ... act of releasing Parent will
have effect on Children
    * MRP has a recommended due date ... you not have to obey it ... you
can release items with due date that your people think wise, due to CAP,
special needs, bottlenecks, setup time etc. but act of setting due date for
an item, other than MRP advice, has impact on MRP due dates for children of
that item whose due date you adjusted
    * Due date for child depends on your engineering ... lead time, time to
make ... if BPCS thinks very short time between make child and use it on
parent, could well say that making it same day is good enough.  Depends on
math of engineering details.
    * If you (like us) have volatility in due dates of some customer
requirements (customers expect short lead time reaction from us, use us
like JIT because THEY do NOT have a good MRP+CAP system or know how to use
it well), it is NOT smart to release shop order on parent item until eve of
you plan to make it ... because until shop order released on parent, what
drives MRP for the child parts is the latest story in the customer order,
but once you release shop order on parent, MRP uses due date THERE to drive
child parts, and ignores volatility of customer order, except advice on
parent shop order, which means greater overhead for your people reaction to
what MRP is saying.


>Hi to All    Using BPCS 405CD.     Have a question concerning MRP due date
>of child part planned order before parent planned order is released  and
>MRP due date of child part planned order after parent order  is released.
>Child part planned order  has due date of one day before parent, when
>parent is a planned order. If the parent gets released before the child
>part is released, after MRP has run the child part planned order part due
>date changes to the start date of parent
>
>.  Why does the  due date for the child change to one day later after the
>parent is released?  The start date for the parent is the same when the
>parent is a planned order and when it is a released order. But, now
>instead of the due date for child part planned order being day before the
>parent start date, the due date of child part planned order is day of
>parent start date.  Why does the due date for the child part say the day
>before the start date of the parent before the release of the parent order
>and day of the start date of parent after the release of the parent
>order?   Would appreciate any help.
>
>Judi Svoboda
>Ridewell Corp

-
Al Macintyre  http://www.ryze.com/go/Al9Mac
Find BPCS Documentation Suppliers
http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html
BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/


------------------------------

message: 3
date: Tue, 13 Jan 2004 08:12:44 -0500
from: "Richards, Mark" <richarma@xxxxxxxxxxxx>
subject: Horizon Date Question

*       We are 6.1.2 MM.
*       We have DC's which are supplied by plants.  The plants also ship
direct.
*       Horizon dates on all item masters are 0.  Horizon date in the system
parameters is 60 days.



Bases on observations of the planned orders created, when BPCS creates
planned re-supply orders it does not use horizon date.  When it creates
planned orders for MPS only items (not a DRP item) it does check the item
master (in our case they equal zero) then uses the parameter value of 60.
True or false?



The dates are calculated as we want them to be but the documentation in
DRP300 states otherwise and I got to wondering ...



o











Mark Richards

Hart & Cooley, Inc.

500 East Eighth Street

Holland MI  49423

W: 616.392.7855 ext 3317

F: 616.392.2323

www.hartandcooley.com <http://www.hartandcooley.com>







------------------------------

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) digest list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.



End of BPCS-L Digest, Vol 2, Issue 5
************************************