EWM Physical Inventory: Count, Difference and the Difference Analyzer (711)

Business scenario

Rack bin RACK-01-03 should hold 100 EA of RM-1000. During the annual storage-bin inventory a counter finds 97 EA. The warehouse supervisor reviews the difference before it is written off.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

1. 01

   Create the physical inventory document open in twin

   PI document for bin RACK-01-03: book quantity 100 EA. The bin is blocked for movements while it is counted.

   Counting is planned by bin or by product, depending on the inventory procedure, so EWM knows exactly what was checked.

2. 02

   Count the bin open in twin

   The counter scans the bin and enters 97 EA. Book: 100. Difference: −3.

   A blind count avoids anchoring the counter on the book quantity.

3. 03

   Post the count in EWM open in twin

   The count is posted: bin RACK-01-03 100 → 97 EA. The missing 3 EA move to the interim difference area.

   The bin is right immediately, so picking and putaway can continue — but finance is not touched until someone has reviewed the difference.

4. 04

   When does finance see the loss? open in twin

   The bin is corrected. When are the 3 missing EA written off in finance?

   Small differences often net out — stock missing from one bin turns up in another. Reviewing before posting avoids writing off and writing back.

5. 05

   Not in finance yet open in twin

   Inventory management still has 100 EA in AFS: 97 in the bin and 3 in the difference area. No accounting document exists.

   Finance sees the difference only after the difference analyzer has posted it, which is a deliberate control point.

6. 06

   Review and post in the difference analyzer open in twin

   The supervisor checks for offsetting surpluses, finds none and posts: −3 EA (711), ₹3,000 written off.

   Only now are stock and value reduced in the books, with a clear audit trail back to the count.

7. 07

   Inventory complete open in twin

   EWM and inventory management agree again: 97 EA. The loss of ₹3,000 is in the books.

   Little moved physically — this process is about discovering and explaining a discrepancy.

SAP documents

Stock impact

Accounting impact

Movement type

• 711GI for inventory difference (warehouse)Reversal: 712

Confirms that recorded stock matches physical stock, corrects bins immediately and posts accepted differences to inventory management and finance through a controlled review.

Transactions & Fiori apps

Configuration

• PI procedure per storage type

  Configuration dependent

  Which procedures are allowed: storage-bin- or product-specific, annual, cycle counting, ad hoc, putaway or low-stock inventory.

• Tolerance groups

  Configuration dependent

  Limit which differences a user may post, by quantity or value.

• Posting of differences to inventory management

  Configuration dependent

  The movement types used (typically 711/712) and the accounts determined. Requires configuration validation.

Prerequisites

• Physical inventory procedures allowed for the storage type (annual, cycle counting, ad hoc, low-stock check)
• Tolerance groups for counters and for the difference analyzer
• No open warehouse tasks on the bins being counted

Master data

Storage bins

Units of counting for bin-specific inventory.

Product (EWM views)

Cycle-counting indicator for cycle counting.

Organizational structure

• Warehouse EW01
• Storage location AFS

Tables

Integration

• MMAccepted differences update inventory management.
• FIThe value of the difference is expensed (or credited for surpluses).

Common errors

• “Bin cannot be counted”

  Likely causes: Open warehouse tasks on the bin; PI procedure not allowed for the storage type

  Where to look: Warehouse monitor — open tasks · PI procedure settings

• “Difference cannot be posted”

  Likely causes: User's tolerance group too low; Posting period closed

  Where to look: Tolerance group assignment · Posting periods

• “Stock in the difference area keeps growing”

  Likely causes: Difference analyzer not run regularly

  Where to look: Difference analyzer backlog

Troubleshooting

Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.

1. CHECK 1

   Counting

   • Are there open tasks on the bin?
   • Is the PI procedure allowed?

2. CHECK 2

   Posting differences

   • Is the tolerance group sufficient?
   • Has the difference analyzer been run?

Interview questions

• How does posting a count in EWM differ from posting a difference in inventory management?

  Posting the count in EWM corrects the bin immediately and moves the difference into an interim difference area inside EWM; inventory management and finance are unchanged. The difference analyzer then reviews differences — often offsetting a shortage in one bin against a surplus in another — and posts the remaining difference to inventory management and FI.

• Which physical inventory procedures does EWM support?

  Annual inventory (storage-bin- or product-specific), cycle counting, ad hoc inventory, and continuous procedures such as putaway inventory and low-stock or zero-stock checks. Which are allowed is set per storage type.

• What is the accounting impact of a count shortage?

  Once posted by the difference analyzer, inventory is credited and an inventory-difference expense account debited at the product's valuation price — typically through automatic account determination. A surplus posts the reverse.

Quiz

Related processes

• 101 · 311EWM Inbound
• FlowReplenishment

References

• SAP SE — SAP Help Portal: Physical Inventory in EWM (source)
• SAP SE — SAP Help Portal: Difference Analyzer (source)
• SAP SE — SAP Help Portal: Inventory Management Integration (source)

Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.

Version history