SAP / SAP Mid Level (3 to 8 yrs) Interview questions
Explain the CRUD operations supported by OData services?
OData maps standard HTTP verbs directly onto the classic CRUD (Create, Read, Update, Delete) operations against a service's exposed entities, giving a consistent, predictable interface regardless of what business object is actually behind the service.
| HTTP Verb | CRUD Operation |
| GET | Read (a single entity or a collection). |
| POST | Create a new entity. |
| PUT / PATCH | Update an existing entity (full replace vs. partial update). |
| DELETE | Delete an entity. |
POST /Z_CUSTOMER_SRV/CustomerList Content-Type: application/json { "CustomerName": "New Customer", "Country": "US" }
Whether all four operations are actually available on a given entity depends on how the underlying service (and, in RAP, its behavior definition) is configured — a read-only reporting entity, for example, might only support GET, while a fully editable business object supports the complete CRUD set.
What HTTP verb corresponds to reading data from an OData entity set?
Does every OData entity necessarily support all four CRUD operations?
More Related questions...
