Error fixAcumatica ManufacturingProduction Management / MRP

Acumatica production demand 'Prepared': what it means and how to clear it

Error
acumatica production demand prepared

Also searched as

  • acumatica prepared status production demand
  • acumatica demand stuck in prepared
  • acumatica MRP prepared demand not planned

Short answer

In Acumatica Manufacturing, a demand record marked Prepared has been staged by a planning step but has not yet been turned into a supply order (production order, purchase order or transfer). It normally clears when the next planning or order-creation step runs against it. If it never clears, the cause is almost always a missing item setting, a replenishment source that is not defined, or a planning run that was never completed.

Applies to: Acumatica Cloud ERP with the Manufacturing edition (Material Requirements Planning, Production Management). Exact status labels can differ slightly between 2023 R2, 2024 R1 and later releases, so confirm on your own screens.

How to move a Prepared production demand forward

  1. 1Open the planning inquiry that lists the demand and note the item, warehouse, required date and quantity on the Prepared line.
  2. 2Open the Stock Items screen for that item and check the Replenishment Source on the Warehouse Details tab. Production demand needs a source of Manufacturing, Purchase or Transfer to become a supply order.
  3. 3Confirm the item has an active, effective-dated Bill of Material and Routing (revision) for the required date. A missing or expired revision leaves demand unplanned.
  4. 4Check the planning options: lead times, order policy, safety stock and lot size. A demand that produces a zero-quantity requirement after netting stays in Prepared.
  5. 5Run or re-run the planning process (regenerate or run MRP) for the affected warehouse and horizon, then reopen the demand list to see whether the status changed.
  6. 6If the demand should become a production order, create it from the planning results or from the sales order demand and release it as normal.
  7. 7If the demand is stale (the sales order was cancelled or changed), cancel or delete the source document, then re-run planning so the Prepared line is removed.
  8. 8Record what you changed, so planners understand why that item was not planning before.

What Prepared means in practice

Acumatica separates demand from supply. Demand comes from sales orders, forecasts, production order materials and safety stock. Supply is the production, purchase or transfer order that covers it. A status such as Prepared marks a point in between: the system has collected and staged the demand but nothing has consumed it yet.

This is not an error message in the usual sense. It is a state. Planners search for it because lines linger in that state and the next step is not obvious. Treat it like an 'ordered but not yet fulfilled' marker: something upstream was done, and something downstream is missing.

Why demand stays Prepared

The four usual causes are a planning run that was started but not completed, an item with no replenishment source for that warehouse, a Bill of Material or Routing that is not effective on the required date, and a quantity that nets to zero because existing inventory or open supply already covers it.

A fifth cause is data that changed after the run. If someone edits an item's lead time, or a sales order date moves, the staged demand no longer matches the master data. Re-running planning refreshes it.

How to diagnose it quickly

Pick one Prepared line and trace it end to end. Find the source document, the item, the warehouse and the date. Then ask three questions in order: can this item be produced or bought in this warehouse, is there a valid BOM revision on that date, and does inventory already cover the quantity.

Whichever answer is 'no' or 'unknown' is your blocker. Fix that one and re-run planning for a single item first, rather than the whole plant, so you can see the effect before committing to a long run.

Cleaning up stale Prepared demand

Old Prepared lines pile up when orders are cancelled without a follow-up planning run. Schedule planning on a regular cadence so staged demand is rebuilt from current data rather than patched by hand.

Avoid editing the underlying demand tables directly. Acumatica enforces integrity through its business logic, and a direct database change can leave planning records that disagree with the documents they came from.

Try it here, free

Acumatica Manufacturing Edition Setup Checklist

Open full tool

A group-by-group checklist covering the foundation, engineering data, shop floor, planning and costing setup for Acumatica Manufacturing.

Common pitfalls

  • !Running planning for all warehouses when only one is misconfigured, which is slow and hides the real cause.
  • !Assuming Prepared is an error and deleting lines, which can break traceability from sales order to supply.
  • !Leaving item replenishment source blank on newly created stock items.
  • !Using an expired BOM revision and not noticing because the item still opens normally.
  • !Fixing the item but not re-running planning, so the screen still shows the old state.

How an ERP-grounded AI assistant handles this

An AI assistant grounded in Acumatica (for example ERPray, read-only by default and showing the query it ran) can take a Prepared line and walk the same checks automatically: replenishment source, BOM effectivity, netting against stock and open supply. It returns the single blocker per line. For companies that cannot send ERP data to a public cloud, the model can run on-prem against the same data, and nothing is written back without human approval.

Frequently asked questions

Is a Prepared production demand an error?

No. It is a status showing that demand has been staged but not yet covered by a supply order. It becomes a problem only when it never moves, which points to a missing replenishment source, a missing BOM revision, or an incomplete planning run.

Will re-running MRP delete my Prepared demand?

Re-running planning rebuilds planning records from current documents and master data. Valid demand is regenerated, while demand from cancelled or changed documents drops away. It does not remove the underlying sales orders.

Why does a Prepared line show quantity zero after netting?

Netting subtracts on-hand inventory and open supply from the requirement. If those cover the demand, no new order is needed and the line has nothing to convert, so it can sit in its staged state.

Can I change the status manually?

Do not force status changes. Move the demand by fixing its cause and running the next planning step, or by cancelling the source document. Manual status edits risk inconsistent planning data.

Related

How-to

How to Create a Generic Inquiry in Acumatica

Generic Inquiries (GI) are Acumatica's no-code query builder for joining tables, adding filters, and exposing the result as an inquiry screen, dashboard data source, or API endpoint. Open System > Customization > Generic Inquiry, add your base table, define joins and conditions, then run and save. No SQL or customization project is required.

How-to

Acumatica Automation Schedule Not Running: Causes and Fixes

If an Acumatica automation schedule does not fire, check that it is Active, that Next Execution is in the future and in the right time zone, that the schedule's user is valid, and review Schedule History for the failure. On premises, an idle IIS application pool is the classic hidden cause: the site must be warmed up and set to always run so the scheduler can trigger.

Error fix

Acumatica Error: Inventory Quantity Will Go Negative

Acumatica blocks a release when the transaction would drive on-hand below zero for a stock item that does not allow negative quantity, tracked by warehouse, location and lot or serial. Fix it by receiving or adjusting the missing stock first, correcting the wrong warehouse, location or lot on the document, or, if the business really needs it, enabling Allow Negative Quantity on the item or its warehouse setup.

Error fix

Fix Odoo AccessError: You Are Not Allowed to Access Records

Odoo raises AccessError when a user's security groups do not grant a CRUD right on a model through ir.model.access.csv, or when an ir.rule record rule filters the specific record out for that user or company. Fix it by adding the user to the group named in the error, editing the model's access rights, or reviewing the record rule's domain under Settings > Technical > Security.

How-to

How to Void a Check in Sage 100

Sage 100 voids checks through Accounts Payable > Main > Check and Payment Voiding. Select the bank code, choose the check number, and Sage reverses the Cash Disbursements Journal entry and reopens the invoice it paid. A check that already cleared in Bank Reconciliation or falls in a closed period needs an extra step before it can be voided cleanly.

How-to

How to Run Requirements Planning (MRP) in SYSPRO

SYSPRO's MRP engine lives under Planning and Scheduling > Requirements Planning. Set planning parameters per warehouse, run the Requirements Calculation to net demand against supply, then review and release the resulting suggestions as purchase requisitions or work orders. A full regenerative run typically runs on a schedule, with net change runs in between to pick up new activity.

AI for ERP

AI for Acumatica Manufacturing Edition, Built on Your Own Data

Add AI to Acumatica Manufacturing Edition without giving up control of your shop and cost data. Private LLMs and agents grounded in your Acumatica instance.

AI for ERP

AI shop floor assistant for operators working inside your ERP

An on-prem AI copilot answers operator questions against your ERP work instructions, travelers, and routings in plain language, at the machine, without a screen full of menus.

Stuck on Acumatica Manufacturing?

Talk to engineers who work inside Acumatica Manufacturing 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

AI on your ERP

Integrations

Software