Making a Plan

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Explain what the SAP Sales Cloud OData API is
  • Know how we’re going to build this app to get data from SAP Sales Cloud
  • Connect the app we build with the data

SAP Sales Cloud OData API

At this point we know that SAP AppGyver is used to create apps and we’ve also learned a bit about SAP Sales Cloud. Also, we’ve established that we want to create an extension application using SAP AppGyver and get the appointments data from SAP Sales Cloud.

Now that you understand the scenario, in this lesson we will focus on making a plan for how to build the application, and on understanding how to get the appointments data into our application, and what resources we need to achieve that. How are we going to get the data from SAP Sales Cloud into the SAP AppGyver app? Well, what we need is called an API, an OData API to be exact, and we will use it to connect the data from SAP Sales Cloud to the extension we will be building in SAP AppGyver! Let’s first spend a moment learning about the API part in more detail, then we’ll follow a 3-step plan to build the app extension.

What is the SAP Sales Cloud API?

To create an extension with SAP AppGyver we need to access data in SAP Sales Cloud. We’ll do this by creating an integration from SAP AppGyver to the SAP Sales Cloud OData API.

SAP Sales Cloud OData API is quite a mouthful of words so let’s unpack it a bit. We already have an idea what SAP Sales Cloud is, but what is an API and what is an OData API?

An API is a way to communicate with a system to fetch or write data to or from the system, or to perform some action in the system. You might remember APIs from an earlier unit, where Esmeé taught you how to leverage an API in her bar scanner app. Generally, APIs are used by applications and services. In our specific use case, we might look up the appointments list in SAP Sales Cloud but the application extension we’re going to build will fetch this data from the SAP Sales Cloud API.

And what about OData? OData stands for Open Data, and it is one of the open standards used for APIs. (An "open standard" in very broad terms means it is publicly available.) In the SAP world, OData is used for a large number of APIs, so OData is going to be of interest to us when working with SAP products, including SAP Sales Cloud.

Of course, SAP AppGyver is also able to make connections to OData APIs which is going to help us a lot with the integration.

We’ll go into more detail on the OData API as we configure the integration in SAP AppGyver.

The Scenario – Connecting Everything

So now that we have an idea of what kind of app we’re building and what the SAP Sales Cloud API is, let’s look at how to connect everything to create a working solution.

We will be working with a list of appointments stored in SAP Sales Cloud and display them in a custom application to make it easy for anyone using the app to access them.

The app, that we are going to create, will let us easily see every upcoming appointment, and we can also use this as an events display, for example.

In our scenario the data for the appointments is in the SAP Sales Cloud system. Our plan has 3 steps to it:

  • Step 1 — build a new SAP AppGyver app to display the appointments
  • Step 2 — make a connection from the SAP AppGyver app to the SAP Sales Cloud OData API
  • Step 3 — configure the SAP AppGyver app to display the appointments data

We are going to use real data just like you would find in an SAP Sales Cloud system, but as setting up SAP Sales Cloud and the OData API would be quite a time-consuming project for you, we will provide you with mock API to complete the exercise.

So, that’s the plan. Next, we’ll start putting it into practice with SAP AppGyver!

Save progress to your learning plan by logging in or creating an account