Master-data change review
Supplier bank details changed. Have review requirements and downstream payments been considered together?
Explore case and packagePeople & organization · Synthetic business case
Access risk and segregation-of-duties review
A user can maintain suppliers and release payments. How should that conflict be reviewed?
Connect access requests with users, roles, risk rules and emergency-access records to review conflicts and mitigating-control proposals.
For · Internal control, IT access management and audit teams
Your path after importing
Follow the process. Check each step.
This is a walkthrough for the product. The page describes the case; calculations and business actions run inside your DataFocus project.
- 01
Inspect linked business records
Select sample U-FIN-023 and inspect users, roles and permissions, access requests and their linked records.
- 02
Analyze risk and source evidence
Analyze the supplier-maintenance/payment-release conflict against job responsibilities, risk rules and mitigating evidence.
- 03
Edit source data and recalculate
Edit a source record in the sample segregation-of-duties rule table and analyze again to compare review evidence; this does not change live account permissions.
- 04
Review and track the current response
Review the response as guided and inspect risk tasks; actions on demo business records do not grant live system access.
Business context
Bring data, knowledge and actions together.
Use these business objects to understand the case. After importing, inspect the fields, relationships and rules, then adapt them to your work.
- Users
- Roles and permissions
- Access requests
- Segregation-of-duties rules
- Emergency accounts
View package resources43 resources
- Business panels
- 1
- Documents
- 5
- Execution definitions
- 1
- Forms
- 15
- Knowledge resources
- 1
- Ontologies
- 1
- Relationships
- 4
- Tables
- 15
From a demo to your business
Bring a concrete question to the next conversation.
Confirm these differences before choosing the data to connect and the rules to retain. Example data and objects do not automatically connect to your production systems.
- Map users, jobs, roles and authorization objects.
- Have control owners define conflicts, emergency-access time limits and mitigation responsibilities.
- Use existing enterprise roles and resource permissions. This package is a synthetic business example; live SAP connections and updates require separate integration and validation.