RAP_CDS_ODATAintermediate
Service Bindings
Understand RAP service bindings as the runtime exposure layer that binds a service definition to OData or another supported protocol. Learn activation, publish/test flow, metadata validation, preview, authorization and deployment considerations.
Overview
Understand RAP service bindings as the runtime exposure layer that binds a service definition to OData or another supported protocol. Learn activation, publish/test flow, metadata validation, preview, authorization and deployment considerations.
Lessons in this topic
- Service Bindings Part 1: From Business Object to OData ServiceUnderstand where a service binding fits in RAP: projection views, service definition and service binding, what each one decides, the binding types available, and how the binding turns your business object into a callable OData endpoint.
- Service Bindings Part 2: Create, Activate, Publish and Test in ADTWalk through the full hands-on flow: create and activate the binding, publish the local service endpoint, check it in the Gateway administration, and test $metadata, reads and a create — in on-premise S/4HANA and in the ABAP cloud environment.
- Service Bindings Part 3: Moving Bindings Through DEV, QAS and PRDLearn what is and is not transported with a service binding, the post-import steps needed in QAS and PRD, how access is granted on-premise and in the cloud, and a checklist that makes every deployment repeatable.
- Service Bindings Part 4: UI vs Web API, OData V4 vs V2Choose the right binding for each consumer: what really differs between UI and Web API bindings, when OData V2 is still justified, and how to build a separate non-draft API service on the same business object.
- Service Bindings Part 5: Troubleshooting 404, 403, Metadata and CacheDiagnose RAP service problems systematically: read the HTTP status first, then go to the right layer — publication, authorization, metadata, business logic or cache — using the right transaction for each.
- Service Bindings Part 6: Preview, $metadata and Fiori Elements AnnotationsTurn the published service into a real Fiori Elements app: add UI annotations in metadata extensions, verify them in the binding preview, read $metadata to see exactly what the UI receives, and generate and deploy the app.
Interview questions covered
- What is the difference between a service definition and a service binding in RAP? Can one service definition have several bindings?
- Your RAP list report works in preview, but the object page shows no Items section and adding an item fails. The behavior definition supports items. What is the most likely cause?
- You activated a new service binding and sent the URL to the UI developer, who gets HTTP 404. What is the difference between activating and publishing a binding, and how do you fix it?
- How do you test a newly published RAP OData V4 service end to end before handing it to the UI team?
- A RAP service works in DEV. After transport, QAS users get 404 and some get 403. What do you check, in which order?
- What belongs in the transport of a RAP app, what must be done per system, and how is user access granted on-premise vs in the ABAP cloud environment?
- An integration team wants to use your Fiori UI service for system-to-system approvals. Would you let them? What is the difference between an OData V4 UI and Web API binding?
- When is OData V2 still justified for a RAP service, and how do you introduce a breaking change to a published Web API?
- A Fiori RAP app fails for some users. Describe a systematic troubleshooting approach based on HTTP status codes.
- You changed a UI annotation in a metadata extension and activated it, but the Fiori app still looks the same. What do you do?
- The Approve action works in EML tests, but the button does not appear in the Fiori Elements app. How do you analyze it, and what controls whether the button is enabled?
- How do you use the service binding preview and $metadata to validate a RAP UI service?