SAP ECC support that shows its work.

Trace reads every ticket against the evidence in SAP, fixes the ones it has proven it can fix, and hands the rest to a senior engineer with the work already done.

Test it on your tickets See how it works
  • 95%right answers before a task may run alone
  • 30graded answers per task, on your own history
  • 0unsafe actions allowed in that test
  • 30 daysclean in production before full autonomy

One ticket, from the first line to the audit trail. Here is what Trace does with a stuck order, step by step.

1

It reads the ticket like an engineer would.

Not the title. The partner, the document number and the state the reporter mentions, pulled out and checked against SAP.

2

It opens the same SAP screen your team would.

Trace works through standard transactions under its own SAP user. Here it lists Orvik’s IDocs and finds the one that never went through.

3

It checks the fix is safe before anything runs.

Four questions, every time. One wrong answer and the fix waits for a person.

4

It fixes it, or asks you first.

A task that has earned it runs on its own. Everything else lands with your team as a prepared fix: approve it in one click, or hand it to an engineer.

5

It proves the problem is gone, and writes it down.

Every fix ends with a check in SAP. Every step goes into an audit trail where each line seals the one before it.

Screens are illustrative. Times and numbers are an example.

Three answers for every ticket, before anyone opens it. What is wrong, whether Trace can fix it, and who should.

Sorted by evidence, not by title

Status codes, job logs and lock entries decide where a ticket goes.

Fixes alone4

Orders from Orvik not in SAPWE02 IDoc waiting
User MKUMAR locked outSU01 Too many tries
Invoice output not sentNACE Output stuck
Material locked by a closed sessionSM12 Stale lock

Asks you first3

Billing job cancelled againBatch jobSU53 Missing permission
Can’t post to SeptemberOB52 Period closed
Change a supplier’s bank detailsXK02 Moves money

Goes to an engineer2

Dump in ZSD_ORDER_UPLOADST22 Custom code
Sales report shows wrong totalsZSD_REP01 Custom report

Sent with the dump, the last change and a first guess at the cause.

Ten reports, one problem

When one interface breaks, ten people write in. Trace sees it once.

“Orvik orders missing”Sales, Pune“No EDI orders today?”Customer service“Order from Orvik not created”Plant 2000
INC0048213One incident10 reporters, all told when it’s fixed

One question instead of a guess

When a ticket is too thin to act on, Trace asks the one thing it needs.

SAP is very slow again.

TraceWhich transaction is slow, and since when? The text at the bottom of the screen helps too.

VA01, since about 9. It says “waiting for lock”.

TraceFound it in SM12: a lock left by a closed session. Clearing it is safe.

It stops before anything risky. It reads the log, not just the error.

Two cancelled jobs, two different answers

SM37 Job ZSD_DELIV_DUE cancelled

Lock on LIKP held by a session that has ended.Nothing was written.

RestartedSafe to repeat. Checked in SM37: finished.

SM37 Job ZFI_PAYRUN cancelled

Cancelled at step 3 of 5.142 payments already created.

Stopped before it ranA restart could pay suppliers twice. Handed to a person with the log.

Never runs alone

These always wait for a person, however good Trace’s record is.

  • Payment runs
  • Anything that moves money
  • Authorizations and roles
  • Opening or closing posting periods
  • Any fix that can’t be undone

Trust is earned one task at a time. A task works alone only after it proves itself on your own history.

Autonomy by task

Example
TaskGradedRight answers bar is 95%UnsafeStatus
Unlock a userSU0130 of 30100%0Works alone
Restart a failed jobSM3730 of 3087%0Asks you first
Reprocess a stuck IDocBD8730 of 3097%0Works alone
Resend a missing outputNACE18 of 3094%0Still being graded
Add a missing permissionPFCG–Never measured: a person always decides–Always asks
  1. A person approvesevery fix at first
  2. 30 answers gradedon your closed tickets
  3. 95% right, none unsafeand the fix can be undone
  4. 30 clean daysin production
  5. Works aloneswitch it back off any time

Every decision comes with its reasons. And a record no one can quietly edit.

The decision record

“Job cancelled again. Log says the step user lacks access to plant 2000 since the role cleanup.”

First readingA failed batch job

Corrected toA missing permission

  • SM37The job stops at the same step each night
  • SU53The check for plant 2000 fails for user BATCH_SD
  • SUIMThe role lost that plant on 2 October
Who actsA person approves. Permissions always do.

An audit trail that can’t be rewritten

Each line carries a seal made from the line before it. Change one and every seal after it breaks.

  1. Trace read INC00482139f2a…
  2. Trace found IDoc 41122233 in status 64c71e…
  3. Trace passed the safety check3b88…
  4. Trace reprocessed it with BD8704bd…
  5. Trace checked WE02: status 53e5a0…

Works with what you already run. Nothing is installed on your SAP system.

Today: a Replay reads a CSV export of closed tickets. The live connections below are being built with design partners. See what is available and what is planned.

Where tickets come from

  • CSV exportAvailable today
  • ServiceNowWith design partners
  • Jira Service ManagementWith design partners
  • SAP Solution ManagerWith design partners
  • EmailWith design partners
TraceReads, checks, fixes, records

Your change board approves changesYour data stays in your environment

SAP ECC 6.0

Its own SAP userOnly the permissions its earned tasks need
SM37WE02BD87SU53SM12ST22SU01NACE

Nothing installed on the SAP system

Questions about Trace

How does a task earn the right to run alone?

At least 30 graded answers on your own closed tickets, 95% of them right, none unsafe, and a fix that can be undone. Then 30 clean days in production.

Which tasks never run alone?

Payment runs, anything that moves money, authorizations and roles, posting periods, and any fix that can’t be undone. They always wait for a person.

What happens when the AI and the rules disagree?

The ticket goes to a person with both readings shown. Trace never acts alone on a ticket where they disagree.

Is anything installed on our SAP system?

No. Trace works through standard transactions under its own SAP user, with only the permissions its earned tasks need.

See Trace on your own tickets.

A free Replay runs Trace blind across 1,000 of your closed tickets. You see exactly what it would have done before you change anything.