openSAP Introduction to SAP Fiori UX WEEK 3, UNIT 1

00:00:12 Hello and welcome to week 3, unit 1.

00:00:15 For those of you just joining the course, my name is Liz Thorburn and Ill be with you for the

first part of this week as we focus on the SAP Fiori UX configuration steps.

00:00.24 At the end of the week when we discuss the details of the analytical app type configuration, my

colleagues Markus and Daniel will take over to explain those steps to you.

00:00:33 Before we get started, I want to point out that I will not be able to cover every intricate detail of

the configuration process.

00:00:39 My hope is at the end of this week youll have a high-level understanding of the necessary

configuration steps, and where those steps take place.

00:00:47 This material follows the flow of the configuration steps on the Help Portal, so please reference

that for more details. In addition, the RDS team has developed in-depth How-to Guides for

configuration.

00:00:58 If youre planning an implementation in your landscape, I suggest you also look at these How-

to Guides, which can be downloaded from Service Marketplace.

00:01:06 Those Guides are not only thorough but have been tested a number of times to ensure

cohesiveness and accuracy.

00:01:11 Also keep in mind that were constantly working to improve and enhance the SAP Fiori apps,

so understand that the help will change over time to reflect these improvements.

00:01:21 With that said, lets jump right in.

00:01:24 Prakalp took you through deployment last week and discussed the required versions of the

different components that are needed in your landscape. We can think of this as laying the

foundation.

00:01:33 This week Im going to take you through how to build up and configure your landscape.

00:01:37 The first thing we need to do is configure our infrastructure by setting up the SAP Fiori

launchpad and Search.

00:01:43 Once that is completed, we can move on and configure each server in our landscape.

00:01:48 We will talk about general configuration steps required, regardless of the specific apps you

choose, and we will discuss how to configure specific apps.

00:01:56 Obviously, we're not going to have time to discuss each of the 300+ apps currently supporting

the SAP Fiori UX,

00:02:02 but all of the apps follow the same flow so well focus on a couple and from there, youll be

able to take what you learn and apply it to any SAP Fiori app.

00:02:12 After our infrastructure is in place, we will focus on the necessary configurations in the front-

end server, the back-end server, creating search connectors, and configuring access to SAP

HANA data.

2

00:02:23 From this slide, you can see where configurations for each server are necessary per app type.

00:02:28 All app types have configuration tasks that need to be performed on the front-end server and

the back-end server.

00:02:33 Fact sheets have additional configuration tasks for creating search connectors for apps, and

analytical apps have additional tasks for configuring access to SAP HANA data.

00:02:45 Following the same logic as the slide before, you can see here the specific tasks were going

to cover on the front-end server, and which app type they are relevant for.

00:02:53 We start by activating ICF and OData services, and configure and assign roles to our users.

00:03:00 When we get into each section, Ill show you the transactions you need to go to, and where the

app-specific information youll need can be found.

00:03:07 This slide details the tasks we need to configure on our back-end server. We have to assign

RFC authorizations to our users and assign roles.

00:03:17 You know that only analytical app types have to access their data from the HANA XS engine,

00:03:23 so it makes sense that when we get to his unit, were only going to focus on the analytical app

type.

00:03:28 Markus and Daniel will discuss with you the steps listed in this slide.

00:03:33 This now concludes unit 1 SAP Fiori UX Configuration Overview.

00:03:37 In the next unit, well talk about the infrastructure configuration. See you soon bye!

3

WEEK 3, UNIT 2

00:00:13 Hello and welcome to unit 2 Configuration of the SAP Fiori UX Infrastructure.

00:00:18 As I mentioned in the previous session: Before configuring specific apps or servers, you need

to make sure your infrastructure is in place.

00:00:27 The SAP Fiori launchpad is the entry point to Fiori apps on mobile or desktop devices. The

launchpad designer (pictured here on the right) is the standard tool for configuring the Fiori

launchpad.

00:00:38 The launchpad designer has two layers to it: the configuration layer and the customizing layer.

00:00:44 The configuration layer is where all the content delivered by SAP is stored, and it is where

system-wide settings or changes take place.

00:00:51 The customizing layer is where customers can make changes to specific clients, and then

those changes will only be valid for the specified clients.

00:00:59 The personalization layer is in the Fiori launchpad, and it is where end users can make their

own personalized changes, such as creating a new group.

00:01:07 Whatever changes are made by end users are stored in the personalization layer.

00:01:11 The Fiori launchpad and the launchpad designer are part of the SAP_UI software component,

which is included in the standard SAP NetWeaver 7.40 version that Prakalp discussed with you

last week.

00:01:24 You need to configure the Fiori launchpad so that users have access to those apps that have

been assigned to them.

00:01:30 In this presentation, we will detail the configuration tasks necessary for this step.

00:01:35 If you remember from the first week, we talked about OData being used as the communication

channel between servers.

00:01:41 OData services have to be enabled in SAP NetWeaver Gateway. And once enabled, they

establish the mapping between the technical OData name and the corresponding back-end

service.

00:01:51 In order to set up the SAP Fiori launchpad and launchpad designer, we have to activate some

specific OData services.

00:01:59 To do this, we will log in to the front-end gateway server and access transaction

/IWFND/MAINT_SERVICE the Activate and Maintain Services transaction.

00:02:09 Within this transaction, youll choose the Add Service button and enter the system alias of

your local system and the technical service name of the OData service.

00:02:18 There are five services that we need to activate in this step (they're listed on this slide here):

00:02:23 The first is the catalog, page and gadget service for the configuration layer of the launchpad

designer.

00:02:29 The second is the catalog, page and gadget service for the personalization layer of the

launchpad.

00:02:35 The third is the catalog, page and gadget service for the customizing layer of the launchpad

designer.

4

00:02:40 The fourth is a service used by the SAP Fiori launchpad for navigation.

00:02:45 And the final service is used by the SAP Fiori launchpad designer to read and assign transport

requests.

00:02:51 Once these services are activated, we can move on to the next step.

00:02:56 Now we need to activate the corresponding ICF nodes for the SAP Fiori launchpad UI.

00:03:02 This is done through the front-end gateway server using transaction SICF.

00:03:07 ICF stands for Internet Communication Framework, and it is the software layer in an

application server that provides an ABAP interface for HTTP, HTTPS, and STMP requests.

00:03:19 This framework is used in Fiori apps to enable the UI service.

00:03:23 For security reasons, all ICF services are made available in an inactive state.

00:03:28 For that reason, you need to follow the paths specified in this screen and activate each service

by right-clicking on it and choosing activate.

00:03:36 NWBC node is for the NetWeaver Business Client for HTML.

00:03:40 Start Up provides the data that is needed for the front-end shell startup.

00:03:44 The ar_srvc_launch is for the launch tile application.

00:03:49 The ar_srv_news is for the news tile application.

00:03:52 The arsrvc_upb_admn is for the unified shell page builder administration page.

00:03:59 ushell is for the unified shell.

00:04:01 ui2 is for the namespace and ui5_ui5 is for SAPUI5 application handler.

00:04:10 Next, we need to assign the necessary roles to both Fiori launchpad administrators and end

users.

00:04:15 To do this, log in to your front-end gateway server and access transaction PFCG the

transaction for Role Maintenance.

00:04:23 Copy the administrator role delivered by SAP to your customer namespace:

00:04:28 On the menu tab, choose authorization default, choose TADIR Service from the drop-down

list, and enter the program ID and object type listed in this slide.

00:04:38 Youll then enter the name of the services we just activated: Choose the Authorizations tab

> Propose profile name > Change authorization data > and Generate.

00:04:47 Then you assign the new role to the admin user by entering their user ID number in the User

tab.

00:04:53 When youre finished, you should see 3 green lights on each of the tabs (just like you do here

on this slide).

00:05:01 To assign roles to end users, the steps are exactly the same as we just went through for the

administrator except you only need to enter these two services listed on this slide into the

TADIR Service table.

00:05:12 Once completed, assign the role to users through the Users tab using their user ID.

5

00:05:17 Fact sheets allow you to access back-end data and start transactions there, for example you

could open an SAP GUI transaction from a fact sheet.

00:05:25 To do this, you need to establish a connection between the Fiori launchpad and the back-end

system.

00:05:31 In the gateway server, you need to create the RFC connection by going to transaction SM59.

00:05:37 You will need the system alias which you will enter as the RFC destination, youll create type H

connection, which is for HTTP connections to an ABAP system,

00:05:46 and then youll enter the target host under the technical settings and save your entries.

00:05:52 The search highlighted in this slide is used to find apps and central business objects.

00:05:57 There is an SAP Note that provides you with an up-to-date list of the search models delivered

for the SAP Business Suite, and that note number is listed on the slide.

00:06:05 There are various steps that need to be taken to set up SAP Fiori search. Detailed on this slide

under procedure, you can see the steps that need to be taken.

00:06:14 In addition, there are more specifics on each step that you can find in the Help documentation

and in the Best Practice guides on Service Marketplace.

00:06:22 This now concludes unit 2 SAP Fiori UX Infrastructure Configuration. In the next unit, well

talk about the front-end server configuration tasks. Bye.

6

WEEK 3, UNIT 3

00:00:12 Hello and welcome to unit 3 SAP Fiori UX Front-End Configuration.

00:00:18 In this unit, we will review all the necessary configuration tasks that need to be completed on

the front-end gateway server, and for which app types the steps are relevant for.

00:00.28 Moving through this presentation, you will notice that some steps are relevant for all app types

while others are only relevant for some.

00:00:35 Ill be sure to point this out as we move through but if you go off on your own to configure your

front-end server, be sure to always reference the Help Guides or the RDS Best Practice

Manuals for the specific app type you're configuring.

00:00:47 All of the configuration steps are specified here in the order that they need to occur consider

each step a prerequisite to the forthcoming steps.

00:00:57 In the previous unit, we activated ICF services for the Fiori infrastructure. Now we need to do

the same thing but on an app-by-app basis.

00:01:05 This configuration step is necessary for all app types since it is for activating the UI5

application of which every app has.

00:01:13 Throughout this presentation, Ill be using the CRM my Leads transactional app as an

example.

00:01:19 When you go to the SAP Help Guides for SAP Fiori, there is a section titled SAP Fiori Apps.

There, you can find information specific to each of the 300+ Fiori apps.

00:01:30 There is a section about the apps' history, the apps' implementation and the apps' extensibility.

00:01:36 For the purposes of configuration, youll need to reference the app implementation part of

whatever app youre configuring.

00:01:42 Once in the Help Guide, you will see a lot of information that the forthcoming presentations will

highlight.

00:01:48 For the ICF service activation, each app comes with a technical name for the UI5 application

component. This slide shows you exactly what the table looks like in the help.

00:01:59 For this activation step, you need to follow the path listed under the technical name of the

Activate UI5 application.

00:02:06 Just like we did before, you will follow the path until you find your service, right-click and

choose Activate.

00:02:13 Next, we need to activate the OData service for each app type. This is only done for

transactional apps and fact sheets.

00:02:20 Analytical apps leverage the HANA XS engine, which well discuss later this week so they

dont have an OData service that needs to be activated.

00:02:28 In keeping with the My Leads transactional app example, again in the App Implementation

section of the Help for your app, youll notice a table titled Activate OData Services.

00:02:39 Youll need to navigate to the Activate and Maintain Services transaction, choose Add

Service, enter the system alias of your local system, enter the technical name from the help in

the External Service Name and the version.

00:02:51 Then choose Get Services at the top of the popup screen.

7

00:02:55 Then add the selected service, enter a technical name and assign it to a package, then choose

Execute to save the service.

00:03:03 You should now see the service in the main list.

00:03:06 It is best to double-check that the system alias is maintained correctly before moving forward.

Upon successful completion, move to the next step.

00:03:16 In order for users to access apps, certain business user rights need to be assigned in the front-

end server. This step is required for all app types.

00:03:25 SAP delivers business roles for users of SAP Fiori apps, and we detail the role names in the

Help Guides.

00:03:31 For each app in the App Implementation section, there is a table titled Enable App for

Access in SAP Fiori Launchpad.

00:03:39 In this table, you will notice there is a list of roles. All these roles are relevant and well discuss

most of them this week.

00:03:45 For this step in the front-end server, we want to just focus on the business role that has been

delivered.

00:03:51 Youll want to copy the business role from this table and navigate to Role Maintenance using

transaction PFCG.

00:03:58 And the role name, enter the role name in the Role field and choose the Copy button in the

upper left-hand corner.

00:04:04 Enter the name of the copied role (we typically put a z or something in front of the role to

differentiate it but this is totally up to you on what you choose to name it), and then choose

Copy all.

00:04:15 In the previous step, we copied the business role of our app to our namespace; now we need

to edit that role to include OData start authorizations.

00:04:24 This is done in the same Role Maintenance PFCG transaction.

00:04:28 If you remember from the infrastructure presentation, we already did this when we assigned

the administrator role for the SAP Fiori launchpad administration.

00:04:36 And for end users, the process will be exactly the same here.

00:04:40 Once in the PFCG transaction, well choose the pushbutton for Insert Node and select the

Authorization default object type option.

00:04:48 In the Service window, choose TADIR service and specify the following values: Program ID

and Object Type.

00:04:55 Then in the table, enter the name of the OData service we just activated for our app (make

sure to enter it as _ with leading zeroes.

00:05:06 Choose the Authorization tab, choose the pushbutton next to the profile name, and generate

the authorization profile for the role.

00:05:14 Choose Change authorization data and then Generate.

00:05:18 Next, you need to assign the business role for the app to users.

00:05:22 This should be familiar by now since weve done this already. But just as a refresher, this is

8

done in the Role Maintenance, PFCG transaction in the User tab.

00:05:30 Simply enter the user ID for all the users you want to have access to this app.

00:05:37 The final step listed here is for fact sheets only. Fact sheets come with a specific authorization

role per fact sheet.

00:05:44 This authorization role contains authorizations for the ICF services as well as the Business

Server Pages (BSP).

00:05:51 These roles are found in the App Implementation section of the Help for fact sheets under the

Assign Authorization Role table.

00:05:57 The technical names for these roles always end in _FSA. You will repeat the same steps we

just went through of copying the role and assigning users to the role.

00:06:08 This now completes unit 3 and the necessary configuration steps for the front-end gateway

server.

9

WEEK 3, UNIT 4

00:00:13 Hello and welcome to unit 4 SAP Fiori UX Back-End Configuration.

00:00:18 In this unit, we will focus on the configuration tasks that need to occur on the back-end server.

00:00.24 While these steps apply to all app types, understand that for analytical apps these

configuration steps only need to happen if your app provides insight to action.

00:00:33 For example, the Sales Order Fulfillment app is an analytical app that allows you to take action

on a sales order.

00:00:39 Therefore, if this app is one youre implementing you would need to configure the following

steps.

00:00:45 Before we get started, it is important to understand that user names on the back-end server

must be exactly the same as the front-end server; user mapping is not supported.

00:00:55 Users need permissions to perform the RFC call to obtain the data from the back-end server.

00:01:01 To grant this permission, you log in to your back-end system and navigate to User

Maintenance using transaction SU01.

00:01:08 Navigate to Information System and check your user or users have the mandatory

authorization objects S_RFC and S_RFCACL assigned to them.

00:01:21 If they dont have these roles assigned, youll need to assign them in transaction PFCG.

00:01:26 Another way to check which users are assigned this role is to go to Role Maintenance,

transaction PFCG, enter the role name or the copied name if you copied the role,

00:01:36 and choose the display or change icon, and then look through the User tab for a list of

users that are assigned to this role.

00:01:43 In the next step, we need to assign a role with OData service authorization to users.

00:01:48 To do this, youll need to return to the app-specific implementation information in the Help and

reference the Enable App for Access in SAP Fiori launchpad.

00:01:58 If you remember, in the previous unit we assigned the business role on the front-end server. In

this step, we will assign the technical role on the back-end server.

00:02:06 This step is completed in transaction PFCG Role Maintenance.

00:02:10 The next steps will be very familiar as weve already done them a couple times throughout

these units.

00:02:15 Thats one of the positives about configuration: Once you get the steps down, it's just repeating

the same process for the various role assignments.

00:02:23 First, copy the technical role, then edit the copied role. Choose the Menu tab >

Authorization Default from the plus sign pushbutton,

00:02:31 choose TADIR Service, enter the listed Program ID and Object Type in the table, enter the

name of the activated OData Service (remember, this is specific to each app).

00:02:42 And then Change authorization data, Save, and Generate.

00:02:46 If youre using fact sheets in addition to the OData service authorizations, there are

authorizations for the underlying search models.

10

00:02:54 This is done in transaction PFCG.

00:02:57 You need to add entries to the authorization object E_ESH_CONN in the subtree Basis:

Administration.

00:03:06 There, you need to enter the four fields listed on this slide.

00:03:10 This now completes unit 4 SAP Fiori UX Back-End Configuration.

11

WEEK 3, UNIT 5

00:00:12 Hello and welcome to week 3, unit 5: SAP Fiori UX Launchpad Configuration.

00:00:19 If all of the configuration steps we discussed in units 2 though 4 are completed for the

infrastructure and the different apps you want implemented,

00:00:27 you are now ready to configure your Fiori launchpad.

00:00:31 We've discussed the launchpad a little bit throughout all the preceding units but this unit will

focus on it further.

00:00:37 First understand that there are two perspectives to the Fiori launchpad.

00:00:41 There is the end-user perspective, which is what you see in this screen,

00:00:44 and there is the admin perspective, which is the launchpad designer.

00:00:48 Before end users access their launchpad, admins need to configure what apps their business

users see.

00:00:54 This unit will detail that process in six steps.

00:00:57 I want to comment here that when creating this presentation, this was the current state of how

to configure the launchpad.

00:01:03 However, with each new release, we're working hard to make this process easier

00:01:08 so please reference the help documents and always be sure to be running the most up-to-date

service pack for access to the latest and greatest.

00:01:16 The first thing to do is to register your app. You'll need to reference the same app

implementation table we've seen before in the help.

00:01:24 In that table, you will notice an LPD_CUST role and an LPD_CUST instance.

00:01:29 The table and fields I'm referring to are highlighted here in this slide.

00:01:33 Keep these roles handy and then log in to your front-end gateway server and navigate to

Overview of Launchpads using transaction LPD_CUST.

00:01:41 This registration process is completed in two steps that we will cover on this slide and the next

slide.

00:01:48 When you first access the LPD_CUST transaction, you will see an overview of all of the

launchpads

00:01:54 and here you can create new ones or edit existing ones.

00:01:57 For our purposes, we will create a new launchpad by choosing the New Launchpad button.

00:02:02 This will result in a popup that you can see on the bottom on this screen.

00:02:06 Enter the role and instance you obtained from the table in the help and then enter a description

of your choice.

00:02:11 The other fields in this popup are optional.

00:02:14 Once you're finished, choose the green check mark to save your entries.

00:02:18 After saving, you will be redirected to the Change Launchpad screen.

12

00:02:22 Choose the New Application button and enter the following mandatory fields.

00:02:27 First, Link Text, which is a description for the app. You can put whatever you want here.

00:02:32 For App Type you'll want to choose URL from the dropdown list.

00:02:35 In the App Parameter field, enter the URL, which can be found in the help guide in the Activate

UI5 application table.

00:02:43 We will leave the System Alias field blank.

00:02:46 In Fiori, we manually define the navigation to a UI5 Fiori application which we defined in app

parameter.

00:02:53 Open the Advanced Parameters, then enter the Application Alias.

00:02:58 For this, choose a unique name.

00:03:00 This is going to be this alias that will be used later to reference your app in target mapping in

the launchpad designer.

00:03:06 In the Additional Information field manually enter the SAPUI5.Component parameter.

00:03:12 This can be found using transaction SE80.

00:03:15 When you're finished, save your entries.

00:03:18 Now that our launchpad is saved, you'll need to create a transport request and assign it to a

system.

00:03:23 This is done using transaction SE01.

00:03:26 Remember, there are two transport request options for the launchpad. There's a customizing

or a configuration request.

00:03:33 Depending on your needs, choose the appropriate one.

00:03:37 After completing your transport, you can access the launchpad designer, which is the image

that you see here on this screen.

00:03:43 The launchpad designer is the admin environment for SAP Fiori UX.

00:03:48 Administrators would log into the launchpad designer to configure tiles, groups, or catalogs

and then transport them to target systems.

00:03:56 Catalogs define the set of all tiles that users can use to personalize their home page.

00:04:02 They are repositories of available tiles and target mappings.

00:04:05 Groups provide predefined content a user sees when first accessing the homepage.

00:04:11 Groups are a subset of catalogs which contain the apps visible on the Fiori launchpad entry

page.

00:04:17 Since groups are a subset of catalogs, they do not contain any target mapping.

00:04:22 After configurations are completed in the launchpad designer,

00:04:26 admins would then communicate the various tile instances, catalog names, and group names

to the PFCG administrator

00:04:33 so that the tiles, catalogs, and groups can be assigned to roles for users to access.

13

00:04:39 This slide details how to add a catalog, but the process is exactly the same for groups.

00:04:44 On the left-hand side you can see a list of all your catalogs and groups, depending on which

tab you're on,

00:04:50 and at the bottom of the list you'll see a plus icon which you can choose to add a new catalog

or group.

00:04:56 Upon choosing that button, a popup will appear asking if you're adding a standard catalog or a

remote catalog

00:05:02 and then it will ask for the title and the ID.

00:05:04 If you choose to add a remote catalog, there is additional information you will need to add,

00:05:09 such as the remote ID, the system alias, and the base URL.

00:05:13 Once a catalog is added, you can add tiles to the catalog, which we'll discuss on the next slide.

00:05:19 On the right side of this screen, you can see an image for deleting a catalog.

00:05:23 You simply highlight and drag the catalog you want to delete and you'll see two popup icons:

00:05:28 a red trash can for deleting, and a blue copy icon for copying a catalog.

00:05:33 Let's say that you might want to adapt a predefined catalog delivered by SAP. You can easily

achieve that using the copy feature.

00:05:42 Once you have your catalog created, you're ready to add target mapping and app launcher

tiles to it.

00:05:47 This screen shows you how to add a target mapping tile.

00:05:50 If you create a new catalog, the catalog will be empty with the exception of a square tile with a

plus sign in the middle.

00:05:57 Choose this tile and you will see options for adding app launchers and target mapping.

00:06:02 Choose Target Mapping and notice a target mapping tile in your catalog.

00:06:06 Choose this tile to add further target mapping details.

00:06:10 Target mapping tiles have three categories of information: Intent, Target, and General.

00:06:18 In the Intent section, you need to specify a semantic object, which is a business entity such as

a customer, sales order, or product.

00:06:25 SAP ships semantic objects and you can choose one from the dropdown list.

00:06:30 Next enter an action. An action is the operation that is to be performed on the semantic object

when a user clicks the tile.

00:06:37 An example would be display.

00:06:39 In the Target category, enter the launchpad role, instance, application alias, and application ID

that we entered in transaction LPD_CUST.

00:06:49 It is important to note that the launchpad designer is case-sensitive; the values need to match

the back-end data exactly.

00:06:57 In the General category, you can enter important or helpful comments or dependencies in the

14

Information field.

00:07:04 Form factors are a new feature and they allow you to specify which devices you would like the

apps to work on.

00:07:10 For example, if you only select Desktop, then users won't see that app on their mobile device

or tablet.

00:07:16 You can also specify parameters here if you wish.

00:07:20 When you're finished save your entries.

00:07:23 Next you'll need to add an app launcher tile to your catalog.

00:07:26 There are four app launcher tile types:

00:07:28 a static tile, which shows predefined static content,

00:07:32 a dynamic tile, which shows numbers that can be read dynamically,

00:07:36 a news tile, which is an app that displays news feeds, and then a KPI tile.

00:07:42 The KPI tiles are configured a little differently, and in a later unit this week Daniel is going to

discuss with you how this works.

00:07:49 To add an app launcher tile, you choose the tile with the plus sign in the middle

00:07:53 same as we did for target mapping, except this time you choose the app launcher tile of your

choice.

00:07:59 This will add a blank app launcher tile to your catalog that you will choose to make further

configurations.

00:08:05 The example in these slides are of a static tile for an employee's leave requests.

00:08:11 On the app launcher tile, there are only two categories: a General category and a Navigation

category.

00:08:17 In the General category, enter a title. This is what is going to be displayed to end users as the

tile name.

00:08:24 You can also enter a subtitle if you choose, but this field is optional.

00:08:28 Keywords is another optional field. If you chose to enter keywords, these are the search terms

users can use to find the app in their launchpad.

00:08:36 Next, choose an icon. You can click the icon in the Icon field for a full list of choices.

00:08:42 Finally, you can add additional information in the Information field if you choose.

00:08:46 In the General field, make sure to use sematic object navigation unless you want to specify a

separate URL.

00:08:54 For the example, in this slide we're going to use the semantic object navigation we established

in the target mapping tile.

00:09:00 Enter the semantic object. This needs to be exactly the same as what you entered in the target

mapping tile.

00:09:06 Same goes for the action. If you want to enter additional parameters, you can do so here.

15

00:09:11 For target URL, if you're using semantic object navigation, this will automatically be generated

when you save your entries.

00:09:19 If you're not using semantic object navigation, then you would enter your target URL here.

00:09:25 We just covered a simple example in the launchpad designer.

00:09:29 The final step would be to assign roles to users. You would do this using role maintenance,

transaction PFCG.

00:09:36 Enter the role you want to assign and if it doesn't exist, create a new role.

00:09:40 On the Menu tab, select the Insert Node pushbutton and choose Catalog,

00:09:44 or if you're assigning a group, you would choose Group.

00:09:47 A popup will appear prompting you for a catalog provider.

00:09:50 In our example, we would want to choose the Fiori launchpad catalogs.

00:09:55 Then you would enter the catalog ID.

00:09:57 You can use the icon next to the Catalog ID field to search for your catalog.

00:10:01 When you're finished, follow the same steps we have used throughout this configuration week

to assign users to the catalog or group.

00:10:08 This now completes unit 5.

00:10:10 In the next unit, you will have the opportunity to get some hands-on experience with an

optional exercise focused on configuring tiles in the Fiori launchpad.

16

WEEK 3, UNIT 6

00:00:00 Hello and welcome to week 3, unit 6

00:00:15 an exercise that shows you how to configure your SAP Fiori app in the Fiori launchpad.

00:00:20 Like all exercises in this course, this is optional and not required for the Record of

Achievement.

00:00:26 If you are interested in doing this exercise, we will go through the entire launchpad

configuration process that I have talked to you about in the last unit.

00:00:34 We will start by navigating to transaction LPD_CUST where we will create a new launchpad

and then create new applications for it.

00:00:41 We will access the launchpad designer where you will create a new catalog, add target

mapping and app launcher tiles.

00:00:48 From there we will go to transaction PFCG to assign user roles and finally you will be able to

see your work in the Fiori launchpad.

00:00:55 If youre interested in this exercise you can access the how to guide from the link in the pdf

version of the slides or directly from here.

00:01:03 Have fun!

17

WEEK 3, UNIT 7

00:00:12 Hello and welcome to week 3 unit 7: Introduction to SAP HANA extended application services

(or HANA XS engine for short).

00:00:22 In this unit, I'll be talking to you about the necessary configuration steps that need to be taken

for the analytical app type in SAP HANA.

00:00:30 In addition, I will review with you the components of SAP HANA that SAP Fiori UX analytical

apps leverage.

00:00:38 We reviewed this architecture in the first week, but for cohesiveness we'll discuss it in more

detail now.

00:00:44 For all the SAP Fiori analytical app types, you need to have SAP HANA as the underlying

databaseno exceptions.

00:00:52 Unless you're just joining this course now, I'm confident this fact is clearly understood.

00:00:58 The analytical app types use what we call a two-tier architecture, which means users exist

directly in SAP HANA,

00:01:05 therefore logging directly into SAP HANA.

00:01:08 You can see from this image that the XS engine is a part of SAP HANA, and not a separate

entity.

00:01:14 The SAP XS engine is a lightweight application server in SAP HANA

00:01:19 which replicates the data from the back-end server and then remodels it using virtual data

models, or VDMs for short.

00:01:26 It was an easy decision to leverage the HANA XS engine when developing analytical Fiori

apps

00:01:32 because the application server is built into and included with SAP HANA.

00:01:37 The VDMs act as a data provider by providing structured representation of SAP HANA

database views.

00:01:45 The virtual data models are deployed with SAP HANA Live for Business Suite,

00:01:49 which is a prerequisite for analytical Fiori app types.

00:01:53 The app content provides filters and views, as well as additional data for the products running

on the SAP HANA server.

00:02:01 The non-smart Fiori analytical apps use this framework.

00:02:04 In the ABAP front-end server, you can see there is product-specific UI add-ons, which we've

discussed previously.

00:02:11 The UI infrastructure consists of design-time and runtime components,

00:02:15 and Daniel is going to talk to you in detail about modeling KPIs for smart business apps in the

next unit.

00:02:22 So why is Gateway needed in this scenario?

00:02:24 We know our data comes from the XS engine using OData as the protocol, so what is

Gateway used for?

18

00:02:30 It's used for the launchpad components. This can be a little tricky and it comes down to

terminology.

00:02:36 There is a difference between gateway components and the Gateway server (aka, the front-

end server).

00:02:41 We need Gateway because we install our front-end UI components on the Gateway server.

00:02:46 Also if you have analytical apps that provide insight to action, such as the sales order

fulfillment app, you need Gateway for the action part.

00:02:55 Let me briefly take you through an end-to-end example.

00:02:58 A user will access SAP Fiori through their launchpad.

00:03:02 They select an analytical app and that request will be sent to the Web dispatcher,

00:03:06 who will select the NetWeaver front-end server for HTTP(s) requests to load to the UI layout.

00:03:12 And then the OData call will be routed to the HANA XS engine.

00:03:16 In the XS engine, the business data is exposed through well-defined database views,

00:03:21 operating directly on the tables of the Business Suite systems

00:03:25 and transforming them into consistent and easily understandable views.

00:03:29 The data will be sent back to the Web dispatcher or reverse proxy server

00:03:33 where it will assemble the data from both the front-end server and the HANA XS engine before

exposing it to the UI.

00:03:41 I just mentioned on the previous slide that SAP HANA Live is included with Suite on HANA, but

here I want to elaborate on some more details.

00:03:49 Although it's included with Suite on HANA, SAP HANA Live is made available as a separate

package to be installed.

00:03:55 For Fiori apps, SAP HANA Live uses the integrated scenario,

00:04:00 meaning SAP HANA Live shares an SAP HANA appliance with the Business Suite system.

00:04:05 SAP HANA Live leverages virtual data models, or VDMs, to consume the Business Suite

source data without data replication, latency, or redundancy.

00:04:16 This allows for operational reporting and quick answers to ad hoc business questions.

00:04:21 A virtual data model is a structured representation of HANA database views in SAP HANA Live

for Business Suite and follows consistent modeling rules.

00:04:31 Let's talk about some advantages of HANA Live compared to regular reporting tools.

00:04:36 First, it's open. It's based on standard mechanisms such as SQL or MDX. There's no BW

modeling or ABAP programming required.

00:04:44 It's uniform in that it provides common reporting across Business Suite applications.

00:04:50 It's intuitive. The virtual data models hide the complexity and customizing dependencies of our

Business Suite data model

00:04:57 to make data available without requiring a deep understanding of SAP models.

19

00:05:03 It's fast. SAP HANA Live for Business Suite features SAP HANA as the underlying computing

engine to enable fast analytics on high data volumes.

00:05:13 And finally, the data is offered in real time. All reporting happens on primary data, or a real-

time replication of it,

00:05:20 so there is no need to wait for data warehousing loading jobs to finish.

00:05:24 The cycle time from recording to reporting is dramatically reduced.

00:05:29 Now that we better understand the SAP HANA XS engine and VDMs used by SAP Fiori UX

analytical app types,

00:05:37 we can discuss the necessary configuration steps.

00:05:40 I've said it before and I'll say it againmake sure to reference the help or best-practice guides

before going out and implementing on your own.

00:05:50 Users accessing SAP Fiori UX analytical apps require users in both the ABAP front-end server

to enable navigation in the SAP Fiori launchpad,

00:05:59 and a database user in SAP HANA to enable access to the relevant views.

00:06:04 Therefore, the first configuration step we need to take is to synchronize the SAP HANA

database users with the existing users in the ABAP front-end server.

00:06:14 To do this, SAP supports three methods.

00:06:17 The first method is user synchronization, which uses the SAP NetWeaver Identity

Management solution that's already implemented in your organization.

00:06:26 If your company has an identity management solution in place, you can leverage that to

synchronize your users as well.

00:06:33 Each solution will obviously have its own specific instructions or methods for synchronization,

00:06:39 so just know that this is an option if you have one of those solutions in place.

00:06:43 The next method is mass synchronization using ABAP DBMS user management tools.

00:06:49 There is an SAP Note that's listed in the slide that you should reference if you use this method.

00:06:56 The Note should be used as a guide, but at a high level you would select the relevant ABAP

users based on user type, user group, and ABAP authorization role,

00:07:06 and then you would select the SAP HANA roles to be assigned.

00:07:09 And then by default, the SAP HANA users will be created with the same name as the ABAP

users.

00:07:15 The third method for synchronizing users is manual user creation in SAP HANA.

00:07:22 In order to use this option, you must have the SAP HANA USER ADMIN system privilege.

00:07:27 Then you would log into the HANA studio instance and choose Security>Users. Right-click

and then choose New User.

00:07:35 You would then enter the user credentials, ensuring that the names are exactly the same as

they are in the front-end server, and then you would save your entries.

00:07:43 The image right here in this slide is of the SAP HANA studio

20

00:07:47 and it shows you what it would look like implementing the manual user creation method in SAP

HANA.

00:07:53 The second configuration task is assigning roles for accessing SAP HANA data.

00:08:00 Authorizations are defined as privileges in SAP HANA and are necessary so that the SAP

HANA XS engine can provide the data using OData services.

00:08:09 Privileges are grouped as roles ,and roles are assigned to SAP HANA database users.

00:08:15 These roles are in addition to the PFCG roles and ABAP users required in the front-end server.

00:08:21 SAP delivers a role that includes all app-specific privileges per app type.

00:08:26 Depending on the type of tile you want to use for your analytical app depends on the role or

roles you are going to need to assign for your users.

00:08:34 For example, if you want to use an app launcher tile for an analytical app, then you just need to

assign the app-specific HANA role.

00:08:42 Or if you want to use a KPI tile, then you need to assign the two generic roles in addition to the

app-specific HANA role.

00:08:51 The third configuration task is to create analytical privileges.

00:08:56 We already assigned roles to users and while privileges might indicate the same thing, they

aren't.

00:09:01 And in addition to assigning roles, we need to create analytic privileges.

00:09:06 Organizations typically restrict the specific entries or rows within the views, therefore creating

the need to define these privileges.

00:09:15 The roles define which views the user can retrieve data from, while the analytical privileges

allow access through organization-specific restrictions.

00:09:24 To accomplish this configuration step, the first thing to do is to identify and understand what, if

any, restrictions

00:09:31 your organization has placed on SAP HANA Live views.

00:09:35 From there, you can create an analytic privilege using the SAP HANA Modeler view in the SAP

HANA studio,

00:09:42 which is the image that you can see here in this screen.

00:09:46 The final configuration step for smart business apps is to model your KPIs and configure

targets for those KPIs.

00:09:54 We reviewed the modeling tiles and concept in the architecture unit in week 1

00:09:58 but in the next, unit Daniel Huber will take you through the details.

00:10:02 Modeling KPIs consists of a number of options and details to meet specific needs,

00:10:07 so we decided that although it is a configuration step, it is worth a unit in and of itself.

00:10:13 With that said, I will now conclude week 3 unit 7, Introduction to SAP HANA extended

application services.

00:10:20 This is the end of our time together.

21

00:10:22 I thank you for taking the course with me so far and wish you the best of luck as you continue

through the next three weeks.

00:10:28 You will be in the trusting hands of my very knowledgeable colleagues Daniel, Prakalp, Jamie,

and Markus. Bye!

22

WEEK 3, UNIT 8

00:00:12 Hello and welcome to week 3, unit 8: SAP Smart Business overview.

00:00:18 My name is Daniel Huber, and I am a Product Owner for SAP Smart Business.

00:00:22 I'm very excited having you here.

00:00:24 In this unit, I'm going to elaborate on the existing SAP Smart Business scenarios and SAP's

KPI modeling capabilities.

00:00:32 If you remember, back in week 1, Liz mentioned this concept to you in an overview unit and

talked about it at a high level.

00:00:40 Today, we will go deeper into the details.

00:00:44 Today, as a business user in finance, sales, or procurement, getting the information you need

at the right time is tough.

00:00:52 You have to wait, as opposed to responsive.

00:00:55 You use old data as opposed to real time.

00:00:58 You leverage generic user experience as opposed to one that is adapted to your role and your

needs.

00:01:05 Information is provided in multiple places instead of one single source of truth.

00:01:11 As a result, you struggle connecting analysis with execution.

00:01:15 This is where SAP Smart Business cockpits come into play.

00:01:18 SAP Smart Business provides new cockpits to help you drive your business through fact-

based information versus gut feeling.

00:01:27 SAP Smart Business cockpits are new cockpits including tailored key performance indicators

and graphical virtualizations

00:01:35 designed for instant insight to action in the context of SAP Business Suite powered by SAP

HANA.

00:01:41 SAP Smart Business cockpits leverage SAP Fiori design principles for a simplified yet beautiful

user experience.

00:01:50 In the last 12 months, SAP has delivered more than 14 SAP Smart Business scenarios with

more than 100 key performance indicators

00:01:58 for key business roles like project managers, cash managers, purchasing managers, and many

more.

00:02:04 And we are continuously delivering new scenarios.

00:02:08 SAP Smart Business cockpits are responsive.

00:02:11 They are bringing together transactions and analytics to close the gap between insight and

action.

00:02:17 They are personalized, offering personalized, role-based, tailored KPIs, actionable insights,

news feeds, and role-specific tasks.

00:02:27 They are seamless, delivering the same real-time insights and user experience across

23

desktops, mobiles, and tablets.

00:02:35 And they are beautiful, combining simplicity, ease of use, and powerful functionality

00:02:41 over completely reimagined user experience.

00:02:47 Basically, SAP Smart Business has a runtime mode which is used by the end user,

00:02:51 and a design time to define all the KPI content.

00:02:55 In the next minutes, I'd like to give an overview of the eight KPI modeling apps SAP provides

for business users and data analysts.

00:03:03 There are apps to create KPS and evaluations.

00:03:06 SAP delivers standard key performance indicators; however, we understand they may not

meet all needs of our customers.

00:03:14 Therefore we created simple apps that walk you through creating your own KPI definitions and

evaluations.

00:03:20 Evaluations allow you to define filters, targets, and threshold values related to your KPI.

00:03:25 Furthermore, there are apps to define the visual aspects of your KPI.

00:03:29 Configure KPI Drill-Down helps you to define the drill-down possibilities from a KPI into the

details.

00:03:36 With this app, you can apply virtualizations in the form of charts or tables.

00:03:40 The drill-down configuration can be defined by simple configuration.

00:03:44 With Configure KPI Tiles, you can configure the tile virtualization based on predefined tile

templates.

00:03:50 In addition, we are providing other apps tailored to specific activities, like Manage KPI as

Authorizations

00:03:57 to define authorizations and access rights, Manage KPI Associations to define relationships

among KPI tiles,

00:04:05 the KPI Workspace, which is a dedicated workspace where you can display and manipulate all

your KPI content,

00:04:12 and a migration tool that allows you to easily migrate existing KPIs from an earlier SAP Smart

Business version to the new data model.

00:04:22 In this presentation, I am going into detail about how to create KPI evaluations,

00:04:27 configure KPI tiles and KPI drilldowns, and manage authorizations.

00:04:32 In addition, I'll show you how to add these tiles to your Fiori launchpad after KPI configuration

is completed.

00:04:41 The first step is to create a KPI definition.

00:04:43 From a process perspective, a business user can maintain all metadata of the KPI, save the

draft, hand it over to a technical user administrator

00:04:52 to define the data source information.

24

00:04:54 As soon as all information is maintained, you can save and activate a KPI.

00:05:00 First you need to enter a KPI ID, title, and description.

00:05:03 The ID is a unique identifier. Please do not use the SAP namespace for the ID.

00:05:09 The title is shown on the KPI tile and can be maintained in multiple languages.

00:05:14 As a goal type, you can choose between minimizing, maximizing, and a specific target range.

00:05:19 For instance, for a KPI like company revenue, you would choose maximizing.

00:05:24 The higher the revenue, the better for your company.

00:05:28 As optional values, you can maintain the name, ID, and e-mail address of the KPI owner,

00:05:33 and any properties that help to identify and search the KPI later on.

00:05:39 In the section Data Source, you can select an SAP HANA Live view, OData service, entity set,

and measure.

00:05:44 However, SAP Smart Business is very, very flexible.

00:05:47 As an alternative to an SAP HANA Live query, you can use any OData servers as a data

source

00:05:53 that is compliant with SAP specification for OData for analytics.

00:05:58 The semantic object is an optional entry and can be used for navigation targets other than the

standard drill-down.

00:06:08 As a next step, we will create a KPI evaluation. A KPI can have multiple evaluations.

00:06:13 The evaluation defines the parameter, filters, and threshold values for the KPI.

00:06:19 The first step again is to maintain the evaluation ID, title, and description.

00:06:23 The title will be shown in the second line of the KPI and can be maintained in multiple

languages.

00:06:30 For targets, thresholds, and trends, you can either define static values or measures.

00:06:34 Using a measure is very, very powerful if you like to compare, for instance, the current revenue

with last year's revenue at this time.

00:06:42 The values for critical warning and target define when the KPI turns red, green, or yellow.

00:06:48 You can activate the evaluation by pressing Save and Activate.

00:06:52 Furthermore, you can directly navigate to the tile virtualization configuration from this screen.

00:07:00 In the first steps, we have defined basic data for the KPI. Now let's choose a nice tile

virtualization.

00:07:06 SAP provides a set of predefined tile templates.

00:07:09 You can choose between a simple numeric tile, a comparison tile, a trend tile, or a tile

comparing your actual value versus the target value.

00:17:17 It's really simple and straightforward to define your personalized tile virtualizations.

00:07:22 You simply need to select a tile type at the top and select Save and Activate.

25

00:07:28 Furthermore, this is the place where you could maintain alternative drill-down options,

00:07:32 for instance, if you like to navigate to an SAP Lumira storyboard instead of the standard KPI

drill-down.

00:07:42 Now let's look into the drill-down configuration.

00:07:45 With the application Configure KPI Drill-Down, a user can define or change the KPI drill-down

configuration

00:07:51 for a specific KPI in a very nice and efficient way.

00:07:54 The app provides you the possibility to edit and define filters, change the microcharts in the

header bar, or configure the KPI drill-down.

00:08:02 So in general, you can adapt nearly all screen elements of your KPI drill-down based on simple

configuration steps.

00:08:12 Let's look into the chart definition. This is very easy and straightforward.

00:08:16 As a first step, you define the dimensions and measures you like to use for the chart.

00:08:20 Please be aware that some chart types, like bubble charts, need more than one measure.

00:08:25 In the second step, you can define advanced attributes like sort order or stacking in case you

like to use a nice stacked bar virtualization.

00:08:34 Afterward, you define a chart type, access definitions, and colors.

00:08:37 SAP Smart Business supports some nice predefined chart types like bars, columns, lines,

combinations, or bubble charts.

00:08:46 Finally, you can define an ID and name for your view.

00:08:48 If you have nice data in the system, you can now directly switch to the runtime mode and see

your result.

00:08:55 Or you can get a simulation based on dummy data.

00:09:01 Now we went through all the required applications to define all the KPI metadata and

virtualizations.

00:09:06 As a final step, I'd like to talk about authorizations.

00:09:09 SAP provides multiple levels for authorizations, for instance, on data level or on specific

functionalities.

00:09:16 I'd like to concentrate on the KPI authorizations.

00:06:19 If you want to avoid that everybody sees and opens a specific KPI, like current revenue of your

company,

00:09:26 you can restrict access on specific users or user groups.

00:09:31 You can simply search for a specific user or user role, assign them to the KPI, and as soon as

you save the KPI authorizations, they are activated.

00:09:43 Now it's time to look at a result in the Fiori launchpad.

00:09:45 As you learned in one of the earlier units, the Fiori launchpad provides role-based access to all

your KPIs and applications.

26

00:09:53 You can open the Groups menu and create your own group to structure the different the KPIs.

00:09:59 Afterward, you can open the Tile Catalog, search for your KPIs, and add the required tiles

simply by pressing the plus icon

00:10:07 below the tile and selecting the target group for the tile.

00:10:10 As soon as you go back to your home screen, your first KPI is available in the Fiori launchpad

with real-time data from SAP HANA.

00:10:19 Furthermore, you will notice that the KPI color will automatically change based on the

threshold values

00:10:24 we have defined earlier as soon as the KPI becomes critical.

00:10:28 In this case, you can simply click on the KPI to analyze it further and take actions.

00:10:34 Now let's go into a demo.

00:10:36 I'd like to show you how you can create all required information for a nice KPI in around about

five minutes. Let's see if this works.

00:10:45 So what you can see here is the Fiori launchpad.

00:10:48 I'm currently the marketing manager, and you can see here some predefined KPIs like

Marketing Spend,

00:10:54 Marketing-Generated Sales Pipeline, Spend Analysis, and many more

00:10:59 like Sentiment Media Mix, Contact Conversion.

00:11:03 We are providing a whole set of KPIs and KPI definitions.

00:11:07 And you can also see based on threshold values that the KPIs have different colors.

00:11:14 So green indicates that everything is okay. Red tells me that I need to look into this in detail.

00:11:21 So first thing I want to do is I want to open the KPI Workspace and create a KPI definition.

00:11:29 The Workspace is the possibility to see all your KPI definitions and all other metadata directly

in a very nice and intuitive workspace.

00:11:39 So here I have a KPI definition like Marketing Spend.

00:11:43 And I just want to Duplicate that. So I create a KPI with a template.

00:11:49 I give it a specific name.

00:11:58 And I enter a title.

00:12:09 We already mentioned those things like goal type where you can define if you have minimizing,

maximizing, or a range.

00:12:16 In this case, I select a range.

00:12:18 I want to have below a specific level, for instance, 300 million,

00:12:14 but on the other side if I do not have any marketing spend, I probably do not sell my products.

00:12:30 Here's the data source information, and I just copied this over from the other KPI.

00:12:35 In the next step, let's say Activate and Add Evaluation.

27

00:12:39 So as I mentioned before, the evaluation helps you define filters and thresholds.

00:12:50 I need to enter an evaluation ID, and the evaluation title would be This year, for instance.

00:12:57 I want to analyze the marketing spend this year.

00:13:04 What you can see here is the area for input parameters and filters.

00:13:07 This shows me all the input parameters and filters that are required by the OData service.

00:13:13 In this case, I select year offset as 0, because I want to have the information from this year.

00:13:19 In this area, I have the threshold values and trends and targets. So as a target, I want to enter

200 million.

00:13:27 I could also enter additional information for critical low, critical high, warning high, and warning

low,

00:13:32 or I could use measures, for instance, compare to last year.

00:13:37 I just enter the target in this case

00:13:41 and as a next step, I activate the KPI evaluation and add a tile.

00:13:47 As I mentioned before, SAP provides predefined tile templates. You see them at the top.

00:13:52 So here's, for instance, a very nice numeric tile.

00:13:56 There is a tile showing me the comparison of different countries.

00:14:01 There is a tile showing me the trend over time, for instance.

00:14:06 And there is a tile which compares my actual versus the target value.

00:14:10 Let's start with a simple tile like a simple KPI tile showing just a number.

00:14:19 So now we did everything that is required to have a KPI defined and virtualize it in the Fiori

launchpad.

00:14:27 The only thing I want to do now as a final step is I want to configure a KPI drill-down. A very

nice KPI drill-down.

00:14:35 So we have some

00:14:41 virtualization and I can directly go into the details of the drill-down.

00:14:47 So here you see the KPI I just configured.

00:14:50 And with Configure, I can define the virtual aspects of the KPI drill-down. For instance, I can

add a chart.

00:14:59 Well the chart configuration is pretty simple and straightforward, as I already mentioned.

00:15:03 I can select where the data is coming from and what data I want to virtualize, like the actual

revenue,

00:15:09 the target revenue, and the actual spend.

00:15:11 I can, in addition, define which dimension I want to see as an x-axis, like the region description.

00:15:20 Just press OK. I would prefer to have bars instead of columns.

28

00:15:26 You can directly see the result on the right-hand side.

00:15:30 And I just define a name and an ID.

00:15:47 And that's everything I have to do.

00:15:50 In addition to that, I can also create some nice tile virtualizations and microcharts.

00:15:57 So I can select, for instance here, different microcharts I want to see at the top.

00:16:02 And as soon as I press Save,

00:16:06 I see the result I've just created in a WYSIWYG editor and I can directly see the result later on

in the Fiori launchpad.

00:16:16 So now you saw how easy it was to create a KPI definition, a tile virtualization, a drill-down

virtualization.

00:16:24 Now let's add the new KPI to my Fiori launchpad.

00:16:39 And there it is.

00:16:40 This is the KPI we just have defined in the last steps.

00:16:45 So it shows you directly the values coming from SAP HANA in real time.

00:16:49 I can click on it and I see the nice KPI drill-down I have just configured with all the microcharts.

00:16:57 I see the different information here.

00:17:01 And I have different bars here showing me the target revenue, the actual spend, and the actual

revenue.

00:17:06 And a pretty nice result, from my perspective.

00:17:12 Thanks a lot for watching the demo.

00:17:14 This now concludes week 3. I hope you enjoyed the session.

00:17:18 Next week, Prakalp will guide you through the topic Securing SAP Fiori User Experience.

www.sap.com

2014 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://www.sap.com/corporate-en/legal/copyright/index.epx#trademark 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 SEs 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.