Ask an SAP user why they can post an invoice but can’t approve it, and the answer is almost always “my role.” Roles decide what every person can see and do in an SAP system. Get them right and people work smoothly while auditors stay calm. Get them wrong and you end up with blocked users on one side and segregation of duties findings on the other.
An SAP role is a collection of permissions that you assign to users so they can do a job in the system. In SAP ABAP systems such as ECC and S/4HANA, roles are built in transaction PFCG (the Profile Generator). A role holds a menu of transactions or Fiori apps plus the authorization objects and field values those actions need.
In one sentence: An SAP role bundles “what you can open” (transactions or apps) with “what you can do inside them” (authorization object values), and PFCG turns that into a profile the system checks every time you act.
Key takeaways
- Roles are built in PFCG and contain a menu plus authorization data, from which the system generates a profile.
- Authorization objects have fields, and fields hold values such as activity (create, change, display) and company code.
- The main role types are single, composite and derived roles.
- SU24 supplies the default authorization proposals PFCG uses, and SU53, ST01 and STAUTHTRACE help find missing access.
- In S/4HANA, roles also carry Fiori business catalogs and launchpad spaces.
How does SAP authorization work?
It helps to see the layers from the bottom up.
| Layer | What it is | Example |
|---|---|---|
| Authorization object | A template that groups up to ten fields the system checks together | F_BKPF_BUK (accounting documents by company code) |
| Authorization field | One element of the object that needs a value | ACTVT (activity) and BUKRS (company code) |
| Authorization | An instance of an object with specific values filled in | ACTVT = 01, 02, 03; BUKRS = 1000 |
| Profile | A set of authorizations the system actually checks against | Generated automatically by PFCG |
| Role | What administrators design and assign | Z_AP_INVOICE_CLERK |
When a user runs a transaction or app, the program code performs an authority check against the relevant objects with the values it needs. If the user’s profiles contain a matching authorization, the action goes ahead. If not, the user gets a “You are not authorized” message.
Activity codes come up constantly, so it’s worth knowing a few: 01 is create, 02 is change, 03 is display and 06 is delete. A role with ACTVT 03 only lets people look. A role with 01 and 02 lets them create and change.
SAP’s own guidance is clear on one point: don’t assign profiles to users by hand. Build roles in PFCG and let the tool generate and assign the profiles, so there’s a clear, reviewable design behind every permission.
What are single, composite and derived roles?
SAP gives you a few role types, and most authorization concepts use all of them.
| Type | What it does | When to use it |
|---|---|---|
| Single role | Contains a menu and authorization data, and generates a profile | The basic building block for a task, such as “process vendor invoices” |
| Composite role | A container of single roles with no authorization data of its own | Bundling several tasks into one job, such as “accounts payable clerk” |
| Master (parent) role | A single role used as a template for others | Defining a task once, with organizational values left open |
| Derived (child) role | Inherits the menu and authorization data from a master role but has its own organizational values | The same task for different company codes or plants |
Derived roles solve a common problem. Say the invoice task is identical in company codes 1000, 2000 and 3000. Instead of maintaining three separate roles that slowly drift apart, you build one master role and derive three children. Each child has its own company code value, and when you change the master, PFCG can push the change down to all derived roles in one step. This is one of the main reasons well-run SAP security teams stay sane.
Composite roles, on the other hand, don’t hold authorization data. If you need to change what a composite role allows, you change the single roles inside it.
What are organizational levels?
Some authorization fields describe where in the company a user can act: company code, plant, sales organization, purchasing organization and so on. PFCG treats these as organizational levels and asks for them in a separate dialog, because the same value appears in many objects in one role.
Organizational levels are the values that change between derived roles. They’re also where many audit findings hide. A role with company code set to * (all values) lets a user act in every company in the system, which is rarely what the business intended.
How do you build a role in PFCG?
The general steps for a single role:
- Create the role. Give it a name in the customer namespace (usually starting with Z or Y) and a clear description. A naming convention helps, because SAP notes you can’t tell single from composite roles by name alone.
- Build the menu. Add the transactions, Fiori catalogs or other services the job needs. This is the “what can they open” part.
- Maintain authorizations. Go to the Authorizations tab. PFCG reads the menu and pulls in default authorization proposals for each item. Fill in organizational levels and any fields still open (shown in yellow or red), and remove anything the job doesn’t need.
- Generate the profile. PFCG creates the technical profile from the authorization data.
- Test. Assign the role to a test user and walk through the real job, including the edge cases.
- Transport and assign. Move the role through development, test and production with transports, and assign it to users through your access request process.
A rule many SAP security people follow: build roles through the menu so the default proposals do most of the work, and avoid adding authorization objects by hand unless there’s a specific reason. Manually added objects are easy to forget and hard to explain later.
What does SU24 do?
When you add a transaction to a role menu, how does PFCG know which authorization objects to propose? The answer is SU24. SAP ships default proposals for its standard transactions (maintained by SAP in SU22), and customers adjust them in SU24 for their own system.
SU24 tells PFCG two things for each transaction: which objects the transaction checks, and which default values to propose. If the SU24 data is accurate, most roles need very little manual work in PFCG. If it’s wrong, every role that uses that transaction inherits the problem. Fixing SU24 once is usually better than fixing the same values in fifty roles.
Custom transactions need SU24 entries too. Developers often forget this, which leaves security teams adding objects by hand to every role that uses the custom program.
How do you find missing authorizations?
Every SAP security team spends time on “I can’t do X” tickets. The standard tools:
| Tool | What it shows | When to use it |
|---|---|---|
| SU53 | The last failed authorization check for a user, with the object and values checked | First step for any access error |
| ST01 | System trace, including every authorization check during a session | When SU53 doesn’t show the problem or several checks fail |
| STAUTHTRACE | A newer trace focused on authorization checks | Same as ST01, with easier filtering and evaluation |
One caution: SU53 shows the last failed check, which isn’t always the one that matters. Some programs check an object, fail quietly and carry on. A trace gives the full picture. And before granting what the trace shows, ask whether the user should have it. The trace tells you what’s missing, not whether giving it is a good idea.
PFCG and SU24 can also read trace results directly, which speeds up role building for new or custom transactions.
How do roles work with Fiori in S/4HANA?
S/4HANA moves many users from classic transactions to SAP Fiori apps, but PFCG is still where roles live. The difference is what goes in the menu. Instead of only transactions, a Fiori role contains:
- Business catalogs, which group the apps for a job area. Adding a catalog to the role menu brings in the start authorizations for the app’s OData services and the authorization proposals for the business data.
- Spaces and pages, which control how tiles appear on the Fiori launchpad home screen. Groups, the older approach, were deprecated as of S/4HANA 2021.
SAP delivers hundreds of template business roles for S/4HANA that you can copy and adjust. They’re a good starting point, but treat them like any template: check what’s inside before assigning, because some are broader than your business needs. If your landscape uses a separate front-end server, you’ll typically need a front-end role for the launchpad content and a back-end role for the data access.
Which authorizations are most sensitive?
Some access is risky no matter how carefully the rest of a role is built. A few examples that security teams and auditors watch closely:
- SAP_ALL and SAP_NEW profiles. SAP_ALL grants every authorization in the system. It belongs only in tightly controlled emergency access, never in day to day use.
- User and role administration. Objects such as S_USER_GRP and S_USER_AGR let someone create users or change roles, which means they can grant themselves anything.
- Table maintenance. S_TABU_DIS with change activity lets users edit table data directly, bypassing the checks built into business transactions.
- Development and debugging with change. Developer access in production can change program behavior or data outside normal controls.
Keep these in separate, clearly named roles, assign them to very few people and review them more often than ordinary access.
What are good role design practices?
Patterns that hold up well in audits and over time:
- Design around tasks. Build single roles for tasks and combine them into jobs with composite roles, instead of one giant role per person.
- Use derived roles for organizational differences. One master per task, derived per company code or plant.
- Avoid wildcards. A * in activity or organizational fields usually grants far more than intended.
- Keep sensitive access separate. Put critical authorizations, such as user administration or table changes, in their own roles that very few people get.
- Check for conflicts before assigning. Run segregation of duties checks on roles and users, ideally with a tool such as SAP Access Control in SAP GRC.
- Document why. Record the business reason for each role and any manual changes, so the next person (or auditor) understands it.
Role design is one part of the wider discipline of identity and access management. The same ideas apply: least privilege, a clean lifecycle and regular reviews.
Frequently asked questions
What is the difference between a role and a profile in SAP?
A role is what administrators design and assign in PFCG, with a menu and authorization data. A profile is the technical object PFCG generates from the role, which the system actually checks at runtime.
What is a derived role in SAP?
A derived role inherits its menu and authorization data from a master role but has its own organizational values, such as company code. It lets you maintain one task design for many parts of the business.
What is SU24 used for?
SU24 maintains the default authorization proposals for transactions and apps in your system. PFCG uses these proposals to fill in authorization data when you add items to a role menu.
How do I find out why a user is missing access?
Start with SU53 right after the error to see the failed check. If that isn’t enough, run an authorization trace with ST01 or STAUTHTRACE while the user repeats the steps.
The bottom line
An SAP role, built in PFCG, combines what a user can open with what they can do inside it, and the generated profile is what the system checks. Use single roles for tasks, composite roles for jobs and derived roles for organizational differences. Keep SU24 accurate so PFCG proposes the right values, troubleshoot with SU53 and traces, and in S/4HANA remember that Fiori catalogs and spaces now live in the role menu too.
Sources: SAP Help: roles, profiles and authorizations; SAP Learning: evaluate users and authorizations; SAP Learning: creating business roles for SAP Fiori content.


