The dilemma of an SAP EWM implementation: do companies need specialists or all-rounders?
Anyone faced with the task of transforming their intralogistics onto SAP S/4HANA is quickly confronted with a noticeable discrepancy. On one side is a technological architecture that, with SAP Fiori, Embedded Analytics and complex cloud interfaces, has become deeper and more demanding than ever before. On the other side is the physical reality on the warehouse floor: here, agility, speed and processes that have to mesh without friction losses still count.
For IT managers, SAP project managers and those responsible for logistics, this situation raises a fundamental question: what skills do the internal project team and external partners need to bring to get this transformation safely on the road? Is classic, isolated module knowledge of SAP EWM still enough, or does the path lead via broadly skilled generalists?
Practice shows that getting the wrong people into this key position leads to rigid system landscapes, project delays and, in the worst case, acceptance problems among end users. To prevent this, decision-makers have to redefine the balance between technological specialisation and cross-functional process understanding.
The reality on the warehouse floor: why SAP projects fail in practice
A common stumbling block in S/4HANA logistics transformations is losing touch with the ground. If IT decisions are made purely at the drawing board, without considering the physical processes at the loading dock or in the narrow-aisle warehouse in detail, there is a risk that the system will be developed in a way that misses practical needs.
SAP EWM (Extended Warehouse Management) is not a small, isolated module but a highly complex, powerful overall system. It controls complex material flow systems (MFS), organises wave management and at the same time has to interact seamlessly with the adjacent business areas. Anyone who falls for the generalist fallacy here and trusts that a consultant “can do a bit of everything” underestimates the depth of the product.
At the same time, pure module specialists often create functional silos. However, a smooth material flow only works if the relevant interfaces – such as the end-to-end EWM-PP interface to production or the connection to sales (SD) – are fully understood. Without this view beyond the confines of the warehouse, rigid IT requirements quickly block the dynamism that logistics practice needs.
The paradigm shift under S/4HANA: Fiori and Embedded Analytics put to the test
With the move to S/4HANA, SAP is undergoing a profound technological paradigm shift that has a particularly strong impact on user interfaces. A striking example of this is the modern design of outbound processes in logistics with SAP Fiori, for instance via the Fiori app “Run Outbound Process”.
Compared with the old GUI world, which was often characterised by confusing context menus and a large number of parallel transactions, Fiori offers a role-based, visual entry point. Integrated functions such as Embedded Analytics in EWM make it possible to see the current picking status as a percentage directly in the process as a real-time status bar. This increases transparency and speeds up operational decisions considerably.
This is where the ergonomics trap lies in wait, however: while the new design is visually convincing and massively reduces the training effort for new employees, the tough day-to-day reality of the warehouse often demands a different dynamic from experienced users making the switch. Anyone who has spent years confirming tasks in a split second in the legacy system using only the keyboard and well-practised key combinations loses picking speed when they suddenly have no choice but to reach for the mouse. A successful project is one that uses these new technological possibilities without giving up the ergonomic requirements of the warehouse floor – for example through targeted adjustments and shortcuts for power users.
The skills profile of the future: why the pure module consultant is dying out
To master this balancing act between modern IT architecture and ergonomic practice, the SAP consultant profile required in logistics is changing drastically. The classic consultant who merely carries out standard Customizing and writes a ticket to development when technical problems arise is becoming a bottleneck.
Practice increasingly calls for the type of the “developing consultant”. This does not mean a pure programmer, but a process expert with pronounced technical depth.
Process expertTechnical depthDeveloping consultant
A typical scenario from live operations: A process error occurs at the loading dock when a document is released. A consultant with a technical profile does not wait for external support, but is able to analyse the code structures directly in the system through targeted Fiori or ABAP debugging.
This combination drastically shortens communication channels and solves problems where they arise – directly in ongoing operations.
Make or break: how to put together the perfect SAP logistics team
When selecting the team and partners, project managers face a strategic question: do you rely on the standardised structures of a large consultancy or on sharply positioned logistics boutiques?
Large consultancies often bring predefined frameworks with them, but tend to follow rigid processes. In an agile warehouse environment, this frequently means that existing processes from legacy systems (such as SAP WM) are squeezed 1:1 into the new world by “copy and paste”, without truly exploiting the potential of S/4HANA.
Specialised partners who deliberately stand out from the standard lockstep usually act more flexibly here. They bring the methodological freedom to help shape the system and combine a deep understanding of EWM with the ability to debug directly. When selecting the team, decision-makers should therefore check the following questions:
- Do the consultants have an eye for the physical processes and the ergonomics on the warehouse floor?
- Is the interaction of the interfaces (e.g. EWM-PP) understood holistically?
- Are the experts able to analyse adjustments for process optimisation unbureaucratically and directly in the system, instead of triggering lengthy specification cycles?
Benefits and impact in practice
When a company establishes the right balance of process expertise and technical flexibility in its team, the benefits show on several levels:
Process
Reduced click and search times in goods issue thanks to integrated detail views instead of confusing wastelands of menus.
Technology
Significantly faster error resolution (time-to-resolution) in live operations, as key users and consultants can narrow down errors directly in the browser.
Economics
Lower follow-up costs for the implementation, as adjustments are made in an agile way and time-consuming rounds of coordination are no longer needed.
Organisation
High acceptance of the new software among warehouse staff thanks to targeted, ergonomic UI optimisation that makes everyday work easier.
Conclusion: flexibility beats rigid structures
Today, a successful SAP EWM implementation rarely fails because of missing functions in the standard. It is decided by the flexibility and depth of the minds in the project. Pure module specialists reach their limits at the modern interfaces of S/4HANA; pure generalists lack the depth required for the powerful EWM system. The future belongs to experts who can bridge the gap between keyboard logic and the warehouse floor and make technical innovations such as SAP Fiori intuitive to use.
If you are facing a decision about SAP EWM, S/4HANA or the further development of your own logistics processes, you should first clarify where the greatest pressure to act lies from a business perspective. That is exactly where sensible consulting begins: not with the system, but with the question of which processes really need to be supported in future.
