From iDataView to SQL Warehouse addresses a problem most SAP landscapes know too well: Stale warehouses and failed night jobs undermine dashboards the C-suite already promoted.
Millions of rows leave SAP nightly through the same engine you test with First Row Test — no separate ETL product to license and wire up.
The SQL Project Cockpit defines source objects, target tables, field mapping, delta parameters, and schedules — monitored in SQL Job Monitor with package-level error detail.
Capabilities you use in iDataEngine
- Methods I, A, U, D, L with delta parameters
- MSSQL and PostgreSQL dual-engine parity
- Delta days configuration (L method)
- First Row Test and Package Error Data popup
- Connection test from the maintenance screen
- Project clone and monitoring KPIs
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.
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
- Enable monitoring alerts and review dashboard KPIs for the first production cycle.
Real-world scenario (2024)
A delta-L job refreshes only the last 30 days of billing documents — full history preserved, nightly window stays inside SLA.
Why it matters
Dual-engine parity means you are not locked to one DBA religion — architecture stays portable while jobs stay monitored the same way.
Measured on lead time, defect rate, and audit readiness, the platform pays back in the first production quarter.