FICTIONAL SAP BACKGROUND-JOB EXAMPLE

This is an illustrative sample, not a client engagement or live-system result.
The source has seven fictional executions in system EX1, client 100.
Snapshot and report generation time: 2026-09-08T12:00:00Z.
Start-delay threshold: 60 minutes or more. Active-runtime review threshold: 120 minutes or more.
Explicit hosted launch limits used to generate this fixture: maxRows=100,
maxFileBytes=32768 UTF-8 bytes, maxCellCharacters=256, maxDependencies=10.
These are DEFAULT_LAUNCH_LIMITS from worker/limits.ts, passed as the third
generateReport argument; they are not the report engine's larger fallback limits.

source.csv: normalized fictional input.
input.json: exact report-engine input and options.
result.json: full output from Kinevra's current deterministic job-review engine.
findings.csv: the same report rows as an escaped CSV.

The engine generated these files without an AI call or live SAP connection.
No actual root cause, business impact, successful recovery, approval or customer outcome is asserted.
To reproduce in the report preview, choose SAP background job review, use source.csv, and set the same snapshot time and thresholds. The preview shows up to five report rows; this public fictional example includes all seven.

The column names and lowercase statuses are Kinevra normalized input format, not an untouched native SM37 export. Map an authorized export to this template and convert captured times explicitly to UTC. Z_* job names and all execution identifiers here are invented; no delivered SAP program or actual customer process is implied.

Reference: SAP, Possible Status of Background Jobs, ABAP Platform 2025 FPS01 (February 2026).
https://help.sap.com/docs/ABAP_PLATFORM_NEW/b07e7195f03f438b8e7ed273099d74f3/4b308aa91dd90a93e10000000a421937.html
Checked September 9, 2026.