OData service
The REST-based protocol of SAP Fiori apps and many SAP APIs: entity sets, keys, properties and navigation properties described in a metadata document (EDMX).
An OData service exposes entity types with keys and properties, entity sets and navigation properties. Its metadata document is the contract consumers rely on: removing or renaming any of these, changing a key or a type, or adding a new required property breaks existing consumers.
Fiori apps call OData services through SAP Gateway. A service must be registered and active, and the user needs the authorization to start it (authorization object S_SERVICE).
In ERP Preflight
API Change Guard compares two versions of an OData (EDMX) or OpenAPI specification and classifies every difference as breaking or not; Fiori 403 Root-Cause Doctor detects services that are not registered or have no system alias.
Problems that involve OData service
- MajorUnreleased BAPI / RFC interface
- CriticalOData entity set removed
- CriticalOData entity key changed
- MajorOData navigation property removed
- CriticalGateway service not registered / no system alias
- MajorSystem-specific endpoint URLs overwritten by the copy
- CriticalScheduled integrations depend on the target
- CriticalEndpoint removed
Related terms
Free tools
- API deprecation lookup
Released and deprecated APIs per release, their successors and a diff between two releases.
- Fiori 403 decision tree
Guided questions to the likely cause category of a Fiori “not authorized” error — and what evidence to collect.
Background articles
- Troubleshooting HTTP 403 Forbidden in SAP Fiori appsThe usual causes of a 403 error when a Fiori app loads or calls its OData service — missing service authorizations, incomplete roles, inactive ICF services — and a systematic way to find the one that applies.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.