# MRP Master Data Readiness Checklist > Source: https://netray.co/tools/mrp-master-data-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Check item, BOM, lead time, supplier and inventory data against what MRP needs before a go-live or a clean-up. ## Category erp-operations ## Audience - Production planner - ERP project manager - Materials manager ## Tool **Kind:** checklist **Groups:** #### Item master planning data **Items:** **Text:** Every planned item has a procurement type: make or buy **Critical:** true **Text:** Every planned item has a lot sizing rule assigned deliberately **Critical:** true **Text:** Lead times exist for purchased items and are based on actual receipts **Critical:** true Manufacturing lead times reflect routing and queue time Safety stock is set only where there is a reason and an owner Order minimum and multiple match supplier terms Planning time fences are set on items with firm near-term builds Phantom items are flagged where subassemblies are not stocked **Text:** Obsolete and inactive items are excluded from planning **Critical:** true Unit of measure and conversion factors are consistent across item, BOM and supplier #### Bill of material **Items:** **Text:** Every planned parent has an active BOM **Critical:** true **Text:** No circular BOM structures exist **Critical:** true **Text:** Quantity per and unit of measure are correct on every line **Critical:** true Scrap or yield allowances are intentional and documented Effective dates are populated and not overlapping Alternate and substitute components are handled by rule Consumables and bulk items are flagged so MRP does not over plan them BOM changes go through a controlled change process #### Routing and capacity **Items:** **Text:** Routings exist for make items with run and setup times **Critical:** true Work centre calendars include shifts and holidays Operation overlap and move times are defined where used Outside processing steps carry a supplier lead time Standard times were reviewed in the last year #### Inventory and supply records **Items:** **Text:** Cycle count accuracy is high enough that planners trust on-hand **Critical:** true **Text:** Open purchase orders have correct due dates and quantities **Critical:** true Open production orders are closed when finished Past-due receipts and orders are cleaned up weekly Stock in quarantine or on hold is excluded from available **Text:** Customer orders and forecasts are loaded with realistic dates **Critical:** true Forecast consumption rules are defined #### Process and governance **Items:** **Text:** Every item has a named planner or buyer code **Critical:** true Planning run schedule and parameters are documented Action messages are reviewed daily by an owner Master data changes are logged and reviewed A planner checklist exists for month-end and quarter-end Exceptions such as late supplier deliveries are tracked to cause **Scoring Note:** Count ticked items. Below 70% of the list, MRP output is unlikely to be trusted. Every critical item should be ticked before relying on MRP for purchasing decisions. ## Content **Intro:** MRP gives accurate results only when item, BOM, routing and inventory records are accurate. This checklist covers the data areas that most often explain why a planning run looks wrong. **Sections:** #### How to use the checklist **Body:** Work through the groups with someone who knows the item and BOM data, not just the system administrator. Tick each item you can show evidence for, such as a report, not just an intention. Items marked critical cause wrong orders or missing orders when they fail. Export the result as a list of open items to turn into a clean-up plan with owners and dates. #### Why data comes before settings **Body:** Most MRP complaints, such as too many action messages, wrong dates or phantom shortages, trace to data rather than the planning engine. A wrong quantity per on a BOM line multiplies through every planned order. A purchased lead time that is a guess shifts every release date. Inventory counted at 80% accuracy makes the netting step unreliable. Fixing data costs less than adding parameters to work around it. #### Typical gaps found **Body:** Reviews of planning data tend to find the same patterns. **Bullets:** - Lead times entered at go-live and never updated. - Obsolete items still on active BOMs generating demand. - Units of measure that differ between purchasing and stock. - Past-due purchase orders left open for months. - Safety stock set high on many items as a blanket fix. **Cta:** If you want these checks run automatically against your live ERP data and reported weekly, we can build that read-only. **Faq:** #### How accurate must inventory be for MRP? **Answer:** Many planning texts suggest record accuracy in the mid to high nineties percent for the items that matter, measured by cycle counts. Lower accuracy means planners add buffers and ignore system advice, which defeats the point of MRP. #### Should lead times be updated automatically? **Answer:** Some ERPs can propose lead times from receipt history. That helps, but a planner should review proposals, because one late shipment can distort the average. Treat automatic values as suggestions on important items. #### How often should this checklist be run? **Answer:** Run it fully before go-live, after a major data migration, and then yearly. The inventory and supply group should be checked weekly in some form, since open orders and stock change constantly. #### What is the most common critical gap? **Answer:** Incorrect BOM quantities and obsolete items still on active structures are the most common, followed by poor on-hand accuracy. These create wrong demand on many components at once. ## Search terms mrp data requirements, mrp master data checklist, mrp setup checklist, mrp go live data readiness, bom accuracy checklist, inventory record accuracy mrp, mrp implementation checklist, item master planning parameters checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json