Skip to Content
Author's profile photo Midhun VP

How To Create HCPMS Apps With Non OData Backend (beta)

OData Provisioning feature in HANA Cloud Integration (HCI) converts non OData protocols to OData, hence HCPMS applications can consume it. This feature is similar to what Integration Gateway do in SMP 3.


In this blog I am explaining how to create HCPMS mobile app using OData service I created from an existing SOAP service as mentioned in my blog.

Business Scenario

Data from backend is exposed as SOAP service. It is possible to define backend of HCPMS application with SOAP service, but the application will not get all the benefits of HCPMS, ex. Offline.

So, to create a mobile app with all features of HCPMS, SOAP has to be converted into OData. To convert SOAP to OData we need to use HCI.

Step to Step Procedure

As mentioned in this blog OData service was created, it will be used as backend in HCPMS application.

The following steps will guide you through creating an HCPMS application, and testing it on a simulator.

Web IDE is used to create the hybrid app.

Configure app on HCPMS

  • Logon to HCPMS cockpit. Click on Applications tile.


  • Press the + icon to create a new application.


  • In the create application screen enter below details. Click Save. Note: Security configuration as Basic means it require Basic Authentication.


  • Click on Configure. Then click on Backend.


  • Fill in the details as given below. Then click Save to complete your configuration.


Create Mobile App using Web IDE

  • Logon to SAP Web IDE select Local root and open the context menu by right clicking.
  • Choose New > Project from Template to open the new project creation wizard.


  • On Template Selection page click on SAPUI5 Master Detail Kapsel Application. Click Next.


  • Enter a name for your project and click Next.


  • Next, choose the backend and provide details to complete the base URL as given below. Click  “Load Service Metadata” button, it will list the OData collections of the OData service. Click Next.


  • Note: I have configured a destination with the details of my HCI system as given below. This backend was used in the above step.


  • Fill out the Project Namespace, Master Section, Master Data Fields and Detail Section as displayed in the screenshot.


  • Click Next.
  • Click Finish to create the project.


  • To run this app as a hybrid app, right click on the project > Project Settings.


  • Under Device Configuration provide below details. Click Save. Note: I am going to test this app on iOS simulator hence chose iOS as the mobile platform. Logon plugin is used to login to HCPMS from the app.

     /wp-content/uploads/2016/04/2016_04_18_13_03_51_931877.jpg      /wp-content/uploads/2016/04/2016_04_18_13_10_33_931878.jpg

  • Finally, to test the app on a simulator right click on the project > Run > Run On > iOS Simulator. Note: To use this feature you need HAT configured.


  • The application will be installed on the iOS simulator. Backend credentials has to be provided to login to the app. Note: In the background Web IDE is creating a cordova project with the plugins and platforms we chose during device configuration.



SAP for Mobile

Regards, Midhun

SAP Technology RIG

Assigned Tags

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

      Hi Midhun,

      Nice article.  When I create the application through HCPms, the app id is not being exposed through the URL - https://hcpms-s********  I am not sure why - I had created this before.  I am not sure if it is a bug in HCPms.  Once I create the application and then a destination and tie the two together, is there a step i am missing.  I have the cloud connector running and I can test the connection from HCP destination to the virtual destination.

      I created the post -  Maybe you can take a look?



      Author's profile photo Jay Malla
      Jay Malla

      In my mobile app, i get the error - { "requestUri" : "https://hcpms-s*******$metadata?sap-documentation=heading", "statusCode": "403", "statusText": "Forbidden", "headers" : [], "body" :".....HTTP Status 403 - Backend connection is not mapped for this application configuration.....}