Building an Effective SoD Ruleset for S/4HANA
2026-01-20

Building an Effective SoD Ruleset for S/4HANA

SoD ruleset for S/4HANA: a segregation of duties ruleset for S/4HANA must cover Fiori apps, OData services, the centralized Business Partner model, and new authorization objects that did not exist in ECC. Simply migrating your old ECC SoD matrix will miss critical risks and produce false positives against the redesigned authorization architecture. MTC Skopos rulesets accept S_SERVICE and S_START values as actions, so Fiori and OData access paths are checked in the same access risk analysis run as transaction codes.

Most S/4HANA projects plan to carry the ECC SoD ruleset over unchanged. It will still run, but it misses access that now goes through Fiori apps and OData services, and it flags conflicts on objects that S/4HANA has replaced.

This guide covers what to add for the new technical layers, which new risk types to define, and how to keep false positives down after the migration.


Why Your ECC SoD Matrix Falls Short

S/4HANA changes more than the user interface. SAP redesigned large parts of the authorization architecture, and that affects both the business functions in your ruleset and the technical objects behind them.

The Business Layer Has Changed

S/4HANA introduces capabilities that simply didn't exist in ECC:

  • Flexible approval workflows that users can configure from their browser
  • Centralized Business Partner model replacing separate vendor and customer masters
  • Extended budget controls with real-time commitment checks
  • Embedded analytics giving users access to data previously locked in reports

Users can now do things that had no equivalent in ECC, and an ECC ruleset has no rules for them.

Example: In ECC, workflow configuration required basis access and custom development. In S/4HANA, a user with the right Fiori app can modify approval thresholds and routing rules directly. If your ruleset doesn't flag "Workflow Configuration" + "Transaction Execution" as a conflict, you have a gap.

The Technical Layer Has Changed

This is where most migrations run into trouble. In ECC, access control was relatively straightforward: check if the user has the transaction code and relevant authorization objects. Done.

In S/4HANA, a single business action might involve:

  1. Fiori Launchpad access (Spaces and Pages)
  2. Fiori app authorization (catalog assignment)
  3. OData service permissions (S_SERVICE authorization object)
  4. Backend authorization objects (the classic checks)
  5. CDS view restrictions (for analytical apps)

Missing authorization at any layer blocks the action. Your SoD analysis has to look at all of these layers to identify conflicts correctly.


The Multi-Layer Authorization Challenge

Let's make this concrete with an example.

Scenario: You want to check if a user can create purchase orders.

In ECC:

Transaction: ME21N
Auth Objects: M_BEST_BSA, M_BEST_EKO, M_BEST_EKG, M_BEST_WRK

In S/4HANA with Fiori:

Fiori App: Manage Purchase Orders (F0842A)
OData Service: MM_PUR_PO_MAINT_V2_SRV
Backend Auth: S_SERVICE (for OData), plus classic auth objects
Catalog: SAP_MM_BC_PO_PROCESS_PC
Space/Page: Procurement workspace

If your SoD matrix only covers the transaction code, you'll miss users who have Fiori-only access. If it only covers the Fiori app, you'll miss users who still access via SAP GUI.

What This Means for Your Ruleset

Your SoD functions need to include both classic transactions AND their Fiori equivalents. And those Fiori apps need to map to their underlying OData services.

A modern S/4HANA function definition looks like this:

Function: Purchase Order Creation
Classic Access
- Transaction: ME21N
- Transaction: ME22N
Fiori Access
- App: Manage Purchase Orders (F0842A)
- App: Create Purchase Order - Advanced (F1943)
OData Services
- MM_PUR_PO_MAINT_V2_SRV
- MM_PUR_PO_ADV_CREATE_SRV
Authorization Objects
- M_BEST_BSA, M_BEST_EKO, M_BEST_EKG
- S_SERVICE (SRV_NAME, SRV_TYPE)

New Risk Categories to Consider

S/4HANA introduces risk categories that didn't exist in ECC. Your ruleset needs to account for these.

1. Workflow Configuration Risks

Users who can configure approval workflows AND execute the transactions those workflows govern can effectively approve their own work. Many ECC rulesets have no rule for it.

RiskFunction AFunction B
Workflow Self-ApprovalConfigure Purchase Approval WorkflowCreate Purchase Orders
Workflow BypassModify Approval ThresholdsProcess Payments
Workflow Master DataMaintain Workflow AgentsExecute Controlled Transactions

2. Master Data Ownership Risks

S/4HANA's unified Business Partner model creates new conflict patterns:

RiskFunction AFunction B
BP + PaymentsBusiness Partner MaintenancePayment Execution
BP + Sales OrdersBusiness Partner MaintenanceSales Order Processing
BP + Credit DecisionsBusiness Partner MaintenanceCredit Management

3. Configuration vs. Execution Risks

More configuration happens through Fiori apps than ever before:

RiskFunction AFunction B
Pricing ConfigMaintain Pricing ConditionsCreate Sales Orders
Tax ConfigMaintain Tax CodesPost Financial Documents
Output ConfigConfigure Output ManagementProcess Transactions

4. Cross-Module Integration Risks

S/4HANA's tighter integration creates risks spanning module boundaries. For finance-specific authorization controls like restricting sensitive G/L accounts, see our guide on G/L account authorization with F_BKPF_BES and F_BKPF_BLA.

RiskFunction AFunction B
FI-MM IntegrationVendor Invoice PostingGoods Receipt
CO-FI IntegrationCost Center SettlementJournal Entry Posting
SD-FI IntegrationBilling Document CreationRevenue Recognition

Building Your S/4HANA Ruleset: Step by Step

Step 1: Audit Your Current Matrix

Before building anything new, understand what you have:

  • How many risks does your current matrix contain?
  • What technical objects are defined (just T-codes, or auth objects too)?
  • When was it last updated? Many organizations are running matrices defined 10+ years ago
  • What's missing? Run your matrix against a test system - how many known risks does it catch?

Step 2: Identify Your Fiori Footprint

Document every Fiori app deployed in your environment:

  1. Extract your Fiori catalog assignments
  2. Map apps to their underlying OData services
  3. Identify apps that replace classic transactions
  4. Flag apps with no ECC equivalent (new risks)

SAP's standard SoD content covers roughly 200 Fiori apps. A large enterprise deployment typically uses about twice that number, so check the ruleset against the apps your users actually have.

Step 3: Expand Function Definitions

For each function in your matrix, add the S/4HANA technical objects:

Before (ECC-style):

Function: Vendor Master Maintenance
- XK01, XK02, FK01, FK02
- F_LFA1_BUK, F_LFA1_AEN

After (S/4HANA-ready):

Function: Vendor Master Maintenance
Classic:
- XK01, XK02, FK01, FK02
- F_LFA1_BUK, F_LFA1_AEN

Fiori Apps:
- Manage Business Partner (F1594)
- Supplier Factsheet (F2723)

OData Services:
- API_BUSINESS_PARTNER
- FAC_SUPPLIER_FACTSHEET_SRV

Additional Auth:
- S_SERVICE
- BOBF authorization objects

Step 4: Add New Risk Categories

Review the risk categories above and add relevant rules for:

  • Workflow configuration conflicts
  • Business Partner risks
  • Configuration vs. execution patterns
  • Cross-module integration risks

Keep it proportionate and focus on risks that match your actual business processes. A manufacturing company needs different rules than a financial services firm.

Step 5: Address False Positives

S/4HANA migrations also produce a specific kind of false positive: the analysis flags risks that can't actually be exploited.

Common false positive scenarios:

ScenarioWhy It's a False Positive
User has T-code but no Fiori accessCan't execute if Fiori is the only interface
User has Fiori app but missing OData serviceTransaction will fail at runtime
User has auth objects but no catalog assignmentCan't launch the app

MTC Skopos handles this by analyzing executable access - checking that users have all required layers rather than individual components. That removes much of the noise from the results.

Step 6: Establish Ongoing Governance

The ruleset needs regular review after go-live:

Quarterly reviews:

  • New Fiori apps deployed
  • Changed business processes
  • Organizational restructuring

Trigger-based updates:

  • S/4HANA upgrade or feature pack
  • New module implementation
  • Custom development deployment
  • Audit findings

Annual full review:

  • Full matrix walkthrough with business owners
  • Regulatory requirement alignment
  • Risk rating recalibration
  • Industry benchmark comparison

Common Pitfalls to Avoid

1. Copy-Paste from ECC

Your ECC matrix was built for a different architecture. Treating it as a foundation rather than a starting point leads to incomplete coverage and false confidence.

2. Ignoring OData Services

Many organizations add Fiori apps to their matrix but forget about OData services. Since S_SERVICE authorization is often granted broadly, this creates blind spots.

3. Over-Engineering

Not every theoretical risk needs a rule. Focus on conflicts that:

  • Represent material business risk
  • Align with your regulatory requirements
  • Match your actual business processes

A 500-rule matrix that's accurate beats a 2,000-rule matrix full of noise.

4. Set and Forget

S/4HANA evolves rapidly. SAP releases new apps quarterly. Your business processes change. A static ruleset becomes obsolete fast.


Automating Your S/4HANA SoD Analysis

Maintaining the ruleset and detecting conflicts by hand doesn't scale past a few hundred users. Look for tooling that:

  • Imports existing rulesets and helps expand them for S/4HANA
  • Understands Fiori architecture including apps, catalogs, and OData services
  • Analyzes executable access across all authorization layers
  • Reduces false positives by validating complete access paths
  • Supports simulation to test ruleset changes before deployment

MTC Skopos for S/4HANA

What MTC Skopos does for S/4HANA:

  • Fiori coverage: import your apps, map them to services, analyze them alongside transaction codes
  • Multi-layer analysis: checks transaction codes, Fiori apps, OData services, and auth objects
  • Executable access focus: flags only conflicts users can actually exploit
  • Simulation engine: test ruleset changes against your real user population
  • Flexible rule definitions: define functions using any combination of technical objects

Try it on your own ruleset

Start Free Trial

Import your existing matrix, extend it for S/4HANA and run a first analysis from table exports. No server install is needed.


Ruleset Maintenance Checklist

Use this checklist when reviewing your S/4HANA ruleset:

Technical Coverage

  • All deployed Fiori apps mapped to functions
  • OData services included in function definitions
  • S_SERVICE authorization object considered
  • CDS view restrictions documented (if applicable)
  • Custom apps and services included

Business Coverage

  • Workflow configuration risks defined
  • Business Partner conflicts addressed
  • Cross-module integration risks covered
  • Configuration vs. execution patterns included
  • Industry-specific risks documented

Quality Assurance

  • False positive rate acceptable (<10%)
  • Risk ratings aligned with business impact
  • Business owner sign-off obtained
  • Regulatory requirements mapped
  • Exception process documented

Governance

  • Quarterly review scheduled
  • Change trigger process defined
  • Version control established
  • Audit trail maintained

Conclusion

A transaction-code-only matrix is not enough for S/4HANA. Functions need their Fiori apps, OData services and S_SERVICE values next to the classic transactions, and the ruleset needs rules for workflow configuration and the Business Partner model.

Start from your current matrix, extend it module by module, test it against a copy of your role data, and put a review cycle in place so it keeps up with new apps and process changes.


Frequently asked questions

Why doesn't my ECC SoD matrix work in S/4HANA?

S/4HANA has a redesigned authorization architecture with Fiori apps, OData services, and the centralized Business Partner model replacing separate vendor/customer masters. Your ECC SoD matrix misses these new access paths and flags conflicts for deprecated transactions, resulting in both false positives and missed risks.

How do you include Fiori apps in an SoD ruleset?

Fiori apps are accessed through OData services with their own authorization objects (S_SERVICE, S_START). Map each Fiori app to its underlying OData service and the authorization objects checked during execution. Use SU24 data (USOBT_C/USOBX_C) to identify the complete authorization chain for each Fiori app.

What is the SAP Business Partner model impact on SoD?

S/4HANA's Business Partner model merges vendor (FK01/MK01) and customer (FD01/XD01) master data into a single transaction (BP). This changes SoD risk profiles because users managing business partners now potentially access both vendor and customer data through one function, creating new cross-process conflicts.

Why should the SoD ruleset for S/4HANA be updated?

S/4HANA introduces new transactions, Fiori apps, OData services, and authorization objects that didn't exist in ECC. Without updating, your ruleset misses risks from new access paths (like Fiori procurement apps) and produces false positives from deprecated ECC transactions. Regular updates ensure your SoD controls match your actual system.

« All posts