Re: Forecast

Version 6.1

That is correct. I wondering why I have to back the planning start date back so far in order for MRP to planned orders for some of the parts. The Facility Planning and Item master appears to be the same as the other parts.

Screen Shots are Attached.

Answers to other questions.
1. In this scenerio the due/need dates of the requirements is Feb 2010.

2. These Parts are component parts. & the start and end dates in Forecast Maintenance and my need requirement dates look accurate. When looking at the Master Schedule Detail(MRP320) the Gross Requirement is as expected but the Planned Receipts show 0 but I do noitce a quantiy in the Net Requirements.

3. Yes they are compononets and are attached in the BOM and we double checked the BOM and the effective and discountinued dates to make sure they were accurate.

4. When checking the Pegging Planning back to the requirement everything also looks good.

Thanks for all the good information, maybe something will stand out as I double check again.

 



________________________________
From: Les Mittman - SBC <lmittman@xxxxxxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Tuesday, October 6, 2009 9:59:07 AM
Subject: Re: [BPCS-L] Forecast

Larenzo:



What BPCS version are you on?



If I understand your problem correctly, you are saying that for certain
parts, if you use the current date as the MRP Start Date, then no Planned
Orders will be created.  But, if you use an MRP Start Date of 11/08/08,
Planned Orders will be created. I am assuming that for other parts, you are
having no MRP planning problems.



I have a few questions and some suggestions of things to look at:



1.    When Planned Orders are being created when the Start Date is
11/08/2008, what are the Due/Need Dates for Requirements and for the Planned
Orders for the Item?  Are they 2008 dates or 2009 dates?  Use MRP
Planning/Inquiry (MRP300) to see this information.  A Print Screen of MRP300
would be very helpful as an example of what you are seeing.



2.    Are these parts Parent End Items?  If so, what are the Start/End
dates in MRP Forecast Maintenance (MRP100) for the Forecast Quantities (in
the KMR File)?  Are they current/future dates or are they dates back in
2008?  When you look at MRP300, what are the Need Dates for the
Requirements?  Since your Demand Code = 3 (Forecast Only), then only valid
Forecast (KMR) records will drive the demand.



3.    Are these parts Component Items?  That is, are they Items used on a
BOM?  If so, check the BOM Effectivity Dates of these Components on their
Parent's BOM.  See if the Discontinue Date is around 11/08/08.  That is, if
the Discontinue Date of the Component is prior to the Release Date of the
Parent's Planned Order, then a requirement for the Component will not be
detected (i.e. the Component is not effective on the BOM).



4.    When Planned Orders are created, use MRP Planning/Inquiry (MRP300) to
peg the requirements up the BOM in order to see what Items are being planned
that are driving the requirements.  By looking at the various
Need/Due/Release Dates and by looking at the BOM's that use the Components,
you should be able to locate where the date problem is.



Please let me know if you have any questions.  You can also contact me
offline.  I would be happy to assist you in tracking down the cause of this
problem.





Thanks.



Les Mittman

847-858-5235

BPCS Consultant for over 20 years.



-----Original Message-----
From: bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx] On Behalf Of
Larenzo Alexander
Sent: Tuesday, October 06, 2009 7:01 AM
To: BPCS Forum Post
Subject: [BPCS-L] Forecast



When we run MRP to generate forecast for some reason, we have to use a
planning start date all the way back to like 11/08/08 so it will generate
planns for some parts.



Any one have any idea of what I may need to check? Her is an example for 1
particular part.



1. Facility Planning

    Requirement Code - S

    Demand Code - 3

    Demand Code 2 - 3

    Order Policy - A

    Demand Time Fence - 30