Atlas Diagnostic

SAP movement types diagnostics

A first-pass structure for finding why a goods movement posts to the wrong stock type, account, or status.

Reviewed

Core idea

Movement types in SAP define the direction, stock type, and accounting impact of every goods movement. A wrong movement type does not just misclassify stock — it can post to the wrong account, trigger wrong valuation, create incorrect GR/IR records, or leave inventory in an unusable status. The support goal is to identify which movement type was used, whether it matches the business intent, and what correction is needed.

Common symptoms

  • Goods receipt posted stock to quality inspection instead of unrestricted.
  • Transfer posting created an unexpected accounting entry.
  • Return to vendor did not reduce GR/IR or created a wrong reversal.
  • Movement type is not allowed for the material type or plant.
  • Inventory count adjustment posted to a consumption account instead of inventory.

Likely causes

  • Wrong movement type selected: user chose 101 instead of 103, or 311 instead of 301, changing stock type or valuation.
  • Movement type not configured for material type: the material type restricts which movements are allowed.
  • Account modification mismatch: the movement type posts to a G/L account that does not match the material's valuation class.
  • Stock type confusion: unrestricted, quality inspection, blocked, or in transit were not distinguished correctly.
  • Custom movement type: a landscape-specific movement type behaves differently from standard and is not documented.

Where to check in SAP

  • MIGO — display the material document and check the movement type on each item.
  • MB51 — material documents list, filter by movement type and material.
  • OMJJ — movement type configuration (transaction-dependent, view-only in production).
  • MB52 — stock overview showing stock types per storage location.
  • Material master — check material type and valuation class.

Key tables / transactions / objects

  • T156 — movement types.
  • T156T — movement type texts.
  • MKPF — material document header.
  • MSEG — material document items.
  • MBEW — material valuation.

Diagnostic workflow

  1. Identify the material document number and item from the user report or error.
  2. Check MIGO or MB51 for the movement type used and compare with the business intent.
  3. Verify the stock type before and after the movement in MB52.
  4. Check if the movement type is allowed for the material type and plant.
  5. Review the accounting document (FI) to see if the G/L accounts match expectations.
  6. Determine if the movement should be reversed and re-posted with the correct type.

Typical fixes or next actions

  • Reverse the incorrect movement with the reversal movement type and re-post correctly.
  • Update user training or MIGO defaults to prevent repeated wrong selection.
  • If the movement type configuration is wrong, escalate to the configuration team with documented evidence.
  • For stock type issues, perform a transfer posting to move stock to the correct status.

Support takeaway

Movement type errors are often user selection issues, not system bugs. Before escalating, collect the material document number, the movement type used, the expected movement type, the material, plant, and storage location. A useful movement type ticket should show the business intent and the system result.

Escalation signals

  • The same wrong movement type is used repeatedly, suggesting training or process design issues.
  • A correction movement affects inventory valuation, financial accounts, or month-end closing.
  • The movement type behavior differs between plants or clients and configuration review is needed.
  • The issue involves special stock (consignment, subcontracting, pipeline) with accounting implications.

Boundaries and non-goals

This page is a diagnostic frame, not a movement type configuration guide. It does not cover custom movement type design, WM movement types, or EWM-specific logic. It does not replace SAP's inventory management documentation.

This is not official SAP documentation and not a replacement for system-specific analysis.