Lesson 3 of 5
Basic and advanced
10 min
Listen to this lesson
Embedded EWM in SAP S/4HANA can be used as basic or advanced warehouse management. The distinction matters for two reasons: which functions you can use, and what you need to license. SAP documents the exact split in the Feature Scope Description for each S/4HANA release, and licensing terms depend on your contract. This lesson explains the idea at a business level; the details must be confirmed by your SAP contacts and solution architects for your release.
What all EWM does
SAP Learning lists the primary EWM functions: inventory management at storage bin level, storage bin determination for incoming goods, stock removal for outgoing goods, stock transfers, and physical inventory. Inbound processing runs from goods receipt to putaway; outbound processing runs from picking to goods issue; internal processes cover stock transfers and replenishment. Warehouse tasks carry out putaway and picking, and the warehouse management monitor gives supervisors a view of stock, bins, documents, resources and workload.
The additional functions in business terms
| Function | What it does for the business |
|---|---|
| Labor management | Plans and measures warehouse work against engineered standards |
| Yard management | Controls trucks and trailers in the yard and at the doors |
| Value-added services | Manages extra work on goods, such as kitting, labeling or packing to customer specification |
| Cross-docking | Moves inbound goods straight to outbound without storing them |
| Slotting | Decides the best storage place for each product from its demand and dimensions |
| Automation (material flow) control | Connects EWM to conveyors and automated storage |
Examples of functions SAP Learning lists beyond the core. Check the Feature Scope Description for which of them are advanced in your release.
Many practitioners summarize the split as: basic covers the core processes a typical manual warehouse needs; advanced adds the specialized functions for complex, high-volume or automated operations. Treat that as a rule of thumb, not a contract. Before a design workshop promises a function, someone must confirm against the Feature Scope Description and the license whether it is in scope.
- Does the design need a specialized function (for example labor management, yard or automation control)?Yes → confirm in the Feature Scope Description whether it is advanced · No → basic may be enough
- Is it advanced?Yes → confirm licensing with SAP before design sign-off · No → proceed
- Is the license confirmed?Yes → include it in design and test scope · No → design without it, or escalate
For testers, the basic and advanced question changes the test scope directly. Every function that is switched on needs scenarios, data and evidence; every function that is not licensed must stay switched off, and someone should check that it really is. A good habit is to keep a short scope list per warehouse number: the processes and functions in use, whether each is basic or advanced according to the Feature Scope Description, and the test cases that cover it. Process owners can read it, and it makes later upgrades easier to plan.
What would you do?
In a Detroit design workshop, the integrator demonstrates yard management for incoming trucks from Lakeside Components. Maria's logistics colleague loves it. What should happen before it enters the design?
| Function in Detroit's design | Needed for | Scope list decision |
|---|---|---|
| Inbound with putaway rules | Regulator kits from Lakeside; finished goods from 171B | In scope; core |
| Outbound with waves | Fleet orders such as sales order 1000457 | In scope; wave settings tested in sap-ewm-203 |
| Replenishment of picking bins | Fast-moving alternators | In scope; core |
| Physical inventory per bin | Year-end and cycle counts | In scope; core |
| Yard management | Proposed in a demo | Out of scope until FSD and license are confirmed |
| Labor management | Not requested | Switched off; checked in the system |
Contoso's scope list for warehouse number 1710: each entry is a design decision and a test-scope decision.
- Embedded EWM can be used as basic or advanced warehouse management.
- All EWM covers bin-level stock and core inbound, outbound, internal and inventory processes.
- Specialized functions such as labor, yard, VAS, cross-docking, slotting and automation may be advanced.
- Confirm scope in the Feature Scope Description and licensing with SAP before design sign-off.
Check your understanding · not graded
Lesson check
1. Where does SAP document which EWM functions are basic or advanced for a release?
2. Which is a core function of every EWM deployment?
3. What should happen before a specialized EWM function enters the design?
4. A function is not licensed and not in Detroit's design. What belongs in the test scope for it?