ERPClimb logoERPClimb

M7 226

Update control of movement type is incorrect

MIGO rejects a goods movement because the movement type control tables do not contain a valid entry for the transaction combination.

Likely root causes

  1. A custom movement type was copied incompletely.
  2. Movement-type control configuration is inconsistent with the transaction/event.
  3. A standard movement type is being used with an unsupported combination of indicators.

What to inspect

  1. Movement type and complete M7 226 key shown in the long text.
  2. OMJJ — movement type definition and update control.
  3. Whether the movement type is standard or customer-defined and how it was copied.

Resolution path

  1. For a custom movement type, compare it with the intended standard reference and rebuild/correct the missing control consistently.
  2. Do not add isolated table entries without understanding the inventory/accounting consequences.
  3. If the combination is unsupported for a standard movement type, correct the business process rather than customizing around it.
  4. Retest stock and accounting updates end to end.

ERPClimb is an independent platform and is not affiliated with SAP SE.