Deployment options: embedded vs decentralised
Embedded EWM runs inside the SAP S/4HANA system and shares master data (product, BP, batches) directly. Decentralised EWM runs on a separate S/4HANA instance connected to one or more ERP systems — chosen for high-volume, highly automated or 24×7 warehouses that must keep running during ERP downtime. Legacy SAP EWM on SCM 7.0 uses CIF to transfer master data.
- Embedded: no master-data replication, simpler landscape, shared database.
- Decentralised: independence, scalability, can serve several ERPs; uses qRFC and master-data distribution.
- Both use the same EWM application code in current S/4HANA releases.
Basic vs advanced warehouse management
S/4HANA includes basic warehouse management in the core licence; advanced features need an additional licence. Advanced capabilities include Material Flow System, labour management, cartonization planning, dock appointment scheduling, yard management, kitting, VAS, cross-docking and slotting.
- Check the current feature scope description for your release before promising a feature.
- A warehouse number can be flagged as basic or advanced.
- Many inbound/outbound basics (RF, waves, HU, POSC/LOSC) are in basic scope.
Organisational structure
The warehouse number is the top level, mapped to plant/storage location in S/4HANA. It contains storage types (physical or logical areas), storage sections (e.g. fast/slow movers), and storage bins. Activity areas group bins for an activity (picking, putaway, PI), and work centres represent pack, deconsolidation, VAS or QI stations.
- Storage type role: standard, work centre, identification point, pick point, staging area, door, production supply.
- Staging area groups and doors connect the warehouse to yard and shipping.
- Supply chain unit (SCU) represents the warehouse as a location for business partners and the organisational model.
- T-codes & apps
/SCWM/LS01/SCWM/LS03/SCWM/SBUP- Configuration
- IMG › SCM Extended Warehouse Management › Extended Warehouse Management › Master Data › Define Warehouse Numbers / Define Storage Type
ERP integration & delivery replication
Plant + storage location are mapped to an EWM warehouse number. ERP deliveries for EWM-managed storage locations are distributed to EWM, which creates its own warehouse request (inbound delivery, outbound delivery order). EWM confirms goods receipt/issue back to the ERP delivery.
- Settings: assign warehouse number to plant/sloc, map ERP warehouse to EWM warehouse, define distribution of deliveries.
- Communication uses qRFC queues — monitor with SMQ1/SMQ2 (and /SCWM/MON for documents).
- Embedded EWM still distributes deliveries internally via the same integration layer.
- T-codes & apps
SMQ1SMQ2/SCWM/MONVL06IVL06O
Master-data transfer for decentralised EWM
In decentralised EWM on S/4HANA, material, BP, batch and classification data are distributed with ALE/data replication (DRF). Legacy SCM-based EWM used the Core Interface (CIF) with integration models.
- Embedded EWM needs none of this — it reads S/4HANA master data directly.
- CIF (legacy): CFM1 creates and CFM2 activates integration models; queues are monitored with SMQ1/SMQ2.
- Plan master-data replication monitoring as a support process.
- T-codes & apps
DRFOUTBD64CFM1CFM2 (legacy SCM EWM)
Embedded or decentralised?
A pharma distributor runs one 30,000-pallet DC with conveyors, 24×7 shipping and S/4HANA upgrades twice a year. Recommend a deployment and list the three arguments you would present to the steering committee.
Interview-style questions
What is the highest organisational level in EWM?
The warehouse number.
Where do you look when an ERP delivery does not appear in EWM?
qRFC queues (SMQ1/SMQ2), the storage-location → warehouse-number mapping, and delivery distribution settings.
Name three advanced-licence features.
Material Flow System, labour management, dock appointment scheduling (also yard management, slotting, cartonization planning).