100+ functions built in-house at ifm. Most were already standard.

More than 100. That’s how many manufacturing functions ifm had built in-house over the years. ifm is a German manufacturer of sensors and automation technology. When the company looked at SAP Digital Manufacturing, it found that most of them were already available as standard (SAP News, 6 November 2026).

ifm has around 9,000 employees and production sites in Germany and abroad. Over time, each site had built its own links between shop-floor systems and business applications. Every local fix solved a real problem. Together, they made the landscape hard to maintain and hard to scale.

What ifm found

According to Martin Haury, head of Global IT Business Services at ifm, the company was “looking for a standard to bring to all production sites and to make use of the solutions already available on the market.” Production order execution, scheduling and track and trace, all functions it had developed itself, turned out to be part of the standard product.

That changed the work. Instead of building and maintaining custom code, teams configured what was already there. “Our OT colleagues were actually surprised that it’s just parameterizing and the solution is there,” Haury said. Less development also meant less maintenance and a faster path from idea to deployment.

There was a second benefit. Production processes, manufacturing orders and product availability are now visible in one shared environment, so teams across sites work from the same information. After a pilot, ifm is now preparing to roll the solution out across its global production network.

Why custom code piles up

ifm’s story is common. In warehouses, plants and transport, we often find the same pattern:

  • A site needs something the system didn’t do years ago, so it gets built.
  • The system later adds the function as standard, but the custom version stays, because it works and nobody has time to check.
  • Each upgrade has to test and fix the custom code again.
  • Knowledge sits with one or two people, and the next site builds its own version.

The cost doesn’t show up in one place. It shows up as slower upgrades, longer test cycles, more support tickets and sites that can’t share processes.

A simple review before your next project

Whether you are moving to S/4HANA, rolling out a new site or just planning the next release, it’s worth checking your own custom code first:

  1. List what you have built. Enhancements, interfaces and reports in production, warehouse and transport processes. Note who uses each one and how often.
  2. Compare with the current standard. Many functions that needed custom code five or ten years ago are now in SAP EWM, in production planning and detailed scheduling (PP/DS) or in manufacturing execution. Check against the release you are on, or the one you are moving to.
  3. Sort into three groups. Replace with standard, keep because it gives a real business advantage, or switch off because nobody uses it.
  4. Start with one site or one process. Like ifm, prove it in a pilot before rolling it out to the network.

The aim isn’t zero custom code. It’s keeping only the code that makes you different, and letting the standard do the rest.

How we can help

Bolders implements SAP supply chain execution, including Extended Warehouse Management (EWM), Transportation Management (TM) and embedded production planning and detailed scheduling (ePPDS), from first design through to ongoing support. Less custom code also makes systems easier to support. That’s why we look at it in our application management services too. See our supply chain execution services →

Related reading: automatic truck check-in with SAP EWM and SAP S/4HANA: beyond migration.

categories Blog