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.
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.
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.
Capabilities you use in iDataEngine
- Inbound call rules with SAP-side write validation
- Shareable service URL with automatic system fallback
- Request tracing for fast troubleshooting
- Service Detail: field set, summary, format, language
- Generate API Document after save
- Assign Users, Allowed/Block IPs, rate limits
Recommended workflow
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- 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.
- Save and capture the generated URL, job ID, or snapshot reference in your change record.
Real-world scenario (2020)
A partner polls customer credit status via REST with fieldset limiting exposure — rate limits protect SAP, trace proves SLA compliance.
Why it matters
When async mode and rate limits are configured, you scale traffic without scaling firefights.
That combination is why enterprises adopt iDataEngine as a lifecycle platform — not a one-off integration tool.