Check what WalkMe can measure

WalkMe’s Q4 release started on November 16, 2026 for US and EU data centers. Before comparing SAP GUI transaction codes (T-codes), confirm with your administrators that Product Analytics is enabled and your desktop setup meets the requirements.

  • Check with your admins whether Product Analytics is enabled for the account.
  • Confirm the desktop requirement: WalkMe Desktop Menu 4.5.0+.
  • Confirm the SAP client version: SAP GUI for Windows 7.70 or 8.00.
  • Confirm SAP GUI Scripting is enabled on both server and client.
  • Start analysis from the enablement date only; earlier activity will not be included.
  • Do not expect browser-based SAP Fiori support here.

Data starts on the enablement date, so an earlier date range does not establish a baseline. Ask your administrator to confirm the account and environment before interpreting a blank view.

Compare error counts and rates

A status-bar error count is a raw tally of error events observed in SAP GUI activity. By contrast, the dashboard metric called Error rate by T-code is a share of activity that results in error. Because those measures answer different questions, you should not treat a larger error count as proof that one transaction is more friction-heavy than another, and you should not assume that dividing error count by uses will reproduce the dashboard’s metric exactly.

Take two hypothetical transactions: A shows 40 errors with 2,000 recorded uses; B shows 10 errors with 25 uses. Sorting by total errors puts A first, but the usage counts show why that is not enough to rank friction. Check the dashboard’s reported error rate and sample size. Dividing these counts by uses does not reproduce the dashboard metric.

How to review SAP GUI analytics more carefully

  • Match the same date range in every view you compare.
  • Keep the environment consistent so you are not mixing test, training, and production activity.
  • Use the same filters, including user, system, or workflow filters where applicable.
  • Compare the same workflow stage or business process, not unrelated T-codes.
  • Watch the sample size: a small number of uses can make a metric look volatile.
  • Separate status-bar errors from warnings, logon issues, and navigation problems.
  • Use an authorized SAP test environment to compare a known status-bar message with what the dashboard reports.
  • Review representative error messages with an authorized process owner before drawing conclusions.

WalkMe Q4 2026 Product Release

SAP GUI Product Analytics

Data Collection Level Settings

Illustration of blue and green analytics cards with a magnifying glass between them.
Illustration of blue and green analytics cards with a magnifying glass between them.