Lesson 5 of 6
Cutover and go-live readiness for the warehouse
9 min
Listen to this lesson
A warehouse goes live with stock on its shelves and orders in flight. Contoso's Detroit warehouse moves from classic warehouse management in ECC to embedded EWM inside the conversion's 60-hour cutover window, from Friday 18:00 to Monday 06:00. The warehouse part of that cutover has its own tests, because a perfect system with the wrong opening stock fails on Monday morning.
What must be true on Monday at 06:00
- Every bin in warehouse 1710 exists with the right storage type, bin type and sort sequence.
- Every product in scope has its warehouse product data, packaging specifications and condition records.
- Every pallet and loose quantity is in the right EWM bin, handling unit and stock type, and EWM stock equals inventory management stock in 171R and 171A.
- Open inbound deliveries and outbound deliveries are in a defined state: completed before cutover or available in EWM.
- Every user has a role, a default resource and a working device; printers print.
Loading stock into EWM
SAP Best Practices include a scope item for the initial stock upload into the warehouse. In Contoso's case the classic warehouse data shows which quant sits in which bin; the cutover team freezes movements, extracts bin stock, maps old bins to new EWM bins, loads stock into EWM and reconciles. Luis, the cutover manager, owns the sequence; Marcus owns the business check; Dan owns the value reconciliation.
- Fri 18:00FreezeLast shipments goods-issued; receipts stopped; classic WM movements frozen
- Fri 22:00ExtractBin stock per product, batch and handling unit from the legacy warehouse data
- Fri 23:00ConversionSUM with DMO until about Sat 23:00, then post-processing (system-wide cutover tasks)
- Sun 05:00LoadBins, warehouse product data and opening stock loaded into EWM warehouse 1710 during post-processing
- Sun 10:00ReconcileEWM bin stock vs inventory management vs value; sample counts in 20 bins; alongside Dan's finance reconciliations
- Sun 12:00Smoke testOne receipt, one wave, one goods issue, one count on real devices
- Sun 14:00Go/no-go 2Grace's decision group decides with the warehouse reconciliation and smoke test results
- Sun 14:00–23:00Business validationKey users run the remaining warehouse scenarios; then ramp-up
- Mon 06:00GoPoint of no return; first shift starts with hypercare on the floor
Rehearse, then rehearse again
Contoso runs two mock conversions and a dress rehearsal. Each one includes the warehouse load with production-like data and is timed. Mock 1 typically finds mapping errors (old bins with no new bin), mock 2 finds timing problems, and the dress rehearsal proves the runbook. Every rehearsal ends with the same reconciliation the real cutover will use, so the team knows what "matching" looks like before it matters.
| Check | Mock 1 | Mock 2 | Dress rehearsal |
|---|---|---|---|
| Bins without a mapping | 312 | 4 | 0 |
| Products without warehouse product data | 57 | 0 | 0 |
| EWM vs inventory management differences | 23 products | 2 products (explained) | 0 |
| Warehouse load duration | 9 h | 5 h | 4.5 h |
| Smoke test on devices | Not run | Passed with 2 defects | Passed |
Deliveries in flight
Decide for every open document type what happens at cutover. Contoso's rule: all outbound deliveries are either goods-issued before Friday 18:00 or cancelled and recreated in SAP S/4HANA; inbound deliveries for trucks arriving Monday are recreated so they are processed in EWM. These rules are tested in the mocks with real open documents, because surprises usually come from the documents nobody remembered.
What would you do?
In mock 2, two products show differences between EWM and inventory management after the load. Both are explained: stock was moved in the legacy warehouse after the extract. Luis asks whether the cutover plan needs to change. What is the best answer?
Plan the first week as carefully as the weekend. Contoso schedules a daily stock comparison and difference analyzer review at 14:00 for the first ten working days, keeps Marcus's super users on every shift, and sets a lower threshold for raising a defect: any unexplained difference, any RF step that needs a workaround. Hypercare ends for the warehouse only when two consecutive weeks pass without a severity 1 or 2 warehouse defect.
- Warehouse cutover needs bins, product data, opening stock, open documents and users ready by the first shift.
- Freeze, extract, load, reconcile, smoke test: each step is rehearsed and timed.
- Every rehearsal ends with the same reconciliation as the real cutover.
- Decide and test the rule for every open document type in flight.
Check your understanding · not graded
Lesson check
1. Why is the initial EWM stock load tested in every mock conversion?
2. What did mock 1 typically find at Contoso?
3. Who owns the value reconciliation of the warehouse load?
4. What is the Sunday smoke test at Contoso?