sapaudit collects what your SAP systems already record, turns it into one consistent trail, and puts search, reporting, alerting and Sage AI on top.
These are the transactions and tables an SAP audit normally works through by hand.
Logons, started transactions and reports, and security events.
Users, roles, profiles and who holds critical authorizations.
Changes to financial documents and to material, customer and vendor master data.
The standard change reports auditors request for master data.
Authorization checks, RFC calls, database operations and kernel traces.
Changes to documents and master data in SAP Business One.
SAP describes events in the vocabulary of each transaction and table. sapaudit describes them the way people ask about them.
With the user type and the person or service behind it.
Stated in plain terms, with the value before and after.
In one time zone across all systems.
Which SAP system was acted on and where the action came from.
One search over all connected systems and clients. Follow a user from the logon to the transaction to the record they changed.
Save any search as a report, schedule it, and send it to the people who must review it.
Define the events that need attention now, with thresholds for activity that is only a problem in bulk.
A standing list of critical authorizations, risky role combinations and dormant privileged users.
Per-user and per-system baselines surface behaviour no fixed rule would describe.
Give process and data owners their own view, so the people who know the context confirm what is normal.
Runs on your own servers. Audit data and Sage AI inference stay inside your network.
Works with SAP S/4HANA, SAP ECC, SAP S/4HANA Cloud, RISE with SAP, SAP Business One and SAP BTP.
Retention is set per system to match your policy. Older records move to a compressed archive and stay searchable.
Tell us which SAP systems you answer for. We will show what their trail looks like.
Request a demo