Exposing SAP data as REST is easy until the payload is a function module with nested tables, a report with summary rows, or a structure that contains another structure. Flat JSON samples break integrators; hand-written ABAP wrappers take weeks.
The API Cockpit in iDataEngine is built for SAP's real, nested data shapes — not simplified mocks. Services can be created from tables, transaction codes, programs, iDataViews, and function modules. The Deep API creator and dynamic body builder let you shape nested request and response structures visually, without maintaining custom middleware.
How nested structures are handled
- Automatic type recognition — every field's real SAP type (structure, table, text, number, date) is detected and mapped correctly, so integrators never have to guess how to parse a value
- Configurable depth limits — prevent runaway recursion when integrators send cyclic or oversized payloads
- Output formats — plain JSON or XML from the same service definition, chosen per consumer
- Field selection sets — limit which columns appear in large responses without redeploying anything on the SAP side
On the Service Detail screen you set fixed filters, selection-screen variants, ALV variants, summary mode, and language. After save, the system generates a stable, shareable API URL. Test Service runs against the real environment with record limits and duration metrics — so nested structures are validated before partners integrate.
Incoming and outgoing in one cockpit
Outbound services publish SAP data. The incoming (WSC) path accepts REST/SOAP, applies rules, and can write back into SAP — useful when external events must land in custom Z/Y tables. Trace and correlation IDs tie a failed nested field to the exact call in Api Monitor.
Why it matters
Integration projects stall when the first real payload exposes a table-inside-structure the proof-of-concept never had. iDataEngine turns SAP's nested data into governed API contracts: testable, monitorable, and reusable across SQL Transfer, TSAP write-back, and BI Portal. You ship complex interfaces in days because the platform already understands SAP's data shapes — your team configures, it does not re-implement.