How to Run Requirements Planning (MRP) in SYSPRO
how to run MRP in SYSPRO
Also searched as
- SYSPRO requirements planning calculation steps
- SYSPRO generate purchase requisitions from MRP
- SYSPRO MRP action messages explained
- SYSPRO regenerative vs net change MRP
Short answer
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.
Applies to: SYSPRO 8 and SYSPRO 9 (Avanti), editions with the Planning and Scheduling module
Run and release a Requirements Planning calculation
- 1Confirm setup under Planning and Scheduling > Setup > Requirements Planning Parameters, including planning horizon and warehouse-specific settings.
- 2Check each stock item's Planning tab in the Inventory/BOM module for a valid Buy or Make code, lead time, order policy (lot-for-lot, fixed order quantity, or economic order quantity), and safety stock.
- 3Go to Planning and Scheduling > Requirements Planning > Requirements Calculation.
- 4Choose Regenerative to recalculate every item and warehouse, or Net Change to process only items with activity since the last run.
- 5Select the warehouse(s) and planning horizon for the run, then start the calculation.
- 6Open the Planning Workbench (or the MRP Action Messages inquiry) and review exception messages - reschedule in, reschedule out, cancel, and expedite.
- 7Use Firm/Release Planned Orders to convert accepted suggestions into purchase requisitions for bought items or work orders for manufactured items.
- 8Route released requisitions through the normal Purchase Order approval workflow.
- 9Run Net Change on a short, regular cadence (daily, or more often for high-volume operations) so new sales orders and receipts keep planning current between full regenerative runs.
Regenerative vs Net Change runs
A Regenerative run recalculates every planned item across the selected warehouses from scratch, ignoring what the last run produced, and is the most accurate but also the slowest option - typically scheduled overnight or weekly depending on data volume. A Net Change run only reprocesses items where something relevant has changed (a new sales order, a receipt, a BOM change) since the last calculation, which runs far faster and is safe to run several times a day to keep planned orders current without a full recalculation.
Most SYSPRO sites run one Regenerative pass on a fixed schedule (often overnight) and Net Change through the day, since relying only on Net Change over a long stretch can let small inconsistencies accumulate that a full regenerative pass clears out.
Reading MRP action and exception messages
The Planning Workbench surfaces exception messages rather than just a flat list of planned orders, which is where the real planning work happens. A Reschedule In message means an existing open order needs to move earlier to cover demand; Reschedule Out means it can move later without shortage risk; Cancel flags an order that no longer has covering demand; Expedite highlights a shortage that needs supplier or shop floor follow-up before the requirement date.
Order policies and how they change planned quantities
The order policy on an item's Planning tab decides how MRP sizes each planned order. Lot-for-lot generates a separate planned order matching each period's net requirement exactly, which minimizes inventory but can create many small orders. Fixed Order Quantity always suggests the same quantity (or its multiples) regardless of the exact shortage. Economic Order Quantity balances ordering cost against carrying cost using the item's EOQ formula inputs. Picking the wrong policy for an item - EOQ on an intermittent, low-volume part, for example - is a common reason MRP output looks wrong even though the calculation itself ran correctly.
Common reasons MRP suggests the wrong thing
Most bad-looking MRP output traces back to master data, not a calculation bug: a lead time that is too short or too long, a Buy/Make code set incorrectly, safety stock left at a stale value, or a BOM that has not been updated after an engineering change. Before assuming the planning run itself is wrong, check the specific item's Planning tab and its BOM/routing for stale data.
Common pitfalls
- !Running only Net Change for weeks without an occasional Regenerative pass, letting small data inconsistencies accumulate unnoticed.
- !Leaving an item's order policy as Economic Order Quantity when its demand is lumpy or infrequent, producing oversized planned orders.
- !Not reviewing MRP action messages before releasing planned orders, turning every suggestion into a firm order without judgment.
- !Forgetting to update lead times after a supplier changes, so MRP keeps suggesting order dates that are already too late.
- !Running a full Regenerative calculation during business hours on a large dataset, slowing the system for other users.
How an ERP-grounded AI assistant handles this
Reading a Planning Workbench full of reschedule and expedite messages, and tracing a wrong-looking planned order back to a stale lead time or the wrong order policy, is exactly the kind of pattern-matching an assistant grounded in the live SYSPRO data can do faster than scanning row by row. Netray's ERPray can summarize the exception messages from a specific MRP run in plain language, or point straight at the item master field - lead time, Buy/Make code, order policy - most likely responsible for a planned order that looks wrong, so a planner spends the review time on judgment calls instead of data hunting.
Frequently asked questions
How often should I run a Regenerative MRP calculation in SYSPRO?
Most manufacturing sites run a full Regenerative pass overnight or weekly depending on transaction volume, with faster Net Change runs during the day. There is no fixed rule - the right cadence depends on how quickly demand and supply data actually changes.
Why does MRP keep suggesting an order I already firmed or released?
This usually means the released order was not marked as firm, or the underlying demand or supply data changed again after release. Check the order's status on the Planning Workbench and confirm it was actually converted rather than left as a soft planned suggestion.
What is the difference between a planned order and a firm planned order in SYSPRO?
A planned order is a system suggestion that MRP can freely delete or resize on the next run. A firm planned order is locked by the planner so subsequent MRP runs respect its quantity and date rather than recalculating it, until it is actually released as a purchase requisition or work order.
Can SYSPRO MRP plan across multiple warehouses at once?
Yes, the Requirements Calculation can be scoped to one warehouse or a selected group, and SYSPRO's inter-warehouse transfer logic factors into supply for warehouses configured to source from each other, depending on the transfer and distribution requirements planning setup in use.
Related
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.
Error fixFix 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-toHow 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.
Error fixFix Fishbowl Error: MySQL Server Has Gone Away
This error means the Fishbowl Server lost its connection to the underlying MySQL database, usually because a session sat idle past MySQL's wait_timeout, MySQL itself restarted, or a large import or report exceeded max_allowed_packet. Raise the relevant MySQL timeout and packet settings, confirm the MySQL service is actually running, and restart both MySQL and the Fishbowl Server service.
Error fixQAD Says "Unable to Connect to the Application Server": How to Fix It
This error almost always means the Progress OpenEdge AppServer broker behind QAD is stopped, unreachable over the network, or out of licensed connections, not a database problem. Confirm the broker process is running and healthy in OpenEdge Explorer, check the port and firewall path from the client, then restart the broker with clean agent settings.
How-toHow to Close a Job in JobBOSS2
A job in JobBOSS2 will not close cleanly until every routing operation is marked complete, all material has been issued or returned, and all labor and cost transactions are posted. Review the job's Work In Process detail first, clear any open items, then change the job status to Complete and run final job costing before it is locked.
AI for ERPAI for SYSPRO, Grounded in Your Own Manufacturing Data
Add AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.
AI for ERPAI Demand Forecasting for Manufacturers: Better Numbers and an Explanation Planners Can Trust
AI demand forecasting explains ERP forecast changes in plain language, flags exceptions for planners, and handles short-history SKUs without Excel overrides.
Stuck on SYSPRO ERP?
Talk to engineers who work inside SYSPRO ERP every week, and who build private AI that answers these questions from your own ERP data.