openSAP

Key Technical Topics in a System Conversion to

SAP S/4HANA
Week 2 Unit 1

00:00:06 Hello, and welcome to week two of this openSAP training. I hope you're having a good time
while learning.
00:00:13 My name is Jorge Baltazar. I am a User Experience Consultant from Latin America,
00:00:18 and I will be your host for this week's first session titled SAP Fiori Overview.
00:00:23 I am sure most of you have already heard about SAP Fiori and may even already had some
implementation experiences.
00:00:30 However, I'd like to start with the most basic concepts around SAP Fiori to set the basis
00:00:35 for the contents of this week. So let's start with the obvious question, what is SAP Fiori?
00:00:44 Some say it is only a development paradigm. Others consider Fiori to be only a collection of
apps,
00:00:50 while others believe it is just a set of fancy color schemes for SAP GUI transactions.
00:00:56 All these statements could be true, but there are a couple of important aspects
00:01:00 to properly define SAP Fiori. SAP Fiori is the design language for all SAP products.
00:01:08 It applies modern concepts and design principles, enabling users to get the job done easily
00:01:14 and have a delightful experience. Amongst the design principles,
00:01:18 we can highlight the following: Role-based. This means SAP Fiori is designed for your
business,
00:01:25 your needs, and how you work. Adaptive. Allowing you to work how and where you want,
00:01:31 regardless of the device you use. Simple. With SAP Fiori, you can complete your job
intuitively,
00:01:38 which helps you to focus on what is important. Coherent. Whether you fulfill a sales order,
review your latest KPIs,
00:01:46 or manage leave requests, SAP Fiori adheres to a consistent interaction and visual design
language.
00:01:53 And delightful, which means that apart from making you work smarter, SAP Fiori also enriches

00:01:59 your work experience by allowing you to simply do your job. But this is just one part of the
definition of Fiori.
00:02:08 In order to fully define what SAP Fiori is, we also need to mention the fact that SAP Fiori
00:02:14 relies on three dimensions in order to take advantage of the design principles.
00:02:19 The first dimension is people, as SAP Fiori is a user-centered solution.
00:02:25 The second dimension is business, as SAP Fiori enables simplification, digitalization,
00:02:31 and allows for innovation in business processes. And the third dimension is technology,
00:02:37 as SAP Fiori takes the most out of web and open standards to take advantage of the main
technologies in SAP HANA
00:02:44 through a service-oriented architecture. So, in summary, we can say that SAP Fiori
00:02:50 is a collection of modern design principles, based on people, business, and technology,
00:02:56 to help SAP users work smarter. Now that we have aligned our understanding of SAP Fiori,
00:03:03 we need to answer a second question. Why do we recommend SAP Fiori in SAP S/4HANA
projects?
00:03:11 There are multiple answers to this question, but let's try what I believe is the simplest one.
00:03:17 The same way humans and animals evolve, systems will evolve. We've been through a long
way since R/2, R/3, ECC,
00:03:25 and although SAP offered multiple technological advances, these were never really tangible
for business users.
00:03:33 This is where SAP Fiori fits best, as it brings the innovations of SAP S/4HANA
00:03:38 to the business users in a real and tangible way. And Fiori brings these innovations by
leveraging the benefits
00:03:47 from SAP S/4HANA and the Intelligent Enterprise. You will be asking: How does Fiori achieve
this?
00:03:54 Let's imagine you want to generate a new business model in your company leveraging
machine learning
00:03:59 and IoT technologies. I'm sure you wouldn't want to see the results
00:04:03 of your high-end algorithms in an old-fashioned ABAP report. You would definitely prefer a
simple and engaging
00:04:10 screen report that shows you your algorithm results. By using simpler and engaging designs,
C- levels, end users,
00:04:18 and anyone in your company will reach the same understanding on the data shown by your
algorithms.
00:04:24 This is the innovation Fiori can bring for you and your company.
00:04:30 The next obvious question would be where is SAP Fiori aiming as a solution?
00:04:37 It is important to note that SAP Fiori has also evolved, and most of this evolution has occurred

00:04:42 thanks to SAP S/4HANA. In the early days, Fiori only covered
00:04:47 the 25 most important processes in Business Suite. And now SAP's offering more than 10,000
apps,
00:04:54 including several technologies like SAPUI5, SAP GUI for HTML,
00:04:58 and Web Dynpro ABAP in SAP S/4HANA systems. Additionally, starting with S/4HANA 1709,

00:05:06 SAP is delivering top-notch content like SAP CoPilot to integrate Conversational AI
technologies into Fiori.
00:05:13 And with the upcoming release of S/4HANA, you will also find the release of SAP Fiori 3,
00:05:19 which aims to deliver simpler user interfaces, and standardize the design of all SAP solutions.

00:05:27 Before we finish with this session, I would like to explain the main purpose of the content
00:05:32 to be exposed during this week. And this is understanding and eliminating the myths
00:05:37 around the implementation of SAP Fiori in SAP S/4HANA projects.
00:05:45 The first myth is that SAP Fiori requires a complex architecture in order to have it working
properly.
00:05:52 So we will have Jocelyn Dart explaining the new architecture recommendations
00:05:56 and adoption best practices for SAP Fiori in unit two. The second myth is based on the idea
that Fiori
00:06:04 is a complex solution to configure, and requires high implementation efforts.
00:06:08 Hannes Defloo will join us in unit three with a brief explanation of the new activation approach
00:06:13 for Fiori apps called SAP Fiori Rapid Activation, which, believe me, will help you configure SAP
Fiori
00:06:20 in a simpler and more reliable way. The third myth is that all security-related settings
00:06:27 are complex and difficult to set up. Peter Nechala will be providing some recommendations

2
00:06:33 for building catalogs, groups, and roles in unit four. The fourth myth is that Fiori offers limited
functionality
00:06:42 and it is a headache to troubleshoot any issue with the Fiori applications.
00:06:47 Jocelyn Dart will be back in unit five to explain some of the SAP Fiori launchpad special
features,
00:06:52 and basics on content troubleshooting. The fifth myth is that, in general,
00:06:59 Fiori performance is extremely poor. I will come back in unit six and explain the basics
00:07:04 on Fiori launchpad performance. And the last myth is that Fiori does not really offer
00:07:10 any tangible innovations to the business. To clear out this myth, we will have Gilbert Wong
00:07:15 providing an overview on SAP CoPilot and its architecture in the final unit for this week.
00:07:23 As you can see, there is a lot of exciting and interesting content for this week,
00:07:27 and we hope you enjoy it to the fullest. For the next session,
00:07:30 please join my colleague and friend, Jocelyn Dart, as she goes through the new architecture
recommendations
00:07:36 and adoption best practices for SAP Fiori. Thanks for watching and hope to see you soon.
00:07:42 All the best.

3
Week 2 Unit 2

00:00:05 Welcome back to week two, User Experience in SAP S/4HANA.

00:00:10 My name is Jocelyn Dart, and I am a User Experience Strategist
00:00:14 with the SAP S/4HANA Regional Implementation group. In this unit, we will go through some
SAP Fiori
00:00:20 architecture and adoption best practices to get you started. You will deep dive into a few of
these topics
00:00:27 in subsequent units of this week. The first aspect you need to understand
00:00:33 is the architecture for your Fiori for S/4HANA Frontend Server.
00:00:37 There's a tightly coupled relationship between the version of your S/4HANA system
00:00:42 and the version of your Fiori for S/4HANA Frontend Server. So with SAP S/4HANA embedded,
shown here in the middle,
00:00:50 is the recommended deployment mode. That means the Frontend Server software
components
00:00:54 are installed directly on the S/4HANA server. Notice how this is a cloud-first approach,
00:01:01 and aligns closely to S/4HANA Cloud, the multitenant edition,
00:01:05 which is shown here on the left. While hub mode, shown here on the right, is still possible,
00:01:11 embedded mode brings several advantages, including better performance, easier
configuration,
00:01:16 and better tooling to minimize efforts such as Fiori rapid content activation.
00:01:22 If you intend to have multiple S/4HANA productive systems in your landscape, then embedded
is near- essential.
00:01:29 You can find out more about your options in the document SAP Fiori Deployment Options
00:01:34 and System Landscape Recommendations. Don't forget to adjust the size of your servers
00:01:41 depending on which modes you choose. If you intend to access your Fiori apps
00:01:47 from a device or over the Internet, you will need to consider your security setup.
00:01:51 Security is a very deep topic, way beyond the scope of this course.
00:01:56 There are lots of considerations around what security layers and network zones you include.
00:02:01 Where you put your firewalls, and what authentication and access mechanisms
00:02:04 you use from your devices. For instance, you might decide to use a VPN tunnel,
00:02:09 apply Network Edge Authentication in your firewalls, and use an encrypted network
connection.
00:02:15 Here you can see a high-level representation of some of your options.
00:02:19 The most consistent recommendation is to place your web dispatcher in your demilitarized
zone.
00:02:25 Your web dispatcher acts as a reverse proxy controlling the routing to your internal systems,
00:02:30 and can be configured to only pass authenticated requests. You might even want to have
separate web dispatchers
00:02:36 for Internet and intranet usage. For more information, you should check out the blog
00:02:41 Considerations and Recommendations for Internet-facing Fiori apps,
00:02:45 and the SAP Best Practices guide, SAP S/4HANA Fiori Advanced Network
00:02:50 and Security Configuration, which you will find referenced in the blog.
00:02:57 When it comes to accessing Fiori from your work desktop, most users will simply use a web
browser.
00:03:03 Fiori supports most HTML5-compliant web browsers, including Chrome, Firefox, Microsoft
Edge,
00:03:09 Internet Explorer 11, and Safari. Check the browser and platform support section

4
00:03:14 in the SAP UI5 Software Development Kit documentation for version details.
00:03:19 The behavior and performance of your apps can be affected by your choice of web browser,
00:03:24 your web browser version, and your web browser settings. Make sure you check the advice for
your browser settings
00:03:31 in SAP Note 2447857. When using a web browser,
00:03:37 any tiles that launch SAP GUI transactions will launch by default in SAP GUI for HTML
00:03:44 with the Fiori visual theme applied. This means you don't need any client footprint
00:03:49 on the desktop other than your web browser itself. If you have a large number of existing,
00:03:55 heavily invested SAP GUI for Windows users, and you don't mind some client footprint,
00:04:01 a good alternative can be to use the latest version of SAP Business Client with the Launchpad
Connection option.
00:04:09 This runs your Fiori launchpad within the Business Client frame,
00:04:12 and any tiles that launch SAP GUI transactions will automatically launch in SAP GUI for
Windows.
00:04:19 So let's see this now. Okay, so this is a desktop,
00:04:23 and I'm just using the Desktop icon to launch up Business Client,
00:04:28 and here I just log in as if I was logging into a system, but you see here I've come into the
launchpad
00:04:34 in the Business Client frame. We can tell the Business Client frame
00:04:38 has some slightly different options, and one of them, for instance, is to use a Chromium
browser.
00:04:44 Okay, so it's just going to restart. You'll see here, it is very close to the desktop,
00:04:50 the launchpad that you get in the browser. We've got our notifications.
00:04:54 We can open Fiori apps, in this case, our procurement overview page that we like so much.
00:05:00 And we can navigate around here quite naturally, just as we were doing, we've done
elsewhere,
00:05:06 using the normal navigation, so it's all very similar to running it in the browser. Okay.
00:05:15 When we want to open up a classic app, we can do that, so here we're using related apps,
00:05:22 just as we would in the browser, but we're going to a GUI transaction,
00:05:26 and instead of opening in GUI for HTML, it's now opening it in GUI for Windows
00:05:30 within the Business Client frame. And there we are, and we can tell here
00:05:34 that we're actually in GUI for Windows. Okay, while on the desktop, a web browser is
sufficient.
00:05:43 When accessing Fiori on a mobile device, it may not be enough.
00:05:47 If you want to use native device features such as the camera to add an attachment,
00:05:51 bar codes, and push notifications, then you need a container app.
00:05:56 Using a container app also improves performance on devices via caching.
00:06:00 The recommended container app is SAP Fiori Client, which is provided free of charge on
Apple App Store,
00:06:07 Google Play Store, and the Microsoft Store. You can even configure and theme SAP Fiori
Client,
00:06:12 for example to present your company theme, Fiori Launchpad URL,
00:06:18 and preset your single sign-on settings. If you need to build or extend Fiori apps
00:06:23 to use advanced native features, such as GPS, voice recording, or offline apps,
00:06:29 then you will usually need to subscribe to and incorporate SAP Cloud Platform Mobile Services

00:06:35 in a mobile, web, hybrid, or native app. Okay. Once your architecture is set up
00:06:45 and your software components are installed, you will need to activate your Fiori apps.

5
00:06:50 The quickest and most efficient way to activate apps is using rapid content activation task lists.

00:06:56 These can save you up to 90% of the effort of activating your apps.
00:07:02 A lot of the effort is saved simply because rapid content activation
00:07:07 guides you to activate whole SAP business roles. A business role represents the type of work
a user does.
00:07:15 For example, accounts payable accountant, cash manager, strategic buyer, warehouse
technician.
00:07:21 Each business role contains a collection of best-available Fiori apps,
00:07:25 and classic user interfaces for that role, and all the logical connection points between them.
00:07:32 By activating the holistic role, you avoid broken app-to-app navigations,
00:07:37 and you get to explore how the apps are intended to work together.
00:07:41 That's the best starting point for your fit-gap analysis. If you have decided to deploy your Fiori
server in hub mode
00:07:49 you can still use the older task list to activate your apps and you can still choose to activate
00:07:54 all apps for a role together. You should also check the SAP Notes
00:07:59 provided with the Fiori rapid content activation for pre- and post-activation activities
00:08:04 for each role to minimize missteps. Once you have completed fit-gap analysis,
00:08:12 you may need to refine which apps are assigned to which role, and adjust the app-to-app
connections.
00:08:20 You can even refine which apps in app-to-app navigations are available
00:08:24 on different device types. You do this by adjusting the Fiori launchpad content,
00:08:30 and then assigning it to your customized business roles. You adjust the launchpad content
using catalogs.
00:08:38 Technical catalogs are collections of original tile definitions and target mappings.
00:08:43 A tile definition controls the text and icons on the tile. A target mapping contains the reference
to the app ID,
00:08:50 the device types in which it can be used, and the parameters passed to the app
00:08:54 during app-to-app navigation. Tiles and target mappings are logically linked
00:08:59 using a semantic object such as Purchase Order, Cost Center, Customer, and an action,
00:09:04 such as Display, Edit, Manage, Approve. You create a custom technical catalog
00:09:09 on the CONF, client-independent, scope if you need to add new tiles or add new target
mappings.
00:09:15 For example, you can copy and override the tile text on an SAP tile,
00:09:19 add custom apps you want to launch, or pass additional parameters during app-to-app
navigation.
00:09:25 Gather up all the related tiles and target mappings you want to assign to a business role
00:09:29 using business catalogs. Business catalogs are a reuse layer
00:09:34 usually created on the CUST, client- development, scope. Client-dependent scope, sorry.
00:09:39 They reference the original tiles and target mappings in the technical catalogs.
00:09:45 Business roles are technically security roles, which you can maintain in transaction PFCG.
00:09:51 Business roles pull together all of the business catalogs to be assigned to a user.
00:09:56 A single user can be assigned to multiple business roles, if needed,
00:09:59 and then they just get all the apps assigned to those roles. Once you have decided which apps

00:10:05 will be assigned to which business roles, then there's one very important last step
00:10:10 needed to ensure good user adoption. You need to look at your Fiori launchpad Home page

6
00:10:15 from the perspective of your business user. Since you probably don't share the same business
role,
00:10:22 it's a good idea to involve a couple of your business users who perform that actual role to help.

00:10:27 After all, they are the real experts in what they do. Introduce them to the Fiori launchpad,
00:10:32 show them the Home page, the App Finder, some of the personalization options,
00:10:36 so they have a general idea of what's possible on the launchpad. Then work out with them how
they want their apps organized
00:10:43 as tiles and links on the Home page on day one. You should only look to put their most
frequently used
00:10:50 tiles and links on the Home page, apps they use every day or every week.
00:10:54 Any others will be in the App Finder, where they can be accessed using the Fiori search,
00:10:59 the Home button, All My Apps navigation, or the App Finder catalog.
00:11:03 Do not overload the Home page. You can then create tile groups
00:11:08 to match what they want in the Fiori launchpad designer, and assign those to their business
roles
00:11:13 as their default Home page. Since apps can be assigned to a group
00:11:17 from any and multiple catalogs, your users are free to organize
00:11:21 their tiles and links however they wish. From S/4HANA 1909 and Fiori 3,
00:11:27 you will also be able to show cards on the Home page. Consider how you will include those in
your design.
00:11:34 The things to keep in mind here are focused and concise, keeping the user's attention on their
job.
00:11:42 Regardless of which apps or classic UIs are assigned to users,
00:11:46 all business users can benefit from native Fiori in S/4HANA features,
00:11:51 particularly Fiori search, notifications, and default values.
00:11:57 These are an important part of the overall user experience and need to be turned on early,
00:12:02 so functional business experts can include them into their fit-gap analysis.
00:12:07 Just like Fiori apps, these need to be activated. However, there's a little bit more to turning
these on,
00:12:13 so we will cover these in unit five on special launchpad features.
00:12:18 There's also a number of optional features you should consider.
00:12:21 User assistance, the out-of-the-box Fiori launchpad and Fiori app help content.
00:12:26 Contact support, which raises a support ticket via SAP Solution Manager or your own custom
ticketing system,
00:12:32 Give Feedback, which sends feedback from end users directly to SAP, and you can also ask
for a copy,
00:12:37 and SAP CoPilot, for collaboration, chatbot-based skills, and self-learning.
00:12:43 It's a good idea to also configure Fiori app My Inbox centrally,
00:12:48 as that typically collects work from multiple business processes.
00:12:53 Finally, you can configure your launchpad to adjust the overall behavior
00:12:57 using configuration parameters. These can be configured globally,
00:13:01 or adjusted for specific business roles. Your Fiori Launchpad Administration Guide
00:13:06 explains how to do this. What you should avoid disabling are personalization options.
00:13:13 Remember, these days nearly every employee is also a smartphone consumer,
00:13:17 and they expect some flexibility to improve their own productivity
00:13:21 and cater for their physical and contextual needs, such as being able to turn on a high-contrast
theme

7
00:13:26 when they are in challenging lighting conditions. There are a couple of launchpad configuration
settings
00:13:32 that are strongly recommended for all users. The "in place" option for GUI and WebDynpro
ABAP
00:13:39 avoids tab proliferation and makes classic UIs more consistent with the behavior of Fiori apps.

00:13:45 The GUI stateful container option improves performance for classic UIs
00:13:49 by keeping alive your GUI session, and you should also consider the option
00:13:53 to move settings from the Me Area to the launchpad Shell header
00:13:57 to make app-specific settings a little easier to find. Okay, let's see the explace versus inplace
approach.
00:14:04 So, I can always do explace deliberately by right-clicking and using the standard browser
option
00:14:10 Open Link in New Tab, and we'll see the behavior is a little bit different
00:14:15 when you open a GUI for HTML in explace. You see once already I've got a new tab,
00:14:23 which can be a bit of a pain, and you can see that the Me Area
00:14:28 and the notifications and some of the other Shell features are not available when I'm in this
mode.
00:14:35 What can happen also is I can still get to the Home page, so I can end up with multiple Home
pages, which is annoying.
00:14:41 If I use inplace option, which we have here set as the default,
00:14:45 you see I've opened a GUI for HTML, but all my usual Me Area, Fiori search,
00:14:51 and notification areas are available, and here I'm just using the About icon
00:14:55 to show that this is actually a GUI transaction code that we've opened here.
00:15:01 Okay, so what you learned in this unit is some best practices for deploying,
00:15:06 activating, and configuring SAP Fiori for S/4HANA. In the next units of this week,
00:15:12 we'll deep dive into a couple of these areas such as rapid content activation
00:15:17 and launchpad content creation. I'll see you again a little later this week.

8
Week 2 Unit 3

00:00:05 Hello, and welcome to the openSAP course on user experience in SAP S/4HANA, week two,
unit three.
00:00:12 My name is Hannes Defloo. I am a User Experience consultant based in Belgium.
00:00:16 I will be your host for this unit where you will learn all about
00:00:19 the new rapid activation for Fiori. SAP Fiori is how business users
00:00:27 can access the new S/4HANA applications and innovations. You may want in your project to
activate hundreds
00:00:33 or in some cases thousands of SAP Fiori applications and also other launchpad content,
00:00:38 such as Web Dynpro ABAP applications and SAPGUI for HTML transactions.
00:00:43 Of course you want an easy way to do this and with the new rapid deployment of Fiori there is
now one.
00:00:50 In the previous approach, you had to select and activate individual applications
00:00:55 before you could test and experience them. With the new approach, you are instead activating

00:01:00 all applications from standard delivered SAP business roles and as a consolidated single unit,
00:01:07 complete with ready-to-test business user IDs. This allows you to experience all the
applications
00:01:13 contained in those selected roles. And because everything is automated,
00:01:17 using the activation task lists, you can dramatically cut down the activation effort.
00:01:22 The feedback so far has been very positive. Not only does this decrease the time needed to
select
00:01:28 and activate applications, this also avoids a lot of common issues,
00:01:32 missteps and difficult points experienced by project teams new to Fiori in SAP S/4HANA.
00:01:42 As mentioned, the previous approach was based on individual selection of applications
00:01:47 which were to be activated. This was leading to cherry picking
00:01:52 and often a low adoption of Fiori applications. This also required you to do multiple tasks,
00:01:59 via task lists or manually creating confusion and higher implementation efforts
00:02:04 to activate Fiori in projects. You can see the task lists that were to be used
00:02:10 in the previous approach in the table on this slide. The new approach using Fiori Rapid
Activation
00:02:20 is working only on embedded deployments. This is as you probably know,
00:02:24 also the best practice architecture for Fiori. So the rapid activation is not working
00:02:29 when you have a separate Fiori front-end server, also known as a central hub deployment
architecture.
00:02:36 Before starting with the content activation itself, there are some tasks lists
00:02:41 that need to be run in advance. You need to activate the embedded analytics,
00:02:45 enterprise search and also do the basic gateway configuration.
00:02:50 This can also be done via new task lists, you can see them here in the table on this slide.
00:02:57 After going through these, you can start with the Fiori content activation,
00:03:01 this step will also be shown in a demo later. The Fiori Rapid Activation has been released
00:03:11 end of 2018 via SAP Notes. It is supported as from S/4HANA 1709.
00:03:18 You can find a link to the blog on this topic in this slide. This blog also contains the note
numbers
00:03:26 via which the rapid activation has been released. The Fiori Activation consists of basic
configuration,

9
00:03:34 generating the PFCG roles for your users, and activating the applications for selected business
roles.
00:03:41 These roles are standard delivered roles and the activation steps can be done
00:03:48 in the sandbox and developing systems. After these steps, all applications of the selected roles

00:03:54 are ready to be tested. To go live with your system,

00:04:01 you will want to adapt these standard roles. This can now be done using the Fiori Content
Manager
00:04:08 and afterwards you can also create custom PFCG roles. More information on this will be given
in the next unit.
00:04:19 As a first step, you will need to select the business roles you want to activate in your project.
00:04:24 There are multiple ways to do this and how to find the relevant business roles.
00:04:30 You could use the Fiori App Library or also use the Fiori Applications Spreadsheets
00:04:36 of the best practices documentation, which is linked in this slide.
00:04:44 In this short demo, I will now show you how to activate or how to find the business roles
00:04:51 that are relevant for you. We start by opening the Fiori Application Library
00:04:56 and we select two Fiori Applications we are interested in. In this case, it is, the Find
Maintenance Order
00:05:07 and the next application is the Scheduling, which we also select now.
00:05:15 The Maintenance Scheduling Board. So the two applications are selected,
00:05:18 we aggregate this information and then we can see the combined information
00:05:23 for these two applications. So we find the business roles
00:05:28 where these applications are found. Next, we can also find which other Fiori applications
00:05:35 are contained in these business roles. So, we can look this up in the Fiori App library.
00:05:40 First, we go to the maintenance planner, you can see all the Fiori applications
00:05:44 that are also contained in this role. Next, also the Maintenance Planner role,
00:05:50 you can see the four applications that are delivered via this role.
00:05:56 So, this is the way how you can look up using the Fiori App Library,
00:06:01 the Fiori applications in a business role. Next, we will activate these two business roles.
00:06:07 First, I show you the foundation task list where you activate the foundation,
00:06:12 so the gateway configuration. You can see the different steps
00:06:17 that are contained in that activation step. Next, we will activate the Fiori content activation.
00:06:24 Here in the first phase, we have to select the business roles we want to activate.
00:06:30 So here, I can configure this so I can search for the name of the business role.
00:06:36 And then in my case, the maintenance planner role I select here.
00:06:48 And then also the second role we want to activate. And then also the technician,
00:07:09 the maintenance technician role. We select, we save.
00:07:14 There are some other things that can be configured here, for example, the prefix for the role
that will be generated.
00:07:20 Next we will run the task list and when that is finished, you can look up a report
00:07:28 where you can see all the details of the roles that were activated.
00:07:35 So here, you see the role is finished. I go to the log and then I can see some information
00:07:41 like all the... three roles that I selected,
00:07:51 and then the OData services that were activated, and also the ICF nodes that were activated.
00:08:01 You can also see everything finished successfully. So now you are ready to test
00:08:07 and experience the Fiori applications you have activated. Okay, next slide is what is contained
in these SAP Notes.

10
00:08:27 So, which information can you now find in these notes? Of course, a short summary or
definition
00:08:33 of what is the Fiori Rapid Activation. The supported releases, the deployment options,
00:08:38 and also other prerequisites. If there would be any errors,
00:08:45 you can of course also create an SAP incident. In the solution section of the note,
00:08:54 you can find the description of how the task list works. Another section is listing the known
limitations.
00:09:01 Some applications for example, require some further work or customizing.
00:09:05 Also, transporting the activation apps will still require some manual steps,
00:09:10 which are also described here. Also, some special cases and tips
00:09:14 for further troubleshooting are listed. If you face any issues, or have any questions,
00:09:21 you can file an incident with SAP Support, who will further help you.
00:09:32 As a summary, the new rapid activation for Fiori will result in a lower adoption effort for your
project.
00:09:39 You will be able to activate and test more applications. And this will allow you to focus on more
important tasks
00:09:45 related to Fiori in your project like application testing, extensibility, performance tuning,
00:09:52 or working on a strategy to adopt even more Fiori applications.
00:09:56 For the next session, please join my colleague Peter Nechala. He will explain you the Fiori
content, adaptation
00:10:03 and the PCFG role concepts. Thank you for watching and hope to see you soon.

11
Week 2 Unit 4

00:00:06 Hello, and welcome to the openSAP course, week two user experience in SAP S/4HANA unit
four.
00:00:14 My name is Peter Nechala, and I'm a solution architect in the S/4HANA RIG team,
00:00:20 and I will be your host for this unit. In this unit, you will learn about the recommendation
00:00:26 for building catalogs, groups, and roles. Once you have activated the SAP Fiori system,
00:00:36 it is time to adjust Fiori content and how it is assigned to your business roles.
00:00:42 Of course, every customer is unique, and you all have different needs.
00:00:48 Some roles you may be happy to use as-is, maybe some of them need small adjustment,
00:00:55 and some do not align closely to what you do. To meet your expectation, you need to tailor
them
00:01:03 to fit your organizational needs, and you should follow our process
00:01:08 to adjust Fiori launchpad content and business roles. Our best practice process starts
00:01:16 with any adjustment needed to technical catalogs, then reference your technical catalogs
00:01:22 to your business catalogs, then assign custom business catalog
00:01:27 to your security roles. Finally, to organize which apps will appear
00:01:33 by default on the Home page, create your groups referencing to business catalogs,
00:01:40 and assign to your roles. So, what is a technical catalog?
00:01:48 Technical catalogs contain all target mappings and app launcher tiles relevant for application.
00:01:55 Apps are assigned to target mappings in your technical catalogs.
00:02:00 You can map apps of different types: Fiori, GUI, Web Dynpro, or just URL.
00:02:08 Tiles and target mapping are logically connected by referencing the same semantic object and
action.
00:02:18 The semantic object represents a business entity such as Sales Order.
00:02:24 And the action is something you would do with that entity, such as Display.
00:02:30 Technical catalogs can be used as a repository to create your own role-specific business
catalogs.
00:02:42 Once you understand what technical catalogs are, and you have all your tiles and target
mapping completed,
00:02:49 you will need to assign that content to different business roles.
00:02:54 Because you may want to reuse the same tile or any technical mappings
00:03:04 in multiple business roles, the best practice way to assign content
00:03:08 is through business catalogs. Business catalogs are a collection of target mappings
00:03:15 and app launcher tiles relevant for your business roles. The content of the business catalog
00:03:23 is referenced to the technical catalog. Business groups, not shown in this picture,
00:03:29 contain a set of applications from a business catalog. These applications are displayed to a
user
00:03:38 by default on the entry page of the SAP Fiori launchpad. Users can modify groups by adding
00:03:47 and removing apps from SAP Fiori launchpad. SAP content is shipped on a CONF layer,
00:03:54 with SAP technical catalogs and SAP business catalogs. Customers can use content on CUST
or CONF Layer
00:04:02 and adopt the technical or business catalogs. They can use SAP business catalogs as
templates
00:04:09 to build their own catalogs. From a best practice point of view,
00:04:13 we recommend creating or configuring tiles and target mapping centrally in technical catalogs.

12
00:04:22 Make reference tiles and target mapping from technical catalogs to business catalogs,
00:04:28 and last to assign business catalogs to business roles. SAP GUI, Web Dynpro, and ABAP,
00:04:39 and Floorplan Manager applications require an application descriptor
00:04:44 to work with SAP Fiori launchpad. You can use the mass maintenance tool
00:04:49 to create all the necessary application descriptors efficiently in one place.
00:04:55 The launchpad designer is used to manage catalogs, groups, and tiles.
00:05:03 It is the standard tool for configuring the tiles for static, dynamic apps, and target mapping.
00:05:10 Also creating pre-configured groups and catalogs for the Home page and transporting the
configuration
00:05:17 via correction requests or customizing workbench. If you only have a few apps and a few roles,

00:05:28 then the Fiori launchpad designer may be enough. But if you are doing a lot of roles and apps,

00:05:35 you can use the new Fiori content manager, which gives you some mass maintenance support

00:05:43 to more easily create and configure catalogs. It offers features like searching for launchpad
content,
00:05:51 creating, configuring catalogs, adding or removing tiles and target mapping
00:05:57 to catalogs in a mass operation. Let's have a look at a demo
00:06:06 and see in action SAP Fiori launchpad content manager. As usual, we will start
00:06:12 with SAP Fiori apps reference library. Let's search for any app.
00:06:18 In our example, we will choose Manage Sales Orders. As you can see, Fiori apps library
00:06:29 is providing a lot of valuable information: application type, Fiori ID.
00:06:36 If you click on the implementation information, and we search for the supported version,
00:06:44 we see all the back-end systems which are supported. Let's go to Configuration,
00:06:49 and here we can see all the necessary technical information: UI5, Internet Communication
Framework,
00:06:55 OData, technical catalogs, so our repository for these apps.
00:07:01 Semantic Object, Action, and all the necessary actions.
00:07:06 Let's copy and we will work with the business catalog. Let's go to our SAP system GUI
session.
00:07:16 We will run the Fiori content manger, client-specific, client-dependent tool.
00:07:23 Let's start this transaction. And as you can see on the initial screen,
00:07:29 we have more than 3,000 catalogs available in this system.
00:07:34 We will search for our business catalog. Let's search for SAP_SD_BC_SO_PROC_OP.
00:07:53 Click Enter or Go. As you can see, the system immediately found all catalogs
00:08:00 which such a name. Read-Only are the catalogs which
00:08:05 have been delivered by SAP. Below, you can see content in this catalog.
00:08:10 We can see all the tiles, target mapping, action, technical catalogs, it means original.
00:08:19 And we can see also the applications are responsible, meaning UI5, GUI and, Target
Application.
00:08:29 From this transaction, we can also call Open in Designer, so it will call Fiori Designer,
00:08:39 and as you can see, we see exactly the same information.
00:08:43 Tiles. We can display also tiles as a table. In our example, we will choose Track Sales Orders,

00:08:51 and we will edit and configure this one. There is additional technical information
00:08:58 which we can use and also target mapping with all the actions and semantic objects.
00:09:07 Okay, let's go back to our GUI session... Now I will select the catalog

13
00:09:20 and I will click on Copy. Let's call it Z_.
00:09:27 We'll also rename the tile... Let's copy it.
00:09:33 It will take time. Of course, as I mentioned,
00:09:36 customizing requests, all the changes will be tracked in the transport request.
00:09:42 Once the catalog is copied, you can see all the technical information is available.
00:09:50 As I mentioned, we will play with tile Track Sales Orders. So select the target mapping and
also the tile.
00:09:58 We can now remove tiles and target mapping.
00:10:04 System will ask if we want to delete all the references from this catalog.
00:10:09 Let's keep the default settings. Execute. Continue.
00:10:14 And now one tile and two target mappings have been removed from this catalog.
00:10:19 So in this example, when we again open it in Launchpad Designer,
00:10:25 we will see that our catalog has been created, but it has different number of tiles
00:10:31 and also all the target mapping. In this example,
00:10:35 you can see Track Sales Orders is missing. It is not available.
00:10:41 In the standard SAP, Track Sales Orders is still available.
00:10:46 Back to our presentation. So this was the demo.
00:10:50 Once you have your catalogs all ready, then you will need to assign your business catalog
00:10:55 to your roles. You can minimize the effort by using these programs.
00:11:01 PRGN_CREATE_FIORI_FRONTENDROLE to perform mass maintenance of front-end role
00:11:09 with menu entries from a catalog and from selected Fiori tiles.
00:11:15 These Fiori tiles catalogs are assigned to roles via a table that you can create,
00:11:22 or you can upload it manually, or it will be created automatically by selecting catalogs.
00:11:30 The result is the business roles, which contain references to a business catalog
00:11:36 and business catalog groups. Once you assign the business role to a user,
00:11:41 the user sees these apps included in the business catalog
00:11:48 and groups on the SAP Fiori launchpad initial Home page. The second program,
PRGN_CREATE_FIORI_BACKENDROLE,
00:11:55 this program is used and will help you copy front-end roles
00:12:00 to the back end if you are using hub deployment and will propose the required back-end
authorization object
00:12:10 based on the information maintained in transaction SU24. Let again, let's see in action
00:12:18 the CREATE_FIORI_FRONTENDROLE. Let's log onto our system, running transaction SE38,
00:12:28 running the program. As you can see, we have a processing mode.
00:12:31 We will create a row with a menu. Now it's about table.
00:12:36 We will add those catalogs. SAP standard one and one which has been created.
00:12:42 Let's execute. Now once we execute this program,
00:12:46 this program will also create this table. We will add here some prefix to our role, business role.

00:12:55 Once we execute, we can see there are three different roles all belonging to the business
catalogs,
00:13:02 and each of them has a different role. We would like to have one role
00:13:06 so we have to rename the name of the role again. Okay, now let's select
00:13:14 because we would like to add also some group. Let's copy this content
00:13:18 and insert as a new role. We will change the menu entry
00:13:22 from a business catalog to business group. And also changing the provider.
00:13:30 Okay, also for a second entry. Changing from a catalog to group.

14
00:13:37 Okay. Now if you are happy and satisfied with all the results, we can select all the entries
00:13:46 and execute this program. This program will create one business role
00:13:51 with all three catalogs in two groups. Once the program successfully finishes,
00:13:57 we can jump to the pfcg transaction. Let's go to pfcg.
00:14:04 Let's have a look at what is inside this role. From Menu, we can see the menu has two groups,

00:14:14 has been successfully assigned, and also our catalog which has been created before
00:14:21 with all the actions and appropriate object. From this transaction,
00:14:29 we can also go to the tab User and assign these to our TESTER user.
00:14:36 Okay, let's execute, save all the changes and now log onto Fiori Launchpad
00:14:42 with this user. As you can see, you will see two groups,
00:14:46 and user can also have access to any tiles which belong
00:14:50 to the business catalog which we have created. Manage Sales Orders.
00:14:55 Let's create, let's run any transaction, any apps which is related to that user.
00:15:02 Also change the Home page and add any groups.
00:15:08 In our example, we will add Sales order as a new group, adding some tiles.
00:15:17 Let's choose our catalog, and we will select apps, Change Sales Orders,
00:15:25 and let's select some additional one. Okay, go to Home page,
00:15:33 close the settings, and now the user can also create some group
00:15:39 and has additional apps. What you have learned in this unit are necessary steps
00:15:46 to adjust Fiori content and roles. Understanding technical catalogs entities,
00:15:51 creating and assigning content to users with Fiori tools. I hope this unit gave you a good
overview about tools
00:16:01 for building catalogs and roles. For the next session, please join my colleague Jocelyn Dart.
00:16:07 She will be talking about SAP Fiori Launchpad Special Features
00:16:12 and Content Troubleshooting. Thank you for watching and all the best
00:16:16 for the rest of the course. Bye-bye.

15
Week 2 Unit 5

00:00:05 Welcome back to week 2, User Experience in SAP S/4HANA. My name is Jocelyn Dart
00:00:11 and I am a User Experience Strategist in the SAP S/4HANA Regional Implementation Group.
00:00:17 In this unit you will find out a little more about SAP Fiori launchpad special features,
00:00:22 and you will get a quick high-level overview of how to go about troubleshooting content issues.

00:00:30 By the end of this unit you will have an understanding of the main steps to configure SAP Fiori
launchpad features
00:00:36 such as the Fiori Search, Notifications, Default values, and more.
00:00:41 Since you will obviously need detailed step-by-step instructions to configure these yourselves,

00:00:46 you can find those in the official product documentation in the SAP Help Portal and the blogs
in the SAP Fiori
00:00:53 for S/4HANA wiki on the All About Apps page. If you want to quickly find the right guide
00:00:59 in the SAP Help Portal here is a quick tip. Go first to the main S/4HANA Product Page for your
version,
00:01:10 Okay, and you can see here you can use the quick link
help.sap.com/s4hana_op_yourversion_yourfeatu repackstack,
00:01:20 and then once you've got to the product page, then search for your relevant guide.
00:01:28 So here, just checking that we were on the right version, and I'm going to search for the Fiori
launchpad guide.
00:01:35 And if you do it this way you'll always get to the correct guide for your S/4HANA version.
00:01:44 Okay, that just takes a couple of seconds for it to bring up the list of guides.
00:01:49 And there it is straight away. And if we go into the Fiori launchpad,
00:01:53 most of the things we're talking about here today are covered in the Administration Guide.
00:02:00 Excellent. When you first turn on your Fiori launchpad,
00:02:04 you will usually find that the search button in the shell header will only search for Apps.
00:02:09 If you see that, you haven't configured the Enterprise Search yet.
00:02:13 You should be seeing the list of Business Objects you are authorized to search for.
00:02:18 For each Business Object you want to include in the search, you need to identify
00:02:21 the matching search connector, which you can find in the Fiori apps reference library
00:02:26 as part of the role and app configuration information. Usually you find this with the Fiori app
Object Page
00:02:33 that displays the relevant business object. You'll need to generate the search index
00:02:37 for the search connector. You can test the search results directly
00:02:41 via the GUI as well as in the Fiori launchpad. And you can use authorizations
00:02:45 to restrict which Business Objects a particular business user or role can search on.
00:02:50 Let's see what this looks like if you've configured it correctly.
00:02:54 So here we are, and at the top of the shell we have that magnifying glass icon,
00:02:58 that is the search. Now here's that list.
00:03:01 If you're only seeing Apps and not the list, you haven't configured it yet.
00:03:05 So that's the list of objects I'm allowed to search on. I'm searching for our wild card here, *S08,

00:03:11 and let's just see what we find across the system. This is everything we found that matched.
00:03:16 Now, you can see here the first item is open, and the related apps are shown as links beneath.

16
00:03:22 You'll see here also that if you're focused on a business object, you get some simple filters
sometimes
00:03:27 that help you quickly narrow down to what you're looking for.
00:03:31 Again, notice that the related apps that I'm authorized to use are shown underneath,
00:03:35 so I don't have to go back to the Home page. Coming back to another example,
00:03:40 here's Customers. You'll see sometimes if you're authorized for the object page,
00:03:44 the search object itself will be a link, and this will take you across to the related object page,
00:03:50 which is basically a one-page summary of that particular object.
00:03:54 So, in this case, of this particular customer. And you'll see here, that object page
00:03:58 also has related apps, so once again, once you've found what you were looking for,
00:04:04 you don't have to go back to the Home page. You can go straight to any of the apps
00:04:08 you're authorized to use. And all of these lists are controlled
00:04:11 by your authorizations. Okay, moving on to Notifications.
00:04:16 There are three main steps to turning on Notifications. The first step is in your Fiori launchpad
configuration.
00:04:23 Your Notification Center, where your users actually see the Notifications,
00:04:27 is usually enabled by default. This is the righthand pane of the Fiori launchpad
00:04:33 where you see your notifications. The second step is in your Fiori front end.
00:04:37 This is where you activate the Notification Hub that collects the notifications
00:04:42 from the notification providers to be displayed to users in the Notification Center.
00:04:48 You can use the Demo Notification provider to send some test notifications
00:04:52 to check that the hub has been configured correctly. Lastly, you need to configure
00:04:57 your real notification providers in your S/4HANA back end.
00:05:01 These control which notifications are sent to the hub and whether any quick actions are
provided.
00:05:07 You can configure the notification providers for workflow tasks, for selected Smart Business
KPIs,
00:05:12 and for SAP CoPilot, and you can also create
00:05:15 your own notification provider if you wish. Since notifications of new workflow task
00:05:21 is the most common usage, you usually also need to configure the Fiori app My Inbox.
00:05:26 That way, clicking on a workflow notification will redirect the user to My Inbox,
00:05:31 where they can view and act on the full details of the task. There are a few really nice features
you can turn on
00:05:40 for business users who use a lot of classic UIs, SAP GUI transactions, and Web Dynpro ABAP
applications
00:05:46 with the Fiori Visual Theme. These include the role-based Easy Access Menu
00:05:51 and the SAP Menu alongside the App Finder catalog. This is useful if you don't have time
00:05:58 to include every transaction in a business catalog or group, but you want your business users

00:06:03 to be able to find and use the transactions they know and love.
00:06:07 Okay, so let's see how this works. In this case, I've got a user
00:06:12 who's been given some product master, product master apps,
00:06:16 but they're actually looking for a specific mass maintenance transaction
00:06:19 that they know as MM17. So, here, if they know what it's called,
00:06:24 they can just search by the name or keyword and they know it's Apps,
00:06:27 so we can at least narrow it down to apps. And you'll see here, if I start typing in
00:06:32 the name of what it is, it starts to bring up some suggestions

17
00:06:36 as to what we might be looking for, and, actually, it is there already.
00:06:41 But let's assume that this user only knows it by MM17. So we're going to search for MM17.
00:06:46 And because there's no keyword in our catalog for that, it's not going to find it, and it says,
hmmm,
00:06:52 you might want to have a look in the App Finder and see if it's there.
00:06:55 Now here in the App Finder we have the catalog, but we also have the User Menu and the
SAP Menu turned on.
00:07:02 So, if it's not in our catalog already and we don't have that keyword in there,
00:07:06 what we could do is swap across and use the standard SAP Menu,
00:07:10 and I can actually drill down through the menu if I want or I can just search for the transaction
code that I know.
00:07:16 And there you go, bang, I've found it, and now I can just add it to whatever
00:07:22 group makes sense to me so that it's captured on my Home page now.
00:07:26 Now, I don't have to put it on my Home page. I could just click on that link right there
00:07:29 and use it directly. But here we have it now.
00:07:32 I've added it to my Home page, and you'll see, okay, I can click on it,
00:07:35 and it's working already. All right, a couple of watch points here.
00:07:41 Everything in the Easy Access Menu must be in a folder, root level items are ignored,
00:07:46 and personal favorites are not included. Okay. Default values are a step up
00:07:52 from Business Suite Set/Get parameters. You can set both a primary default
00:07:59 and extended additional values. Which is different to SET/GET.
00:08:03 Primary defaults are typically the entry you make in most forms and other places
00:08:08 where only a single value can be entered. Additional values are automatically added
00:08:13 where multiple values are supported such as in the search filters of Fiori apps.
00:08:18 Your primary default value is inherited from your SET/GET parameters.
00:08:22 Let's see what this looks like in practice. So here I have an app and I can see here
00:08:27 that there's a Company Code field, but it's empty at the moment.
00:08:30 Now, I could go and search for this right now while I'm in the app,
00:08:33 but that means I have to do it every time, which is tedious, so let's go across to the Me area,
00:08:38 and instead use the default values. In Settings here, I find my Default Values. Okay.
00:08:46 And I can see that one of the default values I can set is Company Code, great.
00:08:50 So, I'll go and use the search here to find it, and this is the exact same search I would have got

00:08:55 if I was using the app itself. Okay, so I've found it.
00:08:59 That's my main value, but I'll add in some additional values,
00:09:02 because maybe when I'm filtering in reports, there's a few other company codes
00:09:06 that I sometimes need to look at. So I can put a range here.
00:09:10 I can even add additional patterns if I wish. I'll add one more just for
00:09:15 the sake of showing how this works. And these default values, I now save them.
00:09:23 And you can see Additional Values is highlighted so I know that there's more values there.
00:09:28 Now that has immediately impacted this app. But if I go back to the launchpad and reopen the
app again,
00:09:34 you'll see now it's picked up my default values. So I can see here there's a few,
00:09:39 and if I open the search again, you can see in the Selected Items,
00:09:43 it's already picked up those default values for me. Excellent.
00:09:48 Okay. Which defaults values are passed

18
00:09:52 can be configured in the Target Mapping of your Business Catalog using the Launchpad
Designer.
00:09:57 You can pass them to Fiori apps, to GUI transactions, to Web Dynpro ABAP applications,
00:10:01 and, of course, your own custom apps. One watchpoint with default values,
00:10:06 you cannot create your own default values in the customer namespace.
00:10:10 Okay. Provided for free with your SAP S/4HANA solution
00:10:14 is some really nice help content from SAP's web-based content platform.
00:10:20 You can use this as-is simply by configuring the web dispatcher
00:10:23 and setting up the user assistance plug-in to call the content matching your S/4HANA version
00:10:28 and Feature Pack stack. You can even get user assistance for the back-end system.
00:10:33 If you want to extend the provided content, then you can do that in the cloud
00:10:37 or on-premise via the authoring tool SAP Enable Now. Check the subscriptions or license
details
00:10:43 for SAP Enable Now with your SAP Account team, of course. Unlike Business Suite,
00:10:50 with S/4HANA not all configuration happens in the back-end system.
00:10:54 There are a number of Fiori apps and some important Fiori features
00:10:58 that you can use to adapt other Fiori apps. These are always the easiest and safest
00:11:03 to fill any gaps from your fit-gap analysis. So you need to make these available
00:11:07 to your key users as well. Who are your key users?
00:11:11 Whoever you authorize. Certainly, you can give these
00:11:14 to process experts or functional leads, but it's fine for developers or a central governance team

00:11:20 to use them as well. These Fiori apps belong to the special roles Administrator,
00:11:25 Analytics Specialist, and Business Process Specialist, which you should always activate
00:11:30 in your development system as a minimum. You will find many of these apps mentioned
00:11:35 in the official documentation as General Functions for the Key User.
00:11:41 Perhaps the most important app is Custom Fields and Logic, which is the safe and simple way
to add custom fields
00:11:49 to a business context scenario set of related tables, CDS views, OData services, Fiori apps,
00:11:56 and even sometimes GUI transactions. All changes are saved to ABAP transport requests
00:12:00 for transport through your production system, which is why you need to set up
00:12:04 the transport adaptation organizer, The most important Fiori feature is UI adaptation.
00:12:14 This enables you to draw attention to the most important aspects for your process,
00:12:20 to show or hide fields, groups, and cards, rearrange your Fiori app somewhat.
00:12:26 These changes are important to the process, but don't usually impact
00:12:29 the underlying technical environment. It's worth noting what's available
00:12:33 to adapt is increasing and becoming more widespread across apps over time.
00:12:38 So get used to these features now, and let us know what you would like to see in the future.
00:12:45 Content troubleshooting is another big topic, so you will just get some highlights here.
00:12:50 Try the Performance and Troubleshoot page of the Fiori for S/4HANA wiki
00:12:56 for many more tips and tricks. If you are interested in end-to-end debugging of Fiori apps,
00:13:02 that was also covered very well in the recent openSAP course Evolved Web Apps with
SAPUI5.
00:13:08 If you missed it, you can always enroll self-paced to look at the videos.
00:13:12 However, end-to-end debugging is rarely needed for delivered SAP Fiori apps,
00:13:18 since these are already fully working apps. You usually get to the most important information
00:13:23 you need to troubleshoot from the About icon. Make sure your users know where to find it.

19
00:13:28 So you can see here, I've got a Fiori App open,
00:13:34 and when I'm in the app, I can just go to the Me area. And the About icon will tell me exactly
which app ID,
00:13:43 support component, and even which browser and UI version I'm dealing with.
00:13:50 Knowing these can save you a huge amount of time if you need to reference official app
documentation,
00:13:56 search for SAP Notes, or raise an SAP incident. And just to show you that this also works for
00:14:05 GUI transactions and Web Dynpro ABAP classic UIs, here's a classic UI, and again,
00:14:11 if I go to the About icon here it tells me exactly which transaction code I'm on
00:14:15 and how I'm running it. Once you know which app you are dealing with,
00:14:19 and you've done some basic due diligence, you might still need to do a little troubleshooting
00:14:24 in your browser, Fiori front end or S/4HANA back end. Okay, so, typical problems you might
need to diagnose
00:14:34 using the developer tools of your Web browser are rendering or navigation issues:
00:14:40 Something doesn't look or behave correctly; caching issues, something hasn't changed
00:14:46 when it should have; and of course single sign-on
00:14:48 and cross-origin scripting issues, so unexpected blank pages or broken links.
00:14:53 Caching issues are always the most common. If you suspect a navigation issue,
00:15:02 it's always worthwhile checking underlying authorizations, since app-to-app navigation is
driven
00:15:07 by both configuration and authorizations. In other words, if you are not authorized,
00:15:13 you can't get to it. So always eliminate authorizations
00:15:17 from your inquiries first. In practice, your most important troubleshooting tools
00:15:23 are behind the scenes in the front-end and back-end servers, or your embedded server,
00:15:27 and this is usually where you need to fix any problems as well.
00:15:31 While you might get a hint at an error message in your browser,
00:15:35 it's often easier to identify, diagnose, and fix issues in your back end.
00:15:40 When you are first getting your apps activated, OData activation issues and caching issues
00:15:45 are the most common. Using the task lists and following
00:15:50 the pre/post activation steps per role in the SAP Notes for Fiori rapid content activation
00:15:55 will avoid a lot of these problems. Missing or no data issues will usually turn out
00:16:01 to be either functional configuration not correct or some authorization issues.
00:16:06 Remember, if you change your OData service or functional configuration or activate
00:16:11 an additional OData service, you will often need to invalidate your server caches
00:16:16 and your browser cache before those changes will take full effect.
00:16:21 Launchpad content issues, including broken app-to-app navigations,
00:16:26 can be diagnosed for a user, business role, or semantic object
00:16:30 using the Fiori launchpad intent analysis, and Fiori launchpad check tools.
00:16:35 The UI2/FLIA and UI2/FLC. You'll find plenty of these in the Fiori launchpad guide
00:16:41 for your SAP S/4HANA version in the SAP Help Portal. And, yes, of course, performance
issues.
00:16:48 While at some point you will need to do an end-to-end trace to sort out
00:16:52 any problems re network or bandwidth or content delivery networks,
00:16:56 it's nearly always worthwhile checking the performance statistics in the back end first,
00:17:01 particularly if you have done extensions or custom-built apps using the "infamous"
compatibility views.
00:17:09 If it doesn't perform well in the back end, it's never going to perform well in the front end.

20
00:17:18 So in this unit, you learned the main steps to configure some SAP Fiori launchpad
00:17:23 special features and apps and how special features behave
00:17:27 when configured correctly. You also learned how to troubleshoot
00:17:31 some content issues in the browser, front-end server and back-end servers.
00:17:35 Thanks for listening, and I'll see you again next week.

21
Week 2 Unit 6

00:00:06 Hello, I hope you remember me from this week's first session.
00:00:10 My name is Jorge Baltazar, and this time we will talk about
00:00:13 SAP Fiori launchpad performance. Whenever we talk about performance,
00:00:20 we are referring to the total effectiveness of a computer system,
00:00:24 which does not only refer to how satisfied your end users are with the response time
00:00:29 of your Fiori solution, but also refers to the throughput
00:00:32 and availability of the system. A system performance covers several domains.
00:00:39 When a performance issue occurs, you need to understand that performance optimizations
00:00:44 will be required at many levels, like application or operating system.
00:00:49 In short, this means that if you are facing a performance issue with a Fiori application,
00:00:55 most times it will not only be caused by a misconfiguration in the SAP Fiori configuration layer.

00:01:01 It could also be caused by other factors at application, database, or operating system level.
00:01:08 Hence, troubleshooting performance issues requires analyzing several domains,
00:01:14 for which we will need to be prepared in order to find the best solution
00:01:17 to our performance problems. So we are now aware that analyzing performance
00:01:24 requires knowledge in several domains. However, we also need to consider
00:01:30 the user perspective on performance for our system, and identify to which extent
00:01:36 we can meet the user expectations in order to provide a satisfactory experience.
00:01:42 We also need to identify the system perspective. This will tell us to what extent
00:01:48 the hardware and application resources of our system can provide a satisfactory experience.
00:01:55 Once we understand both perspectives, we can identify our working range
00:01:59 to clearly define which performance requirements we can meet.
00:02:04 Why do we recommend doing this? Because you may find situations
00:02:08 where you will need to prioritize and decide if a specific issue is really worth tackling,
00:02:14 as you may find scenarios where your system resources will never meet end-user demands, or
vice versa.
00:02:21 Having this range clear will help you optimize your efforts when dealing with troubleshooting
00:02:26 performance-related issues. Another important aspect you always need to remember
00:02:33 when dealing with performance issues is the architecture setup of your landscape.
00:02:39 We will go through a sample architecture which follows a recommended setup
00:02:42 for S/4HANA implementations, the embedded deployment, which you reviewed on unit two of
this week.
00:02:50 In an embedded deployment, the first performance-related issues you may encounter
00:02:55 relate to the connection of devices when the Fiori launchpad is exposed via public Internet.
00:03:01 These type of situations often relate to the bandwidth provided by your data carrier.
00:03:07 The second major type of performance issues you may encounter relate to the configurations

00:03:12 of your SAP Web Dispatcher, or reverse proxy, which we recommend to be placed
00:03:17 in the demilitarized zone or DMZ. Though some of the issues may be caused
00:03:22 by incorrect or complex dispatching configurations, you should also review the network
bandwidth size
00:03:28 between your demilitarized zone and your internal network. Plus, double-check the sizing of
your Web Dispatcher,
00:03:36 or your reverse proxy. The sizing of Web Dispatcher

22
00:03:40 will provide a finite number of web co- connections to be supported by the server.
00:03:45 Hence, if you are expecting a large amount of users, your Web Dispatcher should be sized
properly
00:03:50 in order to avoid performance problems. For the sizing of Web Dispatcher,
00:03:55 also keep in mind that the selection of operating system will also take part in the number of
connections
00:04:02 supported by the reverse proxy. To further avoid performance issues in your landscape,
00:04:08 you should always remember the technologies that are being supported by the Fiori
launchpad,
00:04:13 which are SAPUI5 and OData services, Web Dynpro ABAP, and SAP GUI for HTML.
00:04:20 We suggest keeping these technologies in mind, as each of them will require a different
approach
00:04:25 when troubleshooting performance issues. But before we jump into the main performance
00:04:31 recommendations for these technologies, let's start with the most common SAP Fiori
00:04:35 performance issues in S/4HANA implementation projects. The main issue we have found
00:04:43 in all SAP 4/HANA implementation projects is related to the cache-handling
00:04:48 and high volume of SAP Fiori app assignments per user. You'll be asking, why would this
affect
00:04:54 the performance of the Fiori launchpad? It is very simple.
00:04:58 The amount of apps you assign to a user directly affects three of the principal web calls
00:05:03 that enable loading of the Fiori launchpad, which is based in the browser and server cache.
00:05:10 The way cache works is very simple. On the very first launch of each user's Fiori launchpad,
00:05:16 whenever an object is loaded, details of this object are stored
00:05:20 in a special memory area of the browser. This data is used for the consequent web calls
00:05:25 in order to speed up the loading of the objects, increasing performance.
00:05:30 However, if the cache is deleted, first loading of these objects
00:05:35 will be triggered from scratch, leading to performance issues.
00:05:40 The three web calls allow the display of the Fiori launchpad as they load the tile
00:05:44 and chip contents, which are the calls under the path PAGE_BUILDER_PERS,
00:05:52 plus the target mappings assigned to each user, which are the calls related to the path,
/ui2/start_up.
00:06:02 This situation translates into two major issues. First, if you constantly modify
00:06:08 the app assignments to your users, cache refresh will be triggered,
00:06:12 leading to performance issues. Second, the more apps you assigned,
00:06:17 the more target mappings a Fiori launchpad will load, and the more time it will take to load all
the applications.
00:06:24 An easy way to avoid these issues is first avoid clearing browser and server cache constantly.

00:06:30 We've noticed it has become a regular practice to clear this cache whenever an issue occurs.

00:06:36 This is a procedure that can be valid for development and quality systems,
00:06:40 but it is not recommended for productive systems. Second, limit the number of apps assigned
to your end users.
00:06:48 We've faced situations where users have a large number of apps assigned to them.
00:06:52 For this, you really need to ask yourselves if it makes sense to have a large number of apps
00:06:58 assigned to a user. To exemplify this situation, you can picture it as follows:
00:07:05 When you're preparing dinner, did you really take out all the pots,

23
00:07:08 pans, dishes, forks, spoons, and knives from the cupboard, place them on your table, and then
decide what you will use?
00:07:16 Or do you simply select what you need? Think of the Fiori launchpad as your cupboard.
00:07:21 You really don't need to place all the apps you could use up front.
00:07:26 You rather select them as needed through features like App Finder.
00:07:33 Keeping this idea in mind, which are some of the quick actions you can take
00:07:37 to improve your Fiori launchpad performance? First, focus the Fiori launch Home Page
00:07:43 on the most frequent tasks for each user or role. This way, you will reduce the assignment
00:07:49 of target mappings and tiles. Second, think of the Fiori launchpad
00:07:55 as a mobile application. In a mobile application, you really don't want
00:07:58 to scroll down through a large page. You'll always prefer switching between tabs.
00:08:04 You can set up tab-bar mode as a default to all users. This will surely help you speed up
00:08:09 the loading of the Fiori launchpad. Third, for Web Dynpro ABAP and SAP GUI for HTML-based
apps,
00:08:17 configure Inplace Navigation. It will make this type of applications open
00:08:22 in the same web browser tab as the Fiori launchpad, and will help increase the loading of
these applications.
00:08:30 The main reason being that the runtime objects will only be loaded once per user session.
00:08:38 Fourth, configure OData services in co-deployed mode. You want to do this in embedded or
hub deployments
00:08:44 in order to make use of the special performance features related to system alias runtime
resolution,
00:08:50 which will translate in an increased performance. Additionally, if you are using the rapid
activation setup
00:08:56 for Fiori, this mode will be configured out of the box for you.
00:09:02 Fifth, SAP Fiori launchpad and SAPUI5 are based on HTML5. Hence, a browser that fully
supports HTML5 is required
00:09:12 in order to take the most out of this technology, and unfortunately some browsers like Internet
Explorer 8,
00:09:19 9, 10, and 11 are not fully HTML5-compliant, so expect performance issues
00:09:26 when you're using these browsers. Sixth, for SAP UI5 base applications,
00:09:34 we deliver corrections including performance improvements on each SAP UI5 library release,

00:09:40 so keeping your SAP UI5

libraries up to date will surely help improve Fiori launchpad performance.
00:09:49 Seventh, for Web Dynpro ABAP and SAP GUI for HTML base applications,
00:09:54 review and update your unified rendering libraries. These libraries help load the front-end
contents
00:10:00 for these technologies, and when these are not updated, you'll be facing performance issues.
00:10:07 Eighth, also for Web Dynpro ABAP, and SAP GUI for HTML base applications,
00:10:12 these technologies make use of some kernel- based features to improve performance, hence,

00:10:18 updating or patching your kernel version will help improve performance in your systems.
00:10:28 Apart from knowing the basic performance recommendations, you should also be aware of the
recommended
00:10:33 performance analysis tools. First and available to all the users in your company
00:10:39 are the Browser Developer Tools. These are the most basic analysis tools,
00:10:44 and they are available on all major web browsers. Hotkeys to display these tools on all major
browsers

24
00:10:51 is using the Function 12 key. Using these tools, you can get a simple
00:10:57 but effective waterfall diagram, which can help you track the most time- consuming web calls,
00:11:02 and you can also find details of the runtime errors through the console feature
00:11:06 of these Browser Developer Tools. Another important tool is the UI5 Diagnostics Tool.
00:11:15 This can be launched once you have logged into the Fiori launchpad
00:11:18 and triggered the hotkey combination Control + Shift + Alt + letter S.
00:11:24 These tools offer similar features as the Web Browser Developer Tools.
00:11:29 The only difference is that this set of tools is exclusive to the UI5 runtime,
00:11:34 and they offer additional technical information of the application you're running,
00:11:38 like the intent name, application name, UI5 library version, and so on.
00:11:46 Next, and a very important tool for troubleshooting OData calls is the URL Parameter: sap-
statistics.
00:11:54 By setting this parameter to true in an OData URL, you will be able to see a technical request
header
00:12:00 called sap-statistics, which will bring details about performance statistics,
00:12:05 for example, the ICM web dispatcher, and SAP Gateway total execution time,
00:12:11 which you can later analyze to determine which system in your landscape
00:12:15 is being affected by performance issues. And last is transaction STAD,
00:12:23 which is useful when you wish to obtain the total transfer data volume in bytes,
00:12:27 transferred by each of the web calls to help you verify your network sizing.
00:12:35 So we've given some performance recommendations, but you will also need some guidance
00:12:40 on how and when to apply some of these recommendations. This is why we will now show a
sample
00:12:46 first-level support procedure for performance issues in SAP Fiori launchpad.
00:12:52 First, you should determine if the problem is related to browser-side caching.
00:12:57 For this, you can check the recommended browser cache settings for all major browsers
00:13:02 described in SAP Note 2447857. If you are certain that the issue is not cache- related,
00:13:11 you should then review the SAPUI5 library versions in your SAP S/4HANA system,
00:13:16 for which you can check SAP Notes 2363155 and 2346367 which describe the main
procedures
00:13:25 to check your current SAPUI5 library version, and the required steps to download
00:13:31 and upgrade to a new library version. Let's suppose you have made these first checks,
00:13:37 and you are still facing performance issues. Next recommended step will be to check
00:13:42 your current kernel version, and try to implement a kernel patch or a kernel update,
00:13:47 and in this light you will find the SAP Notes that explain how to perform these requirements.
00:13:55 Additionally, if you're running a hub deployment, try to ensure that the kernel versions
00:14:00 of both front-end and back-end servers match, along with the unified rendering libraries
00:14:06 that we described earlier in this session. Still facing issues?
00:14:11 We recommend double-checking your network bandwidth sizing. This is to make sure that
there are no
00:14:17 network-related issues affecting your implementation. This check is needed, as network quality

00:14:24 would be a domain outside the SAP solution space. Hence, ensuring that network quality is
optimal
00:14:31 will be useful to identify the root cause of a performance issue.
00:14:35 On a side and curious note, network issues could be as simple
00:14:38 as having multiple users connecting to the same wi-fi hotspot,

25
00:14:42 or as complex as having separate network segments between systems with different speed
rates.
00:14:50 If network quality has also been discarded, you can then state that the issue may be caused
00:14:55 by a long running statement in the SAP solution area, for which you can try setting up
00:15:01 co-deployed mode for OData services using the sap-statistics URL parameter
00:15:06 to identify possible bottlenecks in ICM, Web Dispatcher, or SAP Gateway,
00:15:11 or run transaction STAD to validate the amount of data transferred
00:15:15 per each web request. Once you have gone through all these steps
00:15:21 and ensured that the previous validations have not highlighted any major issues,
00:15:26 you can then create an incident to SAP for the specific Fiori application component
00:15:30 of the application you are testing. When you create a new incident to SAP,
00:15:37 you should try to include the following data, which comes as a result of the previous
validations.
00:15:43 First, an HTTP trace, which you can obtain through the Browser Developer Tools,
00:15:49 or using a software program called HttpWatch, or even through the results
00:15:53 of using the URL parameter sap-statistics. Second, try to include a network performance
analysis.
00:16:01 This way, SAP can also discard any network- related issues and focus on the SAP
development bugs
00:16:08 and the different architecture layers. Third, always include the technical details
00:16:14 of the application you are running, which you can obtain from the UI5 Diagnostics Tool.
00:16:21 And fourth, always include the technical details of your S/4HANA system,
00:16:25 including operating system, operating system patches, kernel, kernel patches, and HANA
database version.
00:16:34 Providing all this information will help speed up the resolution of your issue,
00:16:38 and avoid wasting time in the solution process by SAP support teams.
00:16:44 We will now summarize the topics that we have reviewed during this session.
00:16:50 There is a need to define user and system performance expectations to prioritize performance
issues
00:16:55 and define which of these issues are worth dedicating time to solve.
00:17:00 Second, always run the quick actions to improve SAP Fiori launchpad performance,
00:17:05 as your first actions to improve performance. They are sure to solve your issues at a certain
extent,
00:17:12 and do not require major implementation efforts. Third is know the troubleshooting tools,
00:17:18 and establish a first-level procedure for troubleshooting performance,
00:17:22 like the one we showed during this session. This will help you rationalize the possible causes
00:17:27 of your performance issues and quickly identify the component
00:17:31 in your S/4HANA landscape architecture that is being most affected in performance terms.
00:17:37 And last, in the event you need to generate an incident to SAP,
00:17:41 try to include good-quality information in order to speed up the incident processing times,
00:17:47 and allow SAP support teams to provide the best solution for your problem.
00:17:53 I hope you have enjoyed the content of this session. As described earlier, performance is a
complex topic,
00:17:59 and requires knowledge in different domains. Hence, we tried to simplify the content
00:18:04 and provide the most valuable advice for your implementation projects,
00:18:08 which is not necessarily related to technical knowledge. For the next session,
00:18:14 please join my friend and colleague Gilbert Wong, who will be talking about SAP CoPilot and
its architecture.

26
00:18:20 Thanks for watching and hope to see you soon. All the best.

27
Week 2 Unit 7

00:00:05 Hello, welcome back to week two, unit seven, of this openSAP course.
00:00:10 My name is Gilbert Wong. I am a Technical Consultant and Project Expert
00:00:14 in the S/4HANA Regional Implementation Group based out of North America.
00:00:19 In this unit, we will take a look at an introduction to SAP CoPilot and its architecture.
00:00:27 Let's start with a quick introduction of SAP CoPilot. SAP CoPilot is your digital assistant
00:00:33 and bot integration hub for the enterprise. It allows you to accomplish tasks quickly
00:00:39 in your business application. You can add and create objects, such as products,
00:00:44 sales orders, notes, on the go by simply talking or typing to the SAP CoPilot application.
00:00:52 You can use SAP CoPilot on your desktop, mobile device, or through an external channel or
platform.
00:00:59 As a bot integration hub, you can integrate bots that you build using bot-building tools
00:01:05 such as SAP Conversational AI and SAP CoPilot Skill Builder, and connect them with SAP
CoPilot
00:01:12 to create one seamless digital assistant experience. In today's world,
00:01:21 consumers use various intelligent assistants, from Apple's Siri to Amazon's Alexa
00:01:27 to Google's Assistant and Microsoft Cortana. For example, you can ask Siri to play today's
newsfeeds
00:01:34 or ask Alexa to add items to your shopping list, or even make reservations using Google
Assistant.
00:01:40 This seamless interaction with these tools using your voice, has been built for the consumer,
00:01:46 and now our business users expect the same conversational interaction
00:01:51 and intelligence with their business software. This is where we introduce SAP CoPilot,
00:01:57 our digital assistants for your enterprise business applications.
00:02:04 Now let's meet SAP CoPilot. Talking to SAP CoPilot is both simple and intuitive.
00:02:10 SAP CoPilot empowers you to get things done easier, quicker, and more delightful,
00:02:16 and is the first true digital assistant and bot integration hub for the enterprise.
00:02:21 SAP CoPilot conversational user experience: By enabling natural language interaction,
00:02:29 it allows you to either type or speak your commands into the SAP CoPilot interface,
00:02:35 and uses the natural language services to interpret the commands.
00:02:40 Business contacts awareness: Understanding the business situation,
00:02:45 so depending on which transaction or screen you are in, SAP CoPilot is aware of that
transaction
00:02:51 and offers suggestions for your solution. SAP CoPilot is a self-learning system,
00:02:57 using machine learning functionality to gain knowledge based on historical data and
experience.
00:03:04 Cross-applications with one personality and one memory across all SAP.
00:03:09 Open and extensible for integration into SAP and non-SAP solutions,
00:03:15 enabling customers and partners to extend SAP CoPilot functionality with SAP CoPilot skills.
00:03:26 So this is the next paradigm shift in technology. We have seen several major technology shifts

00:03:33 in our lifetime. We started with mainframes and minicomputers

00:03:37 to PC LANS, and then there was a major shift in the 90s to a client/server architecture.
00:03:44 In the early 2000s, technology shifted to the internet, cloud, mobile applications, and social
media,.

28
00:03:50 And today the focus is on IoT and artificial intelligence. Today's new innovations are centered

00:03:57 around machine learning, artificial intelligence, bot integration, and conversational AI.
00:04:04 Quoted from Gartner: "There is a big disruptive platform paradigm shift
00:04:09 coming now. Conversational AI platforms will be
00:04:13 the next big paradigm shifts in information technology. Conversational AI platforms are
00:04:19 already in the market today, but more are coming.
00:04:22 Conversational AI platforms will likely be the strongest instigator of investments
00:04:28 that exploit AI for a decade or more. This encompasses more than chatbots, virtual assistants
00:04:36 and messaging-based applications: the emergence of conversational AI platforms
00:04:42 will stimulate significant growth in the exploration of AI in general."
00:04:50 Here are some SAP CoPilot business benefits. First, provides conversational interfaces
00:04:57 where users can interact through natural language, either through typing or speaking your
commands
00:05:02 in the SAP CoPilot interface. Ensures a delightful user experience.
00:05:09 Next, it enables users to centralize the acquisition of all user interaction data
00:05:15 across all products over time. Enables business users to work seamlessly and efficiently
00:05:21 on a business transaction with colleagues, customers, and partners.
00:05:25 It revolutionizes business processes. Receives relevant information and insights
00:05:31 about user's activity. And finally,
00:05:34 provides customer immediate answers to their questions. Okay, next we have the SAP CoPilot
Skill Builder.
00:05:45 The SAP CoPilot Skill Builder is a non-coding integrated development environment,
00:05:51 used to create and maintain a repository of skills and intents for SAP CoPilot natural language
interactions,
00:06:00 which is based off of OData services. This is currently available today for use
00:06:06 with SAP S/4HANA 1709 FPS01 on-premise or higher.
00:06:13 With SAP CoPilot Skill Builder, customers and partners can build CoPilot skills
00:06:18 without writing one single line of code. Using SAP's pattern-based approach,
00:06:25 we leverage metadata from services of SAP applications like SAP S/4HANA.
00:06:32 This is a highly scalable approach that enables developers to build CoPilot skills
00:06:37 in a very short time without changing any existing back-end processes
00:06:42 or building new functionality. The SAP patterns-based approach is
00:06:47 complemented by SAP Conversational AI and its machine learning-based engine.
00:06:53 It runs on SAP Cloud Platform, and leverages SCP services to securely connect enterprise
systems.
00:07:00 Predefined dialog handlings for standard operations like create, read, update, query,
00:07:08 with minimal training required. Out-of-the-box support for security authentication,
00:07:14 identity management, and more. Flexibility to design your own data flows
00:07:20 for any operations using training sentences. And finally it provides an SDK and templates
00:07:27 to build connectors to back-end services. Now let's walk through the technical architecture
00:07:35 for SAP CoPilot. There are two main components for SAP CoPilot:
00:07:41 the back-end system and SAP Cloud Platform. First, let's cover the back end.
00:07:48 In this scenario, we'll use SAP S/4HANA on- premise as the back-end system with Fiori
deployed
00:07:54 as the embedded system in your internal network. Meaning, your SAP Gateway and UI add-
ons

29
00:08:01 will be co-deployed in your SAP S/4HANA system. An SAP Web Dispatcher will also be
required.
00:08:08 Not only will it load balance your HTTP calls on your SAP S/4HANA system,
00:08:13 but it will also manage the routing rules between your SAP S/4HANA system
00:08:18 and the SAP Cloud Platform services. The SAP Cloud Connector will also be required
00:08:25 to connect your internal back-end systems to the SAP Cloud Platform for the required OData
services.
00:08:33 The SAP Cloud Connector creates a secure SSL tunnel from the SAP Cloud Platform
00:08:39 to your internal on-premise network. Within the SAP Cloud Platform,
00:08:45 this is where all the SAP CoPilot services will exist. The SAP CoPilot service consists of data
assistant,
00:08:54 skills building, collaboration, and bot integration services.
00:08:58 For single sign-on to work with the SAP Cloud Platform, SAP CoPilot will require SAML 2 and
principal propagation
00:09:07 to be set up and configured. You will also have the option of setting up
00:09:12 your back-end system as an identity provider. And, finally, we'll have additional services
00:09:18 for Conversational AI using our bot connector
00:09:24 and for creating native mobile applications using our SAP mobile services.
00:09:33 Next, we'll cover the technical requirements for SAP CoPilot more in detail.
00:09:39 From an infrastructure point of view, you'll need the following:
00:09:44 SAP NetWeaver 7.51 SP06 or higher, or 7.52 SP01 or higher;
00:09:51 an SAP Web Dispatcher 7.53 with the latest patch level; Cloud Connector 2.11.03 with
principal propagation;
00:10:02 a remote SAML 2.0 identity provider; and, on the back end, you'll need
00:10:08 SAP S/4HANA 1709 SPS01 or higher as a minimum release. And you'll need to configure
00:10:15 your SAP Fiori 2.0 launchpad as well. And finally, you'll need an SAP Cloud Platform SCP
account
00:10:24 with the subscribed SAP CoPilot services. Additionally, you'll need the following admin
permissions.
00:10:33 You will need access to the Fiori Launchpad Designer. This will allow you to configure the SAP
launchpad
00:10:40 target mapping, catalogs, and roles. Next, for the ABAP security configuration,
00:10:46 you'll need to configure principal propagation with the SAP Cloud Connector
00:10:51 and you'll need to configure a trust to the service provider using SAML 2.0.
00:10:55 And finally, admin rights to SAP Cloud Connector Administrator.
00:11:00 You'll need to register the proxy host for the SAP CoPilot service
00:11:05 and for configuration as an identity provider. Great, so now let's walk through a quick demo
and
00:11:14 screenshots on some of the capabilities of SAP CoPilot. Once your SAP CoPilot has been set
up,
00:11:26 the SAP Fiori launchpad will display the SAP CoPilot on the top right-hand corner of the
screen.
00:11:36 To use the SAP CoPilot, simply click on the icon, and the SAP CoPilot application will display
on the screen.
00:11:46 So from here, you can either speak or type a request to the SAP CoPilot interface.
00:11:52 In this example, we will type "show my orders" in the SAP CoPilot application.
00:11:59 SAP CoPilot will display the top three values on the list. You can either click on "View more" to
display more results,

30
00:12:09 or select the sales order numbers to display additional details of the sales order.
00:12:16 Here we clicked the sales order number, and more information displayed.
00:12:21 So now, by clicking "Open in App", this will open the sales order
00:12:28 in the respective SAP S/4HANA Fiori app in the background. Here, we are just displaying the
order we just clicked on.
00:12:40 Next, you'll also have the ability to collaborate and share information with other users.
00:12:45 From the Chat tab, click on "New Chat". Then click on the plus icon and select "Add Object".
00:12:55 From here, you can select recently used objects from current screen, recent, and all objects
used.
00:13:06 So next, select the object you want to share and click on "Add".
00:13:14 Now, you can add users in the system to the chat. Simply click on the "invite participant" icon

00:13:22 on the top of the right corner. From here, you can add more participants
00:13:28 to the chat and share data in real time. Finally, you have the option and ability
00:13:36 to share screenshots. Click on the plus icon and select "Screenshot".
00:13:42 From there, you'll have the option to capture a screenshot and add it to the same chat window.

00:13:51 Thank you, this concludes my high-level demo and walkthrough on some of the basic
capabilities of SAP CoPilot.
00:14:00 With this, we come to the end of the unit. In the next unit, we will focus
00:14:04 on development recommendations for SAP S/4HANA. Thank you for your attention,
00:14:11 and see you in the next unit. Bye-bye.

31
www.sap.com/contactsap

© 2019 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.

The information contained herein may be changed without prior notice. 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 or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP 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 e xpectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

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. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/copyright for additional trademark information and notices.