Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

SUIM provides reports about users, roles, profiles and authorizations. A review must define whether it concerns current assignments, historical changes or a different security question.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Security separates verifying an identity from granting permission to perform business actions. A role groups relevant access, while restrictions define the allowed data and activities.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP SUIM access review: Find who has a role without mistaking it for a complete audit
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

ABAP SUIM User Information System role/user reporting. The exercise uses a verified starting snapshot plus a declared complete change history; real historical reconstruction depends on retained evidence and configuration. SUIM assignment reports do not establish every effective permission or prove business-data access.

Reviewed relevant official SAP documentation and available official indexed excerpts on 14 November 2026. The identifiers, requests, timelines and expected checks are original illustrative teaching material; no customer SAP execution or reproduction of an incident is claimed. Apply the documented options for the installed product, release and authentication route.

A MANUFACTURING EXAMPLE

Review purchasing support access by evidence

Date the assignment evidence

Role: Z_AP_BUY. Snapshot: 14 November 2026. Current users: REVIEW_A, REVIEW_B. Historical question: Baseline plus changes
What to notice: A current assignment list does not establish historical membership or actual business-data use.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Role
Z_AP_BUY
Snapshot
14 November 2026
Current users
REVIEW_A, REVIEW_B
Historical question
Baseline plus changes
Words you’ll meet in this guide
Authentication
Checking who an identity belongs to.
Authorization
Permission for an action on particular data.
PFCG
The classic ABAP Role Maintenance transaction for organizing roles.
Role
A grouping of intended tasks and associated permissions.
Authorization object
A grouping of related permission fields checked by relevant SAP application logic.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Review question → Selected SUIM report → Dated evidence. Conceptual diagram for SAP SUIM access review: Find who has a role without mistaking it for a complete audit.
Apply the idea: A manufacturer reviews who currently holds a purchasing support role across its SAP users.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Review purchasing support access by evidence

    A manufacturer reviews who currently holds a purchasing support role across its SAP users.

  2. Start with a review question that a report can answer

    “Who has access?” can mean at least four different questions: who is assigned a named role today, who held it during a past period, who has an authorization value regardless of role name, or who actually performed a business action.

  3. Prerequisites: scope, authority and a dated evidence record

    Use an authorized reviewer account and identify the system/client, role or authorization criterion, review date, relevant period and output audience.

  4. Choose roles-in-users for a named role assignment question

    SAP’s where-used documentation lists Roles → In Users with report RSUSR002.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.