Skip to main content

Conflicts — Summary

The Conflicts — Summary screen is the headline view of segregation-of-duties conflicts on a connected application. One line per (Application, Process, Risk) triplet. Each row carries the count of users that hold the incompatible role combinations defined by the SoD matrix.

It is the screen you open at the start of a quarterly review and the one you screenshot for the steering committee.

At a glance​

Nomasx-1 · Applications · Conflicts · SummaryAPPPROCESSRISKUSERSREFRESH12P2P — Procure to PayCreate vendor + Approve payment142026-05-1412P2P — Procure to PayModify PO + Approve receipt72026-05-1412O2C — Order to CashCreate customer + Post adjustment32026-05-1312HR — Hire to RetireChange pay rate + Approve payroll12026-05-14

Goal of the view​

For each connected application:

  • Where do the SoD risks land in the business? The breakdown by Process (P2P, O2C, R2R, HR…) maps the conflict map to a chart everyone understands.
  • How many users are exposed per risk? The Users column is the headline number. Tracking its evolution quarter over quarter is the simplest SoD KPI.
  • When was the data last computed? Refresh date tells whether the analysis is current. A stale refresh date undermines the value of the rest of the chart.

The dataset is summarised — only rows with CFS_COUNT > 0 surface, sorted by Application → Process → Risk. The Details screen is the drill-down.

Columns​

ColumnSourceWhat it tells you
Application IDCFS_APPS_ID — application identifier.The connected application.
Process IDCFS_PROCESS_ID — business process. Looked up against the SoD Process catalog.The functional process the risk belongs to (P2P, O2C, R2R, HR…).
Risk IDCFS_RISK_ID — incompatibility rule. Looked up against the SoD Risks catalog.The named risk being measured.
Users countCFS_COUNT — number of users holding the incompatible combination.How many people are in conflict on this row. The headline number.
Refresh dateCFS_REFRESH — date the row was computed.Freshness of the analysis.

Context menu​

Right-click a row to open the row menu.

ActionWhere it lands
Display UsersList of users in conflict for the selected (Process, Risk) pair.
Display RolesPairs of incompatible roles for the selected (Process, Risk) pair.
Display ObjectsSource-system objects backing the conflict.
Display DetailsFull Conflicts → Details set filtered on the selected (Process, Risk).

Tips & best practices​

  • Sort by Users count descending to land on the highest-impact risk first. That is the row you discuss at the steering committee.
  • Group by Process to see which business area carries the most SoD weight — often the data point a CFO or COO asks for.
  • Watch Refresh date — a row that hasn't refreshed in weeks usually means the SoD job did not run. Trigger a re-scan.
  • Click into the Details screen for the line-by-line backing data of a given row.