Remediation output is exported per view, so the file you produce depends on which tab you are on and what you have filtered. The choice matters less for the data and more for the audience: a role owner needs a short list of changes, a project manager needs the phased plan, and downstream tooling needs the JSON.
Export targets
| Tab | Default filename | Format | Contains |
|---|---|---|---|
| Remediation, all risks | all_risks_remediation_report.json | JSON | The complete structured report, every risk and recommendation |
| Remediation, all risks | all_risks_remediation_report.tsv | TSV | The same content, flattened for a spreadsheet |
| Remediation, per user | users_remediation.csv | CSV | Per-user remediation view as filtered on screen |
| Remediation, per role | roles_remediation.csv | CSV | Per-role remediation view |
| Recommendations summary | recommendations_summary.csv | CSV | One row per risk with impact and complexity totals |
| Remediation instructions | remediation_instructions.csv | CSV | The flat list of concrete changes to apply |
| Grouped recommendations | grouped_recommendations.csv | CSV | Recommendations consolidated where several users need the same change |
| Removed risks | removed_risks.csv | CSV | Risks the recommendations would clear |
Which file for whom
- A role or composite owner approving a change: filter the per-user view to their population and export
users_remediation.csv. It shows the user, the access, and the usage evidence that justifies removal - Whoever executes the changes in PFCG or the IAM tool:
remediation_instructions.csv, which is the actionable list without the surrounding analysis - Reducing execution effort:
grouped_recommendations.csv, which consolidates the same change requested for many users into one instruction - Reporting what the exercise achieves:
removed_risks.csvalongsiderecommendations_summary.csv - Building your own workbook or feeding another system:
all_risks_remediation_report.json, the only export that preserves the full structure including rationale per recommendation
Exporting for a single risk
Filter to the risk before exporting rather than exporting everything and cutting it down afterwards. Every export writes the current view, so a filtered table produces a filtered file.
Building a deliverable workbook
The JSON export plus remediation_instructions.csv, recommendations_summary.csv and removed_risks.csv are the inputs the remediation workbook tooling expects. Adding single_roles.json and composite_roles.json from the data source export additionally allows a per-user delta showing exactly which transactions and Fiori apps each person would lose.
Verify before you circulate
An export is a proposal, not a validated change. Simulate the recommendations first and confirm nothing new appears in the Added column. See User Simulation.