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
- MSSQL and PostgreSQL dual-engine parity
- Connection test from the maintenance screen
- Key-field matching for update-or-insert loads
- Package size and parallel processing
- SQL Job Monitor with cron schedules
- First Row Test and Package Error Data popup
Recommended workflow
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
- 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.
- Save and capture the generated URL, job ID, or snapshot reference in your change record.
Real-world scenario (2023)
A delta-L job refreshes only the last 30 days of billing documents — full history preserved, nightly window stays inside SLA.
Why it matters
Delta methods save SAP and SQL load; upsert keeps master data current without full-table deletes that frighten operations.
That combination is why enterprises adopt iDataEngine as a lifecycle platform — not a one-off integration tool.