Skip to Content
Technical Articles

SAP Conversational AI with SAP Solution Manager – ITSM

What is Conversational AI?


People today expect 24×7 access to online stores, along with personalized customer support available instantly and on demand. Fortunately, advances in Natural Language Understanding and other artificial intelligence (AI) technologies like machine learning are creating digital opportunities to do just that.

With SAP Conversational AI, you can:

  • Increase sales across digital commerce channels with personalized, 24×7 human-like “bots”
  • Lower costs of customer service, and improve customer satisfaction and loyalty
  • Increase employee productivity and satisfaction by automating high frequency and routine service desk interactions

In short, with Conversational AI, you can boost your revenue streams, improve the customer experience on desktop and mobile devices and enhance operating margins company-wide.


What is possible with SAP Solution Manager?

  • “Alexa,ask solman, How many open changes do we have? “
  • “Alexa, ask solman, How many defects do we have?”

We can also use Conversational AI with other Technology like (Slack, Facebook Messanger or direct on a Webpage)


Youtube – Alexa in action


Amazon Developer Account –

SAP Cloud Platform –

If necessary:

SAP Conversational AI –

Getting Started with SAP Cloud Platform – 

Process Flow with SAP API Management


Why we need SAP API Management?

The Endpoint (SAP Solution Manager) will receive POST requests when a user interacts with your Alexa Skill. The request body contains parameters that your service can use to perform logic and generate a JSON-formatted response. SAP standard OData Services response in a XML- formatted response.

So we need SAP API Management to get a public URL and it’s possible to manipulate the response from the Backend (SAP Solution Manager).

First of all, we need a API Provider. We take the SAP Cloud Connector for the Backend connection.


API Provider use SAP Cloud Connector.


Define Backend OData Catalog.


Next Step is to import the OData Service from  SAP Solution Manager.

Detail view:


API Proxy URL: We need this URL for the ALEXA Skill Endpoint


We need the resources to get Information from Alexa. “GET” is to get Informations like (How many Incidents do we have?) With the “POST” we can push Information from Alexa to SAP Backend




The API to call the SAP Backend (Solman) with a public URL is now available. So we need to manipulate the response of the OData call into a JSON format.

So the next Step is to define a policy for this API.

In the policy Designer we can manipulate the Flow to call the Backend and the response from the Backend. I used Basic Authentication to call the API. To convert the response from XML to JASON I created a flow scipt. Let’s take a look.

So I choosed a “PreFlow” from the Proxy Endpoint (Solman Backend) to convert the XML into JSON.

To call the Proxy Endpoint I choosed Basic authentication. Here you see the scipt to assign a SAP User for this call.

I assigned a User and password to call the Backend. Here you see the variable for this assignment.

So here you see the response call via SAP API Management. For our Skill we need the “COUNT” Number (2) And you see here that we are calling the Odata Service with “MessageResultSet”


My next To Do’s in the next Blog post:




You must be Logged on to comment or reply to a post.