sap-ewm

## 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**: 1. Embedded or Decentralized EWM? 2. S/4HANA release year? (1909, 2020, 2021, 2022+?) 3. Warehouse network complexity? (single, multi-plant, 3PL outsourced?) 4. RF capability? (web-based, native app, mobile device?) 5. 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**: 1. **Fixed bin**: High-value A-items (configured in material master) 2. **Slotting**: AI-driven optimal bin assignment (distance, capacity) 3. **FIFO/LIFO**: Material master setting (FIFO typical for perishables) 4. **Consolidation**: Add to existing partial quantity if space allows 5. **Next empty**: Default fallback **Configuration**: CUSTOMIZING → (cross-module integration) → Warehouse Management → Inbound Processing → Putaway ### Issue: "Goods received but not moving to putaway" **Root Cause**: Putaway wave not created, or quarantine hold active **Check**: - /SCWM/MON → filter by warehouse → check "Warehouse Orders" pending putaway - /SCWM/IQUANT → quarantine active? If yes, QC must release - /SCWM/WAVE → putaway wave exist for this receipt date? **Fix**: 1. /SCWM/WAVE → create putaway wave manually 2. /SCWM/IQUANT → release from quarantine if ready 3. /SCWM/MON → monitor RF execution (worker must scan & confirm) --- ## 5. Outbound Processing (Picking → Packing → Shipping) ### Complete Flow ``` 1. Sales Order (VA01) created 2. Outbound Delivery (VL01N) created → Warehouse Order auto-created 3. Picking wave created (/SCWM/WAVE) - Consolidation: group multiple orders for multi-pick (efficiency) 4. RF worker picks items per warehouse order (pick + confirm) - Staging area: items held until all picks complete 5. Packing task assigned (/SCWM/PACK_MONITOR) - Box/pallet assignment - Weight/dimension verification - Handling Unit (HU) creation 6. Shipping label printed (barcode, address) 7. Post Goods Issue (VF01) → PGI document updates inventory 8. Invoice created → delivery closed ``` ### Wave Management (/SCWM/WAVE) **Purpose**: Group multiple outbound orders into a single picking wave. **Wave types**: - **Consolidation wave**: Multiple customers, same delivery date → Multi-pick efficiency - **Zone-based wave**: All items in zone 1, then zone 2 (minimize RF movement) - **Batch wave**: Time-based (e.g., all orders between 08:00–10:00) - **Route-based wave**: Group by customer route (if using TM — Transportation Mgmt) **Configuration**: /SCWM/WAVEDEF (wave definition template) → trigger settings (time, qty, manual) ### Packing (/SCWM/PACK) **Handling Unit (HU)** = container (box, pallet, carton) | Task | T-code | Function | |------|--------|----------| | **Create HU** | /SCWM/HU_MAINT | Define box type, dimensions, tare weight | | **Pack monitor** | /SCWM/PACK_MONITOR | Assign items to HU, print label | | **Verify HU** | /SCWM/HU_WEIGH | Weight check (label vs actual) | | **Stage HU** | /SCWM/STAGE | Queue HU for shipment | **HU structure**: ``` Outbound Order (SO line items) ↓ Warehouse Order (pick tasks) ↓ Handling Unit (container) ├─ Item 1 (qty X) ├─ Item 2 (qty Y) └─ Item 3 (qty Z) ``` **Label printing**: Integrated with label printer (ZPL format typical) ### Issue: "Picking complete but delivery not ready to ship" **Root Cause**: Packing not completed, or HU weight verification failed **Check**: - /SCWM/PACK_MONITOR → all items packed into HU? - /SCWM/HU_WEIGH → weight variance flagged? (system blocks if tare ±10% diff) - /SCWM/MON → warehouse order status: completed picking but not packed? **Fix**: 1. /SCWM/PACK_MONITOR → pack remaining items 2. /SCWM/HU_WEIGH → confirm weights (or override if acceptable variance) 3. /SCWM/STAGE → move HU to shipping staging 4. VF01 → post goods issue (MM updated, available for invoice) --- ## 6. RF Framework (/SCWM/RFUI) EWM uses **Web-based RF** (HTML5), replacing the legacy proprietary RF in WM. ### Key Advantages | Feature | EWM RF | WM RF (LT0G) | |---------|--------|------------| | **Technology** | Web/Mobile browser | Proprietary (device-specific) | | **Retraining** | Minimal (familiar UI) | Device-specific learning | | **Devices** | Any mobile, tablet, handheld | Specific terminals (Zebra, Symbol) | | **Real-time sync** | Network-based | Batch reconciliation | | **Barcode/RFID** | Both supported | Barcode primary | | **Offline mode** | Limited (local queue) | Robust (offline queue) | ### RF Transaction Types | T-code / Menu | Function | Worker Input | |---|---|---| | **/SCWM/RFUI** | Main RF menu (entry point) | Worker ID, password | | **Putaway RF** | Receive bin location, scan, confirm | Scan item barcode → bin location | | **Picking RF** | Pick items per order, scan confirms | Scan item → qty → confirm | | **Packing RF** | Scan items into HU, verify weight | Scan item → HU ID → confirm | | **Counting RF** | Physical inventory entry | Scan location → bin → qty | | **Cycle count** | Continuous mini-inventories | Workers scan, system compares | ### Configuration **RF Menu Customization** (/SCWM/RES01 → Resource Profile): - **RF verification profile**: Strictness of scanning (batch/serial required? etc.) - **User authorization**: Which RF transactions available per worker role - **Task assignment**: Automatic vs manual queue pull ### Issue: "RF worker can't see assigned task" **Root Cause**: Task not assigned to worker's queue, or authorization blocked **Check**: - /SCWM/MON → filter by worker → any tasks pending? - /SCWM/RES01 → worker resource profile → RF transaction authorization active? - /SCWM/RFUI → worker logged in? Correct warehouse assignment? **Fix**: 1. /SCWM/MON → manually assign task to worker (if system assignment failed) 2. /SCWM/RES01 → update authorization profile 3. /SCWM/RFUI → worker re-login (clears cache) --- ## 7. Physical Inventory in EWM (/SCWM/PI) EWM inventory leverages quant-level detail (batch, serial, shelf-life). ### Cycle Counting (Standard) ``` 1. /SCWM/PI_SELECT → Define scope (warehouse, zones, materials) 2. /SCWM/PI_CREATE → Generate PI docs → Print count sheets 3. RF worker scans quants, records qty → /SCWM/RFUI (PI task) 4. /SCWM/PI_POST → Post differences (generate MM doc) 5. Report variances → investigate root cause ``` ### Continuous Inventory (24/7) Workers scan every outbound/inbound transaction. System calculates variance in real-time. **Activation**: Customize → Warehouse Management → Physical Inventory → Continuous Mode = X ### Key Difference: EWM PI vs WM PI | Aspect | EWM | WM | |--------|-----|-----| | **Batch/Serial** | Full detail, shelf-life included | Batch-level only | | **Quant matching** | Lot attributes compared | Basic location match | | **Root-cause analysis** | System tracks variance by dimension (batch, shelf-life) | Manual investigation | | **Shelf-life expiry** | Automatic flagging, removal recommendations | Manual review | ### Issue: "PI shows significant variance, batch split across bins" **Root Cause**: Multiple putaway rules scattered same batch (inefficient consolidation) **Check**: - /SCWM/QUANT (table browser) → filter material + warehouse → count bins - /SCWM/PI_POST → check variance report by batch/bin **Fix**: 1. Create consolidation TO (transfer to single bin) 2. Update putaway rule to consolidate same batch 3. Re-run cycle count --- ## 8. Resource Management (Workers, Equipment, Labor)