Deep and Nested API Structures Without Pain addresses a problem most SAP landscapes know too well: Integrators need stable JSON; SAP teams need auth and trace — both or neither.
The API Cockpit turns SAP tables, transactions, programs, reports, and function modules into JSON or XML services — with field selection, fixed filters, and a ready-to-share URL for every service.
Partners can call in through incoming services, or iDataEngine can call out to external systems — both tracked in one monitor so a failure is traced in minutes, not days.
Capabilities you use in iDataEngine
- Fixed filters and URL extensions
- Inbound call rules with SAP-side write validation
- Service Detail: field set, summary, format, language
- Generate API Document after save
- Test Service with record count and duration
- Request tracing for fast troubleshooting
Recommended workflow
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- 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.
- Enable monitoring alerts and review dashboard KPIs for the first production cycle.
Real-world scenario (2021)
An iDataView built for operations is converted to API the same afternoon the mobile app team asks for JSON — no separate middleware sprint.
Why it matters
Partners integrate once against a tested JSON contract — not against a consultant's temporary RFC. That shortens revenue-bearing integrations and cuts production incidents from schema surprises.
Your next step is a controlled pilot: Test in cockpit, save with evidence, then extend to the next channel without redesign.