Now we want to expose the newly developed data model to OData as a canonical OData service using the so-called auto exposure approach. In this step, you will use the CDS tools as part of the ABAP development environment to generate all artifacts that are required for service activation in the SAP Gateway hub.
The following rules need to be fulfilled for a CDS view:
ABAP Development Tools delegates the activation request to the SADL (Service Adaptation Description Language) framework. SADL, in turn, generates several Gateway artifacts that are stored in the back end of the application server AS ABAP and are required for OData service activation in the SAP Gateway hub later on:
All generated service artifacts are automatically added to the same ABAP package (and also to the same transport request) as the underlying CDS view.
The decorator within the editor ruler indicates a successful generation process. If you move the cursor over the decorator, an info screen informs you that the service must be activated in the Gateway hub for exposure. This will be done in a separate step using the transaction /IWFND/MAINT_SERVICE.More on this: Activate OData Service in the SAP Gateway Hub