MRP software: How to Read a Material Plan and Resolve Shortages

MRP software calculates what materials a manufacturer needs, how much it needs, and when supply should arrive. It combines demand, product structures, stock records, and expected receipts to recommend purchasing or production activity. The result is a plan for a person to review, not proof that every suggested order is ready to release.

This article explains how to read that plan. You will work through a simple material calculation, see how dates affect supply, and learn how to separate bad inputs from genuine shortages. It also covers capacity limits, exception ownership, and a practical routine for keeping the plan useful.

What an MRP system calculates

MRP stands for material requirements planning. It starts with demand for a product and works through the components needed to make it. Next, it compares those requirements with usable stock and expected supply. Any uncovered quantity can create a proposed order.

SAP’s explanation of material requirements planning describes the role of MRP in recommending material supply. It also explains a key limitation of traditional planning: material calculations do not automatically account for finite production capacity.

Therefore, keep three questions separate. Does the plan cover the required quantity? Can supply arrive by the required date? Can the factory complete the work with its available resources? A positive answer to the first question does not settle the other two.

The system may sit inside an ERP or run as a more focused planning tool. For a broader buying checklist, Anomoz’s article on material requirements planning software covers platform evaluation. Here, the focus is how planners interpret and maintain the calculation itself.

Know the inputs before trusting the output

The main inputs are demand, bills of materials, inventory balances, open supply orders, and planning settings. Each has an owner and a time dimension. For example, a purchase order due next week cannot cover a component needed tomorrow unless the plan also changes the start date.

A bill of materials, often called a BOM, lists the components and quantities needed for a product. Use the approved revision for the relevant order or date. An old structure can produce a mathematically correct plan for the wrong product.

Stock must also reflect its real status. Quarantined or damaged items may not qualify as usable supply. Meanwhile, reserved stock may already belong to another requirement. Define how the system treats each state before staff assume that the on-hand number means available.

Finally, maintain lead times, minimum quantities, order multiples, and safety stock settings. These values strongly affect the proposals. A planner should be able to explain why the recommended quantity exceeds the immediate shortage.

A simple worked example of net material needs

Consider an illustrative order for 100 pump assemblies due in two weeks. Each assembly needs two seals. The gross seal requirement is therefore 200. This example uses made-up operating quantities to explain the calculation, rather than reporting results from a real factory.

Suppose the warehouse has 70 usable seals and expects 50 more before production starts. Ignore other demand and safety stock for this first calculation. The uncovered quantity is 200 minus 70 minus 50, which equals 80 seals.

Now introduce an order multiple of 25. A proposed purchase of 100 seals may cover the shortage while respecting that setting. The extra 20 does not necessarily indicate an error. However, the planner should verify that the order multiple reflects a real supply constraint.

Next, move the expected receipt of 50 seals to a date after production starts. The quantity still exists on an open order, but it no longer covers the original need date. The plan may now recommend expediting, rescheduling, or additional supply depending on its rules.

Understand how demand flows through product levels

A finished product creates dependent demand for its components. If those components contain subassemblies, the system continues down the structure. This process is often called BOM explosion. In plain terms, it turns the top-level order into the parts needed to build it.

For example, a pump assembly may need a motor unit that itself requires a housing and bearings. The motor’s production lead time affects when those lower-level components must arrive. Therefore, a finished-product date can create several earlier material dates.

Check whether a component serves several products. A shortage may reflect combined demand from many orders rather than one large customer requirement. The planner needs a way to trace that demand back to its source. Some systems call this relationship pegging.

Microsoft’s master planning training provides a structured reference for reviewing material and resource needs. Use the concepts to ask how your own system displays the link between a proposed supply order and the demand that caused it.

Distinguish a planned order from a released commitment

A planned order is a recommendation. A purchase order or released production order creates a different level of commitment under your business process. Therefore, decide who reviews and converts proposals, and which checks must happen first.

A buyer may need to confirm supplier availability and price. A production planner may need to confirm capacity, tooling, or approved drawings. Automatic conversion can fit stable cases, but it should not remove review from exceptions that need a human decision.

Next, understand the meaning of firming or fixing an order in your platform. Such controls can protect near-term commitments from constant planning changes. However, they can also preserve an outdated plan if nobody reviews new demand against those commitments.

Ask the team to document what happens after a customer reduces quantity. Does the planner cancel supply, retain it for another requirement, or accept surplus stock? The system should show the options and history rather than silently deleting a commercial commitment.

Read dates as carefully as quantities

MRP software commonly works backward from a required receipt date using lead times and calendars. That process can identify an order start date that has already passed. Such a proposal signals a timing problem, not a time machine.

Separate supplier lead time from internal receiving and inspection time where those steps matter. A component arriving at the dock on Monday may not become available for production until Tuesday. Therefore, define what each date represents in the system.

Calendars can change the result as well. Holidays, non-working days, and supplier schedules affect practical availability. Test a requirement near a shutdown period. Then verify that the proposal uses the intended calendar rather than a default seven-day week.

For capacity decisions beyond the material calculation, Anomoz’s article on production scheduling software explains how resources and sequencing influence a workable schedule. Bring those constraints into the decision before promising a delivery date.

Use safety stock and lot sizes deliberately

Safety stock creates a buffer under your chosen policy. Minimum quantities and order multiples shape how much the system proposes. These settings can protect service, but they can also generate surplus if staff copy them across items without review.

For instance, a slow-moving custom component may not need the same buffer as a shared part used every day. Similarly, a supplier’s pack size may differ from the minimum commercial order. Keep the reason for important settings visible to the people who maintain them.

Next, review settings after demand or supply conditions change. A lead time introduced during a temporary disruption can remain in the system long after the supplier recovers. As a result, the business may keep buying earlier than necessary.

Do not change several settings at once just to remove an uncomfortable exception. First identify the cause, then compare the effect of a controlled change. A quieter exception report is not automatically a better inventory plan.

Separate data faults from real shortages

Before expediting a component, check whether the stock and open orders are current. Unposted receipts, duplicate demand, and unrecorded consumption can all distort the plan. A genuine supply problem needs a different response from a late transaction.

Use a short diagnostic sequence. Confirm the item and unit, review the demand source, inspect usable stock, and check receipt dates. Then review lead times and lot settings. This sequence helps the planner explain the proposal rather than guessing at its cause.

Anomoz’s article on warehouse inventory tracking covers the movement records that keep stock dependable. Planning quality depends on those records reaching the system in time, not simply on a sophisticated planning engine.

Also check substitutions. A physically available alternative does not automatically qualify for every product revision or customer order. Use your approved substitution process and record the decision so planning and production share the same assumption.

Give every exception a decision owner

Typical planning exceptions ask someone to bring supply forward, delay it, increase it, reduce it, or investigate a shortage. Assign responsibility by item group, supplier, or work area. Otherwise, several people may act on one message while another receives no attention.

Prioritize by business impact. A low-cost part can stop a critical order, while a large surplus may create cash and storage pressure. Therefore, combine material exceptions with order importance and the next required action.

Keep a record of the decision and expected follow-up. For example, a buyer may confirm an earlier delivery with the supplier. Update the recognized supply record, then rerun or refresh the relevant plan. A note in a separate spreadsheet will not change the system’s calculation.

Build a stable daily and weekly planning routine

Agree a transaction cutoff or clear refresh pattern so staff know what information each planning run includes. Then review urgent shortages and changed commitments. Use a broader weekly review for settings, recurring supply issues, and excess stock.

Track action quality as well as message counts. Useful measures include unresolved critical exceptions, repeated date changes, and proposals caused by stale inputs. Avoid rewarding staff simply for closing messages if the underlying order still lacks a workable supply path.

Next, review a small sample of completed orders against the original plan. Look at material use, receipt timing, and actual start dates. Those comparisons can reveal a lead time or product structure that needs attention.

Finally, keep sales, purchasing, production, and the warehouse involved. Each function supplies part of the plan’s evidence. MRP becomes more useful when those teams share a routine for resolving conflicts rather than treating the output as the planner’s private spreadsheet.

Test the calculation before a wider rollout

Choose a small product family with clean records. Calculate several simple examples independently, then compare the system’s proposals. Include a shared component, a late receipt, a minimum order, and a revision change.

Expand only after staff can explain the differences. Some differences will reflect valid system settings; others will reveal bad inputs or misunderstandings. Keep those findings as training examples. They teach future planners more than a tour of menu options.

Use the plan as an explanation of supply

The best use of mrp software is a clear, reviewable account of what you need and why. Maintain the inputs, examine dates and constraints, and give exceptions an owner. Start with a small calculation your team can explain before automating larger commitments.