Items with on-hand value > 0 and zero sales in 180 days. Direct write-down candidate.
At a glance
Materials with on-hand stock (MARC.LABST > 0) and zero sales (no goods issue from sales-document delivery) in the last 180 days. The direct write-down candidate at year-end audit. Sums the valuation value of those materials. Configurable threshold (180D default; 365D for spare parts; 90D for fast-fashion).
Calculation
Calculated automatically from your SAP data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US enterprise B2B distributor on S/4HANA Cloud. Snapshot 03 May 26.
This is 5.0% of total inventory ($57.4M). Within the typical 3 to 8% range for B2B distribution but on the higher side.
Five things to notice:
- 2.88M of capital not earning a return. Carrying cost at 25% per annum = 2.0M; at 50% markdown, $1.4M; at full write-down, zero.
- Year-end audit risk. External auditors typically require a write-down on materials aged 365+ days with zero sales velocity. The $1.64M in the 365+ bucket is a likely Q4 P&L hit unless cleared first. Better to clearance-sell at 30 to 50% off than take the full write-down.
- Drill into Top SKUs by Inventory Value to see which materials dominate. Pareto applies: 20% of dead-stock materials drive 70% of dead-stock value. Action the top 50.
- The killer cross-platform finding: Dead Stock with Active Ad Spend. A subset of these dead-stock materials is still being advertised on Google / Amazon / Meta. The merchant is paying to drive traffic to products it cannot sell. That cross-platform join is the highest-impact finding from this card.
- Multi-Company-Code aggregation. Dead stock per CC: US 640K, MX $400K. The MX warehouse has lower dead-stock concentration but smaller base; the CA warehouse has the highest dead-stock-as-percent at 7.6%, suggesting either over-ordering or local demand softness.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in S/4HANA Cloud:
Slow-Moving Stock Fiori app
Inventory Aging Fiori app filtered to 180+ buckets
Material Documents Overview transaction MB51 with movement-type filter
Embedded Analytics: CDS view I_MaterialStockMovement
Direct deep-link: https://my{tenant}.s4hana.cloud.sap/sap/bc/ui2/flp#SlowMovingStock-display
Why our number may legitimately differ from SAP’s Slow-Moving Stock report:
Cross-connector reconciliation: