AL08 — System-Wide Logged-On User Overview

AL08 collects and displays the list of users logged on to every application server belonging to the current SAP system, aggregated into a single screen. Each row typically shows the user ID, the application server name, client, terminal or host, logon time, and the transaction or report currently running in that session. The one structural fact that explains most confusion: AL08 does not read a persisted table, it calls each application server live at the moment the transaction is run and merges the responses. If a server is slow to respond, down, or isolated by a network issue, its users simply do not appear in the list, and the total looks artificially low. This makes AL08 a snapshot, not a log, and it will never agree exactly with a count taken a few minutes earlier or later.

AL08 is reached for whenever someone needs to know total concurrent logons across the whole system rather than on one instance, which is the normal case in any landscape with more than one application server. Typical triggers are capacity checks before a peak period, hunting for where a particular user's zombie session is actually running before issuing a kill in SM04 or SM50, or verifying whether a reported 'system is full' complaint is really a licensing or work process saturation issue. It is also used alongside ST03 or ST06 when correlating user counts with CPU or memory pressure. It has largely no Fiori equivalent for ad hoc use; monitoring dashboards in newer tooling summarize load but do not replace the per-user drill-down AL08 gives.

There is no table behind AL08 to query in SE16, this is the point of confusion most consultants hit first. To reconcile a discrepancy, run AL08 and immediately cross-check against SM04 on the specific application server named in the row in question; the counts should match for that instance at that moment. If they diverge, the gap is almost always timing, a session logging off between the two checks, or a server that failed to respond to the collector call and was silently dropped from the AL08 aggregate. For a historical count, ST03 workload statistics are the only reliable substitute, since neither AL08 nor SM04 retain history.

AL08 behaves the same on S/4HANA as on ECC; it is a Basis-layer administration transaction unaffected by the underlying application changes. There is no dedicated Fiori app that replaces the ad hoc, live drill-down AL08 provides, though system monitoring dashboards in newer administration tooling can show aggregate active-user counts as one metric among many. For hands-on session investigation, the GUI transaction remains the practical route.

This is Basis territory. Functional consultants use AL08 only to report a symptom, such as a user claiming to be logged on twice or a server that seems overloaded. A good handover to Basis names the exact user ID, approximate logon time, and which application server the session showed against, so Basis can go straight to SM50 or SM51 on that instance rather than re-running the system-wide check from scratch.

SM04 is the natural next stop, giving the per-server detail and session-kill capability that AL08 lacks. SM51 confirms which application servers exist and are reachable, explaining why a server might be missing from the AL08 list. SM50 and SM66 give the work process view needed to confirm whether a session shown in AL08 is actually doing anything or is stuck. ST03 and ST06 are the tools to reach for once the question shifts from who is logged on right now to how the system has been loaded over time.