Oracle Fusion ERP
Data Extraction Guide
Share this guide with your Oracle Cloud Administrator, Security Manager, or Application Implementation Consultant before starting a V/ergent assessment. All extractions described here are read-only and non-disruptive to production operations. Includes Release 5 programme packs: 25 AML / Wolfsberg controls + 50 cross-system SoD rules + (SAP-only) 30 SAP-GRC-parity fraud patterns.
Recommended extraction path
Use the V/ergent extractor first. It writes CSVs to a timestamped folder under C:\Vergent\Export, then you upload that folder into the audit project.
Manual path if automated extraction is blocked
Use the required-file list below as the manual checklist. Keep filenames unchanged, leave unavailable files empty with only headers, and record any missing source in the upload notes before running the audit.
The following Oracle Cloud roles are needed to complete the data extractions in this guide. A single administrator with all four access levels can complete the full extraction in one session. All operations are read-only — no configuration changes are made.
IT Security Manager
Required for Security Console access: user accounts, role assignments, role hierarchy, and data security policy exports.
Application Implementation Consultant
Required for Setup and Maintenance tasks: audit policies, approval rules, financial controls, and period status exports.
IDCS Admin Console Access
Required to export Oracle Identity Cloud Service (IDCS) settings: password policy, MFA configuration, session timeouts, and OAuth/API registrations.
OIC Administrator
Required for Oracle Integration Cloud: connection list and inbound/outbound integration configuration exports.
Oracle Fusion Cloud is a SaaS platform — some data requires Oracle involvement
Because Oracle Fusion operates as a managed SaaS environment, certain system-level data is not directly accessible through the UI or BI/OTBI reports. This includes: patch and update history (contact your Oracle Customer Success Manager or raise a Service Request on My Oracle Support), certain IDCS tenant-level settings (may require IDCS REST API access or Oracle Support assistance), and advanced AACG conflict data (requires separate Oracle Risk Management Cloud license). Where a file is optional or requires Oracle Support, this is clearly noted on the relevant card below.
V/ergent — Oracle Fusion ERP Data Extraction Guide — Generated for client distribution. Oracle, Oracle Fusion, Oracle Integration Cloud, and IDCS are trademarks of Oracle Corporation.
Native coverage: 23 ERP SoD rules + 6 HCM SoD rules covering financial postings, period close, intercompany, role governance.
Plus the three Release 5 programme packs that run alongside this platform's audit:
- AML / Wolfsberg Programme Controls — 25 controls spanning sanctions-list cadence, PEP / KYC review, CTR / SAR filing, structuring detection, transaction-monitoring tuning. Wired into all 7 ERP connectors (skips on cloud-only audits). Guide.
- Cross-System SoD — 50 multi-ERP conflict patterns spanning SAP × Oracle × D365 × NetSuite × Sage × AWS × Azure. Detects fraud paths a single-system review will never see. Guide.
- SAP Fraud Patterns — 30 SAP-GRC-parity patterns (STAD audit-log delete, debugger replace in PROD, Z* shadow SAP_ALL, dormant SAP_ALL, posting-period unlock + GL post, etc.). Guide.
Every finding carries citations across 13 frameworks (COSO 2013, COBIT 2019, NIST CSF 2.0, ISO 27001:2022, CIS v8, SOX ITGC, SOC 2 TSC, PCI DSS v4, HIPAA, DORA, NIS2, GDPR, Kenya DPA) — 11 of 13 at ≥75% mapped coverage. See the Check Packs page for per-pack framework coverage badges.