How operative buyer use ERP signals

Material Requirements Planning in Procurement: How Operative Buyers Use MRP Signals

A production line does not stop because the ERP system looks wrong.

It stops because a material is missing.

For the operative buyer, this is where Material Requirements Planning, often called MRP, becomes important. MRP helps the organization calculate what material is needed, how much is needed, and when it should be available.

But MRP does not remove the need for buyer judgment.

An MRP signal can be correct, urgent, and critical.
It can also be based on wrong inventory, outdated lead time, incorrect BOM data, old demand, wrong safety stock, or an unrealistic supplier assumption.

That is why operative buyers must understand how to work with MRP output.

The buyer’s job is not only to place purchase orders from system suggestions. The buyer’s job is to understand which MRP signals should become action, which signals need checking, and which signals should be escalated before they create shortages, excess stock, or production disruption.

In this article, you will learn what MRP means, how it connects to ERP, what data it depends on, and how operative buyers can use MRP signals in daily procurement work.

LHTS classification

Role: Operative
Process: Forecasting, ordering, order management, delivery monitoring, inventory follow-up, excess and obsolete management
Level: Basic
Related course: Operative Procurement Processes 2

Quick answer: What is MRP in procurement?

Material Requirements Planning, or MRP, is a planning method used in ERP systems to calculate material needs based on demand, inventory, lead times, and product structure.

In procurement, MRP helps operative buyers understand what materials should be ordered, in what quantity, and by which date.

The important point is that MRP gives planning signals. The operative buyer must still check whether the signal is reliable, relevant, and ready to become a purchase order or supplier action.

The problem MRP solves

Procurement and production share a simple but difficult challenge:

Materials must be available when needed — but not too early, not too late, and not in the wrong quantity.

If material arrives too late, production may stop.
If material arrives too early, inventory increases.
If too much is ordered, capital is tied up.
If too little is ordered, shortages appear.
If the wrong revision is ordered, the material may not be usable.
If the supplier lead time is wrong, the purchase order may be placed too late.

MRP helps solve this planning problem.

It calculates material requirements based on demand and available supply. It tells the organization what is needed and when action may be required.

But the system only calculates based on the data it receives.

If the data is weak, the MRP result can also be weak.

That is why operative buyers should treat MRP as decision support, not as an automatic truth.

What is ERP?

ERP stands for Enterprise Resource Planning.

An ERP system is the company system that connects important business information across functions such as procurement, finance, inventory, production, sales, and logistics.

For procurement, the ERP system may include:

  • supplier master data
  • purchase requisitions
  • purchase orders
  • contracts or price conditions
  • inventory records
  • goods receipts
  • invoices
  • delivery dates
  • material master data
  • MRP results
  • supplier performance information

The ERP system helps different functions work from the same data. This matters because procurement decisions are rarely isolated.

A purchase order affects inventory.
Inventory affects production.
Production affects customer delivery.
Goods receipt affects invoice matching.
Supplier delay affects planning.

MRP is usually one important planning function within the wider ERP environment.

What is Material Requirements Planning?

Material Requirements Planning is a method for calculating material needs.

In simple language, MRP asks:

  • What do we need?
  • How much do we need?
  • When do we need it?
  • What do we already have?
  • What is already on order?
  • What must we buy or produce?
  • When must action be taken?

For purchased materials, MRP often creates purchase requisitions, planned orders, exception messages, or recommendations that the operative buyer must review.

The buyer then decides whether to convert the signal into a purchase order, change an existing order, expedite a supplier, delay a delivery, check stock, or investigate the data.

The key point: MRP is only as good as the data behind it

MRP depends on data.

If the data is correct, MRP can be a powerful planning tool.
If the data is wrong, MRP can create wrong buying signals.

Important MRP data includes:

  • demand
  • forecasts
  • customer orders
  • production plan
  • Bill of Material
  • inventory balance
  • open purchase orders
  • open production orders
  • supplier lead time
  • safety stock
  • lot size
  • minimum order quantity
  • reorder point
  • scrap factor or yield
  • calendar and working days
  • material status
  • revision or version
  • planning parameters

For the operative buyer, this means that an MRP result should not always be accepted without thought.

A buyer should ask:

Is the signal correct, or is the system reacting to bad data?

This is one of the most important buyer skills in MRP-driven procurement.

How this connects to the operative buyer role

MRP is highly relevant to the operative buyer because it influences daily purchasing activity.

The operative buyer may use MRP output to:

  • create purchase orders
  • release purchase requisitions
  • reschedule open purchase orders
  • follow up suppliers
  • identify shortage risk
  • check delivery priorities
  • reduce excess inventory
  • manage order changes
  • support production planning
  • communicate material availability risks
  • monitor supplier delivery performance

The operative buyer does not usually own all MRP master data. That responsibility may sit with planning, master data, engineering, logistics, or supply chain.

But the operative buyer sees the consequences when the data creates wrong procurement signals.

That is why the operative buyer must understand the logic well enough to challenge, verify, and escalate.

Where MRP fits in the procurement process

MRP is connected to several operative procurement processes.

Forecasting

Forecasts and demand plans influence future material requirements. If the forecast is wrong, MRP may create too many or too few buying signals.

Ordering

MRP can create purchase requisitions or planned orders that the buyer converts into purchase orders.

Order acknowledgement

After the buyer sends a purchase order, the supplier must confirm whether the order can be delivered as requested.

Order management

MRP may suggest changing quantities or delivery dates on existing purchase orders.

Delivery monitoring

MRP helps identify which materials are needed soon and therefore require delivery follow-up.

Inventory management

MRP compares demand with available stock and open supply. This helps buyers understand shortage and excess risks.

Excess and obsolete management

If demand disappears or changes, MRP may show that material is no longer needed. The buyer may need to cancel, postpone, or reduce orders.

MRP is therefore not a separate technical topic. It is part of the daily flow of operative procurement.

What MRP output can tell the buyer

MRP output may appear in different ways depending on the ERP system.

It can include:

  • purchase requisitions
  • planned orders
  • order proposals
  • exception messages
  • shortage lists
  • reschedule-in messages
  • reschedule-out messages
  • cancel messages
  • action dates
  • requirement dates
  • available-to-promise information
  • projected stock levels
  • planned delivery dates

The words may differ between systems, but the buyer question is the same:

What action is the system asking me to consider?

The buyer must then decide whether to act, check, escalate, or ignore the signal.

Practical MRP flow for operative buyers

A simple working method can look like this.

Step 1: Review the MRP signal

Start by understanding what the system is asking for.

Is it asking the buyer to:

  • create a new purchase order?
  • increase an existing order?
  • reduce an order?
  • bring a delivery forward?
  • push a delivery out?
  • cancel an order?
  • follow up a shortage?
  • check a planning exception?

Do not treat all MRP messages the same. Some are urgent. Some are informational. Some are caused by data issues.

Step 2: Check the demand behind the signal

Before ordering, check why the material is needed.

The demand may come from:

  • customer order
  • production order
  • forecast
  • safety stock
  • project demand
  • spare part demand
  • engineering change
  • internal consumption
  • service requirement

A requirement connected to a confirmed customer order may need different attention than a requirement connected only to a long-term forecast.

Step 3: Check current inventory

MRP should already consider inventory, but the buyer should still understand the stock situation when the signal is important.

Check:

  • available stock
  • reserved stock
  • blocked stock
  • quality inspection stock
  • stock in transit
  • safety stock
  • stock at another site
  • stock allocated to other demand

A system may show stock, but not all stock is usable.

Step 4: Check open purchase orders

Before creating a new purchase order, check what is already on order.

Ask:

  • Are there open purchase orders?
  • Are any orders overdue?
  • Are delivery dates confirmed?
  • Has the supplier acknowledged the order?
  • Can an existing order be rescheduled?
  • Can a partial delivery solve the requirement?
  • Is there duplicate supply?

This helps prevent both shortages and unnecessary purchasing.

Step 5: Check lead time and supplier capability

MRP depends heavily on lead time.

If the system assumes a supplier lead time of four weeks but the real supplier lead time is eight weeks, the MRP signal may come too late.

The buyer should check:

  • current supplier lead time
  • contracted lead time
  • actual delivery performance
  • capacity constraints
  • minimum order quantity
  • transport time
  • supplier holidays
  • production batch cycles
  • customs or import lead time

Lead time is not only a number in the system. It is a real supplier capability.

Step 6: Check lot size and order quantity

The suggested order quantity may be influenced by lot size rules, minimum order quantities, order multiples, economic order quantity, packaging quantity, or supplier conditions.

The buyer should understand why the system suggests the quantity.

Ask:

  • Is this quantity based on real demand?
  • Is it caused by minimum order quantity?
  • Is it caused by packaging multiple?
  • Will it create excess stock?
  • Is the demand likely to change?
  • Can the order be split?
  • Is there a better delivery schedule?

A correct quantity is not always the same as the system-proposed quantity.

Step 7: Decide the procurement action

Based on the review, the buyer decides what to do.

Possible actions include:

  • convert purchase requisition to purchase order
  • place a new order
  • change an existing order
  • expedite a supplier
  • request order acknowledgement
  • request partial delivery
  • reschedule delivery
  • cancel or reduce order
  • escalate shortage risk
  • ask planning to verify demand
  • ask master data to check parameters
  • ask engineering to confirm BOM or revision
  • involve tactical procurement for supplier issue

The buyer should document the action when the impact is important.

Example: MRP suggests a new purchase order

An operative buyer opens the ERP system and sees that MRP has created a purchase requisition for a component.

The system suggests ordering 1,000 pieces with delivery in three weeks.

Before converting the requisition into a purchase order, the buyer checks the demand.

The requirement is connected to a production order scheduled in four weeks and a forecast for the following month.

The buyer checks inventory and sees that there are 300 pieces available, but 200 are already reserved for another production order.

The buyer checks open purchase orders and finds that one order for 500 pieces is already confirmed for delivery next week.

The buyer then checks supplier lead time and sees that the system lead time is three weeks, but the supplier has recently moved to five weeks due to capacity issues.

Now the buyer understands the situation better.

The purchase order may still be needed, but the delivery date is probably unrealistic. The buyer contacts the supplier, checks whether partial delivery is possible, updates planning with the risk, and flags the lead time difference for master data review.

This is good operative MRP work.

The buyer did not blindly accept the signal. The buyer used the signal as the starting point for a procurement decision.

Common MRP problems buyers should recognize

Problem 1: Wrong inventory data

If inventory is wrong, MRP may create unnecessary orders or miss real shortages.

Common causes include:

  • late goods receipt posting
  • unrecorded scrap
  • stock in wrong location
  • blocked stock counted as available
  • stock reserved for another need
  • incorrect unit of measure
  • physical stock not matching system stock

When the MRP signal looks strange, inventory accuracy is one of the first things to check.

Problem 2: Incorrect lead time

Lead time is one of the most important planning parameters.

If the lead time is too short, the buyer may order too late.
If the lead time is too long, the buyer may order too early and create excess stock.

The operative buyer should compare system lead time with actual supplier performance.

Problem 3: Outdated forecast

MRP may generate supply based on forecasted demand that no longer exists.

This can create excess inventory.

If the buyer sees large order proposals without clear demand, planning should be involved.

Problem 4: BOM errors

If the Bill of Material is wrong, MRP may calculate the wrong component requirements.

This can result in missing material, wrong quantities, or purchased parts that are no longer needed.

The buyer should not fix BOM data alone, but should flag suspicious BOM-related signals to engineering, planning, or master data.

Problem 5: Lot size rules create too much stock

Minimum order quantities and order multiples may cause MRP to suggest more material than immediately needed.

Sometimes this is necessary. Sometimes it creates avoidable inventory.

The buyer should understand whether the quantity is commercially required, technically required, or simply caused by old planning parameters.

Problem 6: Open purchase orders are not updated

If an open purchase order has an outdated delivery date, MRP may give misleading signals.

A supplier may be late, but the system may still show the old confirmed date.

This hides the shortage risk.

Order acknowledgement and delivery monitoring are therefore important parts of MRP discipline.

Problem 7: MRP creates action, but no one owns the exception

MRP can show shortage or rescheduling messages, but the organization must decide who acts.

If ownership is unclear, system signals become ignored warnings.

The operative procurement process should define who reviews which MRP messages and how often.

MRP and purchase order automation

MRP can support automated purchase order creation.

In some companies, the ERP system can convert planning signals into purchase orders automatically or semi-automatically.

This can reduce manual work, especially for stable, repetitive, low-risk materials.

But automation requires strong control.

Before automating purchase order placement, the company should have:

  • reliable master data
  • correct supplier data
  • agreed prices
  • valid contracts or terms
  • confirmed lead times
  • supplier capacity understanding
  • clear minimum order quantities
  • stable demand pattern
  • order acknowledgement process
  • exception handling process
  • approval rules
  • system integration or EDI where relevant

Automation is not a solution for bad data.

If the data is weak, automation can create wrong orders faster.

A good rule is:

Automate stable flows. Control exceptions manually.

What should not be automated too early?

Operative buyers should be careful with automation when:

  • demand is unstable
  • supplier performance is weak
  • lead times change often
  • prices are not fixed
  • technical revisions change frequently
  • minimum order quantities are unclear
  • quality issues are common
  • materials are high value or high risk
  • stock accuracy is poor
  • engineering changes are frequent
  • supplier acknowledgement is unreliable

In these cases, the buyer may still use MRP, but should review signals manually before placing orders.

How MRP supports better supplier communication

MRP gives the buyer a stronger basis for supplier communication.

Instead of saying:

“We need material soon.”

The buyer can say:

“Our production requirement is on week 34. Current stock covers only one week of demand. The open order is confirmed for week 36, which creates a shortage risk. Can you confirm whether partial delivery in week 33 is possible?”

This type of communication is clearer and more fact-based.

It helps the supplier understand the need, the timing, and the consequence.

MRP also helps buyers provide suppliers with better forecasts, call-off plans, and delivery priorities.

But the buyer should remember that supplier communication must be based on reliable data. Sending unstable or incorrect signals to suppliers can damage trust.

MRP checklist for operative buyers

Use this checklist before acting on an important MRP signal.

Requirement

  • What material is required?
  • What quantity is required?
  • When is it required?
  • What demand created the requirement?
  • Is the demand firm or forecasted?

Inventory

  • What stock is available?
  • Is any stock blocked, reserved, or under quality inspection?
  • Is stock available at another site?
  • Is the system stock reliable?

Supply

  • Are there open purchase orders?
  • Are any purchase orders overdue?
  • Are delivery dates confirmed?
  • Has the supplier acknowledged the order?
  • Can an existing order be rescheduled?

Supplier

  • What is the real supplier lead time?
  • Is the supplier performing according to plan?
  • Are there known capacity issues?
  • Are minimum order quantities or order multiples relevant?
  • Is partial delivery possible?

Master data

  • Is the material master correct?
  • Is the planning parameter correct?
  • Is the lead time correct?
  • Is the lot size rule correct?
  • Is the BOM or revision relevant?
  • Are there pending engineering changes?

Action

  • Should a purchase order be created?
  • Should an existing order be changed?
  • Should the supplier be expedited?
  • Should planning be informed?
  • Should master data be corrected?
  • Should the issue be escalated?

Common mistakes when buyers use MRP

Mistake 1: Trusting every MRP signal without checking

MRP is powerful, but it is not always right.

The buyer should check important signals before acting, especially when the result looks unusual or the material is critical.

Mistake 2: Ignoring small changes until they become shortages

A reschedule message or small delay can become a production issue if ignored.

The buyer should review exceptions regularly.

Mistake 3: Not checking order acknowledgement

MRP may assume an open purchase order will arrive on time, but the supplier may not have confirmed it.

Order acknowledgement protects the buyer from false supply assumptions.

Mistake 4: Focusing only on shortages

MRP is not only useful for shortage prevention. It can also help prevent excess material.

Buyers should also review cancel, postpone, and reduce messages.

Mistake 5: Treating forecast demand as firm demand

Forecasts are uncertain.

The buyer should understand the difference between forecast-driven requirements and confirmed order-driven requirements.

Mistake 6: Forgetting supplier reality

MRP may propose an action date that is mathematically correct but commercially unrealistic.

If the supplier cannot meet the date, the buyer must escalate, negotiate, or find another solution.

Mistake 7: Not feeding back data problems

If buyers repeatedly see wrong signals but do not report them, the system will keep producing the same problems.

MRP discipline requires feedback to planning, master data, engineering, and supplier management.

What good MRP work looks like for an operative buyer

Good MRP work is not simply processing system messages.

Good MRP work means the buyer can:

  • understand why the signal exists
  • check whether the signal is reliable
  • connect the signal to inventory and open orders
  • understand supplier lead time and capability
  • prioritize critical materials
  • act before shortage becomes disruption
  • reduce unnecessary ordering
  • communicate clearly with suppliers
  • escalate data or supplier problems
  • support production with accurate information

The operative buyer does not need to be an ERP expert. But the buyer must understand enough MRP logic to avoid blind buying.

The related Learn How to Source course Operative Procurement Processes 2 gives a practical foundation for how different types of purchases influence the operative buyer’s way of working.

This is a natural next step after reading about MRP because MRP connects directly to forecasting, order acknowledgement, purchase order placement, delivery deviations, invoice discrepancies, and excess or obsolete material.

If you want to understand how MRP signals fit into the wider operative procurement process, this course gives useful structure.

FAQ: Material Requirements Planning in procurement

What is MRP in procurement?

MRP stands for Material Requirements Planning. In procurement, it helps calculate what materials should be purchased, how much is needed, and when the material should be available.

Is MRP the same as ERP?

No. ERP is the wider business system. MRP is a planning function or method often used inside the ERP system to calculate material needs.

How do operative buyers use MRP?

Operative buyers use MRP to review purchase requisitions, create purchase orders, reschedule deliveries, identify shortages, monitor supply, and support production material availability.

Can buyers trust MRP completely?

No. MRP depends on data quality. If inventory, lead time, BOM, forecast, or purchase order data is wrong, the MRP result may also be wrong.

What data does MRP need?

MRP typically needs demand, inventory, open orders, lead times, Bill of Material data, lot size rules, safety stock, and planning parameters.

What is an MRP exception message?

An MRP exception message is a system signal that something may require action, such as a shortage, late delivery, reschedule need, cancellation proposal, or planning conflict.

Can MRP create purchase orders automatically?

Yes, in some ERP setups MRP can support automatic or semi-automatic purchase order creation. But this requires reliable data, agreed supplier terms, correct lead times, and clear exception handling.

What is the biggest risk with MRP?

One of the biggest risks is acting on wrong or outdated data. This can create shortages, excess stock, unnecessary purchase orders, or unrealistic supplier expectations.

What should a buyer check before converting an MRP signal into a purchase order?

The buyer should check demand, inventory, open purchase orders, supplier lead time, order quantity, lot size rules, supplier capability, and any unusual master data or BOM issues.

Conclusion: MRP gives signals, but buyers create control

Material Requirements Planning is one of the most important tools in operative procurement.

It helps buyers understand what is needed, when it is needed, and which actions may be required to protect production and inventory flow.

But MRP is not a replacement for buyer competence.

The operative buyer must understand the signal, check the data, evaluate supplier reality, and decide the right action.

Used correctly, MRP helps prevent shortages, reduce unnecessary inventory, improve supplier communication, and create better control in daily procurement work.

The key lesson is simple:

Do not just process MRP messages. Understand them.

Tags: