202
MODULE TOPICExplore the capabilities that make P2M work

P2M 202 · LEARN

Inventory management records where material is, its status, quantity, and value—and feeds reality back into planning.

Receipts, issues, transfers, reservations, physical inventory, batches, and valuation update supply visibility. Stock can be unrestricted, quality inspection, blocked, or in transfer.

HOW IT WORKS

Execution changes the supply position used by planning

Planning can only make useful decisions when it understands what supply actually exists. Receipts, issues, transfers, scrap postings, and inventory adjustments continually change that position. SAP also distinguishes whether inventory is available for planning or use, such as unrestricted, quality-inspection, or blocked stock.

Concept flow: Execution changes inventory → inventory changes available supply → planning recalculates. The inventory position closes the loop and becomes an input to the next planning cycle.

CAPABILITY MODEL

Understand the input, decision, and result

Read the capability as a connected planning decision before moving into detailed SAP controls.

INPUT

Physical movement

Receipts, issues, transfers, scrap, and adjustments change the material position.

STATUS

Usable supply

Plant, storage location, quantity, batch, and stock status determine what can be used or planned.

OUTPUT

Planning feedback

The resulting available supply becomes an input to the next MRP or replenishment decision.

OPERATIONAL FLOW

How the capability performs

The sequence connects business need to a planning or execution result.

01POST

Record movement

Goods movements update quantity, location, ownership, and the relevant inventory status.

02CLASSIFY

Understand availability

Unrestricted, quality-inspection, blocked, and in-transfer stock do not carry the same planning meaning.

03RECONCILE

Compare evidence

Physical count, movement history, reservations, and inventory balance explain the current position.

04FEED

Return to planning

The changed supply position is read by the next planning run and can create, reduce, or delay proposals.

DESIGN & CONTROL

What shapes the result

These controls work together; a locally correct setting can still produce the wrong planning outcome.

Movement meaning

Movement type, quantity, date, reference, and reversal determine what changed physically and in the system.

Availability status

Plant, storage location, batch, stock type, quality, and reservation rules determine usable supply.

Valuation and correction

Valuation area, account determination, physical inventory, scrap, and adjustment procedures protect quantity and value.

DIAGNOSTIC EVIDENCE

What proves the result?

Use the business input, system objects, and resulting state together.

STOCK POSITION

Material, plant, storage location, quantity, batch, stock type, and availability status.

MOVEMENT HISTORY

Receipts, issues, transfers, reservations, scrap, adjustments, material documents, and reversals.

PLANNING FEEDBACK

Before-and-after supply position, MRP coverage, shortage, proposal, and exception result.

PLANNING MOMENT

A cycle count finds 12 fewer seals than the system balance.

The controlled adjustment changes available stock, and the next MRP run sees the new shortage and creates an appropriate proposal. Inventory correction is therefore part of planning feedback, not a separate story.

  • Movement is traceable
  • Stock status is understood
  • Correction is controlled
  • Next plan reflects reality

IN SAP

Simple representation

These are the main planning objects to recognize before moving into detailed controls.

CORE OBJECTS

Material · Plant and storage location · Stock quantity · Stock status

How SAP controls it

Movement types, valuation area, account determination, storage locations, batch rules, and physical-inventory procedures govern postings.

Example

A cycle count corrects a component shortage; the next MRP run sees the new balance and creates an appropriate proposal.

CONTINUE THE PATHContinue to P2M 303

Connect this capability to the complete execution and integration story.

Open practitioner map