SAP Segregation of Duties Analysis
Overview
This sample dataset demonstrates how mindzie Studio can be used for Segregation of Duties (SoD) compliance analysis on SAP ERP authorization data. The dataset contains 1,950 synthetic SAP user accounts with role assignments and automatically detected SoD conflicts.
Download: SAP_Segregation_of_Duties.csv
Dataset Summary
| Metric | Value |
|---|---|
| Cases | 1,950 |
| Events | 3,281 |
| Activity Types | 43 |
| Time Period | 2018 - 2024 |
| Users with SoD Conflicts | 266 (13.3%) |
| SoD Conflict Events | 486 |
| Unique Roles | 30 |
| Departments | 20 |
What This Dataset Demonstrates
- SoD conflict detection: Identify users who hold roles granting conflicting transaction code access (e.g., same user can create vendors and post invoices)
- Role assignment tracking: See when roles were assigned to each user over time
- Risk categorization: Conflicts are categorized as Critical or High risk
- Compliance monitoring: Track how role assignments create and resolve SoD violations
Case Structure
Each case represents a SAP user account. The case ID is the SAP username.
Case Attributes
| Attribute | Type | Description |
|---|---|---|
| CaseId | String | SAP user ID |
| UserFullName | String | User display name |
| AccountStatus | String | Active, Locked by Admin, Locked by Failed Logins, etc. |
| UserType | String | A (Dialog), B (System), C (Communication) |
| UserTypeDescription | String | Human-readable user type |
| UserValidFrom | String | Account start date |
| UserValidTo | String | Account expiry date |
| TotalRoleCount | Integer | Total roles ever assigned to this user |
| ActiveRoleCount | Integer | Currently active role assignments |
Event Types
Events fall into two categories:
Role Assignments (e.g., "Role Assigned: Z:FI_AP_CLERK"):
| Attribute | Description |
|---|---|
| ActivityName | "Role Assigned: [role name]" |
| ActivityTime | Date the role was assigned |
| Resource | BASIS_ADMIN |
| RoleName | SAP role name |
| RoleType | Single or Derived |
SoD Conflict Detections (e.g., "SoD Conflict: Vendor Fraud Risk"):
| Attribute | Description |
|---|---|
| ActivityName | "SoD Conflict: [conflict name]" |
| ActivityTime | Date the conflict became active |
| Resource | SYSTEM |
| FunctionA_TCode | Transaction code from the first conflicting function |
| FunctionB_TCode | Transaction code from the second conflicting function |
| FunctionA_Role | Role granting the first function |
| FunctionB_Role | Role granting the second function |
SoD Conflict Types in This Dataset
| Conflict | Risk | Description |
|---|---|---|
| Vendor Fraud Risk | Critical | Create/change vendor + post vendor invoice |
| PO Self-Approval Risk | Critical | Create purchase order + approve purchase order |
| Payment Fraud Risk | Critical | Post invoice + execute payment run |
| Bank Detail Redirect Risk | Critical | Change vendor bank details + execute payment |
| GR/IR Collusion Risk | High | Post goods receipt + post invoice |
| Customer Billing Fraud Risk | High | Create sales order + create billing document |
| HR Payroll Manipulation Risk | Critical | Maintain HR master data + run payroll |
| Journal + Payment Risk | High | Post journal entry + execute payment |
Roles Included
The dataset includes 30 SAP roles across these functional areas:
| Area | Roles |
|---|---|
| Finance - AP | Z:FI_AP_CLERK, Z:FI_AP_MANAGER |
| Finance - AR | Z:FI_AR_CLERK, Z:FI_AR_MANAGER |
| Finance - GL | Z:FI_GL_ACCOUNTANT, Z:FI_GL_MANAGER |
| Finance - Payment | Z:FI_PAYMENT_CLERK, Z:FI_PAYMENT_MANAGER |
| Procurement | Z:MM_BUYER_JUNIOR, Z:MM_BUYER, Z:MM_BUYER_SENIOR |
| Procurement - Approval | Z:MM_PO_APPROVER, Z:MM_PO_APPROVER_L2 |
| Procurement - Vendor | Z:MM_VENDOR_ADMIN, Z:MM_VENDOR_CLERK |
| Procurement - GR/Invoice | Z:MM_GR_CLERK, Z:MM_GR_LEAD, Z:MM_INVOICE_CLERK, Z:MM_INVOICE_LEAD |
| Sales | Z:SD_SALES_REP, Z:SD_SALES_MANAGER, Z:SD_BILLING_CLERK, Z:SD_SHIPPING_CLERK |
| HR | Z:HR_ADMIN, Z:HR_PAYROLL, Z:HR_RECRUITER |
| Warehouse | Z:WM_OPERATOR, Z:WM_MANAGER |
| Superuser | Z:FI_SUPERUSER, Z:MM_SUPERUSER |
Suggested Analyses
Once loaded in mindzie Studio, try these analyses:
- Process Map: View the flow of role assignments and conflict detections per user
- Filter by SoD Conflicts: Filter activities containing "SoD Conflict" to focus on violations
- Case Attributes: Filter by AccountStatus = "Active" to focus on current risk
- Variant Analysis: Identify the most common conflict patterns across users
- Timeline View: See how conflicts were introduced as roles accumulated over time
Source
This dataset was generated from synthetic SAP authorization tables (AGR_USERS, AGR_DEFINE, AGR_TCODES, USR02) using the mindzie SAP Segregation of Duties extraction package.
This documentation is part of the mindzie Studio process mining platform.