The new programming model in SAP Cloud Platform ABAP Environment currently only supports publishing OData V2 services. But since the implementation of the service binding is protocol-agnostic, existing service binding implementations can later be published as OData V4 services once OData V4 service binding options are available.
OData V4 Back-End Service Administration
With OData V4, the new service group concept will be introduced with SAP Gateway.
You no longer publish single services on the SAP Gateway hub, but rather service groups.
Thus, OData V4 services have to first be assigned to a service group, which is then published on the SAP Gateway hub.
The reason behind this new concept is the cross-service navigation feature that is supported with OData V4 that is used to minimize the size of metadata documents.
Cross service navigation is only possible between services that have been assigned to one service group.
To make the lives of developers easier, for development systems it is possible to publish an “Über-Service Group” called /IWBEP/ALL.
All services that have been registered in a back-end system are automatically assigned to this service group and can be consumed on an SAP Gateway development hub immediately.
Please note that the service URL depends on the service group to which a service has been assigned.
Assign related services (e.g., zdev904_cds_customer_yxx) to service group ZDEV904_YXX:
/sap/opu/odata4/sap/zdev904_YXX/sadl/sap/zdev904_cds_customer_yxx/0001/$metadata
SAP Gateway Service Administration
Service groups have to be published on the SAP Gateway hub using transaction /IWFND/V4_ADMIN.
Please note that default service group /IWBEP/ALL can only be published in development systems.