Independent IFS Cloud practice · Implementation
Key takeaways
Most articles about ERP business impact are written from the brochure. This one is written from the projects. I have spent seventeen years inside IFS, from Apps 7.5 through Cloud, and the pattern that repeats is not that companies pick the wrong system. They pick a capable one and then implement it in a way that throws the capability away: a template nobody reuses, an automation layer nobody trusts, reports rebuilt one for one from the old system because nobody had the authority to delete any of them.
So this is not a list of what IFS Cloud can do. It is a walk through the places where a decision taken during implementation determines whether the platform pays for itself or just replaces one kind of manual work with another. Where a topic deserves its own treatment, I have linked to the longer piece on the ifs-erp.com blog rather than compressing it into two sentences here.
Grouping sites so they share parts, defaults and process setup is sold as a speed feature. It is really a consistency feature, and the speed is a side effect. When site four inherits the purchasing parameters that sites one to three already run on, you are not just saving a week of configuration. You are removing the possibility that site four quietly does receiving differently, which is what costs you two years later when someone tries to compare performance across the group and finds the numbers are not measuring the same event.
The catch is that a cluster only helps if the template being cloned is one somebody defended. Rolling out a bad standard quickly is worse than rolling it out slowly, because a slow rollout at least gives each site a chance to object. I ask for the template to be signed off by the person who will own the process across all sites, not by the site that happened to go first. That is also where the multi-site purchasing decisions belong: whether demand consolidates centrally, and how stock moves between sites once it has.
Further reading: centralised purchasing in IFS Cloud, distribution orders between sites, and from planning to go-live.
IFS Cloud gives you three tools that cover most of what people used to write code for, and knowing which one to reach for is the whole skill. A Quick Report reads data out: a saved query for a list or an extract, with no logic. A Custom Field stores something the standard data model does not. A Custom Event reacts when a row changes, and can hand off to a Workflow that routes an approval, sends a notification, or calls out to another system.
The failure mode is predictable. Teams discover Custom Events, like them, and attach one to everything. Six months later there is an event layer nobody can explain, firing on saves that were never meant to be significant, and the business has learned to ignore the notifications it produces. The second failure mode is subtler: reaching for a Custom Event when the requirement is actually a scheduled check. An event fires when a row changes. It cannot fire because a row has not changed, which is exactly what an unconfirmed order or an untouched receipt is.
Where the requirement crosses a system boundary, the answer is usually an interface rather than an in-system automation. IFS Cloud's OData projections are the normal integration surface, and keeping the orchestration outside IFS keeps that logic out of your ERP, where it would otherwise become one more thing to retest at every release.
Further reading: Custom Events explained, Quick Reports vs Custom Fields vs Custom Events, IFS Cloud API integration, orchestrating IFS Cloud with n8n. Work that has already been built once sits in the configurations and interfaces sections of the marketplace.
IFS Cloud ships R1 and R2 every year. That cadence is the biggest single change in how you should think about customisation, and it is where legacy habits do the most damage. On Apps 9 or 10 an upgrade was an event you prepared for over months, so carrying technical debt between them felt survivable. On Cloud it arrives twice a year, and anything built outside the Extensibility Framework has to be checked, and often reworked, on that same rhythm.
The boundary is simple to state and easy to cross by accident. Extending the data model with Custom Fields, adding logic through Custom Events and Workflows, adapting screens through configuration: all inside the contract, all carried forward. Touching a core object, or building a report or an interface directly against an internal view rather than a published projection, puts you outside it. Nothing stops you at the time. The bill arrives at the next release, and at every release after that.
I have watched this go wrong in both directions. Companies that refuse all extension end up with a shadow layer of spreadsheets doing the work the system was not allowed to do, which is worse, because at least a customisation is visible. The honest position is that some extension is necessary, and the only real question is whether it is built where the platform will maintain it for you.
Further reading: update-safe extensions, the true cost of customisation, clean core in an SCM context, the upgrade tax, the upgrade readiness checklist, and what a release actually brings, with 25R2 purchasing as the worked example. Scoped modification work is listed under marketplace modifications.
Ask a buyer what goes wrong and you get something dramatic: a late shipment, a line stopped for a missing part. Look in the data and the costly problems are the undramatic ones, because nothing in the system objects to them.
| What is sitting there | Why nobody sees it | What it turns into |
|---|---|---|
| A released PO the supplier never acknowledged | The order is valid and open. No field says "ignored" | A delivery date everyone planned around that was never agreed |
| Goods received, invoice never matched | Both records are individually correct | An accrual that grows quietly until period end |
| A supplier price that moved between orders | The new price applies cleanly, exactly as configured | Margin erosion found during an annual review |
| A buyer who stopped ordering from a usual source | Every individual order is legitimate | Concentration risk, or a supplier problem nobody escalated |
All of this is detectable, and all of it is readable through standard OData projections on a read-only account. That means a monitor can look for it daily without touching a record, installing an object, or adding anything the next release has to be checked against. It is the design principle behind the SCM Automation Pack, and the reason the five-day exception scan exists as a way to see what is already in your own data before committing to anything ongoing.
On the physical side the same principle applies to warehouse work. Picking strategy and packing proposals are configuration decisions that quietly set your throughput ceiling, and they are rarely revisited after go-live.
Further reading: unconfirmed purchase orders, what unmatched receipts do at period end, supplier price changes, advanced picking strategies, the packing proposal.
Anomaly detection, demand forecasting and predictive maintenance are genuinely useful, and they all rest on the same unglamorous foundation: whether your master data is good enough for a model to learn from. A forecast built on lead times copied out of the legacy system in 2019 and never reviewed will be precise, confident and wrong, and it will be harder to challenge than a human guess because it arrives with a number attached.
The second thing the demo leaves out is what happens to the output. Detection is the easy half. The half that decides whether any of it pays off is routing: who receives the signal, how it reaches them, and what happens when they do nothing. An alert stream with no named owner and no escalation is a mailing list, and people unsubscribe from mailing lists in their heads long before they do it in the client.
That is why I design exception rules around the recipient rather than the condition. One deduplicated digest per owner per day beats forty individual notifications that are each technically correct. And a rule that cannot state in one sentence what the recipient is supposed to do about it does not ship.
Further reading: alert fatigue and exception design, the cost of missed exceptions, detecting supplier behaviour change, the data attention gap, assumed vs confirmed records, read-only OData monitoring.
Crystal Reports layouts from Apps 9 and 10 do not carry across to IFS Cloud. That is the fact that matters for your plan, whatever any vendor's support calendar says, and it is usually discovered later than it should be, because reporting gets treated as a workstream that can start once the real configuration is done.
IFS Cloud splits the job across different tools. Quick Reports handle lists and extracts: saved queries, no layout ambition, self-service for anyone who can be trusted with a data set. Laid-out business documents are produced through IFS Cloud's own report layout tooling. Analysis and dashboards belong in the reporting and analytics layer rather than in a printed report at all. Trying to recreate a 200-item Crystal inventory inside any one of these is how reporting becomes the critical path.
The work that actually saves you time is triage, and it is a business job rather than a technical one. Pull the usage data first. Most report inventories contain a long tail nobody has run in two years, a middle band that exists because one person likes the format, and a small core the business genuinely runs on. Rebuild the core properly, convert the middle band to Quick Reports or a dashboard, retire the tail. The conversation about retiring the tail is the hard part, which is why it needs to start early and needs someone senior to close it.
Further reading: when a Quick Report is the right answer, and the reports section of the marketplace.
Permission sets in IFS Cloud are capable enough to express proper segregation of duties. Whether they end up doing so is decided in the first six weeks of the project, when someone is under time pressure and the fastest way to unblock testing is to grant a broad set to a group and move on. That grant is almost never revisited, because nothing breaks. It surfaces at the first external audit, when a tester asks who can both create a supplier and approve a payment to it, and the honest answer takes a fortnight to assemble.
Design the role model against the process rather than the org chart, and build it while the process design is still fresh in everyone's head. It costs days then and weeks later. The same applies to standards work: if you operate under ISO requirements, the evidence those audits want is largely a by-product of decisions you are already taking, provided you record them as you go instead of reconstructing them afterwards.
Further reading: RBAC and segregation of duties, permission sets in IFS Cloud, ISO standards in IFS Cloud, and the security section of the marketplace. My own view on the wider ownership question sits on the data governance page.
Every implementation plan has a migration workstream, and most are optimistic by the same margin. The reason is consistent: the effort is not in loading the data, it is in deciding what the data should say. Loading is mechanical. Agreeing that these 4,000 part records are the ones worth keeping, that this status code maps to that one, and that a customer with no valid tax ID is a customer you are not going to migrate, is a series of business decisions with no obvious owner.
Two habits change the outcome. Rehearse the load more than once, on a schedule, with a defined cut of source data each time, so the failure list shrinks between rehearsals instead of being discovered on cutover weekend. And treat validation as its own deliverable with its own sign-off rather than as the last step of loading, because IFS Cloud enforces its business rules at load time: well-formed source data can still be rejected for violating application logic nobody had read.
Further reading: the data migration checklist, how FNDMIG and the Data Migration Manager fit together, and the data migration section of the marketplace.
In most of the companies I work with, a large amount of operational knowledge lives in one person's head and one person's spreadsheet. The buyer who knows which supplier actually delivers on time regardless of what the lead time field says. The planner whose workbook reconciles two things the system does not reconcile. None of this shows up in an ERP assessment, and all of it walks out of the building when that person leaves.
An implementation is the one moment when you have a mandate to surface it. Every shadow spreadsheet is a documented requirement waiting to be read: it exists because the system does not do something, and finding out what that something is tells you more about your real process than a workshop will. Some of them should become configuration. Some should become a Quick Report. A few are genuinely someone's judgement and should stay human, but at least then you know where they are.
The same logic applies to the implementation record itself. Decisions taken in month two get questioned in month eleven by people who were not in the room, and a project that cannot answer "why is it set up this way" reopens settled arguments for the rest of its life.
Further reading: shadow spreadsheet risk, knowledge loss when people leave, buyer knowledge concentration, and the implementation documentation kit if you would rather not build the templates from scratch.
I am wary of quoting percentage improvements. Published ranges come from situations you cannot inspect, with baselines nobody defined, and a number borrowed from another company's business case is not evidence about yours. What I can offer is the short list of measures that survive contact with an actual steering committee.
Further reading: ERP ROI analysis, why go-live is a load test, the implementation crisis.
If you are live on IFS Cloud and this article has described your situation rather than your plan, the order that works is roughly this. Find out what is actually in your data before redesigning anything, because the exception population usually contradicts the received wisdom about where the problems are. Then fix the governance decisions that get harder with time: the role model, the report inventory, the ownership of master data. Automation comes after that, not before, because automating a process nobody owns only makes it produce wrong answers faster.
What I do is on the offer page, the platform view is on the IFS Cloud page, and the process side sits under business process optimisation. The applications themselves, including the read-only exception monitoring described in section 4, live on ifs-erp.com.
No, but the work changes shape. Before go-live it is a design decision that costs nothing extra. After go-live it is an inventory exercise: list everything built outside the Extensibility Framework, establish what each item actually does, and decide case by case whether to rebuild it inside the contract, replace it with standard functionality, or accept the maintenance cost knowingly. The last option is legitimate. What is not legitimate is not knowing which category each item falls into, which is the usual starting position.
No. In most projects I see, the unclaimed value sits in exceptions a plain query would find: orders nobody confirmed, receipts nobody invoiced, prices that moved. That is rule-based detection rather than machine learning, and it works on data that is merely adequate. Model-driven forecasting is worth doing once master data has an owner and a maintenance routine, and worth postponing until it does.
Yes, and that is the approach I prefer for anything that only needs to read. Standard OData projections plus an integration account with read permission are enough to detect the exception patterns in section 4. Nothing is installed in IFS, nothing is written back, and there is no object for the next R1 or R2 release to break. If you want to see the output before committing to anything ongoing, the five-day exception scan produces the same report in observation mode only.
Budget the triage, not the rebuild. Pulling usage statistics and getting a decision on what to retire takes longer than rebuilding the reports that survive, because it needs business sign-off rather than developer time. Start it in parallel with configuration rather than after it, and give the retire list an owner with the authority to say no. Teams that skip this step rebuild everything one for one and carry the whole inventory forward, including the part nobody has opened since 2019.
The configuration saving is small at that scale. The consistency saving is not, and it compounds: two sites configured independently will diverge on receiving, costing and reporting definitions within a couple of years, and reconciling them later is considerably more work than agreeing a shared template now. If there is any prospect of a fourth site, an acquisition, or a group-level report, treat it as worth it.
Dariusz Myśliwiec: 25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally through an independent practice.
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.
If you are scoping an IFS Cloud implementation, or you are already live and suspect the value case has quietly gone missing, a short call is the fastest way to work out which two or three of the eleven sections above are actually costing you something.
Independent IFS Cloud practice · Purchasing output design
To make IFS Cloud email purchase orders reach suppliers, the PDF_REPORT_CREATED event has to be enabled and an action of type E-Mail has to exist for it. The IFS documentation on e-mail reports states that this event is used to control the mail format and the report to be attached. When the action has the wrong condition, an empty address or no event enabled, the purchase order looks sent in the system and the supplier never receives it.
Key takeaways
When a purchase order report is created as a PDF, the PDF_REPORT_CREATED event is raised, and an action of type E-Mail attached to that event sends the mail. Three things therefore have to be in place: the event, the action and a configured mail path. The page states that IFS/Connect has to be installed and the MAIL_SENDER connector has to be configured properly.
Without a condition the mail is attempted each time any PDF file is created, which is why the action needs one (section 3). The approval step that precedes the mail is a separate topic, covered in the purchase order approval workflow, and events that you define yourself are covered in custom events in IFS Cloud.
The page names the event and action prerequisites: an action with type E-Mail must have been created for the PDF_REPORT_CREATED event, and the event must be enabled. Master data has its own prerequisites. On the Supplier/Purchase/Print/Email page, the option E-mail Purchase Order should be enabled, and the supplier contact used must have an e-mail communication method. The page also describes a lookup for the contact; one step reads: if that is empty, use the primary contact for the supplier address.
On the order side, the page on printing a purchase order states that the purchase order must have been released and cannot be Cancelled, and that the Print Purchase Order option must be enabled. When the order is printed, the Communicated option on the purchase order header is enabled. The option alone does not show that the mail arrived, so check that separately.
The REPORT_TITLE condition restricts the action to the intended report. The page says to make sure that the REPORT_TITLE condition is equal to the report title, and it adds a note: without this condition, IFS/Connect will try to send this e-mail each time any PDF file is created.
The consequence for design is that an action without the condition belongs to every report that produces a PDF. A purchase order mail template can then be attempted for a document that is not a purchase order. Write the report title into the design record next to the action, and test with a second report that also creates a PDF.
For purchasing, the information is passed in the event parameters PDF_PARAMETER_1 through PDF_PARAMETER_10, and the page’s table has an eleventh column. The table shows the columns that matter for a purchase order.
| Parameter | Meaning for a purchase order on the page |
|---|---|
| PDF_PARAMETER_1 | E-mail address for the supplier contact |
| PDF_PARAMETER_4 | Name or person ID of the supplier contact |
| Eleventh column | != TRUE when the user does not wish to send an e-mail when printing the report online |
In an action, a parameter is written with a leading ampersand, for example &PDF_PARAMETER_1. The page also names REPLY_TO_USER, written &REPLY_TO_USER, which retrieves the e-mail address specified for the coordinator in User Details. That makes it possible for the supplier to reply to the purchase order coordinator.
When PDF_PARAMETER_1 has no value and the event action is triggered, the result is an application message with status Failed. The page suggests guarding against this with the condition (PDF_PARAMETER_1 = %), so that the action runs only when an address is present.
A Failed message is a record that someone has to read. Decide who monitors application messages with status Failed. A supplier whose contact has no e-mail address should be found by a data check before go-live, and not by a missing delivery. The data side is covered by the contact prerequisites in section 2.
The page gives an example action for a purchase order. To is set to &PDF_PARAMETER_1 and From User to &REPLY_TO_USER, the subject is Notification of Purchase, and the message starts Dear &PDF_PARAMETER_4.
To attach the report, use the option Attach when defining the action and enter &PDF_FILE as the file name. The page also describes two refinements. A language-specific message uses the LANGUAGE_CODE condition: if the supplier’s language code is German (de), the condition LANGUAGE_CODE = de can be given. And an action can use a specific mail sender connector, for example where some mails are sent as text/plain and some as text/html.
The page on printing a report states that you can redirect the generated report or report data to different output channels or destinations. You can use the Send to Connect, Send Email or Print To Logical Printer action type to send a generated PDF report as an e-mail. For a one-off mail, the same page describes the Send Email slider, in which you enter the e-mail address you want.
Output routing offers more than one route, so decide which route each purchasing document uses, and record it where the support team looks: see the handover to support. For the files that users attach to records, as opposed to the PDF that this mechanism attaches to a mail, see IFS Cloud document attachments. Workflow design around purchasing steps is covered in IFS Cloud workflows.
Test the set-up with purchase orders that cover the cases the page describes, and write down the expected result before each test. The method for planning such tests is in testing in IFS Cloud.
| Case | Expected result | Owner |
|---|---|---|
| Supplier contact with an e-mail address | The mail is sent to the address in PDF_PARAMETER_1 with the report attached | Buyer |
| Supplier contact without an e-mail address | Without a guard condition the action ends with an application message with status Failed; with the condition the action does not run | Administrator |
| Another report that creates a PDF | Without the REPORT_TITLE condition the mail is attempted; with it, the action applies only to the purchase order | Administrator |
| Supplier with another language | A language-specific action applies when its LANGUAGE_CODE condition matches | Buyer |
The e-mail output is ready for go-live when each of the checks below has a record behind it.
IFS Cloud sends a purchase order by e-mail through the PDF_REPORT_CREATED event, which is used to control the mail format and the report to be attached. An action with type E-Mail must have been created for the event, the event must be enabled, IFS/Connect has to be installed and the MAIL_SENDER connector configured.
The e-mail action fires for other reports when it has no REPORT_TITLE condition. The IFS Cloud documentation states that without this condition, IFS/Connect will try to send the e-mail each time any PDF file is created. Set the condition equal to the report title of the purchase order.
For a purchase order in IFS Cloud, PDF_PARAMETER_1 holds the e-mail address for the supplier contact and PDF_PARAMETER_4 holds the name or person ID of the supplier contact. In an action the parameter is written with a leading ampersand, as &PDF_PARAMETER_1.
An e-mail action for a purchase order ends with an application message with status Failed when PDF_PARAMETER_1 has no value, that is, when the supplier contact has no e-mail address. The IFS Cloud documentation suggests adding the condition (PDF_PARAMETER_1 = %) so that the action runs only when an address is present.
Yes. The IFS Cloud documentation on e-mail reports describes the same PDF_REPORT_CREATED mechanism for more than purchase orders; its REPLY_TO_USER parameter, for example, lets a supplier or a customer reply to the purchase or customer order coordinator. The parameters differ per report, so take them from the page's table for that report and give each action its own REPORT_TITLE condition.
Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
A review of the output and e-mail set-up for purchasing documents, with test orders, shows which condition, address or event is missing. A buyer and an administrator take part.
Book an e-mail output review Read about centralized purchasing
Independent IFS Cloud practice · Purchasing design
IFS Cloud multi-supplier ordering divides the quantity of one purchase requisition between suppliers by percentage. One supplier cannot or should not carry the whole requirement, so the business agrees shares. If the shares, the periods and the rounding are not understood, the quantities on the requisition lines do not match the agreement, and for a part that an internal site also supplies, the same quantity can be ordered twice. This article follows the IFS documentation on multi-supplier ordering in the 25R2 tree.
Key takeaways
Multi-supplier ordering creates a new purchase requisition line for each supplier in the supplier split basic data. The documentation limits it to requisitions from these sources:
The page adds two limits. It is only possible to use the function with inventory registered and non-inventory registered purchase parts. And supplier splits are not allowed if you have an acquisition from another order. The planning side of these sources is covered in dynamic structures in MRP and, for the order point, in reorder point planning in IFS Cloud.
The split definition holds periods, and each period holds the suppliers with their percentages. The page states that periods cannot overlap, that for each period there can be multiple suppliers, and that the total of the split percentage must be 100 percent.
The system retrieves the supplier split data for the particular part, site and period, and the desired receipt date should be between the phase-in and phase-out date. Check that the periods cover the receipt dates the business plans.
The page gives the formula Split Qty = Std Multiple Qty * Round (Requisition Qty * Split Percentage / Std Multiple Qty). The standard multiple quantity is based on the purchase unit of measure, and its default value is 1. All calculations are performed in the inventory unit of measure, and after the order quantity is calculated it is converted to the purchase unit of measure for each supplier.
The page works one example. A requisition of 1200 is split 70 and 30 percent with a standard multiple of 200. The first supplier receives 200 * Round (1200 * 0.7 / 200) = 800, and the second receives the rest, 1200 - 800 = 400. The supplier with the highest percentage has first priority for the system’s execution, and in the page’s second example the last supplier receives the remainder, 6000 - 3200 - 2000 = 800.
The design consequence is that the quantity on a line is the formula’s result and not the percentage multiplied by the requirement. A percentage on paper is the input to the formula. Compare the two on a test requisition before the shares go into a contract.
For a manual line, the buyer must decide whether supplier split is used when creating the requisition line, and the page states that it is not possible to do this in a second place. A question dialog opens and asks whether the requested quantity should be split, and it appears only if multiple suppliers are entered for the purchase part.
A buyer who answers the dialog without knowing what it does has taken the split decision for that line. Train buyers on the dialog and agree who may answer it. The purchasing set-up around these lines is covered in mastering centralized purchasing in IFS Cloud and new purchasing functionality in IFS Cloud 25R2.
The page warns that it is important not to double source to a multi-site planned internal supplier, due to a supplier split definition, and it repeats the warning for supplier schedules created by MRP.
The page’s example makes the mechanism visible. MRP needs 100 units. It creates a distribution order for 50 units for the internal supplier and a requisition for the remaining 50 units. That requisition is split between the external suppliers, and the page calculates 25/50 * 50 units = 25 units for one of them. The warning exists so that a supplier split definition does not order the internal share a second time. Distribution orders themselves are covered in distribution orders in IFS Cloud.
Purchasing owns four decisions: the shares, the periods, the standard multiples and the person who maintains them. The shares are a commercial agreement, so they come from the contract or the sourcing strategy, and the system only executes them. Which source delivers an order line in the first place is a separate question, treated in IFS Cloud sourcing rules.
Name one maintainer for the split definition. A share changed in the contract and not in the definition produces requisitions that follow the old agreement.
Test a split with one requisition per source type and compare the lines the system creates with the lines the business expects. The table gives four cases that follow from the documentation.
| Case | Input | Expected result | Owner |
|---|---|---|---|
| The page’s worked example | Requisition of 1200, split 70 and 30, standard multiple 200 | Two lines, 800 and 400 | Buyer |
| Manual line | New line for a part with multiple suppliers entered | A question dialog asks whether to split; the answer is fixed at creation | Buyer |
| Requisition from another order | Acquisition from another order | No supplier split | Purchasing lead |
| Internal supplier | MRP requirement of 100, internal supplier at 50 percent by distribution order | A requisition for the remaining 50, split between the external suppliers | Planner |
A supplier split is ready for go-live when each of the checks below has a record behind it.
Multi-supplier ordering in IFS Cloud divides the quantity of a purchase requisition between suppliers by percentage. A new purchase requisition line is created for each supplier in the supplier split basic data. The percentages are held per period, and the total of the split percentage in a period must be 100 percent.
The IFS Cloud documentation allows multi-supplier ordering for requisitions from MRP, Master Scheduling, Order Point, Next Level Demand and for manually entered purchase requisitions. It works only with inventory registered and non-inventory registered purchase parts, and supplier splits are not allowed for an acquisition from another order.
IFS Cloud calculates each supplier’s quantity as Std Multiple Qty * Round (Requisition Qty * Split Percentage / Std Multiple Qty). For a requisition of 1200 split 70 and 30 with a standard multiple of 200, the first supplier receives 800 and the second 400. The standard multiple quantity defaults to 1 and is based on the purchase unit of measure.
No. The IFS Cloud documentation states that the decision whether to use supplier split must be made when the requisition line is created, and that it is not possible to do this in a second place. A question dialog asks whether the requested quantity should be split, and it appears only if multiple suppliers are entered for the purchase part.
Check that the external split applies only to the requirement that is left after the internal share. The IFS Cloud documentation warns against double sourcing to a multi-site planned internal supplier due to a supplier split definition. In its example, MRP creates a distribution order for 50 of 100 units and a requisition for the other 50, and only those 50 are split between the external suppliers.
Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
A review of the supplier split set-up against the agreed shares, with test requisitions, shows where the quantities differ and why. Purchasing and a planner take part.
Independent IFS Cloud practice · Warehouse floor design
IFS Cloud Warehouse Data Collection is the documentation area for executing warehouse transactions through a scanning page, so that the transaction is entered where the work happens. Without it, the transaction is entered where the system is: the floor works from paper or memory and someone keys the result later. The stake is stock accuracy and the delay between the physical move and the system record. Scanning removes that delay only for the processes that someone configured and tested.
This article stays on the configuration and activity pages cited in it. It says nothing about device types, offline behaviour or the mobile client.
Key takeaways
Warehouse Data Collection is the part of IFS Cloud in which warehouse transactions are captured by scanning or typing at the place where the work is done. The documentation on Warehouse Data Collection configuration describes how the processes are set up.
The scope is the list of processes the documentation names for scan-based execution. That makes the first design task a list: which processes your floor performs, and which of them the documentation supports through scanning.
The processes to move first are the ones where the physical action and the system entry are farthest apart and where a wrong entry is costliest. The method has two passes: list the transactions by where they happen physically, then rank them by what an error costs.
Among the processes the documentation describes for the scanning page are these three. Counting can run as a guided process: in the configuration example the documentation gives, the first sequence number is picked automatically once the count report number is entered, and the operator then scans or types the location number and part number. Picking a part by choice can be run from the scanning page, and shop order receipts can be captured there by scanning or typing according to the configured process. Each of these is a candidate row for the ranking, and the page references are collected in the scenario table below.
The mechanics of resolving count variances, which a scanned count produces as well as a typed one, are covered in cycle count variance reconciliation.
A guided process tells the operator which value to scan next, and a barcode label supplies that value without typing. The documentation on Warehouse Data Collection configuration lists GS1-128, GS1 DataMatrix, GS1 DataBar and GS1 QR as supported and states that stacked and composite barcodes are not supported. Choose the label format from that list, and print a test label in the chosen format before the labels are ordered in bulk.
Labels can be produced at receipt, and the label content has to be decided before go-live. The page on printing barcode labels from a purchase order receipt describes the function. Label content has to match what the downstream process expects, and that includes lot or serial numbers for tracked parts, as discussed in lot and serial tracking decisions in IFS Cloud.
Receipt itself, including the statuses a received part passes through, is covered in goods receipt, inspection and put-away in IFS Cloud.
When warehouse tasks are used, picking is driven by tasks and not by pick lists: if the warehousing functionality is used, the pick list is replaced by a warehouse task and the pick reporting is performed within the warehouse functionality. The documentation on picking describes the relation and names the sources it covers: pick lists connected to customer orders, shipment orders, project deliverables and purchase receipt returns.
Warehouse tasks can be planned and prioritised, and someone has to own that planning. The page on planning warehouse tasks describes the planning step. The design question for scanning is therefore a question about ownership: someone has to decide what a task contains and in which order workers receive tasks. The neighbouring shipping steps have their own articles: the packing proposal and the shipment order.
A scanned transaction names a location, so the location model has to match what the operator sees on the shelf. A location label that the floor cannot find, or two locations that look identical, make a scan as unreliable as a handwritten note. The design of the levels and their names is covered in warehouse structure design in IFS Cloud, and this article does not repeat it.
Test scanning with one scenario per process, run by the people who will perform it, on the device and label they will use. Record the expected system record before the scenario, then compare it with the record that the scan created. The general method for planning and tracking such tests is in testing in IFS Cloud.
| Process | What is scanned or typed | Expected record | Owner |
|---|---|---|---|
| Guided count | Location and part, in the sequence defined with the warehouse team | Counted quantity recorded for that location and part | Warehouse lead |
| Pick part by choice | Part and location chosen at the page | Pick recorded against the stock the operator chose; see the page on picking a part by choice | Picker |
| Shop order receipt | Shop order and quantity, per the configured process; see the page on receiving a shop order | Finished part received into the intended location | Production lead |
| Receipt labels | Label printed at receipt and scanned later | The label content that the next process reads | Receiving clerk |
| Warehouse task | The task assigned to a worker | Task closed with the physical move confirmed | Warehouse planner |
A scanning rollout is ready when each of the checks below has a record behind it.
Warehouse Data Collection in IFS Cloud is the documentation area for capturing warehouse transactions by scanning or typing at the place of work. Each process, such as counting or shop order receipt, is configured and tested on its own. The IFS documentation on Warehouse Data Collection configuration describes how the processes are set up.
The IFS Cloud documentation on Warehouse Data Collection configuration lists GS1-128, GS1 DataMatrix, GS1 DataBar and GS1 QR as supported; stacked and composite barcodes are not supported.
When warehouse tasks are used in IFS Cloud, picking is driven by tasks and not by pick lists. The IFS documentation on picking states that the pick list is replaced by a warehouse task when the warehousing functionality is used, for pick lists connected to customer orders, shipment orders, project deliverables and purchase receipt returns. Define who plans and prioritises the tasks.
Test every scanned process in IFS Cloud with one scenario each, performed by the people who will do the work, on the device and label they will use. Write down the expected system record first, run the scan, and compare. Every difference is a defect in the configuration, the label or the expectation.
Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
A floor-process walk-through decides which transactions to scan first, with the warehouse lead and the people who do the work.
Book a floor-process walk-through Read about warehouse structure design
Independent IFS Cloud practice · Order supply design
IFS Cloud sourcing rules describe where supply for an order line may come from and how the system chooses between the alternatives. An order line needs supply, and the source is picked by a rule that someone set up and nobody revisits. When the rule is missing or mis-set, the order is supplied from the wrong place, at the wrong cost or lead time, and the buyer learns about it afterwards. Delivery performance and purchase cost then depend on a configuration object that sits outside everyone’s daily screens.
Key takeaways
A sourcing rule decides which supply alternative serves a customer order line. The IFS documentation on sourcing sits in the Sales area, because the question it answers belongs to the order: where will the goods for this line come from?
The alternatives are an external supplier, an internal supplier (another site of the company), in-house manufacturing and company inventory. The page on defining a sourcing rule describes how the rule is built.
The rule is configuration, so it does not appear on a screen the buyer or planner opens each day. That is the reason it needs an owner and a test: a decision nobody sees is a decision nobody checks.
When more than one alternative in the source set qualifies, the sourcing objectives narrow the choice as a sequence of criteria, and if more than one alternative still remains, the first alternative is picked. Where no sourcing objectives are set up, the priority is used instead, and among equal priorities the first alternative is picked.
The documentation names five objectives that a rule can put in sequence:
The reason to write the order down is that every tie gets resolved one way or the other. If nobody decided how, the business has not chosen the result. Naming the objectives and their sequence turns that outcome into a documented rule that a planner can read and challenge.
Supplier agreements and multi-supplier ordering are separate mechanisms on the purchasing side. On a supplier agreement, a lower value in the priority field means a higher priority, as described in the documentation on supplier agreements. With multi-supplier ordering, a requisition line created from MRP, MS, NLD or Order Point is split by the suppliers’ split percentages, and a new purchase requisition line is created for each supplier, as the documentation on multi-supplier ordering describes.
These mechanisms belong to the purchasing set-up, which is covered in mastering centralized purchasing in IFS Cloud and in new purchasing functionality in IFS Cloud 25R2. Keep the two layers apart in the design: the sourcing rule answers where supply comes from, and the purchasing settings answer how an external supplier is chosen and how a requirement is split.
For an external supplier, releasing the customer order creates a purchase requisition automatically, both when the goods are delivered via the order-taking site (Purchase Order Transit) and when they go directly to the customer (Purchase Order Direct). The page on releasing a customer order describes the step. A line sourced externally therefore leads to work for a buyer, so settle who sees it: a buyer who is not told that orders now generate purchasing work finds out from a late delivery.
Where the source is in-house manufacturing, the supply is a planning and production matter, which links the rule to the planning set-up discussed in dynamic structures in MRP. The order types and flows that surround this step are covered in customer order types and order flow in IFS Cloud.
Three sourcing decisions carry a business trade-off, and a consultant can configure them only after the business has made them.
| Decision | The trade-off | Who decides |
|---|---|---|
| Priority of alternatives | Which source is preferred when more than one can deliver | Supply chain lead |
| Cost against lead time | Whether a cheaper source with a longer lead time wins over a faster one | Supply chain lead with sales and finance |
| Internal against external supply | Whether a part is made or bought, or moved between own sites | Operations lead with purchasing |
Record each decision with its owner and date. Two neighbouring topics have their own articles: configure-to-order purchasing, and distribution orders for supply that moves between own sites. The related supply chain functions are surveyed in IFS Cloud SCM features.
Test a sourcing rule with one order per alternative and one order where two alternatives tie, then compare the source the system picked with the source the business expected.
| Scenario | Expected source | Owner | Evidence |
|---|---|---|---|
| Order line for a bought part | External supplier | Buyer | Purchasing record created at release |
| Order line for a part held at another site | Internal supplier | Supply chain lead | Supply record against the other site |
| Order line for a made part | In-house manufacturing | Planner | Production or planning record |
| Order line for a part on hand | Company inventory | Warehouse lead | Reservation on stock |
| Order line where two sources tie | The source ranked first by the written objectives | Supply chain lead | Chosen source matches the written order |
A sourcing design is ready for go-live when each of the eight checks below has a document behind it.
A sourcing rule in IFS Cloud consists of a source set and sourcing objectives. Automatic sourcing uses it to select the best supply alternative for a customer order line from external suppliers, internal suppliers, in-house manufacturing or company inventory. The IFS documentation on sourcing describes the rule in the Sales area.
When two alternatives can both deliver, the sourcing objectives of the rule decide in IFS Cloud, applied in sequence, for example Highest priority, Shortest distance or Least expected additional cost. If both alternatives still remain after the objectives, the first alternative is picked. Without objectives, the priority decides.
The IFS Cloud documentation places sourcing in the Sales area, where it governs the supply of customer order lines. Whether a requisition raised by planning follows the same rule is not stated in the page this article cites. Test it in your configuration with one planned requisition and one customer order line before you rely on it.
Supplier agreements in IFS Cloud belong to the purchasing side, and a lower value in their priority field means a higher priority. Sourcing decides where supply comes from, and supplier agreements belong to the separate question of which agreement serves a purchase.
Place one test order per supply alternative in IFS Cloud, plus one where two alternatives tie, and compare the source the system chose with the source written down in advance. Record the expected source, the owner and the evidence for each scenario. Every difference is a defect in the rule or in the expectation.
Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
If nobody can say, a review of your sourcing rules against the real supply alternatives of the business shows which decisions were never made. It needs the supply chain lead and a buyer in the room.
Book a sourcing rule review Read about IFS Cloud SCM features