Separation of duties
1- violations
12:56 1w1d

Separation of duties
measurement could not be done

Separation of duties, where overlapping authorisations are checked

In status since 22.11.2025 at 21:25
Use transaction SLG1 to view SOD check results. Object ALERT and subobject ESCALATE are used for this.

Report ZSENSOR_FDR_SOD is should be scheduled as background job to perform the checks. To exclude users from the check or to control which values (e.g. company code) should be checked, use the variant of the background job.
Compose new groups with new violation candidates ? Consider using transaction STAUTHTRACE to help find authorisation combinations.


o Resultlog selection for today between 07:06:00 and 12:56:00
o Background task for step ZSENSOR_FDR_SOD is not available

Settings overview

Groups of authorizations are displayed below. Users should never have all authorizations on a single group. TCD
ObjectDescriptionNr.of days Autofix
Things developers should not all be able to do
DEVELOPERSS_TCODETransaction Code Check at Transaction StartSM31
S_TCODETransaction Code Check at Transaction Start TCDSM24
DRF_ADMCreating Outbound Messages ACTVT51

o No information available for this sensor (settings, job)
General information on the sensor: warning: no warning level, error: no error level, sensor name: SOD Separation of duties, parameter value: TIMING:350, class/method: ZCL_SENSORS_SEPERAT_OF_DUTIES=>SENSOR_SOD, duration: 30ms.