Dashboards That Reflect Real Health addresses a problem most SAP landscapes know too well: Black-box jobs turn small mapping errors into morning executive escalations.
Monitoring unifies SQL Job Monitor, Api Monitor, job cockpit statuses, event logs, trace export, and dashboard 7-day charts — one place to answer 'where is my data?'
Monitoring unifies SQL Job Monitor, Api Monitor, job cockpit statuses, event logs, trace export, and dashboard 7-day charts — one place to answer 'where is my data?'
Capabilities you use in iDataEngine
- SLA breach notifications
- Job cancel and retry
- Error drill-down by package ID
- SQL Job Monitor statuses
- Api Monitor latency and errors
- Heat-map last 24 hours
Recommended workflow
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
- Enable monitoring alerts and review dashboard KPIs for the first production cycle.
Real-world scenario (2018)
Operator sees package 47 fail in SQL Job Monitor, drills error text, reruns after fixing mapping — users never knew.
Why it matters
When SQL and API health share one dashboard, leadership sees truth instead of three conflicting green lights.
That combination is why enterprises adopt iDataEngine as a lifecycle platform — not a one-off integration tool.