SAP named users carry a category (Professional, Functional, Productivity, Self-Service and others). Misclassification is the leading audit-finding category. The Admodum read on the categories, the activity-based recategorisation, the audit posture and the renewal contest.
Every SAP user account in the digital core carries a category. The category is set at user creation (the SU01 user-master record entry) and updated through the user lifecycle. The category determines the commercial category against which the licence is held: the buyer must hold one Professional User licence for every Professional User, one Functional User licence for every Functional User, one Self-Service User licence for every Self-Service User, and so on.
The category is a buyer-side declaration; the SAP-side measurement reads the buyer-side declaration against the contracted licence inventory. The wider SAP system measurement spoke reads the measurement protocol.
The ECC category set is the on-premise SAP named-user surface that most buyers carry into a renewal or audit reading. The principal categories are: the Professional User (the high-touch, multi-module user with full transaction access); the Functional User (formerly Limited Professional, the user with material activity in a defined functional area); the Productivity User (the lighter, restricted-transaction user); the Self-Service User (the employee with self-service-only access, typically HR self-service and time-and-attendance); the Developer User (the developer with code-change permissions); the Test User (the user with permission restricted to a defined test environment); and the Employee variants (the wider Employee, the Employee Limited, the Employee Self-Service named-user variants).
The category set has historical drift: the names changed over the years (Limited Professional became Functional in 2014; the Self-Service categories were narrowed in subsequent product-term updates); the categories carry different price points; the categories are not interchangeable. The product terms in force at the contract anniversary are authoritative.
The S/4HANA category set rebuilds the structure. The principal categories in S/4HANA are: the Advanced User (the closest analogue of the Professional); the Core User (the closest analogue of the Functional); the Functional User (a narrower scope in S/4HANA than the corresponding ECC Functional); the Self-Service User; and the corresponding new-world classes. The FUE conversion from ECC to S/4HANA (as part of the brownfield conversion or the RISE transition) applies the conversion-credit ratio table.
The renewal-preparation question is the prospective recategorisation: the buyer reads the ECC user activity now, recategorises down where the evidence supports it, and converts the recategorised position. The wider S/4HANA conversion planning spoke reads the conversion sequencing.
The principal misclassification pattern is the over-classified user: a user is held as Professional when the user's actual activity inside the system would support the Functional or Productivity category. The pattern is historically driven: an organisation creates the user as Professional at onboarding because the activity profile is unknown; the user's actual activity over time settles in a narrower scope; the category does not move; the licence is held at the higher rate.
The pattern is at scale on most estates. A typical ten-thousand-user SAP estate carries between fifteen and thirty percent over-classified users where the actual activity supports a lower category. The wider SAP audit defence spoke reads the audit-side response.
The activity-based recategorisation is the buyer-side audit move. The procedure reads each user's actual SAP-system activity over a defined window (typically twelve months, against the product-term definitions) against the category definitions in force. The activity is the transaction-code execution log (the ST03N read), the document-create activity (the user's record-creates inside the digital core), the data-update activity (the change documents that the user produces), the session activity (the SM04 read for the active session pattern).
The procedure produces, for every user, a defensible category against the activity evidence. The recategorised category is the buyer-side category at renewal; the buyer-side category at audit. The wider SAP system measurement spoke reads the measurement-tool surface.
The recategorisation is the principal lever inside the SAP renewal preparation. The buyer-side reconciliation runs ahead of renewal and answers four questions per user: the user's category at assignment (the current SU01 entry); the user's actual activity (the twelve-month transaction-code, document-create and data-update log); the category that the activity demonstrably supports; the licence position at the new category. The release of over-classified Professional licences produces shelfware credit; the corrected position reduces the inflation on a RISE conversion.
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The indirect-access mechanism that runs in parallel with the named-user inventory.
The measurement-tool surface against which the recategorisation evidence is built.
The audit-side response framework against which the recategorisation reading is presented.
A senior Admodum SAP advisor will read your SU01 user inventory, your ST03N transaction-code activity log and your category-by-category evidence against your renewal and audit posture on a private call. Active renewal moments route to Renewal Programme.