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.
Quick answer
- Most likely cause
- A custom movement type was copied incompletely.
- Check first
- Movement type and complete M7 226 key shown in the long text.
- First resolution step
- For a custom movement type, compare it with the intended standard reference and rebuild/correct the missing control consistently.
Likely root causes
- A custom movement type was copied incompletely.
- Movement-type control configuration is inconsistent with the transaction/event.
- A standard movement type is being used with an unsupported combination of indicators.
What to inspect
- Movement type and complete M7 226 key shown in the long text.
- OMJJ — movement type definition and update control.
- Whether the movement type is standard or customer-defined and how it was copied.
Resolution path
- For a custom movement type, compare it with the intended standard reference and rebuild/correct the missing control consistently.
- Do not add isolated table entries without understanding the inventory/accounting consequences.
- If the combination is unsupported for a standard movement type, correct the business process rather than customizing around it.
- Retest stock and accounting updates end to end.
Share this diagnosis
Paste a credited summary into a ticket, chat or forum reply. Your pasted input is never included.
ERPClimb is an independent platform and is not affiliated with SAP SE.