OData Navigation Properties and Referential Constraints
The provided sources do not contain sufficient information to define a specific SAP developer concept, as the concept name is listed as "undefined" and the source snippets cover a broad range of unrelated topics — including OData V2 Mock Server features, custom mock data, Quick Views, and list area configuration — without converging on a single definable concept. A meaningful, source-grounded definition cannot be written without a valid concept name and relevant supporting material.
Tutorials that teach this
Docs explaining this concept
Prerequisites
- Concept OData Entity Relationships and Associations An **EntitySet with Input Parameters** is an OData construct that allows developers to configure an entity set to accept input parameters when querying data. In SAP development, a developer uses it to pass specific values that filter or shape the data returned by the OData service at the entity set level. This is configured as part of an OData service definition, as described in [Configuring an EntitySet with Input Parameters](https://ui5.sap.com/#/topic/b40e5ae5cdd647c490bd03b9d5f98d56).
- Concept OData EntityType and Property Definitions An **OData metadata document** is a machine-readable description of an OData service's data model, which developers use to understand the structure, entity types, properties, and relationships exposed by that service. Developers read the metadata document to learn how to correctly construct queries and interpret responses when consuming an OData API.
- Concept OData Entity Set Configuration OData Entity Set Configuration refers to the use of OData metadata associated with a specific entity set to drive the behavior and structure of UI5 controls and server resource access. For example, the [`SmartFilterBar`](https://ui5.sap.com/#/topic/594f1111efd54bc8baef87ef4dcb2a75) control uses the OData metadata of an entity set to automatically generate filter fields and their properties. Similarly, the [request object](https://ui5.sap.com/#/topic/33da7d53b5c19456e10000000a423f68) uses entity set configuration to define how a client accesses a server resource. Developers rely on this configuration to bind UI components and data requests to the correct OData service structure without manually specifying each field.