Canceled job recorded1
The snapshot records an abnormally ended or administratively canceled job. Inspect its job log and dependent business process; cancellation alone does not identify the cause.
FICTIONAL SAP OPERATIONS EXAMPLE
From a job snapshot to a review queue.
See exactly what Kinevra flags, where the evidence comes from, and what a responsible operator should investigate next.
For SAP Basis and operations teams, and consultants reviewing authorized job exports. Seven invented executions. Real deterministic checks. No client results or production experience are implied.
THE FIXED SNAPSHOT
One file. Every execution accounted for.
Snapshot: September 8, 2026 at 12:00 UTC. Start-delay review: 60 minutes or more. Active-runtime review: 120 minutes or more.
- Source records
- 7
- Critical review
- 1
- Review
- 3
- No rule exception
- 3
Normalized Kinevra input
This CSV uses Kinevra’s documented columns, lowercase status names and explicit UTC timestamps. It is not an untouched SM37 export. Map an authorized export to this format before running the check.
EX1, client 100, the Z_ job names and all executions are fictional. Blank cells mean evidence was not supplied. CSV record 1 is the header; data records are 2–8.
SOURCE → FINDING → REVIEW
Choose an execution. Follow the evidence.
The finding and calculated values below come from the downloadable engine result. Investigation steps are suggestions, kept separate from the result.
SOURCE RECORD 2
Z_ORDER_SYNC
Exact values from the fictional source file
systemEX1client100job_nameZ_ORDER_SYNCjob_count00000001statuscanceledscheduled_start2026-09-08T09:00:00Zactual_start2026-09-08T09:00:00Zend_time2026-09-08T09:08:00Z
ACTUAL RULE RESULT
Canceled job recorded
The snapshot records an abnormally ended or administratively canceled job. Inspect its job log and dependent business process; cancellation alone does not identify the cause.
Why this row received that result: The supplied status is canceled. The critical-review label is a Kinevra rule priority, not a measured business impact.
- Calculated start delay
- 0.00 minutes
- Calculated runtime
- 8.00 minutes
SUGGESTED INVESTIGATION
Open the job log and spool for this exact job name and count in SM37. Confirm the affected business process with its owner before deciding on recovery.
What remains unknown: A canceled status does not tell us whether the cause was a program error, an administrative action, or something else.
TAKE THE EVIDENCE WITH YOU
Download the input and the actual output.
These static example files are free to inspect without an account. No AI generation or hosted report is triggered by opening this page.
Read the full generated report · all 7 rows
7Source records
7Report rows
1Critical review
3Review
3No rule exception
1Canceled jobs
1Overdue starts
1Long-running active jobs
Report findings
7 report rowsTime-based start is overdue1
The job has no supplied actual start and the delay from the recorded scheduled time meets or exceeds the selected threshold. Investigate queue resources and start conditions.
Active runtime threshold reached1
The recorded active job runtime meets or exceeds the selected review threshold. Check SM37 logs and work-process evidence before intervening.
Job state and timestamps conflict1
The supplied timestamps do not fit the recorded job state, or required runtime evidence is missing. Verify one execution in SM37 before relying on duration or delay.
No time-based start evidence1
No scheduled timestamp was supplied. The job may use an event or dependency; no start-delay conclusion was made.
Technical table headings, source values, and downloaded files retain their original identifiers and language.
| Review priority | Source record | System | Client | Job name | Job count | Status | Scheduled start (UTC) | Actual start (UTC) | End time (UTC) | Start delay (minutes) | Runtime (minutes) | Review notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Critical review | 2 | EX1 | 100 | Z_ORDER_SYNC | 00000001 | canceled | 2026-09-08T09:00:00Z | 2026-09-08T09:00:00Z | 2026-09-08T09:08:00Z | 0.00 | 8.00 | The snapshot records an abnormally ended or administratively canceled job. Inspect its job log and dependent business process; cancellation alone does not identify the cause. |
| Review | 3 | EX1 | 100 | Z_WAREHOUSE_EXPORT | 00000002 | ready | 2026-09-08T10:00:00Z | — | — | 120.00 | — | The job has no supplied actual start and the delay from the recorded scheduled time meets or exceeds the selected threshold. Investigate queue resources and start conditions. |
| Review | 4 | EX1 | 100 | Z_BILLING_PREP | 00000003 | active | 2026-09-08T08:00:00Z | 2026-09-08T08:00:00Z | — | 0.00 | 240.00 | The recorded active job runtime meets or exceeds the selected review threshold. Check SM37 logs and work-process evidence before intervening. |
| Review | 8 | EX1 | 100 | Z_LOG_CONFLICT | 00000007 | finished | 2026-09-08T10:00:00Z | — | 2026-09-08T11:00:00Z | — | — | The supplied timestamps do not fit the recorded job state, or required runtime evidence is missing. Verify one execution in SM37 before relying on duration or delay. |
| No rule exception | 5 | EX1 | 100 | Z_EVENT_HANDOFF | 00000004 | released | — | — | — | — | — | No scheduled timestamp was supplied. The job may use an event or dependency; no start-delay conclusion was made. |
| No rule exception | 6 | EX1 | 100 | Z_NEXT_CYCLE | 00000005 | planned | — | — | — | — | — | No exception identified by the implemented rules. |
| No rule exception | 7 | EX1 | 100 | Z_COMPLETED | 00000006 | finished | 2026-09-08T11:00:00Z | 2026-09-08T11:02:00Z | 2026-09-08T11:15:00Z | 2.00 | 13.00 | No exception identified by the implemented rules. |
NEXT STEPS
From findings to follow-through.
- Investigate canceled jobs using the job log, spool, and business-process owner.
- Check queued and long-running jobs against resource availability and their actual start conditions.
- Resolve timestamp and duplicate-identity issues before comparing this snapshot with later exports.
REPORT SCOPE
What this report can tell you.
- Map your export to this documented CSV template first. Raw SAP exports are not automatically recognized. Reports are review evidence, not import files or certification.
- One row per system/client/job_name/job_count. Use planned (or scheduled), released, ready, active, finished, canceled (or cancelled). Raw status letters must be mapped first.
- Timestamps must be UTC YYYY-MM-DDTHH:mm:ssZ. Leave unavailable times blank. Delays are evaluated only for supplied time-based start conditions.
- Finished means the recorded steps completed, not that the business result is correct. Event dependencies, expected job occurrences, job logs, and business impact are not evaluated.
- Record numbers refer to CSV records, including the header, not physical lines.
- Age calculations use snapshot time 2026-09-08T12:00:00.000Z. Planned jobs have not necessarily been released and are not labeled overdue; event-only jobs have no inferred schedule.
- Active limits: 32 KiB UTF-8 per file, 100 source records per file, 50 columns, 256 characters per cell, 10 transport dependencies per row, and 4 MB for the generated report.
REPRODUCE THE CHECK
Same input. Same settings. Inspectable results.
Download the source CSV and open the job review. Set the snapshot to September 8, 2026 at 12:00 UTC, the start-delay threshold to 60 minutes and the active-runtime threshold to 120 minutes. The hosted free preview displays up to five rows; the example above includes all seven.
Using your own data requires authorization under your organization’s policies. The hosted job review uploads its input to Kinevra; this example page uses only the supplied fictional fixture.
Open the job review