Lesson 1 of 6
Physical inventory procedures in EWM
9 min
Listen to this lesson
Auditors want to know that the inventory on the balance sheet exists. Warehouse managers want to know that the bin the scanner sends a picker to really holds what EWM says. Physical inventory in EWM serves both, and it does so at bin level, not storage location level. This lesson introduces the procedures EWM offers and how Contoso Motor Co. combines them in warehouse 1710.
Two ways to count: by bin or by product
A storage-bin-specific count counts everything in a bin: all products and handling units. A product-specific count counts one product wherever it sits in the selected bins or handling units. Bin-specific counts find stock that should not be there; product-specific counts focus effort on valuable or troublesome products.
When to count: the procedures
| Procedure | Trigger | Contoso use |
|---|---|---|
| Periodic (annual) | All stock counted on one day or a short window, usually at fiscal year end; movements can be stopped | Not used in Detroit; replaced by cycle counting |
| Ad hoc | Started manually when needed, bin- or product-specific | After damage or a pick denial |
| Low stock / zero stock | Created in the background when picking takes a bin below a threshold (zero for zero-stock) | Fixed bins in 0020: count when a bin empties |
| Low stock check without document | Check during picking with the same threshold; no PI document | Not used |
| Putaway | First putaway into a bin in the fiscal year; worker confirms the bin content | High-rack 0010 |
| Cycle counting | Products counted at intervals by class (for example A, B, C) | All products; A every 20 workdays, B every 60, C every 120 |
| Storage bin check | Verifies a product is in its bin; no quantity count, no document | Spot checks by Marcus |
| External | Counting or sampling done outside EWM; data uploaded and downloaded | Not used |
EWM physical inventory procedures and Contoso's choices.
Cycle counting uses a cycle counting indicator on the warehouse product (from an ABC classification). Each indicator has an interval in workdays, so fast or valuable products are counted more often. The putaway procedure is cheap: a bin is counted the moment it is first used in the year. Low stock counts are cheaper still: counting an almost empty bin takes seconds.
Physical inventory areas and completeness
Each warehouse defines one or more physical inventory areas, each assigned to an activity area with a sort sequence. That activity area is the one SAP says every EWM warehouse really needs. The PI area carries settings for the procedures it allows, low-stock thresholds, what the counter sees (for example whether the book quantity is shown), and whether small differences post automatically after counting. SAP advises agreeing display and posting options with your auditor.
EWM tracks completeness. A PI area is complete when all its relevant bins are counted in the fiscal year; a product is complete when all its stock is counted per PI area and party entitled to dispose. Completeness persists through the fiscal year: a bin counted in January still counts in December. That is how continuous procedures can replace a year-end count, provided every bin and product is covered by year end.
- JanuaryFiscal year opensCompleteness resets; putaway counts start as bins are first used
- MonthlyCycle countsA products every 20 workdays, B every 60, C every 120
- DailyLow and zero stock countsFixed bins counted as they empty
- NovemberCompleteness reviewMarcus and Dan list uncounted bins and products
- DecemberClose the gapsAd hoc or periodic counts for what is still uncounted
What goes wrong in testing
| Symptom | Usual cause | Check before the cycle |
|---|---|---|
| Cycle count run finds no products due | Cycle counting indicator missing on migrated warehouse products | List warehouse products in 0020 without an indicator |
| No low-stock documents although bins empty | PI area does not allow the procedure, or threshold not set | Read the PI area settings for each activity area in scope |
| Completeness report shows bins as uncounted after a count | Count entered but never posted | Include posting, not just counting, in every PI test |
| Counts land in the wrong PI area | Bins assigned to an activity area that is not linked to a PI area | Check activity area assignment of every storage type |
Physical inventory set-up defects that show up as "nothing happened" in testing.
In SAP S/4HANA Cloud Public Edition, the same EWM physical inventory concepts apply, but configuration is done through the settings the Public Edition exposes and users work in the Fiori apps and the mobile (RF) framework. Check the apps and procedures available in your release before writing test cases.
- EWM counts at bin level: storage-bin-specific or product-specific.
- Procedures: periodic, ad hoc, low/zero stock, putaway, cycle counting, bin check, external.
- PI areas are built on an activity area and carry thresholds and display and posting settings.
- Completeness per fiscal year lets continuous counting replace a year-end count.
Check your understanding · not graded
Lesson check
1. Which count finds stock of a product that is in a bin where it should not be?
2. What triggers a low stock physical inventory document?
3. What sets how often a product is cycle counted?
4. A bin was counted in January. Is it complete for the year in December?