How-to: SAP S/4HANA – Guide to the logistical changeover.

For many companies, the switch to SAP S/4HANA is more than just a technical project - it is a strategic change that affects all areas of the organisation. While the focus is often on the modules relating to finance and controlling, logistics processes can easily fall by the wayside. Yet they are the heartbeat of many companies: Without functioning warehouse processes, the business stands still.

Directly to us? Talk to our S/4HANA experts!

Target image and scope: What should the logistics of the future look like?

Especially in intralogistics, a clean changeover is crucial - not only from a technical perspective, but above all in terms of processes. In this article, we show how companies can successfully migrate their SAP warehouse management to the S/4 world. With practical relevance, a structured approach - and a clear focus on what really matters. It doesn't start with the technology, but with a simple question: What should logistics look like in the future?

In many companies today, warehouse and transport processes are stable - but not necessarily efficient. The changeover to S/4HANA is an opportunity to critically scrutinise and rethink established structures. Will you continue to work with SAP WM in compatibility mode? Or should the switch be made directly to SAP EWM Embedded or decentralised? Risk also plays a role: some companies initially adopt their existing WM processes before switching to EWM in a second step. This reduces complexity in the short term - but delays necessary modernisation.

Typical questions in this phase:

  • Which processes are particularly critical today - e.g. in the warehouse or in production?

  • Which systems are connected - e.g. conveyor technology, pick-by-light or AutoStore?

  • Which areas can be modernised directly, where does a gradual transition make sense?

Conclusion: A clearly defined vision is the foundation of every successful transformation - not only for the project team, but also for stakeholders and specialist departments.

Evaluating and analysing your SAP Warehouse Management - What is running today and why?

Before you break new ground, you should understand how you have been travelling so far. Many SAP Warehouse Management processes have grown over the years - with in-house developments, customised solutions and workarounds.

There is enormous potential here: by analysing existing processes, it is often possible to identify where standardisation, automation or streamlining is possible.

Particularly relevant in the analysis phase are

  • Which in-house developments (e.g. Z transactions, user exits) characterise today's SAP warehouse management?

  • Which movement types, fields and reports are really used - and for what?

  • Are there integrations with modules such as MM, SD or PP?

  • Which functions have been omitted or replaced in the S/4HANA environment?

Practical observation: Almost every project shows that the warehouse is not a pure SAP standard. A critical clean-up saves a lot of effort later on - also in terms of training, documentation and support.

Migrating to SAP S/4HANA? This way!

We are experts in S/4HANA integration and migration. Read more guides and success stories from our customers here:

July 13, 2026

Mobile processes in SAP LGM

SAP LGM must prove itself where warehouse processes actually take place: on the move, right where the action is. The “SAP Warehouse Logistics” mobile app demonstrates what system-human interaction on the shop floor looks like today—deliberately streamlined, without an RF framework.

In Part 3 of our practical series, we show which processes in SAP LGM are already running on mobile devices—putaway, picking, and stock transfers—what the requirements are, and where the limitations lie: from handling unit (HU) management to inventory counts (as of July 2026).

In this way, Status C provides sound, practical guidance for anyone planning mobile warehouse processes with SAP LGM—based on the actual functional status, not the marketing pitch.

June 25, 2026

SAP LGM or SAP EWM? Which warehouses are suited to the streamlined SAP cloud solution?

The most important question regarding SAP LGM is rarely a simple ‘yes or no’, but rather: Which is more suitable for my site – SAP LGM or a lean SAP EWM? Both approaches can be implemented quickly – but they lead to different paths for the future.

In Part 2 of our practical guide series, we provide guidance for decision-makers: which warehouses SAP LGM is suitable for, how it differs from EWM, and when a streamlined EWM is the more viable choice – including a comparison of functions and a decision matrix.

In this way, status C provides well-founded, practical guidance for anyone looking to choose the right solution for their site between SAP LGM and SAP EWM.

June 4, 2026

SAP LGM in practice: Goods receipt & putaway

SAP LGM is more than just another SAP warehouse management system: this streamlined, cloud-native warehouse management solution deliberately standardises processes such as goods receipt – quick to roll out, intuitive and fully accessible via Fiori, on both desktop and mobile devices.

In Part 1 of our practical series, we demonstrate goods receipt, including putaway, step by step in a live system – using screenshots rather than theory. At the same time, we honestly assess where SAP LGM still has its limitations today.

This provides a well-founded, practical guide for anyone considering SAP LGM as a reliable complement to SAP EWM.

May 7, 2026

The action framework of status C Connected Warehouse

The action framework in the Connected Warehouse is more than just a technical feature: it makes warehouse processes modular, reusable and customisable – across all applications.

With constant process logging in the SAP application log, processes become traceable and support cases can be resolved more quickly. At the same time, customer-specific requirements can be added without modification, without changing the standard code base.

This creates a robust, maintainable and scalable process architecture for SAP EWM-based warehouse control with status C.

February 26, 2026

Guide to switching to SAP S/4HANA

The S/4HANA conversion is much more than a system change – it is the strategic lever for modernising processes and aligning logistics with real-time transparency. It bundles all procedural decisions into a clear, future-proof transformation path.

Through in-depth readiness analyses and simplification assessments, risks can be managed in a targeted and stable manner – without carrying expensive legacy issues into the future.

Together with status C, this creates a secure, efficient and scalable target architecture that facilitates the transition, accelerates processes and enables future-proof warehouse control.

January 14, 2026

CubeDeploy: The new AutoStore update tool for fast, secure and cross-location rollouts

With CubeDeploy, AutoStore is entering a new era of software deployment: updates are faster, more secure and fully automated – without downtime and without manual effort. A single installer keeps the entire system up to date worldwide and ensures maximum stability and IT efficiency.

In combination with status C store:IT, a perfectly coordinated connection between AutoStore and SAP is created – for smooth processes, maximum availability and an automation landscape that remains effortlessly scalable.

Process design and prototyping: Now it's getting real.

The switch to S/4HANA is the ideal opportunity to rethink processes - not just technically, but also in terms of usability and efficiency. Modern tools such as Fiori apps, improved RF solutions and embedded EWM functionalities open up new possibilities.

Instead of just sketching processes on paper, we recommend Prototyping in a sandbox system. This allows new processes to be tested, trialled and evaluated with key users at an early stage.

These five things pay off:

  1. Early development of a realistic test system with real master data

  2. Close involvement of the operational teams (warehouse, dispatch, production)

  3. Clear definition of which processes should "return to the standard"

  4. Check where it makes sense to automate logistics - e.g. for replenishment strategies

  5. Documentation of functional gaps for later development phases

The earlier real processes are played through, the lower the risk of surprises later in the go-live.

Data migration in SAP: detailed work with a big impact.

Logistical data migration is one of the most challenging tasks in a project - and yet it is often underestimated. Yet it is critical to success: a warehouse can only be operated stably with complete, consistent data.

In practice, this applies, amongst other things:

  • Material masters, storage bins, storage types

  • Handling units, stocks and open documents

  • Transaction data and custom fields

Many companies rely on the SAP Migration Cockpit here - this makes sense, but often reaches its limits in the WM/EWM area. LSMW scripts or specific ABAP programmes are often necessary.

Tip: Data migration is not a one-off event. Plan several test runs with real scenarios - this significantly increases security in live operation.

Test, integration and go-live with SAP S/4HANA.

A clean test phase is crucial to the success of the changeover. And this does not mean the classic unit test - but real end-to-end scenarios as they occur in everyday warehouse operations:

  • Goods receipt with HU handling

  • Transfer via conveyor technology

  • Shipping including labelling and customs

The connection of subsystems - e.g. AutoStore, pick-by-light, mobile devices - should also be tested. Important: No pure "happy path" scenarios, but real variants including exceptions. A clean test strategy is essential, especially when integrating SAP EWM implementation into existing system landscapes.

The centrepiece of planning is the preparation:

  • Training the operational teams on new interfaces, devices and processes

  • Cutover planning at detailed level: When, how and where is data transferred?

  • Support from key users and project team in the hypercare phase

Experience has shown that a "soft go-live" with a limited scope - e.g. in just one warehouse area - helps to identify errors at an early stage. Remember: Without functioning logistics, the operation stops. Plan at least as much time for training, testing and support as for development and customising.

Conclusion: Your logistics deserve more attention.

The switch to SAP S/4HANA is a must for many companies. But it can also be an optional extra - if you take the opportunity to rethink warehouse and production processes. With clear goals, a structured approach and a focus on the essentials, solutions are created that not only work - but inspire. Whether SAP Warehouse Management, automated logistics or digital intralogistics with AutoStore: those who plan early and prioritise correctly lay the foundations for a sustainable, future-proof supply chain.

Frequently asked questions about SAP S/4HANA in warehouse logistics - on-premise, cloud and EWM simply explained:

What advantages does SAP S/4HANA On-Premise offer for warehouse logistics?

SAP S/4HANA On-Premise gives companies full control over their IT infrastructure and impresses with maximum performance in the warehouse. This variant is particularly suitable for complex warehouse environments in which individual processes, e.g. with conveyor technology or automated guided vehicles (AGVs), need to be seamlessly integrated. The high level of data security, real-time capability and precise control of the material flow make On-Premise the preferred solution in regulated or highly automated areas.

How does SAP S/4HANA Cloud support modern warehouse processes?

SAP S/4HANA Cloud impresses with its flexibility, scalability and rapid implementation. Companies benefit from a modern IT architecture, automated updates and a transparent pay-per-use model. New warehouse locations can be connected quickly - ideal for dynamically growing organisations with standardised processes or seasonal requirements.

What makes hybrid SAP architectures particularly attractive in warehouse logistics?

Hybrid models combine the strengths of both worlds: SAP S/4HANA On-Premise is used for real-time processes such as automated picking, while SAP S/4HANA Cloud takes over analysis, reporting and planning processes. The result is a future-proof IT landscape that can be individually expanded while maximising efficiency.

What role does SAP EWM play in conjunction with SAP S/4HANA?

SAP EWM (Extended Warehouse Management) is the modern warehouse management software from SAP and can be flexibly integrated into SAP S/4HANA - both in the cloud and on-premise. This provides companies with a powerful solution for controlling all warehouse processes, from incoming goods inspection to picking and dispatch processing - all in real time and completely in the SAP standard.

How do SAP WM, SAP EWM and SAP S/4HANA differ?

  • SAP WM was the standard solution for warehouse management for a long time, but is being replaced.

  • SAP EWM is the modern successor solution with extended functions and perfect integration in SAP S/4HANA.

  • SAP S/4HANA forms the technological foundation of the new SAP generation and, as a platform, enables both on-premise and cloud operation - with SAP EWM as a flexibly deployable building block.