sap-ewm
This skill handles SAP EWM (Extended Warehouse Management — S/4HANA modern replacement) including Warehouse Process Types, Warehouse Order (/SCWM/MON), Inbound/Outbound Processing, Wave Management (/SCWM/WAVE), Packing (/SCWM/PACK), RF Framework (/SCWM/RFUI), Physical Inventory (/SCWM/PI), Resource Management, Yard Management, Labor Management, and EWM-TM Integration. Covers Embedded EWM (S/4HANA on-premise/RISE) and Decentralized EWM. Use when user mentions EWM, 확장창고관리, extended warehouse, warehouse order, 창고오더, wave, 파도, packing, 패킹, RF, 핸드헬드, putaway strategy, 적치전략, yard management, 야드관리, embedded EWM, decentralized EWM, /SCWM, 웹 기반 작업자, 리소스 관리, 라벨 프린팅.
BoxLogoDev · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add BoxLogoDev/sapstack --skill sap-ewmAbout this skill
name: sap-ewm description: > This skill handles SAP EWM (Extended Warehouse Management — S/4HANA modern replacement) including Warehouse Process Types, Warehouse Order (/SCWM/MON), Inbound/Outbound Processing, Wave Management (/SCWM/WAVE), Packing (/SCWM/PACK), RF Framework (/SCWM/RFUI), Physical Inventory (/SCWM/PI), Resource Management, Yard Management, Labor Management, and EWM-TM Integration. Covers Embedded EWM (S/4HANA on-premise/RISE) and Decentralized EWM. Use when user mentions EWM, 확장창고관리, extended warehouse, warehouse order, 창고오더, wave, 파도, packing, 패킹, RF, 핸드헬드, putaway strategy, 적치전략, yard management, 야드관리, embedded EWM, decentralized EWM, /SCWM, 웹 기반 작업자, 리소스 관리, 라벨 프린팅. allowed-tools: Read, Grep
1. Environment Intake (Critical)
S/4HANA Mandatory: EWM only runs on S/4HANA (on-premise, RISE, or Cloud PE).
- Embedded EWM: Integrated in same S/4HANA instance (typical for manufacturing)
- Decentralized EWM: Separate EWM system, multiple S/4HANA instances (complex networks)
Questions to ask user:
- Embedded or Decentralized EWM?
- S/4HANA release year? (1909, 2020, 2021, 2022+?)
- Warehouse network complexity? (single, multi-plant, 3PL outsourced?)
- RF capability? (web-based, native app, mobile device?)
- Current pain point: inbound process, picking speed, wave management, resource allocation, yard?
2. EWM Architecture (Embedded vs Decentralized)
Embedded EWM (typical)
Single S/4HANA instance runs both FI/MM/SD and warehouse operations.
| Component | Table Prefix | Purpose |
|---|---|---|
| Warehouse Master | /SCWM/ | Warehouse structure, zones, resources |
| Inbound Order | /SCWM/OBO | ASN → goods receipt → putaway |
| Outbound Order | /SCWM/OBO | Sales delivery → picking → packing → ship |
| Warehouse Order | /SCWM/OI... | Movement instructions (pick/put/pack) |
| Quant | /SCWM/QUANT | Stock holder (replaces LQUA from WM) |
| Resource | /SCWM/RESRC | Labor, equipment (forklifts, scanners) |
Data flow:
MM/SD document (MKPF/VBEP) → Warehouse Order (/SCWM/OI...)
↓
RF/Web worker executes → Confirmation
↓
Post goods receipt/issue back to MM/SD (MKPF/VBEP updated)
Decentralized EWM (complex networks)
Separate EWM system (own database, own S/4HANA or legacy) manages warehouse. Multiple plants connect.
Use when:
- 3PL outsourced warehouse (external operator)
- Multi-region distribution (each region own WH system)
- Existing legacy warehouse system to preserve
Challenge: ALE/IDocs for MM/SD ↔ EWM synchronization
3. Warehouse Structure & Master Data
Warehouse Configuration (/SCWM/MIGO_SAC or /SCWM/INIT)
| Entity | T-code | Definition | Table |
|---|---|---|---|
| Warehouse | /SCWM/WM01 | Top container (plant level) | /SCWM/WHSC |
| Warehouse Process Type | /SCWM/WM02 | Logical zone (receiving, picking, packing) | /SCWM/WOTY |
| Warehouse Zone | /SCWM/WM03 | Physical area (aisle, bay, level) | /SCWM/WHZONE |
| Storage Bin | /SCWM/WM04 | Individual location | /SCWM/BINLOC |
| Resource | /SCWM/RES01 | Worker, equipment, gate | /SCWM/RESRC |
Key Difference from WM
| Aspect | ECC WM | S/4HANA EWM |
|---|---|---|
| Bin address | Fixed 9-char (ST-SEC-BIN) | Flexible identifier |
| Quant structure | Simple (material + location) | Rich (batch, serial, shelf-life) |
| Resource mgmt | NOT built-in | Built-in (workers, equipment, capacity) |
| Yard mgmt | NOT available | Built-in (vehicle queue, gate management) |
| Wave picking | NOT standard | Standard feature |
| RF technology | Proprietary WM RF (LT0G) | Web-based (HTML5) + native app |
| Integration | TR/TO intermediate | Direct order integration |
4. Inbound Processing (Goods Receipt → Putaway)
Complete Flow
1. Purchase Order (ME21N) confirmed
2. ASN (Advanced Ship Notice) sent by vendor
- Optional but recommended (enables automatic dock assignment)
3. Create Inbound Delivery (/SCWM/CREATE_INBOUND or auto from PO)
- Assigned to receiving dock / gate
4. Goods arrive → Create Inbound Order (/SCWM/TRAD)
- Automatically triggered OR manual
5. RF worker scans items, verifies quantity/quality
- If quality issue: quarantine bin, hold for inspection (/SCWM/QUAD)
6. Confirm goods receipt → moves to putaway queue
7. Putaway wave created (automatic or manual batch)
8. RF worker executes putaway → bins stock according to putaway rule
9. Stock available for picking (same or next day)
Key Transactions
| T-code | Function | Audience |
|---|---|---|
| /SCWM/TRAD | Create Inbound Order manually | Planner (exception) |
| /SCWM/TRAD1 | Inbound Order list | Planner (daily monitoring) |
| /SCWM/MON | Warehouse Order monitor (all types) | Supervisor |
| /SCWM/IQUANT | Quality hold / Quarantine bins | QC (if inspection needed) |
| /SCWM/GOODS_RECEIPT | Post GR to MM (after putaway confirm) | System automatic |
Tables
Inbound Order Header (/SCWM/ORDICT):
- LGNUM: Warehouse
- ORDERID: Inbound order number (auto-generated)
- STATUS: 01=created, 02=ready-to-execute, 03=in-execution, 04=completed
Warehouse Order (/SCWM/ORDIM_*):
- ORDIM_O (outbound header), ORDIM_C (confirmation)
- Task type: 01=pick, 02=pack, 03=putaway, 04=transfer, 05=count
Putaway Strategy
Unlike WM (LS0N), EWM uses Putaway Rules (customizable ABAP exit).
Standard putaway logic:
- Fixed bin: High-value A-items (configured in material master)
- Slotting: AI-driven optimal bin assignment (distance, capacity)
- FIFO/LIFO: Material master setting (FIFO typical for perishables)
- Consolidation: Add to existing partial quantity if space allows
- Next empty: Default fallback
Configuration: CUSTOMIZING → (cross-module integration) → Warehouse Management → Inbound Processing → Putaway