SAP Gateway

The first OData service implementations used the Service Builder to design the OData Model and a code based implementation of the methods of the data provider extension class. Using the SAP Gateway AddOns this kind of service implementation is available for all SAP Business Suite Releases that run on top of SAP NetWeaver 7.0 SP18 and later.

OData service development with SAP Gateway – code-based service development – Part I

OData service development with SAP Gateway – code-based service development – Part II

How to add annotations to an OData service using code based implementation

How to handle etags in SAP Gateway using code based implementation

Starting with SAP NetWeaver 740 OData Services read and query methods can leverage CDS views. Whereas in 740 the Mapped Data Source approach has be used with 750 the Referenced Datasource approach became available that is more flexible and does not require manual creation and mapping of entity types.

OData service development with SAP Gateway using CDS via Referenced Data Sources

OData service development with SAP Gateway using CDS via Referenced Data Sources – How to implement updates

How to redefine RDS based OData services?

To build greenfield applications on SAP S/4HANA 1909 or lower releases, you can use the ABAP programming model for SAP Fiori to efficiently develop OData V2 based, SAP HANA-optimized, and draft-enabled SAP Fiori apps.

How to develop a transactional app using the ABAP Programming Model for SAP Fiori

The ABAP RESTful Application Programming Model (RAP) supports the efficient development of cloud-ready and SAP HANA optimized OData (V2 and V4) based services for SAP Fiori apps and Web APIs. Greenfield and brownfield implementations are supported. RAP is the evolutionary successor of the ABAP Programming Model for SAP Fiori.

RAP is available on SAP BTP ABAP Environment, SAP S/4HANA as of edition 1909, and SAP S/4HANA Cloud, ABAP Environment.

SAP plans to provide a migration path for applications built with the ABAP Programming Model for SAP Fiori for customers and partners who want to take advantage of RAP.

Find out more about RAP on our community page Modern ABAP Development with RAP.

If you must create OData V4 services in a system that does not allow the development of RAP based OData V4 services and cannot wait until an end-2-end support for OData V4 will be available through the new ABAP RESTful Programming Model you will find here information how this development can be performed using code based implementation.

OData V4 code based implementation – Overview

OData V4 code based implementation I (basic interface, read access)

OData V4 code based implementation II (basic interface, create & update)

SAP Gateway can be configured in different deployment options that also encompass the deployment of the SAP Gateway Server component in SAP BTP Environment.

However the deployment option that is recommended for SAP S/4HANA is the embedded deployment option where SAP Gateway is used as the SAP Fiori Frontend Server.

SAP Fiori deployment options and SAP Fiori front-end server strategy