# Parts Not Showing Demand in Epicor Kinetic: Forecast, Planning BOM and Time Fence Checks > Source: https://netray.co/erp-help/parts-not-showing-demand-in-epicor-kinetic-mrp > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer If a part shows no demand in Epicor Kinetic, MRP either did not see the demand source or filtered it out. The usual reasons are: forecast not entered or not included in the MRP run, a planning BOM that does not explode to the component, a demand outside the planning or time fence window, order releases not firm, or the part not being planned at that plant. ## Kind error ## System epicor ## Erp Epicor Kinetic ## Module Advanced Planning / MRP ## Query parts not showing demand in epicor kinetic ## Alternate Queries - epicor kinetic planning time fence - epicor kinetic planning bom - epicor kinetic forecast entry - epicor kinetic capable to promise ## Applies To Epicor Kinetic and ERP 10.x with Advanced Material Management or standard MRP. Field names differ slightly by release. ## Steps ### Trace missing demand in order **Items:** - Confirm the part is set up for planning at the plant (Part Plant: not marked as non-stock when it should be planned, and a valid lead time). - Look at the source: is the demand a sales order release, a job material, a forecast line or a planning BOM? Check it exists with a need-by date. - For sales orders, check the release is open, has a quantity and a ship-by date, and is not on credit hold or marked so it is excluded from MRP. - For forecast, open Forecast Entry and verify the part, plant, dates and quantities, and that the MRP run options include forecast. - For planning BOMs, check the planning bill is approved and the quantity per and effectivity dates cover the demand date. - Check the time fence settings on the part plant. Demand inside a fence may be firmed and not re-planned, and demand beyond the horizon is not picked up. - Re-run MRP (regenerative if setup changed, net change otherwise) and review the Planning Workbench or Time Phase view. - If a customer-facing promise is the issue, review the capable-to-promise logic separately. ## Sections ### Forecast entry **Body:** Forecast is not demand until MRP is told to use it. Enter forecast in Forecast Entry with the right customer or generic context, then include forecast in the MRP process options. A forecast with dates in the past is ignored. Watch for forecast consumption. When actual orders arrive, they can consume forecast inside a window, so what looks like missing forecast may be a consumed one. ### Planning BOM **Body:** A planning bill lets you forecast a family and derive component demand by percentage. If the planning BOM is not approved, its effective dates do not cover the horizon or the quantity per is zero, no component demand appears. Test with one component: check the where-used to confirm the planning parent exists and carries the expected quantity. ### Time fences **Body:** Time fences protect near-term supply from constant reshuffling. Inside the fence MRP generally will not create or reschedule suggestions the way it does beyond it, so a late demand within the fence can look ignored. Review the fence days against lead times. A fence longer than the lead time means new demand cannot be met by new supply without manual action. ### Capable to promise **Body:** Capable to promise looks at available stock, supply and capacity to give a date. If it shows nothing, it is a data problem upstream (the same checks above), not a separate failure. ## Pitfalls - Forecast entered but not included in the MRP run options. - Planning BOM left unapproved or with wrong effectivity dates. - Time fence longer than the actual lead time. - Running net change after changing setup instead of regenerative. - Demand on a plant where the part is not planned. ## Ai Angle Tracing a missing demand line crosses many tables. A grounded assistant can take a part number and report each demand source it found or did not find, with dates and flags, and show the query. For on-prem Kinetic that all runs on your own network. ## Faq ### Why is there no demand for my part in Epicor MRP? **Answer:** Typically the demand is not flagged for MRP, falls outside the planning horizon or time fence, comes from a forecast or planning BOM that is not included or approved, or the part is not planned at that plant. ### Do I need to run regenerative MRP? **Answer:** Run regenerative after changing setup like planning BOMs, time fences or plant settings. Net change only recalculates parts with changes since the last run and can miss setup changes. ### How does forecast entry work in Epicor? **Answer:** You enter forecast quantities by part, plant and date in Forecast Entry. MRP uses them only if the run options include forecast, and actual orders can consume the forecast within a window. ### What is a planning time fence? **Answer:** It is a window of days in which MRP will not freely create or reschedule supply. It stabilises near-term plans but can hide new demand if set longer than your real lead time. ## Search terms parts not showing demand in epicor kinetic, epicor mrp no demand, epicor planning time fence, epicor planning bom, epicor forecast entry, epicor capable to promise, epicor mrp missing demand --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json