Configuration Change vs Code Rewrite — Checklist addresses a problem most SAP landscapes know too well: Custom code TCO grows until configuration replaces plumbing for standard paths.
Reusable pipelines (clone SQL project, republish API with new fieldset) cut TCO; Activate and Save are change events, not full redevelopment.
Low-code in iDataEngine means configuration in cockpits — iDataView design, API Service Detail, SQL project mapping — replacing weeks of custom ABAP and middleware for standard extract-and-deliver scenarios.
Capabilities you use in iDataEngine
- SQL project mapping UI
- Configuration vs ABAP rewrite
- Clone and republish patterns
- Activate not redeploy
- iDataView drag-and-drop design
- Template libraries
Recommended workflow
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Enable monitoring alerts and review dashboard KPIs for the first production cycle.
Real-world scenario (2020)
A power user clones last month's SQL project for a new sales org — mapping adjusted in an hour, not a project charter.
Why it matters
Reusable pipelines mean the tenth integration costs a fraction of the first — economies of scale internal IT rarely achieves with custom code.
Your next step is a controlled pilot: Test in cockpit, save with evidence, then extend to the next channel without redesign.