Error fixEpicor KineticAdvanced Planning / MRP

Parts Not Showing Demand in Epicor Kinetic: Forecast, Planning BOM and Time Fence Checks

Error
parts not showing demand in epicor kinetic

Also searched as

  • epicor kinetic planning time fence
  • epicor kinetic planning bom
  • epicor kinetic forecast entry
  • epicor kinetic capable to promise

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.

Applies to: Epicor Kinetic and ERP 10.x with Advanced Material Management or standard MRP. Field names differ slightly by release.

Trace missing demand in order

  1. 1Confirm 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).
  2. 2Look 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.
  3. 3For 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.
  4. 4For forecast, open Forecast Entry and verify the part, plant, dates and quantities, and that the MRP run options include forecast.
  5. 5For planning BOMs, check the planning bill is approved and the quantity per and effectivity dates cover the demand date.
  6. 6Check 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.
  7. 7Re-run MRP (regenerative if setup changed, net change otherwise) and review the Planning Workbench or Time Phase view.
  8. 8If a customer-facing promise is the issue, review the capable-to-promise logic separately.

Forecast entry

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

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

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

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.

Try it here, free

Epicor MRP Run Checklist

Open full tool

A practical checklist for planners running Epicor MRP, with critical checks on part data, lead times, firm jobs and the review of suggestions.

Common 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.

How an ERP-grounded AI assistant handles this

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.

Frequently asked questions

Why is there no demand for my part in Epicor MRP?

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?

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?

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?

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.

Related

How-to

Epicor MRP Runs but Generates No Suggestions

When Epicor's MRP process completes without a job or purchase suggestion for a part you expect one for, the cause is almost always the part's own configuration (Part Class Type, Make Direct, Non-MRP flag, planning Time Fence) or the demand not being linked in a way MRP recognizes, not a defect in the MRP engine. Work through the part's Planning tab, its safety stock and lead time setup, and the demand source (sales order line status, job material requirement) before assuming the run itself failed.

How-to

How to Issue Material in Epicor Kinetic

In Epicor Kinetic you issue material to a job either manually with Issue Material (against the job material line, from a bin and lot) or automatically through backflush when labor is reported. Substitutions are handled by changing the job material part or using the alternate part on the material line, and requests can be routed through the material queue so the warehouse pulls and issues them.

Error fix

Epicor Kinetic: Job Will Not Release in Job Entry

A job in Epicor Kinetic will not release when it is not Engineered, when a material or operation fails validation, or when the part revision on the job is not approved. Open Job Entry, confirm the Engineered flag first, fix any part, revision or method errors shown in the exception panel, then tick Released.

Error fix

Fixing Epicor BusinessObjectException: BPM Directive Errors

A BusinessObjectException that says "A Business Process Management (BPM) directive has raised the following error" means a directive on that business object stopped the transaction, either deliberately via a Raise Exception widget or accidentally via an unhandled .NET error in Custom Code. Expand the InnerException on the error dialog to see the real message and the directive name, then open BPM Designer for that object and method to find the widget that fired.

How-to

Fixing a Slow Epicor BAQ (Business Activity Query)

A slow BAQ in Epicor is usually caused by unindexed join columns, a subquery or calculated field forcing a table scan, or the BAQ pulling far more rows than the dashboard actually displays before filtering client-side. Fix it by reading the SQL Server execution plan Epicor generates, moving filters into the BAQ criteria instead of the dashboard filter panel, and replacing subqueries with joins where possible.

Error fix

Fixing Epicor REST v2 API 401 Unauthorized Errors

A 401 Unauthorized calling Epicor's REST v2 (api/v2/odata) endpoint almost always comes down to one of three things: a missing or wrong x-api-key header, valid credentials but an API key scoped to a different company than the one in the URL, or REST services simply not enabled for that endpoint. Confirm the API key exists and is active in Application Studio (or the classic REST API help page), matches the company segment in the URL, and that the account used for Basic auth or OAuth has the right security group.

AI for ERP

AI for Epicor Kinetic, Beyond What Prism Covers

Add AI to Epicor Kinetic beyond Prism: private LLM over BAQs, BPM data, and REST v2, on-prem or private cloud, with honest guidance on when Prism already covers you.

Stuck on Epicor Kinetic?

Talk to engineers who work inside Epicor Kinetic every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software