SAP Access Control 12.0 leaves mainstream maintenance on December 31, 2027, with an extended maintenance option to 2030. SAP's successor, SAP GRC for SAP HANA, is a migration project, not a support pack. Teams that mainly use Access Risk Analysis can move that part to a specialist instead: MTC Skopos runs SoD and critical access analysis at authorization-object level on a desktop application, from €5,736/year for the base license, while access requests and emergency access stay in SAP GRC or move to an IAM tool.
When does SAP GRC 12.0 maintenance end?
Mainstream maintenance for SAP Access Control 12.0 ends on December 31, 2027. Process Control 12.0 and Risk Management 12.0 share the date. SAP has announced an extended maintenance option to 2030, at additional cost on SAP's usual terms. After that, support moves to customer-specific maintenance.
Nothing stops working on January 1, 2028. What ends is the regular stream of corrections and legal updates included in standard maintenance, and that is what auditors and security teams depend on for a control system.
| Date | What happens |
|---|---|
| December 31, 2027 | End of mainstream maintenance for Access Control, Process Control and Risk Management 12.0 |
| 2028 to 2030 | Extended maintenance available at additional cost |
| After 2030 | Customer-specific maintenance only |
Check the current terms in SAP's support documentation and your maintenance contract before planning around these dates.
What does SAP offer as the successor?
SAP positions SAP GRC for SAP HANA as the successor to the three 12.0 products. It runs on the SAP HANA database with a Fiori-based interface, keeps the core modules, and entered early adoption in 2026. Because the database and platform change, moving to it is a migration project: system build, configuration, ruleset and mitigation catalog transfer, testing and cutover.
SAP Cloud Identity Access Governance (IAG) remains SAP's cloud offering for access governance, on SAP BTP. It is a different product with a different scope, not a hosted copy of Access Control.
What are the options before the deadline?
| Option | What it covers | Effort | Fits when |
|---|---|---|---|
| Migrate to SAP GRC for SAP HANA | Full suite: risk analysis, access requests, emergency access, role management | Migration project | You use most of the suite and want to stay with SAP |
| Buy extended maintenance | Current 12.0 system, to 2030 | Contract only | You need time, for example until S/4HANA is settled |
| Move to SAP Cloud IAG | Cloud access governance on SAP BTP | New implementation | Your landscape is heading to SAP cloud |
| Replace with another suite (Pathlock, Delinea Fastpath, smartGRC, CERPASS) | Suite scope, product-dependent | New implementation | You want workflows and a different vendor |
| Split: specialist for risk analysis, workflows elsewhere | Access risk analysis in a dedicated tool; requests and emergency access in GRC or an IAM | Small for the analysis part | Risk analysis is the module you rely on most |
The SAP GRC alternatives comparison covers the suites in detail, and the 16 SAP SoD tools comparison covers the full market.
Why does Access Risk Analysis deserve its own decision?
In many SAP GRC installations, Access Risk Analysis is the module that carries the audit value: the SoD ruleset, the conflict reports, the mitigation catalog. Access requests and emergency access often run on a fraction of the users, or have already moved to an IAM tool.
If that describes your system, the deadline is an opportunity. Migrating the whole suite to keep one module running is the most expensive way to keep risk analysis. Taking analysis out first shrinks whatever the migration has to carry, or removes the need for it.
MTC Skopos covers that module and stops there. It reads standard SAP table exports (AGR_1251, AGR_1252, AGR_USERS, USR02 and the related role tables) or connects over RFC, evaluates every rule at authorization-object level with field and organizational values, and analyzes a full 10,000-user system in under 2 minutes on a standard laptop. Remediation proposals, simulation and Did-Do evidence of executed conflicts are optional add-ons. It does not handle access requests, provisioning or emergency access, and never writes to SAP. The access risk analysis page lists how it answers the standard RFP questions.
Should you clean up SoD conflicts before migrating?
Yes, whichever option you pick. A migration copies the ruleset, the role design and the mitigation catalog as they are. If the ruleset no longer matches the roles, or half the mitigations cover conflicts that were never executed, the new platform inherits that debt and the migration estimate is built on the wrong numbers.
An independent analysis before the decision gives you three numbers to plan with:
- The real conflict count at authorization-object level, by user and by role
- How many conflicts were actually executed, from change documents (Did-Do analysis)
- The remediation effort: which role changes remove the most conflicts with the least disruption (remediation)
With MTC Skopos that analysis takes under 15 minutes from extraction to findings, and the ruleset you refine converts to SAP GRC format, so the work carries over if you stay with SAP.
Frequently asked questions
When does SAP GRC 12.0 mainstream maintenance end?
Mainstream maintenance for SAP Access Control 12.0, together with Process Control and Risk Management 12.0, ends on December 31, 2027. SAP has announced an extended maintenance option to 2030; check the current terms in SAP's support documentation and your contract.
What replaces SAP Access Control 12.0?
SAP positions SAP GRC for SAP HANA as the successor to Access Control, Process Control and Risk Management 12.0. It runs on the SAP HANA database, so moving to it is a migration project rather than a support pack. SAP Cloud Identity Access Governance (IAG) remains the cloud alternative.
Do we have to migrate SAP GRC before 2028?
No. Extended maintenance covers the period to 2030 at additional cost, and the system keeps running after mainstream maintenance ends. What changes is the support and update path, which is why most teams use the deadline to decide their target architecture rather than to rush a migration.
Can I replace only the Access Risk Analysis part of SAP GRC?
Yes. Access Risk Analysis is the module many teams use most, and it can run outside GRC. MTC Skopos replaces it with authorization-object-level SoD and critical access analysis on a desktop application, from €5,736/year for the base license, while access requests and emergency access stay in SAP GRC or move to an IAM tool.
Should we clean up SoD conflicts before migrating SAP GRC?
Yes. Migrating a ruleset and a mitigation catalog that no longer match the role design carries the problems into the new platform. Running an independent analysis first shows the real conflict count, which conflicts were actually executed, and how much remediation is needed, and that sizes the migration project.
Related reading: SAP Access Risk Analysis · SAP GRC alternatives compared · 16 SAP SoD tools compared · Planning SAP GRC or Pathlock? Start With MTC Skopos · Building an SoD ruleset for S/4HANA
