OData
OData is the protocol every Fiori app uses to talk to the SAP backend. In Fiori specifically, understanding OData means knowing how apps get their data and why activating and securing these services is essential.
OData services are secured by the same backend authorizations the role grants; the service checks authorization objects as it runs.
- Each Fiori app is bound to one or more OData services that expose the backend data and operations it needs.
- A frequent setup task (and cause of errors) is activating the app’s OData service in the backend/gateway (transaction…
- OData lets apps request precisely what they need using $filter, $select, $expand, $orderby and paging ($top/$skip).
- Watch out: Inactive OData service, the classic "app not working".
OData: the Fiori data channel
Each Fiori app is bound to one or more OData services that expose the backend data and operations it needs. When the app loads or the user acts, it calls the OData service over HTTP (returning JSON), which runs the backend logic (often a CDS view) and returns the result. No OData service, no data.
Activating services
A frequent setup task (and cause of errors) is activating the app’s OData service in the backend/gateway (transaction /IWFND/MAINT_SERVICE). If the service is not active, the app shows errors or no data, one of the most common Fiori issues.
Query capabilities
OData lets apps request precisely what they need using $filter, $select, $expand, $orderby and paging ($top/$skip). Well-built apps use these to fetch minimal data, keeping performance good; poorly-built ones over-fetch.
Security
OData services are secured by the same backend authorizations the role grants; the service checks authorization objects as it runs. Frontend access and backend authorization must align for the app to work.
Common pitfalls
- Inactive OData service, the classic "app not working".
- Over-fetching data instead of using query options.
- Missing backend authorization for the service.