RZ04 — Maintain Operation Modes and Instances
RZ04 is used to define operation modes and assign work-process distributions to application-server instances. It is most useful when a system changes dialog/background capacity by time of day or administrators maintain instance operation-mode settings. For reliable SAP support, capture the exact system, client, user, time and object context first, then use the transaction's evidence before making configuration or data changes.
Verified practitioner reference for RZ04 — Maintain Operation Modes and Instances. It explains what the transaction does, when it is appropriate, which parameters and evidence matter, how to use it safely, common diagnostic traps, and how its role changes or remains relevant in S/4HANA.
Published 19 Sept 2026· 607 words
Purpose
define operation modes and assign work-process distributions to application-server instances. The transaction is most valuable when used as part of an evidence chain rather than as a shortcut. Start from the exact business or technical incident, preserve its user, time, system and object context, and distinguish display/analysis functions from actions that can alter system state.
When it is used
RZ04 is typically used when a system changes dialog/background capacity by time of day or administrators maintain instance operation-mode settings. Consultants also use it during project testing and post-change validation because a repeatable selection gives objective evidence. In production, keep the initial scope narrow and widen it only after confirming that the first result matches the reported incident.
How to use it in practice
- Review current instances and operation modes.
- Define the intended work-process mix for each mode.
- Ensure every productive instance has consistent mode definitions.
- Maintain the switching schedule separately and validate transitions.
- Monitor SM50/SM66 after a mode switch to confirm the expected distribution.
Key data objects
These are the most useful anchors for work in RZ04. Capture them in incident notes or test evidence so another consultant can reproduce the same result.
- operation mode — verify the exact value and its relationship to the affected execution or business object.
- instance — verify the exact value and its relationship to the affected execution or business object.
- dialog/background work processes — verify the exact value and its relationship to the affected execution or business object.
- operation-mode schedule — verify the exact value and its relationship to the affected execution or business object.
- server definition — verify the exact value and its relationship to the affected execution or business object.
How to prove it in the data
Build a reproducible before-and-after proof. Capture the exact selection or object, record the status, log or result that demonstrates the issue, then apply one controlled correction and repeat the same check. Correlate with neighboring SAP logs, documents or repository objects where needed. A successful retry with changed input is not the same as proving the original root cause.
ECC vs S/4HANA
RZ04 remains part of ABAP CCMS configuration in S/4HANA application-server environments. Availability of a classic transaction does not automatically make it the preferred implementation pattern for new work; distinguish support compatibility from clean-core and cloud-oriented design guidance.
Common pitfalls and how to diagnose them
- Reducing dialog capacity without considering peak users. Validate the exact object, user, timestamp and release context before applying a fix.
- Defining modes but never maintaining the calendar/switching plan. Validate the exact object, user, timestamp and release context before applying a fix.
- Changing production work-process allocation without capacity evidence. Validate the exact object, user, timestamp and release context before applying a fix.
Whose problem this is
Primary ownership is usually with the BASIS team. Bring in Basis, Security, functional or development specialists only when the evidence crosses those boundaries. A high-quality escalation includes the exact transaction, selection or object, timestamp, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/rz04ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.