SAP S/4HANA, SAP Business Technology Platform, SAP Integration Suite, SAP BTP

Exposing master data as ODATA service from S/4 HANA on-premise

The ABAP CDS views are present already in the S/4HANA on-premise waiting to be used up. The question is how to expose these CDS views from S/4HANA and consume as APIs in SAP BTP.

CDS Views for Sales

In this blog post I will try to explain the steps to identify and expose the ABAP CDS views from SAP S/4HANA on-premise, which can be later consumed as APIs in SAP Integration Suite.


In t-code SDDLAR (CDS Analysis and Repair Tools) in backend S/4HANA on-premise system, you can find other ABAP CDS views consuming the current view based on name.

CDS Analysis and Repair Tools

Select the entity you want to expose.

Display Entities

Preview the Entity Data.

Entity data preview

Display Data Structure

Structure I_Customer_VH

Check the DDL source with the name.

DDL sources with name

Tcode: SEGW

SEGW is the transaction to build a service in SAP.

SAP Gateway Service Builder

CDS Entity – I_SalesOrganization

CDS Entity

Finish CDS-Entity exposure

CDS-Entity exposure

Create Transport Request for CDS Enity.

Transport Request

Model Provider Class and Data Provider Class are created.


Successful Service registration in SAP Gateway.

Service Registration

ODATA Service created successfully.

Service created

Activate the ODATA service in Service Catalog.

Activate and Maintain Service

Keep this handy


Defined ServiceName

Test service in browser

Execute as XML
Execute as JSON

Now we can use this ServiceName by deploying the SAP Cloud Connector in S/4HANA on-premise and mapping this ServiceName as a source of service in the Cloud Connector.

SAP Cloud Connector

Later we can consume this ServiceName as API in SAP BTP through the SAP Integration Suite.

SAP Integration Suite