sapaudit
CHANGE · CDHDR · CDPOS · S_ALR_87012293

What changed in the business data, with the value before and after.

SAP writes a change document whenever master data or a financial document is modified. sapaudit reads those records and presents them as one audit trail: who changed what, when, from which value to which value.

CDHDRCDPOSS_ALR_87012293Financial documentsMaterial masterCustomer and vendor master
WHAT IS RECORDED

The full trail, in plain terms.

Financial documents

Changes to posted documents: the field, the old value, the new value, the user and the time.

Vendor and customer master

Bank details, payment terms, addresses and blocks, as they are created, changed or removed.

Material master

Changes to the material data that drive valuation, purchasing and stock.

One trail

Header and item records joined into a single line a reviewer can read without knowing the tables.

QUESTIONS IT ANSWERS

Ask it the way an auditor would.

Search the trail in ordinary terms and keep the searches you repeat as reports.

Who changed the bank account on this vendor, and what was it before?
Which posted documents were changed after period close?
Which master records did this user change in the last 30 days?
Were any payment blocks removed this week, and by whom?
SAGE AI

And the things nobody thought to ask.

Sage AI learns the normal pattern for each user and system here, and raises what falls outside it.

Bank details changed, then changed backSAGE AI

A vendor bank account is modified shortly before a payment run and restored shortly after it.

Master data changed by an unusual userSAGE AI

A record is edited by someone outside the team that normally maintains it.

A burst of changesSAGE AI

Many times more records changed in an hour than this user changes in a normal week.

See the change trail behind your own master data.

A short evaluation shows what your trail looks like within the first day.

Request a demo