Two warehouse sites, separately analysable in one SAP EWM.
One system for two warehouses of opposite character – bulky goods here, a classic range there – only works if each site still retains its own view. That was precisely the requirement, and it was solved without a second system landscape.
The key lies in the master data: Here, too, the tried-and-tested EWM approach has proved its worth. By setting up a second dispatch centre, the two sites were able to be systematically separated. In the SCU hierarchy, these shipping office SCUs are assigned as subordinates of the warehouse SCU (business attribute “Warehouse”). As a result, each site can filter the outbound deliveries relevant to it in the warehouse management monitor via its shipping office. The actual separation of work control is achieved through separate queues per site with distinct naming – so the warehouse orders and waves of the two sites run separately and without affecting each other. In practice this means: each site sees at a glance where backlogs are forming, processes its own queues independently and carries clear responsibility for its throughput – without disrupting the other site’s processes.
The result is a warehouse operation that delivers three things at once: close to standard and therefore low-maintenance, lean and therefore manageable for users, and scalable – the architecture is designed so that further processes, volumes and, in future, a third site can grow with it without re-laying the foundations.
What the SAP EWM implementation at Ultra-Pharm shows for other projects.
The concern that SAP EWM is “too big” for one’s own operation often leads to the wrong alternative – a smaller stand-alone solution that blocks the path to S/4HANA. The Ultra-Pharm case shows: this calculation doesn’t add up if you frame it wrongly. Whether the legacy system is an older warehouse software such as Sage here or an existing SAP WM – EWM can be deliberately implemented lean and still run high-performance processes such as batching, prioritisation and mobile picking, entirely within the standard.
The transferable lesson lies less in the technology than in the approach. Anyone planning an EWM implementation should run two questions against their own core processes: Which of them does the SAP standard already cover? And where does a standard enhancement tool – BAdI, RF enhancement, PPF or monitor – suffice instead of custom development? Those who implement this way keep complexity low and remain future-ready.