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.
Every service lets you choose the output format, toggle summary mode, reuse saved selection variants, and test against the live environment before handing the URL to a partner.
Capabilities you use in iDataEngine
- Convert iDataView to API in one click
- Inbound call rules with SAP-side write validation
- Generate API Document after save
- Request tracing for fast troubleshooting
- Service Detail: field set, summary, format, language
- Fixed filters and URL extensions
Recommended workflow
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
- 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.
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
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
Publishing SAP data as governed APIs frees digital channels from SAP GUI licenses while keeping auth and trace under IT control.
Measured on lead time, defect rate, and audit readiness, the platform pays back in the first production quarter.