Sodly
SAP Segregation-of-Duties analysis
Rinexis isn't only a service — it's a multi-tenant platform behind it. Modules under one Control Shell govern the ruleset, find access risk, fix it, prove the fix against a live SOD engine, and export a PFCG-ready workbook your Basis team imports. Findings flow between modules: a Sodly conflict becomes a Roleforge redesign in one click, and Ask Reductus answers across all of them.
Stage 1 of 5: Detect — Sodly. See every SOD conflict — with the evidence.
Match assigned transactions and authorizations against your ruleset to surface every Segregation-of-Duties conflict, rated Critical → Low and backed by real execution counts — so you remediate confirmed risk first, not theoretical noise.
Explore SodlySAP Segregation-of-Duties analysis
Can you even trust your SOD ruleset?
The transactions GRC can't see
Redesign the role. Prove it's clean. Ship it.
Run the whole ITGC audit in one place
Govern the rulebook every SOD check runs against
The read-only AI agent built across the platform
A critical SOD conflict surfaces — with real execution evidence.
Edit T-codes, auth objects, and org-levels in a 3-pane editor.
Re-simulate against the real engine: 2 → 0, coverage 100%.
Emit an AGR_1251 workbook a Basis admin imports directly.
And Tcodex exposes a class of risk GRC literally can't see — custom wrapper transactions like ZME23 → ME23N that bypass transaction-level SOD checks entirely.