Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Finance

sap-wm

This skill handles SAP WM (Warehouse Management — ECC legacy module) including Warehouse Structure (LS01N/LS02N), Storage Type/Section/Bin (LS01/LS03N), Transfer Order (LT01/LT03/LT0E), Transfer Requirement (LB01/LB10), Picking/Putaway Strategies, WM-MM/SD Integration, Physical Inventory (LI01N/LI02N), and Decentralized WM (MWMII). Also covers ECC WM → S/4HANA migration (WM deprecated in S/4HANA; use EWM instead). Use when user mentions WM, 창고관리, warehouse, storage bin, 저장위치, transfer order, 이관오더, putaway, 입고적치, picking, 피킹, storage type, 저장유형, quant, decentralized WM, LS01N, LS03N, LT01, LB01, LI01N, MWMII.

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-wm

About this skill


name: sap-wm description: > This skill handles SAP WM (Warehouse Management — ECC legacy module) including Warehouse Structure (LS01N/LS02N), Storage Type/Section/Bin (LS01/LS03N), Transfer Order (LT01/LT03/LT0E), Transfer Requirement (LB01/LB10), Picking/Putaway Strategies, WM-MM/SD Integration, Physical Inventory (LI01N/LI02N), and Decentralized WM (MWMII). Also covers ECC WM → S/4HANA migration (WM deprecated in S/4HANA; use EWM instead). Use when user mentions WM, 창고관리, warehouse, storage bin, 저장위치, transfer order, 이관오더, putaway, 입고적치, picking, 피킹, storage type, 저장유형, quant, decentralized WM, LS01N, LS03N, LT01, LB01, LI01N, MWMII. allowed-tools: Read, Grep

1. Environment Intake (Critical)

ECC vs S/4HANA Alert: WM is DEPRECATED in S/4HANA (all releases).

  • S/4HANA on-premise / RISE: Use embedded EWM (sap-ewm skill) or Stock Room Management
  • ECC 6.0: WM fully supported through extended maintenance (2025)
  • Dual-run transition: ECC WM → S/4HANA EWM requires process redesign (not 1:1 mapping)

Questions to ask user:

  1. ECC 6.0 (which EhP?) or S/4HANA already?
  2. Warehouse network: single, multi, or 3PL outsourced?
  3. RF terminal / barcode capability active?
  4. Current issue: process bottleneck, data accuracy, integration, or migration planning?

2. Warehouse Structure (LS01N / LS03N / LQUA)

Hierarchy & Tables

LevelT-codeDefinitionTable
WarehouseLS01NTop container, assigned to plantsLAGP
Storage TypeLS01Physical zone (rack, yard, high-bay, flow)LTYP
Storage SectionLS03NSub-zone (aisle, row)LEIN
Storage BinLS03NIndividual slot (address: WH-ST-SEC-BIN)LQUA

Warehouse Master (LAGP) Key Fields

  • LGNUM: Warehouse number (2 chars, e.g., "01")
  • LGSYS: Flag — W (WM system) or D (Decentralized)
  • WERKS: Plant assignment
  • LGPLA format: 3-digit ST + 3-digit section + 3-digit bin (e.g., "001001001")

Issue: "Cannot create storage bins"

Root Cause: Missing storage section linking Check: SE16N → LEIN (verify section exists); SE16N → LQUA (verify bins) Fix: LS03N → Create Section → Create Bins (batch entry) → Trigger MRP


3. Transfer Order (LT01 / LT03 / LT0E / LT06)

Key T-codes

T-codeFunctionField
LT01Create TO manuallyLGPLA (from), LGPLB (to)
LT03Release picking TOQty by storage section
LT0ERelease putaway TODestination bin
LT0AConfirm TO executionUpdates LQUA stock
LT0GRF execution (handheld)Worker mobile entry
LT04Cancel TOFull reversal

Process Flow

GR (MIGO 101) → TR created → LB10 batch → TO created (LT01)
  ↓
Release (LT03/LT0E) → RF Execute (LT0G) → Confirm (LT0A)
  ↓
Stock in LQUA, available for picking

Tables (LTAK / LTAP)

LTAK (header):

  • LGNUM, TANUM (TO number)
  • TPTYP (10=picking, 20=putaway, 30=inventory)
  • KZVLP (two-phase picking flag)

LTAP (lines):

  • LGPLA (source bin), LGPLB (dest bin)
  • MATKX (material), MENGE (qty), ERFME (UOM)
  • LGMNG (actually moved qty)

Issue: "Transfer Order stuck in Pick phase"

Root Cause: Partial RF execution + system failure Check: SE16N → LTAP: LGMNG vs MENGE; LT01 → Messages tab Fix: LT0A (resume confirm) OR LT04 (cancel & recreate)


4. Transfer Requirement (LB01 / LB10)

Auto-Creation Triggers

SourceT-codeType
GRMIGO 101Putaway TR
DeliveryVL01NPicking TR
ProductionPPComponent withdrawal TR
Inventory diffLI07Correction TR

Key Transactions

T-codeFunctionAudience
LB01Create TR manuallyPlanner
LB03Release TR for TOCoordinator
LB10Auto-convert TR → TOBatch job
LB05TR search/listDaily monitoring

LB10 Batch Job (Auto TO Creation)

Purpose: Convert released TRs → TOs using putaway strategy Execution: Nightly (e.g., 23:00) — if fails, goods stuck in receiving Monitor: SM37 (job log) or LS12 (TO creation report)

Table LTBK (TR header):

  • LGNUM, TRID (TR number)
  • TDRTY (01=putaway, 02=picking, 03=replenish)

5. Putaway & Picking Strategies

Putaway Strategy (LS0N)

Determines destination bin for incoming stock.

StrategyNameBest ForLogic
00Fixed BinHigh-value A-itemsAlways same bin
01High-Rack (ASRS)High-bay volumeEmpty level/aisle
02Addition StrategyNormal WMSame bin + space, else next-empty
03Next EmptyFlexible rackAlways first available
10ManualSpecial casesPlanner override

Issue: "Putaway directs to wrong bin"

Root Cause: Strategy misconfiguration or bin full Check: LS0N → strategy assignment; SE16N → LQUA: LGMNG vs LTCAP Fix: Increase capacity (LS03N) OR change strategy (LS0N) OR manual override (LT01)

Picking Strategy (LS20)

StrategyNameUse Case
00Fixed BinSlow-movers
01FIFOPerishables, batch-tracked
02LIFOFrozen goods
03Bulk / OpenPalletized high-volume
10ManualFlexible picking

Issue: "Picking TO shows 'No stock available' despite inventory"

Root Cause: Stock in wrong section or strategy mismatch Check: SE16N → LQUA: locked status? Strategy allows section? SE16N → LTAP: which bins picked? Fix: Move stock via TO (LT01) OR override strategy (LT01 manual) OR unlock section (LS16)


6. WM-MM Integration (Goods Receipt → Warehouse)

Complete Flow

PO (ME21N) → GR (MIGO 101, MVT 101) → Material doc (MKPF/MSEG)
  ↓
If WM active: TR created (LTBK, putaway)
  ↓
Putaway strategy applied (LS0N)
  ↓
LB10 batch: TR → TO (LTAK/LTAP)
Read the complete source ↗