Turn a RAP model into a service contract
The BO’s data and behavior are not automatically a published API. A service definition selects what to expose; a service binding connects that definition to a protocol and publishes it.
Expose a projection
define service ZUI_PURCHASE_REQUEST {
expose ZC_PURCHASE_REQUEST as Request;
}
ZC_PURCHASE_REQUEST is an illustrative projection entity. A service binding is a separate repository artifact created in ADT; its protocol and usage determine whether the consumer is, for example, an OData UI service or a Web API. Publish the binding in the target system to make the service available.
The definition does not deploy to Cloudflare or create an external endpoint by itself. Authorization, communication setup, service publication, and client configuration are system tasks outside this static example. Verify the supported protocol and binding options for your ABAP environment.
Sources
- SAP Samples: RAP service definition and binding layers
- SAP Help: Create an OData UI service from scratch
Developer practice · ABAP
Practice: map service artifacts to their responsibilities
Write a service definition that exposes the fictional request projection as Request.
Complete the task using the syntax and structure described above. Variable names can differ if you use them consistently. This browser checker checks structure only; it does not compile or run ABAP.
0 required structures detected · 0 checks
Write your solution, then check its structure.
One possible solution
define service ZUI_PURCHASE_REQUEST {
expose ZC_PURCHASE_REQUEST as Request;
}