
How to Convert an Authorisation Field into an Organisational Level Field
About this episode
Listen to the SAP Security & GRC podcast – helping you on your journey to effective access risk management in SAP.
In this episode, Ross Robertson, SAP Senior Authorisations Consultant at Soterion, walks through how to convert an authorisation field into an organisational level field within SAP role design – and explains exactly why this matters for centralised, scalable authorisation management.
🔑 Key Takeaways:
- The difference between authorisation fields and organisational level fields in SAP
- Why org level fields enable centralised maintenance across multiple authorisation objects within a role
- How org levels behave independently in parent and derived role designs – protecting child role values from being overwritten
- How to convert an authorisation field to an organisational level using SAP’s built-in functionality
- Practical business case using movement type (BWART) in a goods movement role
If you work with SAP role design, authorisations, or GRC and want to streamline how you manage authorisation values across derived roles, this episode is for you.
👥 Featuring:
- Ross Robertson – Senior SAP Authorisations Consultant, Soterion
Get every episode summarized
Each time SAP Security & GRC publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from SAP Security & GRC

How to Set up and Analyse STUSOBTRACE
SAP Security & GRC

How to Set Up and Analyse STUSERTRACE
SAP Security & GRC

How to Set up and Analyse STAUTHTRACE
SAP Security & GRC

Technical Series: Using LSMW in SAP Authorisation Management
SAP Security & GRC