openSAP

Design Your First App with Build*

Week 1 Unit 1

00:00:10 Welcome to Designing Your First App with Build! I’m Sam, the Chief Design Officer here at
SAP.
00:00:18 Have you ever enjoyed an app or video game, and wondered how their creators made them
so
00:00:24 Or, have you ever looked at an awe-inspiring building, and wanted to know how its architect
and engineers planned it all?
00:00:31 There are so many things you see and use everyday that might make you curious about
how they were created.
Well, during this course you will get to know some of the secrets behind all those well-
designed products
00:00:43 and learn how to think-through and design your very first app. And, along the way, you will
learn a process for creative thinking and problem solving called Design Thinking.
00:00:54 Design Thinking is a methodology or framework commonly used to innovate so that you can
create useful and delightful products and services.
But, before we hit the high gear, let’s ensure we understand some common terms and the
meanings behind them.
So, what is ‘Design Thinking’ and why does it matter?
Design Thinking is a human-centered process used to define and solve problems.
00:01:21 It can be applied to any subject, industry, or field of study. And while it’s a process, there are
no hard and fast rules here.
00:01:29 It follows five basic phases that overlap and loop- back until you reach a desired outcome.
00:01:37 And by human-centered, we mean focused entirely on the user (the person using your
product or service). Design Thinking is collaborative, creative, fun,
00:01:48 and it empowers you to tackle the world’s biggest challenges. It was inspired by the natural
way designers solve all kinds of design problems — by thinking outside of the box and
allowing ideas to flow
00:02:00 creatively without limits of finding the ‘correct’ solution.
00:02:06 Some consider Design Thinking to be more of a mindset, a way of thinking and looking at
things.
00:02:12 Which is also true. We look for an opportunity that motivates the search for solutions,
00:02:17 create a process for idea generation and then we make it real.
00:02:21 We, the practitioners of design thinking, start with deepening our understanding of the
problem or idea first, then use some techniques to generate ideas, and finally, we create
something that is tangible and real.
00:02:35 Although Design Thinking doesn’t have any hard and fast rules, it has five core phrases:
Empathize, Define, Ideate, Prototype, & Test.
00:02:46 If some of these terms sound alien to you, fear During this course, you will learn all about
these concepts all while designing your app.
When we are designing a product, we don’t just start building it right away.
00:03:02 Instead, we try to simulate how it’ll actually be used by the user before creating the final
product. Think of it this way: when you want to build a house, you don’t just start laying the
bricks and pouring concrete.
00:03:16 Rather, you first draw a diagram called a blueprint, and then start adding more details to it
like the kind of materials, etc. Professional architects would even build a digital or physical
3D model so that they can study more details and modify the design as needed.
00:03:34 This approach of building models and simulating the end-product is called prototyping.
00:03:40 What's so great about prototyping? Well, It allows you to study the eventual product more
quickly,
00:03:47 and correct any potential mistakes in a timely manner before you’ve started laying your
bricks and pouring the concrete, so to speak. For this course, you will be using SAP’s world-
class toolset, Build,
00:04:00 to do your prototyping and many other activities. We would like to invite all of you to start
using this cool tool.
00:04:06 Okay, let me introduce you to Bassam, a product manager on the Build team. He will walk
us through many demo videos in this course.
00:04:15 Okay, here you go Bassam. Thanks Sam.
00:04:18 Please go to sapcsr.build.me and sign up for a free membership. Sign up is easy.
00:04:26 Go to our website, click sign up, insert your email address, and fill in your personal
information. Once you're ready, go to your email to verify your information.
00:04:42 Then Tah Tah… Your Build account is ready! We will walk you through all the cool stuff
within Build, but, if you can’t wait, feel free to start exploring!
00:04:53 Okay. Thank you Bassam. Thanks Sam.
00:04:57 During this course you will be designing your first app and learning the Design Thinking
methodology by doing. This week we will lay the groundwork by helping you prepare your
mind for innovation,
00:05:09 a crucial step for creating your first app. We'll cover the basics of design thinking while
practicing it through fun exercises and allowing you to get familiar with Build.
00:05:21 Week 2 will be all about learning by doing. You will learn what it means to design an app
and why it’s important to have a well-defined problem statement in order to create
00:05:33 brainstorming solutions for your user. Weeks 3 and 4 will take what you’ve learned to draw
out solutions,
00:05:40 first by sketching them out, then creating a real working visualization of your idea to test with
users. You will learn how to take your solution to the next level
00:05:51 from importing real data into your app as well as options for getting your idea out into the
world. At the end of this course, you will not only create your first app, but you will learn a
valuable creative problem solving tool
00:06:04 that you can apply to vast range of challenges – big or small, digital or analog. Are you
ready?
00:06:12 Alright, let’s do it!

2
Week 1 Unit 2

00:00:00 Welcome back.

00:00:12 My name is Jai Godara and I'm the head of the design team for SAP's Build product. Now
that you have a basic overview of the course, we hope you are excited to
00:00:25 start learning more about design thinking and getting your hands dirty creating.
00:00:28 In this unit, we will introduce the five core phases of design thinking as well as an activity to
help familiarize you with Build.
00:00:37 I hope you have already signed up for a Build account because you will need it soon. As
Sam introduced in Unit 1,
00:00:45 design thinking is a mindset, a way of looking and thinking about things in order to solve
real-world problems.
00:00:52 It doesn't have any hard and fast rules, but it does have some core tenants or phases:
00:00:59 Empathize Define
00:01:02 Ideate Prototype
00:01:04 and finally, Test Let's look at each of these phases separately.
00:01:10 The first one is empathize. Now, as the name implies, empathy is all about understanding
the people that you want to design for.
00:01:23 Well, that makes sense because the more you know about the people for whom you want to
design
00:01:31 or whose problems you want to address, the better off your solution will be.
00:01:37 If you want your solutions to resonate and be meaningful to the people you are designing
for, then it makes sense to know about those people,
00:01:48 to know the environment they live in, to know their problems,
00:01:52 to know their aspirations, to know their limitations as well their strengths.
00:01:58 And that is what empathy is all about. After empathy, we move on to the next phase called
Define.
00:02:06 Define is the phase where you are taking all that learning from the previous phase of
Empathize and putting them together in a meaningful way that gives you an idea, a holistic
overview of the problem that you want to solve.
00:02:25 So this is where you are taking your learnings and your insights and putting them together in
such a way that you can start coming up with ideas to solve a particular problem.
00:02:37 And then we move on to the next phase, Ideate. This is the fun phase where you take all
your insights and learning from the earlier phases of Empathize and Define
00:02:49 and start working on ideas and solutions to address them. The main idea behind this phase
is to start working on as many ideas or solutions as possible,
00:03:04 and then you will have the chance to narrow them down to solve a specific problem. After
Ideate, we move on to a very critical phase called Prototype.
00:03:17 Prototype is the phase where you are giving shape or life to your ideas. This is where you
make them real.
00:03:27 A prototype could be a paper prototype, a physical prototype, a 3D model, or even a role-
play. The main idea is to bring those solutions and ideas from your brain to real life where
others can see them, touch them,
00:03:43 and interact with them. After that, we move on to the last phase called Testing or Test.
00:03:52 Let's say you have invited some guests over for dinner and you are preparing a delicious
dish. I believe it would be a good idea to taste a little before serving that dish to your guests.

00:04:06 Even if you followed the entire recipe. It is the same idea behind this phase called Test, that
before you start making your prototype a real product,
00:04:20 start putting it in stone, so to speak, that you can put it in front of your actual users, in front
of the people for whom you are designing, and let them interact with it.

3
00:04:34 That way, you can learn about whether it is working, whether it appeals to them, or there are
some shortcomings that you can fix before making it a real product.
00:04:48 We will revisit these design thinking phases again later. But for now, let's get you familiar
with the tool you will be using to design your first app.
00:04:59 Have a look at a quick video introducing Build. User experience. You’ve probably heard the
term
00:05:16 a lot! Everyone is talking about it. Business leaders, managers, coworkers.
00:05:21 Even grandma! Okay, maybe not grandma.
00:05:24 But what is user experience and why is it so important? People want well-designed software
that’s easy to use.
00:05:31 Yes, even those who use enterprise software. But it’s difficult understanding the needs of
your users.
00:05:36 And you may not have the right tools or expertise to verify what they want. This can lead to
Frankenstein applications that result in unhappy users who demand revisions and making
changes during development is
00:05:48 crazy expensive. We can do better than that.
00:05:51 Introducing Build. A comprehensive set of tools that helps you learn, prototype, gather
feedback
00:05:57 and get inspired. It’s one tidy solution that lets you create better business applications.
00:06:03 Learning parts teach you design methods like identifying and interviewing users to find their
needs. Or sketching out ideas.
00:06:10 Wait, not those! Yes, these!
00:06:13 Create clickable mockups of your application from your sketches. Turn them into refined
prototypes by dragging and dropping user interface elements,
00:06:22 importing data, creating dynamic charts,
00:06:25 and more. Gather feedback on your prototype.
00:06:28 Whether it’s already perfect... ...or needs a few adjustments to get it just right.
00:06:34 And if you’re feeling lazy... I mean if you want to take your project to the next level,
00:06:40 browse our gallery of prebuilt SAP Fiori applications. Feel free to duplicate and customize
them to your heart’s content.
00:06:47 And here’s the best part. Instead of giving developers a large business requirements
document,
00:06:52 you hand them a working prototype with exportable code, knowing your team is on the
same page.
00:06:57 So this is why user experience is important. You identify and understand who you’re
building for,
00:07:03 brainstorm ideas, make prototypes,
00:07:05 gather feedback, revise accordingly,
00:07:08 and repeat until the end of space and time… or until your users are happy.
00:07:16 Whichever comes first. Launch your app with Build today.
00:07:23 Now that you know a little bit more about Build, let's get started.
00:07:28 Bassam will walk you through how to create your first project in Build. After logging in, you
will find an orange Create New Project button.
00:07:38 Click it and give a name to your first project. For example, Jai’s first project.
00:07:43 And yes, it is that simple. Now you have your first project on Build.
00:07:48 Please be sure you have this setup, as we will be coming back to this project space very
often throughout the course. Thank you for the walkthrough Bassam.
00:07:59 Well before we part ways, let's quickly go over what we learned today. We learned that we
don't just start working on a problem.

4
00:08:07 We don't just start solving a problem. We learn first about people that we are designing for.
00:08:15 We learn about their environment. We learn about their problems and needs.
00:08:20 And then we define the problem that we want to solve. Then we create a bunch of ideas
00:08:28 and we make those ideas real through prototyping. And finally, we test those prototypes
00:08:36 to see whether they resonate with the people we are designing for, or they need some
fixing.
00:08:42 Well, that's all for today. See you next time.

5
Week 1 Unit 3

00:00:00 Welcome back!

00:00:12 I’m Gaby, a Product Manager at Build. Now that you have had a brief introduction into the
different phases of Design Thinking
00:00:20 and the tool we will be using throughout this course, Build, let’s dive deeper into the first
phase, Empathy.
00:00:28 To help us better understand, Lisa will accompany us on our journey.
00:00:34 Lisa works in a local neighborhood grocery store, Fresh Mart, and is in charge of
cataloguing and managing the store’s produce inventory.
00:00:45 She’s having some trouble dealing with produce that spoils and wants to figure out a way to
waste less food.
00:00:52 We’ll find out more about her as we continue through the lessons. Now that we know a little
more about Lisa,
00:01:00 let's help solve her problem using the first phase in Design Thinking,
00:01:06 Empathy! But how can we help solve her problem when we know very little about what it’s
like
00:01:13 to work in a grocery store? What happens when food spoils?
00:01:17 And how to manage the produce department? Well, we can answer all these questions with
the help of empathy.
00:01:25 But what is empathy exactly? Remember we talked about empathy
00:01:30 and it’s importance in understanding our users? As we learned in the previous unit,
00:01:36 empathy is the centerpiece of a human-centered design process. But wait.
00:01:43 What’s human-centered design again? It’s where you work to understand people
00:01:49 within the context of their problem. It is your effort to understand their physical and
emotional needs,
00:01:57 how they think about the world, the way they do things,
00:02:01 and why. To empathize is to see the world through their eyes,
00:02:07 to see what they see, feel what they feel,
00:02:10 and experience things as they do. Does that remind you of something?
00:02:15 Have you ever gone to a movie and felt personally invested to the main character?
Depending on certain scenes,
00:02:23 you might be laughing until your stomach hurts or crying your eyes out.
00:02:28 How do they do that? Through empathy!
Of course, none of us can fully experience things the way someone else does,
00:02:37 but we can attempt to get as close as possible, and we do this by putting aside our own
ideas of
00:02:45 how we think things are and choosing to understand the ideas,
00:02:50 thoughts, and needs of our users instead.
00:02:54 We must assume the beginner’s mindset and leave our own assumptions
00:02:59 and experiences behind in order to fully immerse ourselves in our user’s reality.
00:03:06 Our own life experience affects the way we see,
00:03:10 interact, and make sense of the world.
00:03:13 However, by constantly and consistently reminding ourselves
00:03:19 to hold our judgement on what we observe
00:03:22 and to question everything, we can connect with our users
00:03:27 and be able to better understand their needs. Isn’t that so cool?
00:03:32 To structure our thinking about the problem entirely around the people

6
00:03:37 we are trying to solve the problem for. It’s not about you – it’s about them!
00:03:44 In order to do this, we need to somehow find out more about what concerns them
00:03:52 - through observing, engaging, and identifying with your users to better understand their
experiences and motivations.
00:04:02 If possible, it’s good to immerse yourself in their physical environment to have a deeper
understanding of the issues involved.
00:04:13 Empathy can be a challenging topic to understand, because the exercises rely heavily on
feeling
00:04:20 and experience versus written knowledge. But the key to tackling this topic
00:04:26 is to stay curious. Continuously ask questions,
00:04:31 ask for more details, ask about different thoughts
00:04:35 and feelings so that you can better understand. How do we practice and apply empathy?
00:04:43 There are many methods we can use to practice and apply empathy. One of our favorites is
asking questions.
00:04:52 Asking questions helps us move from the concrete observations to unpack abstract
motivations that influence the actions of our users.
00:05:03 We can achieve this by asking three essential questions: What?
00:05:08 and Why?
00:05:10 What?, How? and Why? is a powerful technique to help you dive into deeper levels of
observation. You will move from concrete observations of a particular situation
00:05:23 to the more abstract emotions and motives that are at play in that situation.
00:05:30 To practice this method, get out a piece of paper and make 3 columns,
00:05:36 like you see on screen. You will use this paper to write down your observations
00:05:42 and interpretations as we go through the steps. Now let’s look at this photo of shoppers in
Lisa’s store.
00:05:52 Feel free to pause the video at any time to fill in your paper. What is the person doing in the
photo?
00:06:00 Notice and write down the details. Try to be objective and don’t make assumptions here.
00:06:08 Stick to the facts of the photo. This question helps provide insight on the person’s emotional
state.
00:06:18 How are they doing what they are doing? For example, their body language and facial
expressions.
00:06:27 Does what they are doing require effort? Do they appear rushed?
00:06:33 Is the person happy or depressed? Does their activity or situation appear to be impacting
their state
00:06:41 of being either positively or negatively? Write down the answers to these questions as
descriptive phrases, packed with adjectives.
00:06:54 The “Why” question is all about trying to interpret what you see and should lead you to
make educated guesses
00:07:03 of the emotional drivers behind the person. How people interact with their environment
00:07:11 can give clues on what they need, think,
00:07:15 and feel. Why are they doing it this way?
00:07:20 Take a guess! Now start writing down your guesses in column three.
00:07:27 Now let’s take a quick look at other methods you can use to observe and gather information
about your users.
00:07:36 Each of these methods aims to notice their behavior and see how they interact in the
context of their lives.
00:07:47 In the first method, photographing and recording user-based studies, users are filmed
and/or photographed in a natural setting

7
00:07:56 or in specific sessions with a group of people who have the sole purpose of gathering
information. Another method, engaging with extreme users,
00:08:09 might seem unconventional but it can provide a lot of insight on your design challenge.
Extreme users are people who don’t fit within the normal definition
00:08:23 of your expected user but are instead on the fringes,
00:08:27 the sides. In Lisa’s scenario,
00:08:31 a regular user is the typical shopper at the grocery store.
00:08:36 But an example of an extreme user is a customer who only buys sale items.
00:08:44 The next technique, empathy maps are a collaborative tool to help us unpack all the
information we’ve gathered by
00:08:54 representing a group of users. Maps are broken into four sections:

00:09:02 Think, and Feel

00:09:04 which act as a guideline to organize all the observations you’ve made. Although this
technique is labeled as an “interview,”
00:09:17 it should really feel more like a conversation. Talking directly to the users we are designing
for
00:09:24 helps provide a better grasp on their wants, needs,
00:09:29 desires, and goals.
00:09:33 The method we are going to focus on today is Bodystorming which is to physically
experience a situation by immersing oneself in the users’ environment.
00:09:45 The environment must be filled with things present in the real world which relate to the
general atmosphere of the user’s setting.
00:09:56 Bodystorming allows us to put ourselves in the user’s shoes to increase feelings of
empathy.
00:10:07 One way to replicate this is to personally go and shop at Lisa’s store. If you are feeling
motivated and want to give this a try,
00:10:18 visit your neighborhood grocery store and walk around the entire store to get a lay of the
land. Then head to the produce section.
00:10:27 See what catches your eye. How is the store organized?
00:10:32 Who is working in the store? Observe and ask yourself questions to increase empathy for
our friend, Lisa.
00:10:41 Exit the grocery store with a newfound understanding and some insights you gathered from
your field trip.
00:10:49 At the core of empathy is the care for our user. It requires us to tap into a power that each of
us has:
00:11:00 human connection. We can begin to understand how and why they do things,
00:11:07 emotional and physical needs, and how they see the world.
00:11:12 Once we cast aside our own judgements and assumptions and immerse ourselves in
understanding the situation
00:11:21 and the person we are designing for, empathy will lead the way to creating a meaningful
product.
00:11:29 In the next unit, Cara will take us through the process of interviewing your user,
00:11:36 a method we use quite a lot to gain empathy for and insights from our users. Okay, that’s a
wrap for empathy.
00:11:45 I will see you next time! Bye!

8
Week 1 Unit 4

00:00:00 Hi! My name is Jono and I'm a User Experience designer here at SAP.
00:00:17 Before we move on to interviewing methods, let’s do a quick recap of what empathy is.
Empathy is the centerpiece of a human-centered design process
00:00:26 where we work to understand people, their physical and emotional needs, how they think
about the world, the way they do things, and why.
00:00:34 We structure our thinking about the problem entirely around the people we are trying to
solve the problem for. We touched on the interview method in the previous unit
00:00:43 and now we’ll go deeper into how to prepare and conduct an interview with your user.
Although this method is labeled as an “interview,” it should feel more like a conversation.
00:00:53 Talking directly to the users we are designing for helps provide a better grasp on their
wants, needs, desires, and goals. The interviewer will usually have a set of questions that
revolve around certain themes and topics.
00:01:08 Keep a flow of conversation and see what direction the interviewee goes to. The script is
there to help guide the conversation but don’t feel tied down by it.
00:01:17 Sometimes, during an interview, the interviewee might say something that is interesting or
unexpected. If this happens, you can go off script to follow what they say.
00:01:27 Follow up with questions in order to uncover deeper meanings. And now, to help out Lisa,
00:01:33 let’s interview her to better understand her day-to-day activities. Here’s an example of how
an interview will look like:
Hi Lisa! Thank you for taking the time to sit with us.
00:01:44 This interview is to help develop the “Spoil Alert” initiative. Our goal is to provide you with
better tools to successfully carry out the new plan to reduce unsold inventory,
00:01:54 and to minimize waste. We encourage you to openly share your thoughts and feedback with
us.
00:01:59 So please think aloud and as we’re going through the interview remember there are no right
or wrong answers.
00:02:05 Any feedback you give us will help us greatly! It's great to be here Jono!
00:02:10 Awesome! Well let’s get started! Can you please describe your role and main
responsibilities?
00:02:15 Like, what does your typical day look like? Well, the first thing I do when I come to work is
restock all of the produce.
00:02:22 I want to make sure our customers receive the freshest groceries possible when our doors
open. Just like the name of the store, Fresh Mart!
00:02:30 And then later in the day, I recheck our produce inventory in the back and catalog it. Okay,
how would you describe your biggest challenge in your current role?
00:02:40 Honestly? Taking inventory is probably my least favorite responsibility.
00:02:46 Why is that? Well, for one thing, the current system is very tedious.
00:02:51 For instance, I have to use a certain clipboard to write everything down which includes all
the serial numbers, all the dates, all the shipping addresses.
00:03:02 Frankly, with so many letters and numbers, it makes my head hurt! Okay, I see. Is there
anything else you don’t like about working in the current system?
00:03:11 Frankly, it pains me to see food go to waste. Currently there is no system in place that
provides any insight
00:03:18 into what and where food is about to spoil. Okay, duly noted.
00:03:22 So what are some things you like about working in the current system? After I get past all
the pen and paper shenanigans,
00:03:29 logging into the computer is relatively easy. Most of the information is sorted once it’s in the
system
00:03:35 so I really appreciate some of the filters that organize all of the data. For instance, when did
the product arrive and where it came from. That sort of thing.

9
00:03:47 How frequently do you take and record inventory? It varies slightly from week to week, but
mainly I log inventory about every other day.
00:03:57 Sometimes if it’s a busy week, I’m in the backroom logging every day. But it just depends.
00:04:02 Okay, I see. Well, thank you so much for speaking with us Lisa! We really appreciate all
your honest feedback!
00:04:09 With such a simple interview, we were able to gain a better idea of some of the thoughts
and feelings that Lisa has. For example, we know that she takes pride in her work
00:04:19 and in making sure that she delivers quality products to her customers. Another detail is that
she thinks the current inventory system is confusing.
00:04:28 Maybe that’s a problem we can help her solve. Well, now that you saw how interviews work,
are you ready to try it on your own?
00:04:35 Don’t worry, we’ll help you out. For an interview, your goal is to gain a better understanding
of Lisa
00:04:42 and the work that she does. But, because you don’t have direct access to Lisa,
00:04:46 try to interview someone who works in a grocery store. If you don't know anyone who works
in a grocery store,
00:04:52 no problem! Another alternative is to find someone who shops at a grocery store.
00:04:57 We want you to take what you've learned in the current and previous lessons and apply it to
real life.
00:05:03 So go out and be curious! Remember to listen and observe,
00:05:06 and from that you’ll be able to experience the power of empathy. Now let me hand it over to
Bassam where he will show you how to utilize Build to learn more about interviewing your
users.
00:05:19 First things first. Log into your account on Build.
00:05:22 Scroll to the Learning section. Click on the Research node on the double helix
00:05:28 and find the tile labeled Interview Your Users. Click on it and the button will direct you to a
page with more information about how to interview your users.
00:05:40 Go to the toolkit section on the left-hand side and click on the file named How to Prepare an
Interview Script.
00:05:45 The template of the interview guide should be displayed on the screen. In the interview
script guide, you will find a basic structure of an interview.
00:05:53 This guide is split up into five sections: Introduction and context setting,
00:05:59 Background questions, High-level questions,
00:06:02 Detailed questions about tasks, and closing. Once you've read this document, navigate
back to the Toolkit section
00:06:10 and download the interview script example and template. Use this template to conduct your
interview.
00:06:17 You can print it out and use it to write down the answers you get back from your user. Use
these documents to help organize your questions
00:06:25 and create a better flow so that your interview runs smoothly. While preparing for your
interview, craft questions.
00:06:33 These questions can establish background, to gain a better understanding of the user
00:06:37 and to shed light on the problem. During the interview, be observant and take note of any
tiny details.
00:06:44 Jot them down so you can refer back to your notes later in the Design Thinking process.
Don’t worry if there are some awkward silences – it’s normal.
00:06:54 Don’t rush into the next question, but instead, give the interviewee some time to think and
collect their thoughts.
00:07:02 You are there to get their response and to hear about their experiences so make sure that
they feel comfortable!

10
00:07:09 The interview should feel more like a conversation. That way, it will feel more natural to you
and the interviewee.
00:07:16 And remember, feel free to go off script. The script is only a loose guideline for the
interview.
00:07:22 Okay, I will now hand it back over to Bassam where he will show you what to do after you've
conducted your interview.
00:07:31 Once you've finished conducting your interview, compile all your information the questions,
the interviewee’s response,
00:07:38 and the observations you’ve made into a single document. Then navigate back to the Build
web page and go into your workspace.
00:07:45 Click on the project you are working on. On the top navigation bar, find the title Project and
click it.
00:07:52 In the dropdown menu, click Files. Upload your document and then you’re all done!
00:07:58 This folder will be your storage place for all the different files related to this project. Get
familiar with it because you'll be navigating here very often!
00:08:06 Well, that’s it for this unit. We’ll see you next time!

11
www.sap.com

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affiliate
company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. Please see
http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company products and
services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue
any course of business outlined in this document or any related presentation,
or to develop
or release any functionality mentioned therein. This document, or any related
presentation, and SAP SE’s or its affiliated companies’ strategy and possible
future developments, products, and/or platform directions and functionality
are all subject to change and may be changed by SAP SE or its affiliated
companies at any time
for any reason without notice. The information in this document is not a
commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and
uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these
forward-looking statements, which speak only as of their dates, and they
should not be relied upon in making purchasing decisions.