Deutsch (Deutschland) 
Polski (PL) 
Independent IFS Cloud practice · Purchasing
The part that has demand and nowhere to buy it
The planning run wants the part. The reorder point says buy it. A requisition is raised, or a planned order is sitting there ready. And then nothing happens, because the part has no active supplier to source it from. The demand is real and the data is correct. What is missing is the one link that turns a need into an order. So the part waits, unsourced and unseen, until a stockout on the floor makes it everyone’s problem at once.
Key takeaways
- A part can carry real demand while having no active primary supplier, or only a supplier that is blocked or inactive. The need exists, but there is no sourcing path to act on it.
- This is not a requisition that was never converted. There a route to a purchase order exists and a step was skipped. Here the route itself is missing, so there is nothing to convert.
- It is the supply-side twin of a sales order without coverage. One end promises goods to a customer with nothing behind it. This end needs to buy goods with no one to buy from.
- A supplier can also go quiet without being removed, the way a supplier price edit slips through. A part sourced only from a supplier now blocked is, in practice, a part with no active supplier.
- The part, its demand and its supplier links all live in IFS Cloud, so a read-only monitor can list parts that have demand and no active source, and hand them to a buyer before the shelf runs dry.
1.How a part ends up with demand and no source
Sourcing and demand are maintained separately. Demand comes from planning, from a reorder point, or from a requisition someone raised. The source comes from the part-to-supplier relationship: a primary supplier, an agreement, a valid purchase part record. When both are in place a buyer has a route from the requisition to a purchase order. When the source is missing, the demand has nowhere to go.
The source goes missing in ordinary ways. A new part is created and stocked before anyone sets up its supplier. The one supplier that carried it is blocked for a quality or compliance reason, and no alternative is added. An agreement lapses and the link that depended on it goes quiet. In each case the part record still looks complete at a glance, because the gap is in a related record, not on the part itself.
So an unsourced part is not a data error you can see. It is a true picture of demand with no buying route attached, sitting among thousands of parts that are sourced correctly, with nothing on the screen telling them apart.
2.Parts where demand meets a missing source
A part with no supplier is fine if nothing needs it. The value is in finding the parts where demand and a missing source meet, because those are the ones that will fail quietly.
| What you see | What it points to |
|---|---|
| Active demand, no primary supplier on the part | Nothing will source it automatically: the requisition or planned order stalls with no route to a purchase order. |
| Demand present, only supplier is blocked or inactive | A source exists on paper but cannot be used, so the part behaves as if it had none at all. |
| Planned order exists but no purchase order follows | An early warning that the sourcing link broke somewhere between the plan and the buy. |
| Reorder-point part below its point, no open supply | The floor is heading for a stockout while the system has no one to order from. |
A blocked sole supplier hides best. The part was sourced for years, so the team assumes it still is, but the only supplier behind it has been blocked and no one noticed. Read the demand against the supplier status and that gap shows up before it becomes a shortage.
3.Finding parts that need buying with no one to buy from
The demand signals, the part record and the supplier links are all available through standard OData projections, so they can be read without touching anything. Detection joins the two sides and looks for two things:
- Demand with no active source - where a part has a requisition, a planned order or a reorder point below its level, and no active primary supplier, so parts that cannot be bought surface before the shortage does.
- Source present but unusable - where the only supplier link is blocked, inactive, or tied to a lapsed agreement, so a part that looks sourced but effectively is not is separated from one that can actually be ordered.
Because it is a read-only monitoring pattern, it runs beside purchasing and writes nothing back to IFS. It adds no object inside the client system, so an R1 or R2 release leaves nothing of ours in your IFS to retest. Before each release I check that the standard projections it reads still match, as part of the subscription. It hands the buyer a short list of parts that have demand and no working source, and the decision to add a supplier, unblock one, or renew an agreement stays with the person who owns the category.
4.Rolling it out without noise
- Start where demand is real - scope first to parts with live requisitions or below reorder point, so the list is about shortages, not dormant records.
- Dry-run first - log which parts would have been flagged over a full planning cycle before a single item reaches a buyer.
- Separate the missing source from the unusable one - keep demand with no active supplier apart from demand whose only supplier is blocked or inactive.
- Read only, no footprint - standard OData reads, nothing written back, no new object inside IFS Cloud.
Related reading
5.Frequently asked questions
Why can a part with demand and no supplier go unnoticed?
Demand and sourcing are held in separate records. Planning raises the need, and the part-to-supplier relationship provides the route to buy. When a part has demand but no active source, a requisition or planned order can sit without becoming a purchase order, because nothing in either record points at the other. Reading demand against supplier status is what surfaces those parts.
How is this different from a requisition that was never converted?
A requisition that was never converted has a route to a purchase order, and a step in that route was skipped. This case is earlier: the route itself is missing because the part has no active supplier, so there is nothing to convert. One is a stalled process; the other is a broken sourcing link.
What if the part has a supplier, but that supplier is blocked?
A part whose only supplier is blocked or inactive behaves, for buying purposes, like a part with no supplier at all. The link looks present on the record but cannot produce a valid order. The monitor treats demand against an unusable source the same way it treats demand against no source, because both leave the buyer with nothing to act on.
Does this monitoring write anything to IFS Cloud?
No. The demand signals, part record and supplier links are read through standard OData projections and joined outside IFS. Nothing is written back, so there is no upgrade footprint and no new object inside the client system. Adding or unblocking a supplier stays a human decision.
6.About the author
Dariusz Myśliwiec brings 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Find the unsourced parts before the shelf does
Tell me how sourcing gaps show up in your planning today. On a 30-minute fit call we check whether a rule comparing demand signals with supplier status fits your data. The SCM Automation Pack runs three rules today (unconfirmed purchase orders, late deliveries, stock below minimum), so this would be an additional rule built to order, read-only, with a dry-run period before anything reaches a buyer.
