Hello,

Please note that your posting about R3483 Not Creating Planning Message for Component Items has been moved to Manufacturing - JDE1 (MOSC) to better deal with this topic"

Please refer to the following document Note 641434.1 - E1: 34: R3482/R3483 MRP Not Planning Correctly or S&D P4021 Appears Incorrect FAQ (Doc ID 641434.1)

Question 1.  What to check if R3482 or R3483 MRP fails to plan lower level items or dependent demand?

MRP is not planning the correct component demand, or blowing down correct demand. i.e. Demand viewed in the P4021, is larger than the order message, or there is no demand and should be.

Answer 1.  If MRP does not appear to create correct component demand, view the P3413 Time Series (G3413/P3413) for more detail, or absence of any detail.

1.  Check the low level codes (LLX) for both the component and parent (item Branch F4102, alias LLX).  Are they being planned at same level?  JDEdwards recommends the Integrity Analysis program (R30601) be run before MRP and Costing Programs, if BOM conversions, or levels of high activity on BOMs have taken place.  Users may also use the On-line BOM validation flag within the Manufacturing Constants (G3041/P3009).  Standard MRP processes items in the order branch plant, than low level codes beginning with LLX = 0, LLX=1, LLX=2 etc.  If the parent and component are the same, the LLX must be corrected. This can be done in 2 ways:

a. Run Integrity Analysis (R03601). Confirm LLX are set correctly, re-run MRP.
b. Activate the BOM Validation in P3009 and re-validate the BOM (open P3002, find the BOM, Select, click OK to save without making changes)

2.  To avoid problems insure that BOM entry and maintenance is done in a manner that will allow programs to generate proper values for LLX.  This means not entering BOM's, costs etc, when MRP is running.  (Copy/pasting from an Excel Spreadsheet, Copy/Paste from Excel is considered 'converted data'.)

3.  Verify the planning horizon.  MRP can handle 52 periods, including past due, however, the system is restricted to 900 days. This impacts those wishing to schedule only using months. You will need to lower the monthly periods to 36 - 44 dependent upon how you've set up your Shop Floor Calendar.  If using a calendar that is strictly work days, 30 a month, it will shorten your monthly periods used for MRP planning.

4.  Validate Effectivity Dates on the BOM's containing the missing demand.  Are they too close to the start date?  Be safe on new BOM's - test with the Effective Start Date back into time.

5.  Validate Planned Yield Percentages.  If set to zero, MRP will not plan.  Reference any PDM Manual - E1: 30: Product Data Mgmt (PDM) Implementation Guides, search on Planned Yield Percentages, an excerpt below: This value represents the planned output yield percent for a step. The system uses this value to adjust the operation scrap percent for the components at that step. Material Requirements Planning (MRP) uses the step scrap percent along with the existing component scrap percent to plan component demand.

6.  Check the work files MRP uses (F34UI001 - F34UI006).  If any contain data after MRP has quit running, SQL out old records.  Reference E1: 34: R3482/R3483 Understanding & Use of MRP (Material Requirements Planning)  Document 626116.1.

7.  If MRP does not appear to create correct component demand, view the P3413 Time Series (G3413/P3413) for more detail, or absence of any detail.

MRP is smart enough to know if a parent demand has a decrease or cancel message and will not plan for the component quantity no longer required, once the parent message is acted upon.  A common mistake is viewing only the S&D inquiry (P4021).  This inquiry only displays unadjusted amounts, not reflecting the action messages in queue waiting to be acted upon.  By using the Time Series (P3413), you can view both adjusted and unadjusted values, and back into why the system is not creating an order for the amount to cover the S&D inquiry amount.  This is done by viewing pegging records,  "W" line type sales orders that perhaps were canceled, and the corresponding WO not yet canceled.

8.  Understand where and what type of demand is created.  Validate the Planning Fence Rule and Planning Fence Day (Item Branch/Additional System Information). 

With the Planning Fence Rule being any of the below and Planning Fence set to desired number of Days:

C - Customer Demand before; Greater of Forecast or Customer Demand after
F - Forecast before; Forecast plus Customer Demand after
G - Greater of Forecast or Customer Demand before, Forecast after
S - Customer Demand before; Forecast after
1 - Zero before, Forecast after
3 - Zero Before, Forecast plus Customer Demand after

R3482/R3483 plans for the Quantity associated with -FWO: Firm Work Order either before the Planning Fence or after the Planning Fence.

Firm Work Order demand (-FWO) is an adjusted demand, not direct from the work order quantity, that is created by a change to the Parent Work Order.  It reflects the date and quantity of the demand based on acting upon the Parent's MRP message like Expedite, Defer, Increase or Decrease.

This demand, displayed on the P3413 Time Series -FWO line, is considered "dependent" demand.  All firmed dependent demand is always considered in MRP planning.  It is not possible to "suppress" the demand associated with -FWO, by manipulating any of the Planning Fence Rules, as the demand associated is due to the Parent WO.

If the demand is not correct, research the component demand using the P3412, Pegging Inquiry.  Look into the parent demand and validate at that level first.

9.  Check  whether data selection is changed, items are made obsolete, or MRP stopped unexpectedly.
If yes, then this may cause corruption in the MRP tables.  We recommend clearing the F3411/F3412/F3413 files via the MRP Performance Tab, Processing Option 1.  Clear F3411/3412/3413 Tables).