I'm engaged in a project on SAP BTP ABAP environment and encountering challenges with OData services. Traditionally, in the on-premises ABAP environment, we could utilize the SEGW transaction to create and adjust OData services, including renaming entities to meet our naming standards or needs. However, SEGW is not accessible in the SAP BTP ABAP environment, where RAP has become the preferred technology. I'm exploring alternative methods to achieve similar outcomes.
One of our goals is to rename navigation properties (associations) in OData services generated from referenced CDS views. I aim to align the names of navigation properties in OData services with our project's naming guidelines, preferring "Entity" over the usual "toEntity".
Additionally, I've encountered issues with reserved words, such as CDS fields, in the SAP BTP ABAP environment, which were not problematic in on-premises settings (link).
The reason I wish to keep the services identical (at a metadata level) in SAP BTP ABAP environment and on-premises is to connect the new cloud OData services to existing development resources, such as Fiori applications and third-party integrations.
Creative solutions or indirect methods may be necessary due to these limitations. Any advice, tips, or documentation references would be highly valued.
Why not use RAP for all systems types (Cloud and On-Prem). If you use RAP and the "ABAP Cloud", all your OData services will be developed exactly the same way and will be in line with the "Clean Core" approach.
Thank you for your reply. If we could have everything in RAP it would be great. However, we would like to keep the legacy code in SEGW at this moment. We are evaluating the possibility of moving this code to RAP, but right now there is no migration tool that we are aware of. Maybe there is any plan on implementing this tool in the near future?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.