OMJJ — Movement Type Configuration
OMJJ is used to display and configure Inventory Management movement-type controls including field selection, quantity/value updates and account grouping. It is most useful when implementing a custom movement type or diagnosing movement behavior that differs from standard design. Work from the exact document, organizational level and business date, then verify downstream status or accounting evidence before changing master data or configuration.
This page explains OMJJ — Movement Type Configuration — as a practitioner reference: what it does, when it belongs in the process, the fields that matter, how to prove the result in SAP data, and the mistakes that create the most rework.
Published 19 Sept 2026· 582 words
Purpose
display and configure Inventory Management movement-type controls including field selection, quantity/value updates and account grouping. The key is to treat OMJJ as one step in an end-to-end process. What users see here is often determined earlier by master data, document status, organizational assignments or configuration, so always capture those inputs before changing the transaction result.
When it is used
OMJJ is typically used when implementing a custom movement type or diagnosing movement behavior that differs from standard design. It is also valuable in integration and regression testing because the resulting document/status provides objective evidence of whether upstream data and configuration are aligned. Narrow the working population first so any change can be reconciled safely.
How to use it in practice
- Start from a standard movement type that matches the intended business event.
- Compare every control area before copying/customizing.
- Document stock, valuation, accounting and reversal behavior.
- Transport configuration and test both movement and reversal.
- Validate generated accounting and downstream process integration.
Key data objects
These fields and business objects usually explain the result in OMJJ. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- movement type — verify the exact value, status, organizational context and date relevance.
- reference movement — verify the exact value, status, organizational context and date relevance.
- field selection — verify the exact value, status, organizational context and date relevance.
- quantity/value update — verify the exact value, status, organizational context and date relevance.
- account grouping/reversal relationship — verify the exact value, status, organizational context and date relevance.
How to prove it in the data
Prove the issue through document flow and chronology. Start with the source requirement or document, identify the exact master/configuration keys used, then inspect the generated logistics or accounting document and its status. For quantity issues, reconcile ordered, received, delivered, invoiced and current/historical stock; for value issues, reconcile pricing, account determination and the FI document.
ECC vs S/4HANA
OMJJ remains powerful and risky on S/4HANA. Inventory simplification does not make movement-type customizing less consequential. In an S/4HANA program, keep valid GUI transactions as support tools but use the strategic Fiori, workflow, embedded analytics and clean-core integration patterns where they provide the preferred business surface.
Common pitfalls and how to diagnose them
- Changing a standard movement type to fix one process. Check the complete document flow before applying a workaround.
- Copying only part of a movement type and creating inconsistent update control. Check the complete document flow before applying a workaround.
- Testing quantity movement without checking FI account determination. Check the complete document flow before applying a workaround.
Whose problem this is
Primary ownership sits with MM/P2P depending on the transaction, with Finance joining where accounting is created and EWM/integration teams joining where execution happens outside core ERP. Escalate with document numbers, organizational keys, date, expected result and proven status.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/omjjERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.