Configuration Change vs Code Rewrite addresses a problem most SAP landscapes know too well: Custom code TCO grows until configuration replaces plumbing for standard paths.
Power users deliver; specialists handle edge BAPIs and custom UX — the split enterprises actually need.
Reusable pipelines (clone SQL project, republish API with new fieldset) cut TCO; Activate and Save are change events, not full redevelopment.
Capabilities you use in iDataEngine
- 15-minute first API path
- Configuration vs ABAP rewrite
- Power user ownership
- TCO reduction narrative
- API without middleware code
- SQL project mapping UI
Recommended workflow
- Save and capture the generated URL, job ID, or snapshot reference in your change record.
- 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.
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
Real-world scenario (2022)
First API shipped before lunch because REP Test already proved the dataset — developers wire UI in the afternoon.
Why it matters
Activate-not-redevelop changes how business requests data — from 'project' to 'ticket'.
Your next step is a controlled pilot: Test in cockpit, save with evidence, then extend to the next channel without redesign.