Charley -
Requirements should drop off when the date is earlier than the current date.
You can preserve a requirement by putting a 'hold' code on it, then it won't
drop off until they get past the past due horizon
Are you really only rolling your current date once a month?
BTW - you might consider buying a copy of "Planning in MAPICS" that walks
you through all this logic and how it should be used. Call or send me an
e-mail. $40 including shipping.
Dave Turbide
(603) 964-6903 (office)
(603) 401-0192 (cell)
dave@xxxxxxxxxxxxxxx
www.daveturbide.com
message: 1
date: Tue, 18 Sep 2007 16:57:42 -0700
from: "Charley Simpson" <csimpson@xxxxxxxxxxxxxxxxxx>
subject: [MAPICS-L] MRP and MLI schedule...
Version R6
I need some detail guidance from this helpful body of folks. I am about to
show some ignorance in the nuances of XA MRP behavior when using MLI
schedule so please don't hammer me too hard.
My issue stems from not clearly understanding how XA MRP treats an MLI entry
that has aged past the Current Date on the horizon setup.
My belief is that there is no consumption logic with MLI. So if I was to MLI
schedule 10 units for September, take customer orders for and ship 10 units
in September, and then roll into October without deleting the September MLI
entry for those 10 units, MRP would attempt to plan them again, presuming my
MRP Start Date was older than the September MLI date. Is that a correct
understanding or am I having flashbacks from the 70's??
TIA for any insight and be easy on the old guy... ;-)
Charley
Charley Simpson, CPIM
Director of Operations
805-426-3410
www.turboneticsinc.com <
http://www.turboneticsinc.com/>
As an Amazon Associate we earn from qualifying purchases.