What "Digital Manufacturing Roadmap" Actually Means When You're Rolling Out EWM in Automotive

I keep seeing articles about "digital manufacturing roadmaps" and "end-to-end supply chain transformation" — and honestly, most of them read like they were written by people who've never had to explain to a forklift driver why their RF device suddenly can't find the bin location.

I'm currently in the middle of an EWM rollout at a German automotive manufacturer, and the gap between "roadmap" and "what actually needs to happen on Monday morning" is wide enough to park a forklift in.

So when I read SAP Insider's piece on digital manufacturing roadmaps, I found myself mentally translating every strategic point into the actual warehouse and production decisions we're facing right now.

What "Integration" Means When Production Meets Warehouse

The article talks a lot about connecting S/4HANA Manufacturing with the broader supply chain. In theory: yes, absolutely. In practice: you're trying to figure out whether to trigger warehouse tasks from production orders or manufacturing execution system (MES) confirmations, and the answer isn't in any best practice guide.

We just spent two weeks working through staging scenarios where production needs materials that EWM thinks are in quality inspection. The "integration" isn't just technical — it's about aligning how production planners think about availability with how warehouse operations actually move and stage materials.

The configuration exists (/SCWM/MOB_MAT_STAGING and related settings), but nobody tells you that automotive Kanban replenishment and standard EWM goods staging don't always play nicely together without custom logic.

The Part Nobody Mentions: Master Data Hygiene

Digital manufacturing roadmaps love to talk about real-time visibility and IoT sensor data. What they don't mention is that none of it works if your MARC table shows lead times from 2018 and your bin assignments in /SCWM/LAGP are a creative interpretation of reality.

Before we could even think about "digital" anything, we spent six weeks cleaning up:

• Material master warehouse views that contradicted S/4 plant data
• Storage types that existed in configuration but not on the actual warehouse floor
• Handling unit management settings that were copied from a template and never adjusted for actual packaging dimensions

This isn't glamorous. But it's the actual work that makes everything else possible.

BTP and Shop Floor Reality

Here's where my side interest in BTP starts connecting with my day job: the automotive clients I work with are starting to ask about custom UIs for shop floor scenarios that standard SAP Fiori apps don't quite cover.

We're exploring a BTP-based app for production supervisors to manually trigger warehouse staging when they know a line is going to need materials earlier than the production order suggests. It's not rocket science — calling EWM APIs from a CAP service — but it's the kind of thing that actually helps on the ground.

The challenge is that most "innovation" conversations happen with IT strategy teams who've never stood in a warehouse at 6 AM during shift handover. The real wins are small and specific: a mobile app that lets warehouse leads see exactly which production orders are waiting on which materials, updated every 30 seconds instead of every batch job.

What Scalability Actually Means in Automotive

The article emphasizes scalable architecture. Fair point. But in automotive manufacturing, "scalability" often means: can we roll this exact configuration out to the next plant without spending another eight months?

That means:

• Clean separation between global template settings and plant-specific configuration
• Clear documentation of every custom development and why it exists (because the person who built it won't be around for plant #3)
• Making sure your EWM process types and warehouse orders are generic enough to handle slightly different production processes across plants

We're currently documenting every configuration decision in Markdown files in a Git repo (yes, configuration documentation in version control — controversial take, but it's working). When we go to the next plant, we'll have a clear baseline and clear reasons for any deviations.

The Honest Takeaway

Building a digital manufacturing roadmap isn't wrong. But if you're actually implementing EWM or working on shop floor integrations, the roadmap needs to survive contact with:

• Operators who've done things a certain way for 15 years
• Production planners who don't trust "the system" until it's proven itself for six months
• Physical constraints (conveyors, space, equipment) that no amount of configuration can change

The real work is in the translation layer between strategy and Monday morning reality. That's where EWM configuration, master data cleanup, and increasingly, small targeted BTP applications, all come together.

If you're working on similar rollouts — especially in automotive or discrete manufacturing — I'd be curious what your "translation layer" looks like. You can find more of what I'm working through at markus-mildner.com.