Use cases.
One problem, the checks we ran and what they found. Most come from our own project work with the client names removed; the rest are illustrative scenarios, and each one is marked.
Use cases
5 results for “SAP”. Show everything
A building-materials maker runs 64 exception checks on its full SAP data
Reviewing purchases, payments, assets and sales by sample left gaps. We moved the company's SAP data into one database and built a library of 64 checks that run on every record.
A consumer-goods company puts six applications under one control framework
Six business applications around SAP were each governed on their own. One matrix of 91 controls and 103 segregation-of-duties rules, tested against real user data, showed what to fix first.
Segregation of duties where one application feeds SAP
A distributor system and a cloud procurement platform both feed SAP, and neither had a segregation-of-duties rule set. We defined 293 functions, found 41 conflicts and rated each by whether one person alone could cause a loss.
An engineering manufacturer's SAP audit, built from raw tables
An engineering manufacturer wanted its SAP configuration, access and transactions audited together. Rule-based analytics on raw table extracts found over-privileged accounts and segregation-of-duties conflicts.
Open orders and real customers, checked every month
An electronics maker could not easily see which purchase orders were still open, or whether every customer in its master was a real company. A monthly Python run on its SAP data now answers both.
No use cases match every filter.
Read the thinking behind it
Short articles on revenue leakage, fraud, controls, forecasting and private AI.