USR01 table — USR01 user master runtime and format defaults

One row in USR01 represents the presentation and runtime defaults for a single user in a single client, dating from before the user master was consolidated into the tables used today. It records things like the logon language the user prefers, the date and decimal format used to render numbers and dates on screen, the initial menu shown at logon, and a default output device for printing. It does not carry the password hash, account validity dates, user type, or any authorization assignment. Consultants encounter it mainly when chasing a display formatting complaint, or when comparing what a user sees against what SU01 shows on the defaults tab, since the SU01 screen surfaces some of this data even though the underlying persistence has shifted for parts of it.

Always restrict by MANDT first, then BNAME. The table is one row per user per client, so it is small and a full table scan causes no performance concern on its own; the risk is not selectivity, it is misinterpretation. Do not read USR01 in isolation and conclude anything about what the user currently sees, because several of these settings can be overridden at session level by user parameters, by role-driven menus, or by newer personalization stores that were introduced after this table stopped being the sole source. Treat a USR01 read as one input among several, not the final answer.

A user reports numbers displaying with the wrong decimal separator after logon. Select USR01 for MANDT equal to the working client and BNAME equal to the user ID, and inspect DCPFM. Compare that value against what is shown on the SU01 defaults tab for the same user rather than assuming the table value is what is actually rendered, since a personalization override or a different logon path can present a different value even though USR01 has not changed.

USR01 continues to exist on S/4HANA for compatibility, but it should not be treated as the primary source for user format defaults on current releases. The SU01 interface and the underlying user administration function modules manage the authoritative data, and some of what USR01 historically held has effectively been superseded in practice. There is no CDS compatibility view marketed specifically for this table, and no functional reshaping has been documented; it is simply a table whose relevance has diminished rather than one that has been formally replaced.

This is Basis or security team territory. Any question about a user's format defaults, start menu, or logon language should be resolved through SU01 by the team that administers user masters, not by a functional consultant querying or editing the table directly. Functional teams should report the symptom and let security confirm it against the current SU01 settings.

USR02 holds the logon and password administration data for the same user and is the table to check first for any access-related symptom. USR04 and UST04 relate to older profile assignment structures. USR21 links the user to the associated address and person record. AGR_USERS and AGR_1251 are where role assignment and authorization values actually live, and are the correct place to look for any question that sounds like access rather than display formatting. SU01 is the transaction that writes and displays this data in practice.