Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

Physical inventory compares recorded stock with counted stock. Creating a count document, entering the count and posting an approved difference are different stages of that process.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Materials Management supports purchasing and inventory. A request, order, goods receipt and supplier invoice describe separate events, each with its own record and status.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for MI01, MI04 and MI07: Separate inventory documents, counts and difference postings
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

MM Inventory Management physical inventory in ERP and supported S/4HANA. Classic MI01/MI04/MI07 availability, combined actions, book-inventory timing, recount, approvals and valuation differ by installed process; WM/EWM are separate.

Reviewed the cited official SAP indexed documentation excerpts on 14 November 2026. Direct Help Portal opens did not consistently expose readable page text. This is documentation-based teaching, not customer-system execution. All document identifiers, quantities and outcomes in the worked case are illustrative; installed release, edition, configuration and authorizations require local verification.

A MANUFACTURING EXAMPLE

Reconcile a component-store count

A count is not an adjustment

Recorded stock: 100. Physical count: 95. Count entry: Observation recorded. Difference posting: Separate approved step
What to notice: Entering the observed quantity does not itself establish that the inventory difference was posted.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Recorded stock
100
Physical count
95
Count entry
Observation recorded
Difference posting
Separate approved step
Words you’ll meet in this guide
Material
A product or supply item managed in SAP.
Plant
An organizational unit for relevant logistics operations.
Goods receipt
A recorded receipt of goods in a business process.
Purchase order
A purchasing document requesting goods or services from a supplier or supplying plant.
Invoice
A supplier’s bill for goods or services.
HANA
SAP’s database platform.
EWM
Extended Warehouse Management: SAP’s application for warehouse processes.
WM
Warehouse Management: the warehouse application or component in the relevant SAP product.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Count document → Recorded count → Approved difference posting. Conceptual diagram for MI01, MI04 and MI07: Separate inventory documents, counts and difference postings.
Apply the idea: A plant count finds 95 components where SAP records 100, and stores must distinguish entering a count from posting an inventory difference.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Reconcile a component-store count

    A plant count finds 95 components where SAP records 100, and stores must distinguish entering a count from posting an inventory difference.

  2. A count document, a count and an adjustment are separate events

    MI01 creates a physical-inventory document in the classic flow, MI04 enters counts and MI07 supports difference processing/posting.

  3. Scope and prerequisites

    The scope is MM Inventory Management physical inventory in classic ERP and supported S/4HANA.

  4. Define exactly what is being counted

    A count must identify the stock population.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.