Skip to Content
Author's profile photo Subhro De

Using SAP Hana Cloud Integration with SAP HCI Odata Provisioning

SAP HCI Odata Provisioning is a part of SAP Hana Cloud platform based tools which among other functionality provides secure exposure of REST based interfaces from On Premise SAP Business Suite into the SAP Hana Cloud. In this case, let us look into an approach to use SAP Hana Cloud Integration to leverage SAP HCI Odata Provisioning to fetch data from on Premise SAP Business Suite.


For this approach we will use the following:

1)   SAP Gateway trial service that is been provided by SAP – for details please refer to the link .

2)   SAP Hana and SAP Hana Cloud Integration Trial account

3)   SAP Cloud Connector: 


SAP Gateway :

We will use the SAP Gateway trial as a substitute for on Premise system and connect to it from locally installed SAP Cloud Connector. Check if the SAP Gateway can be accessed from your local machine.

SAP Cloud Connector Configuration

  1. Start the go.bat from the SAP Cloud Connector directory (in case of Windows OS).
  2. Login to the SAP Cloud Connector – the default is https://localhost:8443.

Set the Access Control so that the virtual host and port (sapgateway 1234) is pointing to the IW_BEP service in the SAP Gateway. This hides the actual hostname of the on Premise system and securely sets up the communication from the SAP Hana Cloud.


  SAP HCI Odata Provisioning Configuration (formerly Gateway as a Service)

  1. Log in to the SAP HCI Odata Provisioning tool – using the following URL or by going into the Services tab in your SAP Hana Cloud Account. Please make sure you have assigned in the Authorization of your user the two roles ‘GW_User’ and ‘GW_Admin’ from Account ‘gwaas’ and Application ‘gwaas’.


   2.  In the HCI Odata Provisioning Configuration there are 4 sections :


   a) Browse to the ‘Destinations’  section and create a destination to point to the onPremise system. The hostname and port will be the virtual hostname and port provided in the SAP Cloud Connector above and the credentials would be the details to log in to the SAP Gateway.


b) Browse to the ‘Services’ section and register a new Service. Choose ‘Select from the list’ option and the destination name created in the last step./wp-content/uploads/2015/02/5_641126.jpg

c) Fill in the details in the Register Manually section – you can use the service name as GWDEMO and the other details as below : /wp-content/uploads/2015/02/6_641127.jpg

d) Save and browse to the ‘Explore’ section to view the metadata accessed from SAP Gateway./wp-content/uploads/2015/02/7_641128.jpg

e) In the ‘Services’ section refer to the ‘Open Service Document’ link to get the URL to be used by SAP Hana Cloud Integration to use this service.


The link should open an URL https://gwaas-<user>;v=1

SAP Hana Cloud Integration Configuration

  1. In the Eclipse tool let us develop a simple Integration iFlow to fetch the data from the URL above. Basically the scenario would be to fetch data from the URL above using the Odata adapter in SAP HCI.
  2. The iFLow details are as follows :


3.   The Odata communication channel should be configured as below :

      a) Choose the Adapter type as below :


     b) In the Connection section provide the connectivity details :


    c)  The credentials to access the service should be deployed as ‘User Credential’ artifacts and the same name is referenced in the communication channel above.


   d) Click on the ‘Model Operation’ to build the Query for fetching the data from the service.  Fill up the URL , username and password to proceed.


  e) Click on next to get the Entity list – the filter box above makes it easier to search through Entities.


f) Select the particular entity to create the query – and then choose the particular fields. Optionally click on next and create filter conditions for the query.


On completion of the creation of the query – the Query appears in the Operation Details section.


g)  Deploy the Integration Project (Put the Starter Timer at ‘Run Once’ in the iFlow) and check for errors.In the SFTP server check for the file created – it should be available for confirmation of the testing.

Result of the scenario – The file created contains the data queried from the SAP Gateway.


Relevant links are mentioned below:

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Nice Blog Subhro... will be looking for more blogs from you...



      Author's profile photo sridevi garapati
      sridevi garapati

      Hi Subhro De,

      Thanks for sharing good information.



      Author's profile photo Sindhu Gangadharan
      Sindhu Gangadharan

      Hello Subhro,

      Interesting blog! In this case you are only using HCI OData Provisioning trial to mock a backend system right?

      Thanks and Regards,


      Author's profile photo Hemendra Sabharwal
      Hemendra Sabharwal

      Nice blog and well explained Subhro.

      Thanks for sharing and giving exposure to HCI Data Provisioning and HCI.

      Warm Regards


      Author's profile photo Pallavi Uppuleti
      Pallavi Uppuleti

      Hi Subhro,

      Very nice blog.I tried to implement the same but with Mail adapter instead SFTP adapter.

      And I have checked run once option in start timer.Do I need to perform any other steps to execute the service because I am not able to see that in Message monitoring.Please advice.

      Thanks in Advance


      Author's profile photo Former Member
      Former Member

      Hi Subro - Nice information on the GW service availability usage.

      Other possibility I can think of now is register OData service on premise and access the same at HCI adapter using the option Onpremise and HCC Connection with HCI.



      Author's profile photo Mounia Erradi
      Mounia Erradi

      Please help ASAP!

      we are implement C4C for a client , they gave us the HCI URL for C4C but other Cloud implementation are going on at the same time (concur, Success Factors, S&OP)

      SAP provided different HCI urls for every application..

      Do we use all of them separately to integrate with SAP ERP or do we only use one HCI for all the SAP Applications?

      pelase help!