How to Test SAP EWM Physical Inventory After LE-WM

When you move from LE-WM to EWM, testing physical inventory means proving the whole chain, not just the count screen. That chain is: create the document under the right procedure, count it on RF (including the exceptions), post it in EWM with /SCWM/PI_PROCESS, approve the difference in the Difference Analyzer (/SCWM/DIFF_ANALYZER) under tolerance groups, and finish with a clean stock comparison against Inventory Management. The step teams test least is that last one. In EWM, posting the count and posting the money are two separate decisions, often made by two different people.

Why this is a go-live question in October 2026

Classic LE-WM only ran in S/4HANA as a compatibility pack. For on-premise customers, that deadline has now passed. SAP first set December 31, 2025 as the end date. It then added a final five-month transition period, moving expiry to the end of May 2026 (SAP News Center). RISE with SAP customers are treated differently. SAP says existing RISE S/4HANA systems can keep using compatibility packs until 2030 (SAP Community). Check your own contract against SAP Note 2269324 before you rely on that date.

1. 1610Embedded EWM arrivesS/4HANA ships EWM inside the core, next to LE-WM
2. Dec 2025Original compatibility pack expiryThe date SAP announced for most compatibility packs
3. May 2026Final on-premise expiryFive-month transition period ends; LE-WM usage rights are gone
4. 2030RISE compatibility rights endApplies to existing RISE S/4HANA systems; check your contract

LE-WM customers have two places to go. One is Stock Room Management, which reuses major parts of LE-WM. The other is EWM (SAP Learning). SAP points customers to Note 2882809 to check whether a warehouse fits Stock Room Management's scope, and says it won't invest further in that product (SAP Community). If you're unsure which path a warehouse should take, start with the free course Warehouse Management Options in SAP S/4HANA. For the wider maintenance calendar, see ECC end of maintenance: what 2027, 2030 and 2035 really mean.

What changes for counters and inventory controllers

The broad steps look familiar: create, count, recount, clear. Most of the differences are in the details. In LE-WM, counting is bin-specific. EWM lets you choose bin-specific or product-specific counting, and cycle counting is product-specific (SAP Community). EWM supports these procedures (SAP Learning):

• Periodic (annual) inventory
• Ad hoc inventory
• Putaway inventory
• Low stock and zero stock checks
• Storage bin checks
• Cycle counting
• External procedures

Each procedure has to be allowed for a physical inventory area. External counting, for example, needs procedure EL (bin-specific) or ES (product-specific) enabled. Files come in through /SCWM/PI_UPLOAD and go out through /SCWM/PI_DOWNLOAD (SAP Learning).

The biggest change for the business is approval. The Difference Analyzer collects differences and posts them to inventory and financial accounting. Those differences don't come only from counts. They also come from warehouse task confirmations and from claims on sales orders and stock transfers (SAP Help Portal). So at year-end, the queue your controller reviews will include picking exceptions, not just count differences. Your test data should include both.

Embedded vs decentralized: where the posting lands

EWM has been embedded in S/4HANA since release 1610 (SAP Learning). In embedded EWM, the Difference Analyzer posts inside the same S/4HANA system. You can see the material document and the accounting impact without leaving the system. In decentralized EWM, the same posting has to cross the integration to a separate ERP system. That adds a failure point you have to test: stuck or failed messages, and a warehouse that looks clean while ERP doesn't.

In both setups, your evidence should include /SCWM/ERP_STOCKCHECK (Compare Stock – Inventory Management). The same SAP transaction list also includes /SCWM/WM_ADJUST, for posting differences automatically in the background. Run the stock comparison before the count starts and again after posting. Don't skip it just because you're embedded. Open differences, stock in the wrong stock type, and batch mismatches turn up there too.

The end-to-end chain to test

1. Baseline/SCWM/ERP_STOCKCHECK clean before the count
2. Create/SCWM/PI_CREATE, or /SCWM/PI_DOC_CREATE and /SCWM/PI_CC_CREATE in the background
3. CountRF via /SCWM/RFUI, /SCWM/PI_COUNT, or /SCWM/PI_COUNTLIST for paper
4. Post in EWM/SCWM/PI_PROCESS: recount or post the count
5. Approve/SCWM/DIFF_ANALYZER posts to IM and FI within tolerance
6. ReconcileStock comparison and material documents tie out

All of the transactions above come from SAP's EWM transaction code list. Before you trust any value-based tolerance result, run /SCWM/VALUATION_SET (Determine and Set Prices from ERP), which appears in the same list. The tolerance checks compare values, so a product with no price gives you meaningless pass/fail results.

Test two more behaviors from SAP's documentation. First, a physical inventory area can be set to post automatically, so test both the automatic and the manual setting if your warehouses differ (SAP Community). Second, if a counter corrects a difference after posting, EWM creates and posts an extra physical inventory document automatically (SAP Help Portal). Auditors will ask about that second document, so make sure your evidence covers it.

RF counting: the exceptions are the test

A count where everything matches proves very little. A typical manual RF path is /SCWM/RFUI → Internal Processes → Inventory Counting → Inventory Counting Manually, against the warehouse order the document created. Your menu numbering depends on how your RF menu is configured. A field-tested scenario list (SAP Community) includes:

• Count with no differences: the baseline
• Count with a shortage and with an overage
• An empty HU in the bin
• A product found in a bin that should be empty
• An unexpected product found in a bin that already holds stock
• A recount triggered and completed by a different user
• Batch-managed and serialized products, including a wrong batch found in the bin

Watch the HU rules. HU collective counting lets you count the full HUs, the quantity per HU and any partial quantity without scanning every serial number. It only works with bin-specific procedures: HL (ad hoc), AL (annual) and EL (external) (SAP Community). If your design depends on it for a cycle count, catch that in fit-to-standard, not on the floor in December.

Tolerance groups and roles: test the negative cases

EWM uses two sets of assignments: /SCWM/PI_USER for recount and clearing, and /SCWM/PI_USER_DIFF for the Difference Analyzer. SAP's own Best Practices test script has a Warehouse Clerk (EWM) open this assignment from the Fiori launchpad. It also warns that even with no tolerance check at company code level, a maximum value limit still applies by default (SAP Help Portal). Write negative tests for each tier:

• A clerk tries to post a difference above their limit. Expect a block.
• A supervisor posts the same difference. Expect a material document.
• A counter tries to approve their own count, if your segregation-of-duties rules forbid it.
• A difference posts with a reason code, and finance can see that reason.

Put these in your Security, Role & SoD Test Plan rather than leaving them to the warehouse stream.

Evidence and who signs off

Test area	What to prove	Evidence	Signs off
Procedure setup	Each PI area allows only the intended procedures	Config screenshots, one document per procedure	Warehouse lead
RF counting	Every exception scenario books correctly	PI document history, warehouse order log	Warehouse lead
Approval	Tolerance tiers block and allow as designed	Negative test results, user assignments	Inventory controller
Financial posting	Differences reach IM and FI with the right value	Material and accounting documents	Finance / controlling
Reconciliation	Warehouse and IM stock match after posting	/SCWM/ERP_STOCKCHECK before and after	Inventory controller, auditor

Capture each step with the SAP Test Script Template and close the cycle with the UAT Sign-Off Form. For configuration depth, the free course EWM Physical Inventory and Internal Movements covers procedures and PI areas. Testing and Signing Off Warehouse Processes turns this table into a full warehouse sign-off pack.

Frequently asked questions

Which transaction posts EWM physical inventory differences to Inventory Management?

First, post the count in EWM with /SCWM/PI_PROCESS. Then post the difference to Inventory Management and Finance from the Difference Analyzer, /SCWM/DIFF_ANALYZER. To run that second step in the background, use /SCWM/WM_ADJUST. Test both the manual and the scheduled route if you plan to use both.

Can we keep LE-WM physical inventory in S/4HANA?

On-premise, not under the compatibility pack: those usage rights ended in May 2026. Stock Room Management is still an option if your warehouse fits its scope, and SAP's Note 2882809 explains how to check. RISE customers have compatibility rights until 2030, but that only buys time. It doesn't remove the need to move.

Do we still need a stock comparison in embedded EWM?

Yes. Embedded EWM removes the cross-system message hop, but it doesn't stop stock types, batches or open differences from drifting. Run /SCWM/ERP_STOCKCHECK before the count and after posting, and keep both outputs as audit evidence.

Can we count with paper or an external system instead of RF?

Yes. /SCWM/PI_COUNTLIST suits paper counts. External systems use /SCWM/PI_DOWNLOAD and /SCWM/PI_UPLOAD with procedures EL or ES. Whatever the counting method, the Difference Analyzer approval and the reconciliation steps stay the same.

Sources

1. SAP Announced Final Transition Period for Compatibility Packs for SAP S/4HANA On Premise, SAP News Center, December 31, 2025
2. SAP S/4HANA Compatibility Packs, SAP Community (SAP blog), accessed October 2026
3. The SAP Extended Warehouse Management FAQ Series: End of Mainstream Maintenance, SAP Community (SAP blog), 2024
4. Differentiating the SAP Solutions for Warehouse Management, SAP Learning, accessed October 2026
5. Performing a Physical Inventory, SAP Learning, accessed October 2026
6. Setting Up the Procedures for Physical Inventory, SAP Learning, accessed October 2026
7. Difference Analysis, SAP Help Portal, accessed October 2026
8. EWM Transaction Codes, SAP Help Portal (Support Content), accessed October 2026
9. Assign User to Tolerance Group for Difference Analyzer, SAP Best Practices, SAP Help Portal, accessed October 2026
10. RF Physical Inventory: HU Collective Count & Collective Item Count for a Serialized Product, SAP Community (SAP blog), accessed October 2026
11. Compare Physical Inventory IM – WM – EWM, SAP Community, accessed October 2026
12. Inventory in SAP S/4HANA, SAP EWM, and SAP ATTP: Step-by-Step Guide, SAP Community, accessed October 2026
13. User not assigned to tolerance group in warehouse number, SAP Community Q&A, accessed October 2026
14. Physical Inventory (automatic posting setting), SAP Community Q&A, accessed October 2026