What NÖM's Automated Warehouse Rollout Tells Us About EWM in Real Production Environments

Automated warehouse logistics sounds clean on a slide deck. Getting SAP EWM to actually talk to conveyors, AS/RS systems, and material flow controllers in a live dairy production environment is a different conversation.

NÖM — one of Austria's largest dairy producers — recently went live with SAP EWM as part of a push to automate their warehouse logistics. The announcement from Technische Logistik is brief, but it's enough to think through what this kind of project actually requires — because the technical challenges in automated EWM rollouts don't change much whether you're handling milk crates in Lower Austria or automotive parts in Bavaria.

What "Automated Warehouse Logistics" Actually Means in EWM Terms

When a project is described as automated warehouse logistics with SAP EWM, you're usually looking at some combination of:

Automated Storage and Retrieval Systems (AS/RS) — high-bay racking with cranes or shuttles
Material Flow System (MFS) integration — EWM's built-in layer for talking to PLCs and conveyors
Automatic Transfer Orders — no human picking, warehouse tasks triggered and confirmed by system events

The keyword in EWM for this is MFS — Material Flow System. It sits between EWM and the physical automation hardware. If you've only worked on manual or RF-based EWM warehouses, MFS is a step up in complexity. It requires specific Customizing in the SCM Basis layer and tight coordination with the automation vendor's team.

For a food/beverage operation like NÖM, you'd also factor in catch-weight management and potentially batch management with FEFO (First Expired, First Out) logic — both of which interact directly with how Transfer Orders are generated and prioritized.

The EWM-to-Automation Interface: Where Projects Get Complicated

The integration between EWM and warehouse automation hardware is where most of the real project risk lives. It's not an SAP-only problem — it's a three-way conversation between the SAP team, the WCS/WMS automation vendor, and the customer's internal IT.

In practice, this usually means:

Defining Workcenters and Activity Areas in EWM to mirror the physical layout of the automated zones
Configuring Queues so that Transfer Orders are routed correctly to automated versus manual stations
Setting up MFS Monitor (transaction /SCWM/MFSMON) to track material movements from the conveyor layer — and debugging when telegrams don't arrive or arrive out of sequence

That last point is worth saying plainly: telegram sequencing issues are common, and they're painful to diagnose. When a pallet is reported at the wrong station or a confirmation never arrives, the MFS Monitor is your first stop, but reading the logs takes practice.

DACH Rollouts: What's Regionally Specific

The DACH region (Germany, Austria, Switzerland) has some consistent patterns that affect how EWM projects play out:

GS1-128 label compliance is usually non-negotiable for goods movements — this affects HU (Handling Unit) labeling configuration early in the project
Works council involvement in process design is real and can slow down decisions around labor tracking, task interleaving, and exception handling
Existing automation investments — many DACH manufacturers already have automation hardware from vendors like SSI Schäfer, Dematic, or Swisslog, which means EWM is being integrated into an existing system rather than greenfielded alongside new equipment

For NÖM specifically, dairy logistics adds cold chain requirements. That typically means shorter time windows for certain warehouse tasks and stricter FEFO enforcement — both configurable in EWM, but they have to be modeled correctly in the warehouse order creation rules and stock removal strategies from day one.

What a Go-Live Like This Actually Takes

Projects of this type — automated EWM, food production, real-time hardware integration — tend to run 18 to 30 months from blueprint to go-live when done properly. The SAP configuration itself is maybe 30–40% of the work. The rest is:

Mapping physical process flows before touching Customizing
Extended testing with the automation hardware in a staging environment (not just unit tests in a sandbox)
Cutover planning that accounts for active inventory in automated zones — you can't just stop a running warehouse
Hypercare support post-go-live, because the first few weeks of live operation in an automated warehouse surface edge cases that no test script catches

It's genuinely complex work, and NÖM going live is a real achievement — not a given.

Key Takeaways

MFS configuration is its own discipline — if you're moving into automated EWM projects, invest time in understanding telegram handling and the MFS Monitor before you're on-site.
Food/beverage EWM rollouts have non-negotiable constraints around batch, FEFO, and labeling — model these early or redesign late.
The automation vendor relationship matters as much as the SAP config — misalignment there is where go-live dates slip.

If you've worked on an automated EWM rollout — especially in food, dairy, or cold chain — I'd be curious what surprised you most. Drop a comment or reach out via markus-mildner.com.