Semantic Objects and Launchpad Tiles addresses a problem most SAP landscapes know too well: Launchpad tiles that open wrong data destroy trust in UX modernization.
Fiori Integration starts with one click — Export to Fiori from iDataView — then a documented checklist walks you through catalog, tile, and target mapping in SAP's own Launchpad Designer, plus the matching role assignment.
Fiori Integration starts with one click — Export to Fiori from iDataView — then a documented checklist walks you through catalog, tile, and target mapping in SAP's own Launchpad Designer, plus the matching role assignment.
Capabilities you use in iDataEngine
- One stable OData path for every export
- User default parameters carried through transport
- Built-in Launchpad verification step
- Tile and target mapping generated automatically
- Export to Fiori from Operations menu
- Pre-built tile group layout
Recommended workflow
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
Real-world scenario (2021)
Warehouse team opens a Launchpad tile tied to the report they already tested — same fields they approved in ALV Test, no surprise columns.
Why it matters
Tiles without target mapping are decoration; iDataEngine documents both because operations need apps that open, not icons that shimmer.
Innovation here means business sees results faster — IT keeps control because every step is configured, tested, and monitored.