Consuming External APIs into Your Landscape 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
- Service Detail: field set, summary, format, language
- Generate API Document after save
- Assign Users, Allowed/Block IPs, rate limits
- Fixed filters and URL extensions
- Shareable service URL with automatic system fallback
- Convert iDataView to API in one click
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.
- Enable monitoring alerts and review dashboard KPIs for the first production cycle.
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
Real-world scenario (2024)
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.
Your next step is a controlled pilot: Test in cockpit, save with evidence, then extend to the next channel without redesign.