SMLG — Logon Group Maintenance
SMLG is used to create and maintain message-server logon groups used for SAP GUI load-balanced logons. It is most useful when administrators distribute dialog users across application servers or troubleshoot a load-balanced SAP Logon entry. 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 SMLG — Logon Group Maintenance. 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· 614 words
Purpose
create and maintain message-server logon groups used for SAP GUI load-balanced logons. 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
SMLG is typically used when administrators distribute dialog users across application servers or troubleshoot a load-balanced SAP Logon entry. 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 existing group membership and server health first.
- Add only dialog-capable instances intended for the group.
- Use thresholds that reflect real capacity rather than arbitrary symmetry.
- Test the SAP Logon group through the message server.
- Monitor distribution in SM04/AL08 and workload tools after changes.
Key data objects
These are the most useful anchors for work in SMLG. Capture them in incident notes or test evidence so another consultant can reproduce the same result.
- logon group — verify the exact value and its relationship to the affected execution or business object.
- application server — verify the exact value and its relationship to the affected execution or business object.
- response-time/load thresholds — verify the exact value and its relationship to the affected execution or business object.
- message server — verify the exact value and its relationship to the affected execution or business object.
- group membership — 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
SMLG remains the ABAP logon-group maintenance transaction for S/4HANA application-server landscapes. 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
- Adding an instance that should not accept the target user workload. Validate the exact object, user, timestamp and release context before applying a fix.
- Using logon groups to mask an unhealthy server. Validate the exact object, user, timestamp and release context before applying a fix.
- Changing thresholds without measuring actual workload distribution. 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/smlgERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.