openSAP Gain Experience with a System Conversion to SAP S/4HANA Unit 1

00:00:04 Hello and welcome to our openSAP course, Gain Experience with a System Conversion to

SAP S/4HANA.

00:00:11 My name is Thomas Csapo, and I'm leading our global technical expert community

00:00:15 within our SAP S/4HANA Regional Implementation Group. We also call this team the SAP RIG.

00:00:22 I'm part of this team for the Asia Pacific Japan, the APJ region,

00:00:26 and I have helped, myself, many customers achieve successful projects with SAP S/4HANA.

00:00:32 This is the first openSAP course about technical SAP S/4HANA topics where our team

00:00:38 from the SAP S/4HANA Regional Implementation Group and our Product Management have teamed up together

00:00:44 and have prepared some hands-on exercises for you. The idea of this nutshell course is that

00:00:50 you're going to learn several important technical topics and details which will be required

00:00:55 for your conversion from SAP ERP to SAP S/4HANA. Let me provide you with an overview

00:01:04 of what contents we have prepared for you. You are now in unit one,

00:01:14 where I give you this overview about the contents, what we are going to cover in this course.

00:01:20 In order to perform the hands-on exercises, you will require access

00:01:23 to several SAP Cloud Appliance Library, so-called CAL, solutions.

00:01:28 You will learn which CAL solutions are available and how you can create the required instances.

00:01:37 Let's look at unit two. In that unit, we will explain

00:01:40 the preparation activities for the technical conversion. Those will be done with the Software Update Manager.

00:01:47 The unit will explain the prerequisites, and highlight where to find related information

00:01:52 to compatibility of add-ons, preparation activities for the Readiness Check,

00:01:57 the Simplification Item Check, and also Notes deployments

00:02:01 for the customer-vendor integration. Let's move on to unit three.

00:02:08 That unit is about our SAP Readiness Check. As you prepare your SAP S/4HANA transition project,

00:02:14 it is very critical to understand both the technical and functional considerations and implications

00:02:20 that can influence the project scope and duration. Our SAP Readiness Check tool for SAP S/4HANA

00:02:27 provides you with analysis tools and an interactive dashboard

00:02:31 to evaluate your existing SAP ERP system in preparation for the transition to SAP S/4HANA.

00:02:39 In this openSAP course, we will take a closer look at the preparation steps

00:02:42 for the SAP Readiness Check. We will look at a selection of checks of interests,

2

00:02:47 transfer and upload of the analysis data as well. And eventually we will evaluate some of the results

00:02:53 in the readiness check dashboard. In unit four, we will look into custom code checks

00:03:02 and the evaluation of results. In your conversion journey, one important task

00:03:07 is to identify custom code modifications so that you can continue using your custom developments

00:03:13 in the new SAP S/4HANA system. In that unit, we will learn about the main procedures

00:03:19 for custom code analysis, as well as the required tooling,

00:03:23 so that you can get some insights on code remediation scenarios.

00:03:31 Let's look at unit five. You will learn how the Maintenance Planner is used

00:03:36 within your SAP S/4HANA conversion project. We will start with the prerequisites for it, and objectives,

00:03:42 and finally cover specifically the handling of add-ons and business functions.

00:03:51 Unit six explains the execution of the technical conversion with the help of the Software Update Manager, our SUM tool.

00:03:59 It lists the prerequisites, explains the tasks of SUM,

00:04:02 and we will also highlight specific options for the execution.

00:04:06 Furthermore, we will provide an overview on required post-processing steps.

00:04:13 In unit seven, you will learn about the necessary steps

00:04:16 to configure analytics in SAP S/4HANA. We will describe the configuration of the analytics engine,

00:04:23 which will enable several end and key user tools. Such tools are for example,

00:04:27 the Query Browser or the Custom Analytical Queries tool. In addition, you will learn how to perform

00:04:33 content activation for SAP Best Practices for analytics. We will also provide some guidance on how to get started

00:04:40 with SAP S/4HANA Embedded Analytics. In unit eight,

00:04:48 you will get to understand the major steps and tools needed to activate and refine

00:04:52 your SAP Fiori user experience for SAP S/4HANA. We will gain hands-on experience in activating SAP Fiori,

00:05:00 and also activating initial business roles in our training environment.

00:05:07 Finally, in unit nine, the last but most important step in your journey to SAP S/4HANA

00:05:12 is to learn how to enable new product features and help your business become an Intelligent Enterprise.

00:05:19 In that session, you will learn about the new intelligent features

00:05:21 which come available as part of SAP S/4HANA. For example, Situation Handling, Flexible Workflow,

00:05:28 and so on. We will explain how you can extend these features

00:05:31 to greater lengths by leveraging the SAP Business Technology Platform,

00:05:35 SAP BTP. Let's take a look at all units in this overview again.

00:05:45 One thing to keep in mind is that we're focusing on technical topics in this course.

00:05:50 In a conversion project, however, you will also require help from functional experts.

00:05:54 This is required, for example, to clean finance inconsistencies,

00:05:58 and also to prepare for the customer-vendor integration. Those activities need to be done

00:06:03 before running SUM as the technical tool. We have prepared several nutshell courses for you,

00:06:10 and there's one available about customer-vendor integration as well, for example.

00:06:19 Now that you know the contents of our course, let's look into the hands-on systems,

3

00:06:28 I would like to stress that performing the hands-on exercises is not a prerequisite

00:06:32 to gain the record as achievement for this course. However, we highly recommend that you run through the exercises

00:06:39 to foster your understanding and knowledge, and I'm sure it will lead to some questions

00:06:44 that you can discuss with us in the openSAP course discussion forum.

00:06:50 In a real customer system conversion, you will of course require an SAP Support S-User.

00:06:57 We know, however, that some course participants don't have access to such a user.

00:07:02 Most of our exercises can be done without this user, but it is required

00:07:07 for the SAP Readiness Check unit's exercises. Now, how do you get access to your own hands-on system?

00:07:18 We have prepared four SAP Cloud Appliance Library, CAL, solutions for you.

00:07:22 And you will have to book your own personal instance. It is necessary to have an account with a cloud provider,

00:07:34 such providers are Amazon Web Services, Google Cloud Platform, or Microsoft Azure.

00:07:40 From SAP side, we offer you for each solution instance a free trial license for 30 days,

00:07:46 but your cloud provider will charge for the infrastructure usage.

00:07:51 So you should make sure that you suspend, respectively terminate, your instances

00:07:55 when you are no longer requiring them. In case of being multiple colleagues inside your company,

00:08:02 we recommend that you try to share your instances. That will help you keep your overall costs lower.

00:08:12 There are four different solutions available for you, each unit will indicate in the exercises

00:08:18 which solution will be required. The reason why we have prepared multiple solutions for you

00:08:24 is to give you snapshots of different phases during the conversion,

00:08:28 so you don't have to run the entire conversion procedure from beginning to end,

00:08:32 that would take you many more hours. We want to focus on some of the most important activities

00:08:38 for you to understand and learn in this course. Now let me give you a short demo,

00:08:47 how to create your own CAL solution instances. Okay, first of all,

00:08:56 you will have to navigate to cal.sap.com. On that Web site, you will have to log on.

00:09:04 You need an account for that, of course, and that account you either already have,

00:09:08 or you would create it during the registration procedure. Once you have logged on,

00:09:14 you can look at the different solutions. This is solution number one, the ERP source system

00:09:18 in its initial status. Let's look at solution number two.

00:09:26 Solution number two is the SAP ERP source system after preparation steps

00:09:30 before running our Software Update Manager tool. Solution number three is our SAP S/4HANA target system

00:09:40 directly after the technical conversion and before we do additional configuration.

00:09:50 And finally we have our solution number four, which is the SAP S/4HANA target system

00:09:55 with all included additional configuration. So now let me show you

00:10:05 how you can actually create your own instance by example of solution number two.

00:10:11 Once you're in the solution, click on Create Instance. In the next step,

00:10:19 you have to select your cloud provider account, give a name for the solution, and provide a password.

00:10:26 So let's just give it, as an example, the name "Solution 2: before SUM run".

4

00:10:33 We also provide a password, according to the password policy rules.

00:10:38 The next step is to click Create, but first let's look at the cost involved,

00:10:44 and let's create the instance. There will be a generation of a private key.

00:10:55 In a normal situation, you would typically download this key.

00:10:58 However, this is a training system, so we can just store it in the CAL solution.

00:11:02 This is the easiest way forward. There's no productive data in it.

00:11:07 Click on Close. And as you can see now,

00:11:10 the procedure of creating an instance can take up to 60 minutes,

00:11:14 so please be patient. Once your instance has been created,

00:11:21 we want to connect to it, of course. In this screen, we can see that the instance is active.

00:11:29 So that means we can connect. Let's click on Connect.

00:11:32 First of all, let's have a look at the Windows Remote Desktop, RDP.

00:11:37 Let's click on Connect. That will open up a pop-up

00:11:41 and we will click that link. Okay, next step,

00:11:46 click on Connect. User is administrator,

00:11:50 and the password is the master password that you just specified when you created your instance.

00:11:57 Confirm the security pop-up, and wait for a moment for your remote desktop to come up.

00:12:07 On the remote desktop, there's also a Welcome Page.

00:12:10 So I would like to invite you as well to have a look at that Welcome Page,

00:12:14 which will provide further details about your CAL solution instance.

00:12:23 Okay. In this example,

00:12:25 let's simply disconnect now from the remote desktop. Your remote session will be disconnected, okay.

00:12:35 Let's look at SAP GUI. We can also provide a direct connection to SAP GUI.

00:12:40 Let's select the client number 100. Click on Connect.

00:12:46 We have a pop-up again. Click on it.

00:12:50 Next screen, click on Allow, and provide a user and password as it is required

00:12:57 and instructed in the exercise. One of the usernames, for example, is 10STEPS2S4.

00:13:03 Password is, once again, the master password, as you have defined it when creating the instance.

00:13:10 Click on Connect. And you SAP GUI will come up

00:13:16 and you can start working. That's not the entire story though,

00:13:23 because we also need to understand how to suspend an instance so that we can lower the costs.

00:13:28 And the end of your exercises, typically you would see an instruction to suspend your instance.

00:13:33 Click on Suspend. Also finally,

00:13:38 you will terminate the instance when you're being told to do so.

00:13:41 Make sure that you can actually terminate it because you will lose all your data when you do so.

00:13:46 It will eventually be required to stop the instance creating costs for you.

00:13:56 Okay. During this course,

00:13:58 you will understand that the system conversion comes with a certain complexity.

00:14:04 We are a small team and might potentially have hundreds, or even thousands, of course participants.

5

00:14:11 This means our support will mostly have to be limited to the scope presented in the units

00:14:16 and prepared in the exercises. I hope for your understanding.

00:14:24 Let's wrap up this unit. You now know what the course will be about,

00:14:28 what you're going to learn, and how to create your own hands-on system instances.

00:14:34 I wish you lots of fun with this course.

6

Unit 2

00:00:05 Hello and welcome back to the openSAP course. I'm Ashuta Sheth.

00:00:10 I'm part of the Regional Implementation Group and based in the APJ region.

00:00:15 Here, we are in unit two. This unit is about required patches to the source system.

00:00:22 I'm going to provide here information on how to refer DMO, how to refer PAM,

00:00:29 Product Availability Matrix, architecture coverage, how to perform additional sizing

00:00:34 for Fiori and Embedded Analytics, how to prepare system for simplification item check,

00:00:40 Readiness Check, and CVI. Also, I'm going to provide you information

00:00:46 on where to find additional information before converting your ECC system to SAP S/4HANA.

00:00:56 So from where to start? Let's take an example.

00:01:00 If you have ECC 6.0 EHP6 on MS SQL 2008 R2 and installed on Windows Server 2008 R2,

00:01:09 refer to the respective note for SUM 2.0 version, and check what is the requirement of the source database.

00:01:17 As per the SUM 2.0 note, it requires MS SQL 2008 and higher

00:01:22 if the target SAP_BASIS is 7.51 and higher. Also, use Product Availability Matrix, PAM,

00:01:34 and check compatible operating system for SAP S/4HANA. Windows Server 2016 is supported for SAP S/4HANA

00:01:43 but also, you need to check Windows Server 2016 support for ECC 6.0 EHP6.

00:01:51 If database and operating system version is on a lower release,

00:01:57 then consider a upgrade, and treat it as a separate prerequisite project before conversion.

00:02:06 Platform coverage - in SAP S/4HANA 2020, inside of this, base component is S4CORE 105.

00:02:15 It is again, based on S/4HANA foundation 2020. It has ABAP Platform 2020,

00:02:22 and it is again based on SAP Basis 7.55 and SAP Kernel 7.81.

00:02:30 SAP S/4HANA 2020 based on HANA database 2.0 SPS 05.

00:02:39 Supporting operating system is Windows Server 2016, SUSE Linux 15, Red Hat Linux 8, and so on.

00:02:48 That means if you are on a lower operating system, you may have an issue.

00:02:53 That is why Software Update Manager supports temporary freeze.

00:02:58 If the source system is lower, then you have to refer the operating system

00:03:03 listed here in this SAP Note, and you can convert your system to SAP S/4HANA.

00:03:10 But after conversion, you can update the operating system.

00:03:18 There are some additional information notes. Always check release information notes

00:03:23 and additional release information notes, where you will get information

00:03:28 on minimum database revision and what would be the minimum support pack level

00:03:35 of NetWeaver or ABAP-based system. And from additional information note,

00:03:40 you will get information on if your support pack is on higher level in ECC system,

00:03:47 then how to select target SAP S/4HANA release as fix pack or service pack.

00:03:55 Let's take an example. If you have ECC 6.0 EHP6

00:04:01 and which has SP26, then target to SAP S/4HANA 2020 fix pack 00 has restrictions.

00:04:10 In that case, you have to refer to the note for fix pack 01. SAP Note 2655761, which talks about restrictions

7

00:04:22 and recommendations for HANA database usage for SAP S/4HANA. It gives you general recommendations

00:04:29 on how to pick or how to select SAP HANA database revision for SAP S/4HANA.

00:04:36 So how to refer to this note? First of all, the first point is check

00:04:40 the release information note of target SAP S/4HANA release, where you will get information on minimum database revision.

00:04:50 You will get general advice. Also, it recommends to use higher

00:04:55 supported HANA database revision. Second thing, check tabular information

00:05:00 given in this SAP Note, and check if anything would apply

00:05:07 based on the decision which you made in step number one.

00:05:11 Third step is if there is any additional recommendation from the SAP support team,

00:05:16 if something like fixed in revision Y, then use that revision.

00:05:21 Also, refer to SAP Note 2600030. Now, this is for parameter recommendation.

00:05:28 These are revision-specific sometimes, for Y revision if a workaround is available,

00:05:34 but no need to fix it for Z revision since Z revision is the latest revision,

00:05:38 and it is already fixed in Z revision. Version interoperability -

00:05:46 to validate version interoperability, refer to SAP Note 2251604.

00:05:56 To check potential dependencies for older releases of SAP products,

00:06:01 for that, you can use Upgrade Dependency Analyzer. Also, you can refer to the wiki page,

00:06:07 which is mentioned here in this PPT. Plan necessary pre-projects to keep system

00:06:14 interoperability in your current system landscape. These checks do not have any business impact.

00:06:22 If one or more systems in your landscape need to be upgraded, it would require

00:06:28 further analysis on business impact. Integration dependencies with NetWeaver system.

00:06:38 Refer to Note 2251604. Basically, SAP NetWeaver 7.31 and 7.40

00:06:48 went out of maintenance the at end of 2020. Installation of SAP S/4HANA on-premise system

00:06:56 always requires connected SAP NetWeaver systems based on Java to be on version 7.50.

00:07:04 This is the diagram, and this is the diagram from SAP Note 2251604,

00:07:11 which gives you detailed information. On-premise integration,

00:07:18 this is the reference tabular information given here. This is basically integration

00:07:23 between the SAP S/4HANA system and other solutions. These notes are revision-specific.

00:07:30 Let's take an example for SAP GTS. GTS is SAP Global Trade Services.

00:07:36 Installation of GTS 10.0, 10.1, 11.1 on a separate system is supported,

00:07:43 and its connection to SAP S/4HANA is also supported. That means a side-by-side approach is supported.

00:07:50 In SAP S/4HANA, GTS plugin is no longer required. Refer to SAP Notes for further information.

00:08:00 This is the screenshot from sizing report. First of all, sizing is important

00:08:06 if you're planning for on-premise deployment because you float quotation in the market for SAP HANA vendor,

00:08:11 and for some customers, this is a lengthy process, depending on their policy.

00:08:18 To have the latest version of sizing report, you have to refer to SAP Note 1872170.

00:08:27 FAQ documentation is given in the note based on your SAP Basis and ST-PI release,

00:08:33 or you can complete SAP HANA database sizing well in advance. We recommend to archive as much data as possible

00:08:41 to reduce technical downtime, as well as the memory data footprint

8

00:08:45 of the target HANA database. Let's check how to execute that.

00:08:50 Go to transaction sa38 and access program /SDF/HDB_SIZING.

00:08:56 Click on the Execute button. So based on your SAP Basis release,

00:09:01 execute this sizing report. Select "Perform Sizing of SAP S/4HANA",

00:09:07 and select HANA database 2.0. In technical options,

00:09:11 you can set the number of parallel dialog processes from default.

00:09:16 By default, it is one. You can execute it directly,

00:09:19 or you can execute it in the background. So once you execute that,

00:09:26 initial means whenever you're doing conversion, it estimates what will be the memory

00:09:32 requirement after conversion. Also, you need to think about buffer.

00:09:36 Basically, buffer is your future database growth. There are some housekeeping jobs, notes, reports.

00:09:44 Those are available, which talk about how to reduce technical object size

00:09:50 and how to handle that. When you start sizing, you must make sure

00:09:55 all relevant activities related to the system housekeeping, like regular jobs,

00:10:01 data management and archiving, deletion of unnecessary clients,

00:10:05 deletion of unnecessary data, for example, application logs,

00:10:10 and every item that can help you to reduce your actual database size

00:10:15 was completed or evaluated in advance. Sizing considerations - for new implementation

00:10:25 greenfield customers, sizing report is available. For customers who are going to transition

00:10:31 from ECC to SAP S/4HANA, for them report is available. Many deployment options are there.

00:10:40 If sizing report is matching with your hardware, then you can go for TDI.

00:10:46 Basically, it gives you more flexibility and choice. Cloud deployment is a fully managed service.

00:10:53 You can even reach out to vendor for HANA appliance. You can even subscribe SAP CAL

00:11:02 for POC or demo and hands-on purpose. Sizing for a front-end server.

00:11:15 This is necessary to add resources for Fiori in case

00:11:20 FES is embedded in SAP S/4HANA back-end server. It can be estimated with Quick Sizer.

00:11:27 Let's take an example. If there are a thousand users

00:11:31 and half of them, like 500 users, log in in peak hour, from 9:00 a.m. to 10:00 a.m.

00:11:37 In that case, here the screenshot is mentioned from the sizing, Quick Sizer,

00:11:43 where you have to put information, like 500 is the highest number of logon users per hour,

00:11:49 and you have to mention start and end time as 9:00 a.m. and 10:00 a.m.

00:11:55 Sizing for Embedded Analytics. It is necessary to add the resources for Embedded Analytics

00:12:01 which can be estimated in Quick Sizer too. It is recommended to check

00:12:06 with an analytics expert for this sizing. Let's take an example.

00:12:11 If you have a thousand users and 500 users log in at peak hour,

00:12:16 and users access 10 tiles, so 10 times 500, that means 5,000 queries are getting executed

00:12:25 in S/4HANA system. So here, I'm not considering caching.

00:12:31 So your hardware must be capable to match this throughput.

00:12:35 Also, queries have to be fine-tuned as well. Maintenance Planner is a successor of MOPZ.

9

00:12:45 Earlier, people used to generate stack file from MOPZ. Now, Maintenance Planner is used.

00:12:51 Basically, this is the cloud-based tool, and your release mentioned here in the PPT.

00:12:55 This is used for installation, update, upgrade, conversion.

00:12:59 Maintenance Planner checks business function and add-ons as well.

00:13:04 If you're planning for embedded Fiori deployment, then it is possible to include that part

00:13:10 when you generate stack file. Add-ons can be deployed using two scenarios;

00:13:20 side-by-side usage, co-deployment. So basically, it enhances functionality of your system.

00:13:27 If an add-on is no longer required, in that case, check SAP Note,

00:13:32 and check whether you can uninstall that add-on. Also, you need to check additional

00:13:36 licensing implications regarding the add-on that is compatible.

00:13:41 If the add-on is not compatible, and if it is a third-party add-on,

00:13:45 then check with your third-party vendor. Check if he is ready to provide an compatible add-on.

00:13:51 If an add-on is not supported by the vendor, or the vendor is not ready to support,

00:13:57 in that case, this will be a serious situation. Refer to SAP Notes, which are given here,

00:14:03 how to uninstall the add-on if you're planning to uninstall.

00:14:09 Basically, Maintenance Planner will analyze currently deployed software components.

00:14:15 Sometimes you may get a warning when you generate a stack file from Maintenance Planner,

00:14:22 like maintenance transaction requires equivalent support packages,

00:14:25 and those packages are not available. In this case, you will have to wait for the next

00:14:31 fix pack, service pack, or release. If that add-on is not used,

00:14:38 then check if you can uninstall that add-on. Refer to this blog for further information.

00:14:47 Business function preparations. It is important to find out the status of business function

00:14:52 at an early planning stage for system conversion. We need to be aware of any business function

00:14:59 which is switched on in ECC source system, and which is defined as ALWAYS_OFF

00:15:04 in target SAP S/4HANA. In that case, system conversion is blocked.

00:15:11 Refer to these notes, which are given here, that gives you a list of ALWAYS_OFF

00:15:14 and ALWAYS_ON business functions. Readiness Check, it is the high-level analysis

00:15:22 which gives you results in dashboard format. Let's look how to apply notes

00:15:27 and how to prepare the system for Readiness Check. First of all, you have to refer to

00:15:33 SAP Note 2758146 and 2912617. It has a table like Excel.

00:15:45 It gives you a list of relevant notes to prepare the system for Readiness Check.

00:15:51 Once you apply all these SAP Notes in the development system, then you can transport it to across the landscape.

00:15:59 After that, you can run ABAP program and download archive zip file.

00:16:04 Then you can log in to the Readiness Check application, which is again a cloud-based application,

00:16:11 and you can click on Start New Analysis and upload this file.

00:16:17 So the will be available after some time, and after that, you can upload

00:16:23 custom code analysis file. After a few minutes, it will be reflected there.

00:16:28 We have unit three, where you will get detailed information on how to perform Readiness Check

00:16:35 and what is the Readiness Check. SI check is a list for data model

10

00:16:43 changes in SAP S/4HANA. This is the mandatory step.

00:16:47 You can access SI items via SI catalog. As of SAP S/4HANA 2020,

00:16:53 there are around 660 objects are available. Why is SI check mandatory?

00:16:59 Because the Software Update Manager tool executes it two times;

00:17:03 one is in the configuration phase, and second will be in the pre-processing phase.

00:17:10 Make sure you have performed all mandatory steps. Otherwise, the conversion procedure

00:17:16 can stop to ensure a consistent system conversion. How to implement SI check notes,

00:17:23 which is given here in SAP Note 2399707 and 2502552? In order to minimize the number of notes,

00:17:35 you have to enable system for TCI implementation. How to do that?

00:17:38 It is also stated here in the SAP Note. Each SAP S/4HANA release, or fix pack, or SPS

00:17:46 has a specific minimum version of SAP Notes. If you're in an early stage,

00:17:52 it is always recommended to use the latest version of these SAP Notes.

00:17:57 Once you convert the development system, freeze the check contents of the SI catalog.

00:18:03 SI checks gives you a relevance check as well as a consistency check.

00:18:11 CVI implementation is a prerequisite for converting an SAP ERP system to SAP S/4HANA.

00:18:18 You can check the FAQ document and refer to the CVI cookbook.

00:18:24 Implement required notes to monitor and run CVI. CVI is Customer-Vendor Integration.

00:18:31 For each phase, there are many activities. You can find out detailed information in this blog.

00:18:43 Deletion of unnecessary clients. Client 006 is Early Watch client,

00:18:54 which is set up in your ECC ERP system, and which is not required for SAP S/4HANA.

00:18:59 Refer to this note which is mentioned here and plan uninstallation for that client accordingly.

00:19:05 If there are any unused clients, you can plan it for uninstallation.

00:19:13 If you do not know the user ID and password of standard sapstar user,

00:19:18 then you can set parameters. Also, there are SQL commands given here

00:19:22 on how to reset the password from database level. Verify implemented note for Readiness Check,

00:19:29 simplification item check, and CVI. So exercise documentation is given here.

00:19:35 You just copy paste notes for Readiness Check and click on Execute.

00:19:40 So once you execute here, you will get list of SAP Notes for Readiness Check,

00:19:46 which we implemented in this SAP CAL solution. Go back in S-Note.

00:19:55 In Note Browser, paste SI check notes, and click on Execute.

00:20:04 Similarly, you have to check notes for CVI. Go back.

00:20:14 Check exercise document, and enter SAP Notes which are mentioned

00:20:19 there for CVI, and click on Execute. So it will give you a list of SAP Notes

00:20:32 that we have implemented in CAL system for CVI. Key takeaways - sizing is an important activity,

00:20:41 and you must consider Fiori and analytics requirements on top.

00:20:46 Start early preparation activity in SAP ERP system. Also try to archive as much you can

00:20:53 because technical downtime and HANA memory footprint depend on that.

00:20:59 Prepare system for Readiness Check and SI check at an early stage.

00:21:03 Make sure you have checked hardware compatibility. Check availability of add-ons in an early stage

11

00:21:09 because if any third-party add-on is not compatible, then you have to reach out to the vendor,

00:21:14 and you have to check for a compatible add-on. Thank you, I would like to thank you for your attention,

00:21:21 and I hope you're going to enjoy the remaining sessions of the openSAP course.

00:21:26 With that, goodbye.

12

Unit 3

00:00:04 Hello, and welcome to unit three of the course, Gain Experience with a System Conversion

to SAP S/4HANA.

00:00:11 This unit covers the SAP Readiness Check and will mainly talk about the data collection

00:00:16 for the SAP Readiness Check and how to analyze the results you see

00:00:20 in the SAP Readiness Check dashboard. My name is Astrid Tschense

00:00:24 I'm in the global IT Planning Architects team in the customer success area,

00:00:28 and I present to you from Walldorf in Germany. We start with the first question.

00:00:35 What is SAP Readiness Check, and how do you collect the data in your ERP system

00:00:40 for the SAP Readiness Check? The SAP Readiness Check is a tool that helps organizations

00:00:46 perform functional and technical assessments of their current SAP ERP systems,

00:00:52 prior to an SAP S/4HANA migration. The Readiness Check analyzes the usage

00:00:57 and the configuration data of existing systems. It determines the conversion compatibility

00:01:03 and preparation steps and presents the results in an interactive dashboard.

00:01:08 It helps you to find out which simplification items are relevant for you.

00:01:12 How high the effort is for each simplification item. And when you can start with these activities.

00:01:19 Custom code is another very important topic. The custom code analysis identifies mandatory change areas

00:01:25 due to the simplified application architecture of SAP S/4HANA.

00:01:30 It shows which ones can be solved by quick fixes and which ones require manual effort,

00:01:35 or even a functional redesign by an application expert. And of course, the compatibility of add-ons

00:01:42 and business functions is checked. For incompatible add-ons and business functions,

00:01:47 the conversion of your system to SAP S/4HANA will be blocked during the execution

00:01:51 of the Software Update Manager. So it is very important to solve these issues

00:01:56 prior to the conversion and the preparation phase. Forrester Research states

00:02:01 that the time saved with SAP Readiness Check by reducing project risk is at least three months.

00:02:07 And the efficiency in collecting and analyzing system data is at least 60%.

00:02:13 Now, how do you start with the SAP Readiness Check? First, you have to prepare your source ERP system,

00:02:19 which is at least an ERP 6.0. There's a central SAP Note for the Readiness Check,

00:02:25 which explains all notes you have to implement in your ERP system

00:02:29 to collect several types of data for your analysis. You decide yourself which analysis you want to run

00:02:35 and collect the corresponding data. Then you execute the analysis job

00:02:39 and upload the results to the SAP Readiness Check front end. It is statistical data that you're collecting

00:02:45 and not business data, but still you can review the collected data

00:02:49 and mask anything sensitive before sending the data over to SAP.

00:02:55 You see the application landing page link here to the right, with the blue button Start New Analysis.

00:03:01 There you upload your data zip file, which is then processed and displayed in the dashboard.

13

00:03:07 There's of course documentation for the Readiness Check available in the SAP Help Portal,

00:03:11 but also an expert guided implementation session, recorded overview sessions,

00:03:16 like the one you see on the right of the help page. And we publish blogs on each new feature

00:03:21 and update of the tool. Let us take a closer look at the process steps

00:03:29 of the data collection and the analysis upload. First, you prepare your ERP system

00:03:35 by implementing the analysis collector notes as described in the central SAP Note 2913617.

00:03:43 Then you transport them to the system being analyzed. This can be the production system

00:03:48 or a recent copy of the production system. You have already heard about these required notes in unit two.

00:03:55 In addition, you check if the simplification item catalog is available

00:03:58 in the newest version. Then you execute the collectors.

00:04:02 To do this, you select the target version of the S/4HANA system you are converting to,

00:04:07 and you select all data collectors you want to process. Then you can schedule the analysis collector jobs

00:04:12 and wait until they are processed successfully. The next step is the transfer of the collected data

00:04:18 to the SAP Readiness Check launch page, where you create a new analysis and upload the data.

00:04:24 As I already said, it is possible to review and mask the collected data

00:04:29 if there is sensitive information inside before you upload.

00:04:33 Finally, you can explore the results in the new analysis in the SAP Readiness Check.

00:04:39 We will take a closer look at some example results in a few minutes.

00:04:44 Here I have included the central SAP Note for the Readiness Check.

00:04:47 And this note is being updated frequently and contains first of all,

00:04:51 the list of all available analysis included in the Readiness Check

00:04:55 with the SAP Notes you need to implement, if you want to include the analysis.

00:05:00 In the table you see which analysis is mandatory and the SAP Notes must be implemented,

00:05:05 and which analyses are optional. The SAP Note also contains important information

00:05:12 and frequently asked questions. So it is really beneficial to read it completely

00:05:16 before you start with the preparation for the SAP Readiness Check.

00:05:20 For example, it explains how you can review the data before uploading it to the Readiness Check.

00:05:26 And it highlights the data collectors, which you better run separately

00:05:30 because they may take some time to be processed like the collector for financial data quality

00:05:35 and the data volume management, or which you better run later,

00:05:39 like the simplification item consistency check. When the ERP system is converted to the new S/4HANA system,

00:05:47 there are changes in the application functionality and in the coding,

00:05:51 which are documented in the simplification item catalog. SAP Readiness Check refers to the simplification item catalog

00:05:58 in the ERP system to identify the relevant changes

00:06:02 and lists the required simplification items, especially all you have to solve

14

00:06:06 before you can start the conversion. The catalog can be uploaded, checked,

00:06:11 and updated with the report /STF/RC_START_CHECK. If there has never been any simplification item content

00:06:18 in the ERP system, the report downloads the content automatically once.

00:06:23 By default the report does not automatically update the simplification item catalog content from the SAP server.

00:06:30 But if you want to download or update the content from the SAP server,

00:06:34 you explicitly have to trigger this via the update catalog with the latest version from SAP.

00:06:40 If there is no connection from the system to SAP, you could also download the content

00:06:46 from the simplification item catalog and upload it manually. When you come close to the conversion date,

00:06:52 it also makes sense to freeze the version of the simplification item catalog

00:06:56 and not incorporate any newer versions. After you have prepared the ERP system

00:07:03 with all required SAP Notes and checked the simplification item catalog,

00:07:07 you can execute the program, RC_COLLECT_ANALYIS_DATA. This should be done in the productive client

00:07:14 to collect the relevant data, with the exception of the simplification the item consistency check.

00:07:20 This ensures that all checks are executed properly. In case you have more than one productive client,

00:07:26 the result of the business process discovery check, the business partner check,

00:07:31 and the data volume management will currently only include the analysis of the client

00:07:36 where the SAP Readiness Check was executed. All other SAP Readiness Check analyses

00:07:40 are client-independent, and you will always get complete results of the ERP system,

00:07:45 considering the data of all productive clients. The simplification item consistency check,

00:07:51 which you should run later anyway, after you have solved most of the simplification items,

00:07:56 must be executed in client 000, which is also where the Software Update Manager is executed.

00:08:04 Select the target S/4HANA version, usually you select the newest available,

00:08:09 and select all the checks you want to include in the first analysis.

00:08:13 Ensure that the simplification item consistency check box is not selected.

00:08:18 And you may already include the simplification item effort drivers

00:08:22 because they give a good indication of the simplification items

00:08:25 which would potentially require the most effort in your specific system.

00:08:30 Note that there are some interdependencies of the data collectors,

00:08:33 like the planned downtime calculator will only show data if the HANA sizing report is included in the analysis.

00:08:41 And once you have finished the selection, schedule the analysis and monitor the collector jobs

00:08:46 until they are processed successfully. You may already know

00:08:52 that there is the simplification item check as an ABAP tool. And now we talk about simplification items

00:08:57 in the SAP Readiness Check. So let me elaborate a little on this,

00:09:01 why we have both of them. While both the SAP Readiness Check

00:09:05 and the simplification item checks are able to display information

00:09:09 on the simplification item relevance and the consistency, They serve different purposes,

00:09:14 and they are both required. In the roadmap viewer graphic on the slide,

15

00:09:18 you see that the SAP Readiness Check is used in the discover phase, it is mainly a planning tool,

00:09:24 which you should run already early in the project, and before the system conversion

00:09:29 really starts to be planned, including the simplification item-related tasks.

00:09:35 Nevertheless, it can be rerun and used for tracking the resolution of the simplification items

00:09:41 via the burndown chart of the simplification item consistency errors,

00:09:45 and also for progress in all the other checks. The simplification item check on the other side

00:09:51 is used on operational level during the cleanup of the simplification item consistency errors

00:09:57 in the prepare phase, up to the downtime in the conversion.

00:10:03 Hence the simplification item check offers some more fine-granular control

00:10:07 over running the checks. This includes the option to rerun the checks

00:10:12 for individual simplification items instead of running all checks again,

00:10:16 like in the SAP Readiness Check. In case you just want to recheck if a specific error

00:10:22 which you have just fixed is really gone, you better take the simplification item check.

00:10:27 In addition, the simplification item check offers the option to exempt certain types of errors.

00:10:32 And before the conversion, the Software Upgrade Manager

00:10:35 starts the simplification item check again for a final examination.

00:10:40 For more information on this complete topic, you may refer to the S/4HANA transition roadmap

00:10:46 in the roadmap viewer. Now we see a short demo of the first steps I have explained.

00:10:55 In our first demo, we want to have a look in our source ERP system

00:11:00 in transaction sa38. And we want to have a look

00:11:04 at the simplification item catalog. So we check

00:11:12 for the /SDF/RC_START_CHECK, and execute this program.

00:11:18 And here we see the simplification item check options. We first have the target S/4HANA version.

00:11:25 And here we can select the S/4HANA 2020 initial shipment stack

00:11:30 that we are using currently for this openSAP course. And you see here below the simplification item catalog source.

00:11:39 So currently we have a local version uploaded in this system, which we do not want to change now,

00:11:45 but we could update the catalog with the latest version from SAP

00:11:50 if we are connected to the SAP server. If we are not connected to the SAP server,

00:11:56 we could upload the simplification item catalog manually from file. And you could also download

00:12:02 the current simplification item catalog, from this point here.

00:12:06 We do not want to change anything here. We just wanted to check

00:12:09 if there is a simplification item catalog uploaded. If we are new in a system and there is no catalog yet,

00:12:17 the catalog gets uploaded automatically with the first run of this program here.

00:12:23 So now we want to go back and go to our Readiness Check collector program.

00:12:36 So we have the RC_COLLECT_ANALYSIS_DATA data program that we want to execute.

00:12:42 And now here again, we select the right target S/4HANA version

00:12:46 against which it should be checked. So we have the initial shipment stack now in here,

16

00:12:52 and here you see all the available checks for the SAP Readiness Checks you can select.

00:12:59 And for example, we have the transaction usage in here. We check for the interfaces, business process analytics,

00:13:07 the business warehouse extractors. And also we have here the data volume management.

00:13:12 And let me tell you, if you have a lot of data in the system,

00:13:17 it may make sense to take this check mark out and to run this check separately.

00:13:23 The same is with the financial data quality, which we also leave out in here,

00:13:27 because this is a long running job, depending on the amount of data you have.

00:13:32 And it makes sense to execute this separately. Here in the simplification item area,

00:13:38 the simplification item consistency is a check we should run later

00:13:43 when we have already prepared and solved some of the simplification items

00:13:48 to check the consistency. But what we want to include now

00:13:51 is the simplification item effort drivers because this makes a lot of sense to include this.

00:13:57 They check for the potentially high-rated simplification items, and display details

00:14:06 about the effort for the single checks. So now you can schedule the analysis,

00:14:13 which we have already done here in our system, and then you can check the job.

00:14:19 So we enter here our RC_COLLECT_ANALYSIS_DATA job. And we want to see the job monitor for this.

00:14:29 And now you see here, okay, this has been executed, but the status is canceled.

00:14:34 So we display the details in the job log, click here on the job log.

00:14:39 And now you can go through the complete list and check where the problem is

00:14:44 and how you can solve this one. But this will be one of your exercises.

00:14:49 So I will not scroll down now here because you have to find out.

00:14:58 Question two is, how do I create and work with the SAP Readiness Check analysis?

00:15:04 When the data collector job is completed, you download the analysis data.

00:15:09 This generates a zip file, which you should store locally.

00:15:12 You can now review the collected data and mask any data you rate as sensitive before you upload the zip file

00:15:18 to the Readiness Check application. Open the Readiness Check landing page

00:15:22 and create a new analysis. Note that the analysis is visible to all users

00:15:27 that belong to the customer number, but you can choose also that all SAP employees

00:15:32 may access the analysis, but this is optional.

00:15:35 Access can also be granted to single e-mail addresses at a later point in time.

00:15:43 Once the data is processed, which usually takes less than 30 minutes,

00:15:46 you can start browsing through the results in the dashboard. The dashboard consists of tiles with graphics

00:15:53 and summaries per topic, and you can click on a tile to open the details view.

00:15:58 You can also generate a downloadable document as an offline record,

00:16:02 and you can add comments to the single values and activities for collaboration with a project team.

00:16:08 On top of the dashboard, you see the relevant simplification items

00:16:12 with the effort ranking and the amount of action items per conversion phase.

00:16:16 In the second row, you see the add-on compatibility and the business function compatibility.

00:16:22 Below you see the sizing estimation, and next to it, the custom code analysis.

00:16:28 Then we have the recommended Fiori apps based on the usage statistics

17

00:16:31 in your existing ERP system, and next to it, the compatibility analysis

00:16:36 of the existing BW extractors and IDocs, and there are more checks below.

00:16:43 We now want to take a closer look at the simplification items and the effort ranking.

00:16:48 Effort ranking shows the amount of simplification items with medium and potentially high effort

00:16:53 for a better effort estimation. You can display all activities

00:16:57 belonging to one simplification item and open detailed documentation for it.

00:17:02 You can set a status to the items and add comments by working on the single simplification items.

00:17:08 And in addition, you can include the results of the detailed simplification item consistency check later

00:17:14 in the project. The activities view on the simplification items

00:17:19 categorizes the activities in mandatory, conditional, and optional on the one hand,

00:17:26 but it also sequences the activities into the project phases.

00:17:30 This helps you sort out how to start. So focus on the most important activities first,

00:17:37 for example, which business decisions are to be made. Then filter on mandatory activities

00:17:43 to ease the project planning, and take the pressure out of the conversion project

00:17:47 by addressing the right topics early in advance. A very helpful feature

00:17:54 for working with the simplification items is the analysis of the effort drivers

00:17:59 for the potentially high-ranked items. The effort drivers show factors that influence the effort

00:18:05 of implementing the potentially high-ranked simplification items, which may help you to come to a better effort estimation,

00:18:12 like the number of active company calls, or if asset accounting and general ledger

00:18:16 are already migrated from classic to new, or how many parallel currencies are defined in the system,

00:18:22 how many company codes, and the like. Let's see a short demo of the navigation

00:18:29 and the SAP Readiness Check dashboard, and where to find the details

00:18:33 I have explained on the last slide. Now let's move over to the demo

00:18:39 to give you a live impression of the dashboard. You open the SAP Readiness Check start page,

00:18:44 for which an S-user or a partner user is required to log in.

00:18:48 Select the blue button, Start New Analysis, enter a name for the analysis, and your customer number,

00:18:55 and then select the file with the data that you have downloaded in the ERP system,

00:19:02 and open it here. Then you have to accept the terms of use,

00:19:06 saying that you acknowledge that you have read the SAP Readiness Check disclaimer,

00:19:10 and the SAP Readiness Check terms of use. Then you can select the Authorization checkbox,

00:19:16 which means that you acknowledge that all SAP employees may access and use your Readiness Check results

00:19:22 for SAP business purposes, like for support, services, and marketing.

00:19:27 If you do not check this, the analysis will only be visible for you.

00:19:32 Later on, then you can specify e-mail addresses and grant access to single persons,

00:19:37 but for everybody else, your results will be hidden. Then you click Create, and after 30 minutes or so,

00:19:45 you can access your results from the list of recent analysis.

00:19:50 So from this list here, it will appear then in here. I have opened this already.

18

00:19:57 And on top of this dashboard here, now you see the simplification items tile,

00:20:02 which is sorted by relevance, and on the other side by effort ranking,

00:20:07 where low effort means, for example, that you can handle this simplification item in a few days,

00:20:13 medium would mean in a few weeks, and potentially high means that this is significant effort,

00:20:20 which you should examine in detail. If we click on the title of the tile,

00:20:25 then we can see the details here. You have the bars you can use for filtering.

00:20:30 And if we, for example, select here now the potentially high ones,

00:20:34 they are displayed in detail below. And here you see in the effort ranking,

00:20:40 there are also calculated ones which contain additional effort drivers.

00:20:45 And we can open these ones, and you see here now, an example of effort drivers

00:20:51 for a potentially high-ranked simplification item. And you see here that some are indicated in green,

00:20:58 which means there is no issue, no work to do, but others are displayed in red.

00:21:04 Like here, for example, in the general ledger, this is still classic,

00:21:09 and this has to be changed to the new mode. Then we have slides in here with an indicator,

00:21:17 like here, for example, the number of currencies. So there are zero currencies in our system,

00:21:22 so this means no effort, and so on. So if you can go down this list

00:21:28 and, for example, number of company codes with more than one open fiscal year

00:21:33 here is extremely high in our system. So this is an important effort you have to calculate,

00:21:41 and so on. So these effort drivers are really important

00:21:45 and it helps you to have a good estimate on the effort of the simplification item.

00:21:53 So now we go back to the dashboard, and we go over to the activities.

00:21:58 So the activities related to simplification items, they are sorted by conditions, so meaning

00:22:05 you see the mandatory ones, the conditional, and the optional ones on the one hand,

00:22:11 and on the other hand, you see the conversion phase. So some of these activities can be solved

00:22:19 before the conversion project or during the conversion project.

00:22:24 Others are done later, so during the conversion project,

00:22:28 or you can do them at any time. So if we go into the details of this one, you see here,

00:22:36 you can filter for the conversion phase. So if you select here "Before conversion project"

00:22:42 and for the condition "Mandatory", you see all the activities you should start with

00:22:49 when you begin to plan the conversion. So going back to the dashboard,

00:22:57 I want to show you one additional tile that is really important,

00:23:01 so the S/4HANA sizing. So here you see a sizing simulation on this detail view,

00:23:11 you see here the influencing factors. Like you have the initial target S/4HANA size,

00:23:17 which is calculated from your current ERP database size. You can enter an estimation of future database growth.

00:23:25 Like in percentage here, we have a 5% database growth in five years.

00:23:33 And if you have the data volume management check activated, you can see here how you could archive,

00:23:44 how much data you could archive and how you can reduce the data volume.

00:23:48 So this is also included in the calculation in here, and you can also enter an estimation on growth

19

00:23:57 coming from future functionality. So here you also enter a value in percent

00:24:03 and the number of years you are calculating with. And this brings you to a complete

00:24:10 S/4HANA sizing simulation. Here we have some helpful buttons also.

00:24:22 So you have the Learn More section here, which opens the side panel.

00:24:27 And here we have very good documentation for each tile, which gives you indications for the next steps,

00:24:34 but also some general information on the checks that you are looking at currently,

00:24:40 and also some additional remarks. And then we have also a Web assistant included.

00:24:46 So you see here the buttons explained, for example, and this is something which is very helpful

00:24:55 for the navigation on the dashboard. So what you have learned in this unit is that

00:25:03 the SAP Readiness Check helps you to prepare for the conversion of your existing ERP system

00:25:08 to the SAP S/4HANA system. Then SAP Readiness Check offers a variety of checks,

00:25:15 which can analyze both functional and technical aspects of the existing system

00:25:19 in the preparation for the conversion. You perform the data collection

00:25:23 in the source ERP system yourself, and you can review and mask the data before you upload it

00:25:29 to the Readiness Check tool. You create the analysis

00:25:32 in the Readiness Check landing page, and you define who has access to it.

00:25:37 And you can navigate in the analysis dashboard, use the filtering options, and find additional information

00:25:42 on the side panel. With that, we come to the end of this unit.

00:25:46 And I thank you for listening. Stay tuned for unit four,

00:25:50 with my colleague, Gilbert Wong.

20

Unit 4

00:00:07 Hello. My name is Gilbert Wong,

00:00:09 and I'm an SAP S/4HANA technical product expert and part of the SAP S/4HANA Regional Implementation Group.

00:00:17 I'll be presenting unit four from Southern California in the United States,

00:00:21 and the topic will be custom code checks and evaluation of results.

00:00:26 Hopefully after this unit, you'll get a better understanding of the tools available

00:00:29 to assist you with your custom code adaptation as you move to SAP S/4HANA.

00:00:37 Why do I need to run custom code remediation in a system conversion to SAP S/4HANA?

00:00:47 SAP S/4HANA is a new product line built on the new architecture and data model

00:00:52 containing renewed application and new UI technology. SAP customers have invested heavily

00:00:59 into custom ABAP development within their source SAP ERP system.

00:01:04 When moving to SAP S/4HANA, you want to make sure that that custom code

00:01:08 developed in your source ERP system will work in the new SAP S/4HANA landscape.

00:01:16 Since there are significant changes within the SAP S/4HANA simplification and data model,

00:01:21 much of the custom code developed in your SAP ERP system may or may not work for several reasons.

00:01:28 For instance, certain functionality in your SAP S/4HANA

00:01:33 will not be available anymore, or function modules have been deprecated or removed,

00:01:39 resulting in syntax errors or ABAP dumps. Or due to the simplification in S/4HANA,

00:01:46 some data models or data types have changed. Or if you're using any database-specific vendors,

00:01:53 specifically native SQL, or if you have database operations

00:01:57 against pooled or cluster tables, these will not work in the new HANA database

00:02:03 and will need to be adapted. As your system moves to the new data model,

00:02:14 objects developed with the SAP ERP data model will need to be adjusted.

00:02:20 In the new SAP S/4HANA model, some BADIs, BAPIs, function modules, or code exits

00:02:26 may not be available anymore. In the SAP S/4HANA,

00:02:31 direct access to some of these tables is not allowed, hence read or write operations to these tables

00:02:37 may require calling a proxy object to run these operations. In order to identify what changes

00:02:46 must be adapted in your custom code, we have multiple tools and recommendations to guide you

00:02:51 through the process for custom code remediation. The first tool we offer is a simplification item database.

00:02:59 The simplification database contains a list of simplification items,

00:03:03 and each simplification item refers to an SAP Note that describes the impact on how it relates to custom code

00:03:11 and what will need to be adapted. It also describes the changes or deletions

00:03:17 that have been made to this functionality or business process.

00:03:21 The simplification database is provided as a zip file and can be downloaded from the SAP Marketplace.

00:03:30 What do I need to run custom code analysis in my system conversion to SAP S/4HANA?

21

00:03:42 In order to run custom code analysis on your SAP ERP system, we recommend deploying and setting up

00:03:49 the SAP ABAP test cockpit, also known as the ATC. In this figure, we have a central ATC system

00:03:58 connecting to multiple ERP or ECC back-end systems. The ATC system must be deployed

00:04:04 on the NetWeaver ABAP, stack 7.52 or higher, and will have the simplification database uploaded to it.

00:04:14 Your essential ATC system will connect to your SAP ERP back-end systems via RFC connections

00:04:21 with minimum versions of NetWeaver ABAP 7.0. The central ATC system will analyze your custom code

00:04:30 across your whole landscape and perform the following activities.

00:04:34 It will connect to your remote stub and perform the custom code checks.

00:04:38 It will perform the check logic, which will be executed on the central system.

00:04:43 It will analyze the results and will display it in the ATC central system.

00:04:48 It will also integrate into your development environment, and multiple custom code checks will be performed,

00:04:55 including core modifications and enhancements. You also have the ability to suppress

00:05:00 false positive findings with pseudo comments. And finally, like I mentioned before,

00:05:07 we have provided SAP Note 2241080 on steps how to download and install

00:05:13 the simplification database. For more information on remote code analysis with ATC,

00:05:21 we have provided a link with additional details on this information here.

00:05:29 What procedures should I follow to run the custom code analysis?

00:05:38 There are two main phases in the system conversion process: the preparation phase and the realization phase.

00:05:45 For this unit, we'll concentrate just on the custom code analysis

00:05:48 and remediation activities. Before the SAP S/4HANA system conversion

00:05:55 and during the preparation phase, we recommend getting rid of your old, unused custom code.

00:06:02 A typical ERP customer system contains a large number of custom developments,

00:06:09 from Z objects to enhancements to core modifications that are no longer used productively.

00:06:17 Therefore, it is recommended to monitor your system landscape for a longer period of time

00:06:23 in order to do some housekeeping and eliminate a code which is no longer used anymore.

00:06:30 This procedure is very important and will significantly minimize

00:06:34 your custom code adaptation efforts. To do this,

00:06:38 we recommend turning on the ABAP Call Monitor, or SCMON, or UPL, the usage procedure log, in your production system

00:06:47 to find out which custom ABAP objects are really being used in your system.

00:06:54 You will then use a transaction SUSG to aggregate the collected usage data

00:07:00 and disaggregated usage data can be used to identify when an ABAP program or

00:07:06 procedure was used last so that you can minimize your

00:07:11 adaptation efforts when converting your system to S/4HANA. Now that you've identified the custom code objects,

00:07:20 the next step is to run the ATC. So after setting up your central ATC system,

00:07:27 you will schedule the ATC job to scan your custom code and identify custom code that will need to be remediated.

22

00:07:36 ATC will identify and flag both simplified S/4HANA objects, as well as HANA-specific changes.

00:07:44 Starting with S/4HANA 1809, a new SAP Fiori app, a Custom Code Migration app has been developed for efficient

00:07:52 custom code analysis, based off the remote ATC infrastructure.

00:07:58 The app performs the SAP S/4HANA checks on your custom code and provides the analytic representation

00:08:07 of the ABAP test cockpit check results, where you can filter and navigate.

00:08:14 The app also identifies unused code based off your collected usage data

00:08:20 and enables you to remove automatically the unused code during your system conversion

00:08:26 to S/4HANA. After the S/4HANA system conversion is complete,

00:08:34 during the realization phase, the next step is functional adaptation.

00:08:39 First you'll need to adapt the modifications and enhancements using transaction codes SPDD and SPAU.

00:08:46 This is the same process as in other previous upgrades or within your business suite environment.

00:08:55 Only that the SPDD and SPAU tools have been renewed. When moving your ERP system to S/4HANA,

00:09:05 many of these modification enhancements can be removed or even set to SAP standard.

00:09:13 Next you'll need to fix any of the SAP HANA and S/4HANA findings from ATC.

00:09:21 This is the functional adaption part where the tool that is recommended is the ADT,

00:09:29 the ABAP Development Tools for Eclipse. In order to minimize your adaptation efforts,

00:09:36 we've now offered automatic code adaptations using a quick fix feature,

00:09:44 which is developed within the ABAP Development Tools in Eclipse.

00:09:49 Some of the available quick fixes include the select without order by,

00:09:55 MATNR and amount field length extension. We also have new quick fixes for SD billing documents,

00:10:03 for DB accesses to VBRK and VBRP. We have improved quick fixes for VBTYP,

00:10:14 and data model changes to KONV and VBUK and VBUP and BSEG. And finally,

00:10:23 after you have successfully performed your system conversion to S/4HANA,

00:10:27 you will need to make sure that the custom code is optimized to utilize the full power of the SAP HANA database.

00:10:35 in regards to performance. Therefore you'll need to look at which SQL statements can

00:10:42 be optimized. And to do that,

00:10:45 you can use the SQL monitor or transaction SQLM to get performance data for all SQL statements

00:10:53 executed in your production system. A SQL monitor will help you understand what are the most

00:11:01 expensive and most frequently used, or executed SQL statements,

00:11:06 which SQL read or write operations occur in your productive system, and provides a transparent SQL profile.

00:11:21 So what procedures should I follow to run a custom code analysis? Right, so here we have two exercises for this unit

00:11:30 that will walk you through the tools used for a custom code analysis.

00:11:35 The first exercise is execute SAP Fiori, Custom Code Migration app

00:11:41 and the second exercise is the ABAP Development Tools in Eclipse utilizing the quick fixes features.

00:11:51 So in the first exercise, execute SAP Fiori Custom Code Migration app,

23

00:11:57 you'll be connecting to the CAL solution 4, this will act as your central ATC system

00:12:05 and source system for this exercise. And you'll perform the following activities

00:12:12 in the activity guide. First thing you'll configure,

00:12:16 the ABAP test cockpit object provider. You'll launch the SAP Fiori Custom Code Migration app.

00:12:23 So we've done the activation of the app for you. Then you'll go in and create a new custom code project

00:12:32 and you'll start your analysis. And at the end,

00:12:35 you review the results from the analysis. Let's start with a demo

00:12:44 of the Fiori Custom Code Migration app. So here you'll launch the Fiori launchpad, and here you'll

00:12:54 click on the Custom Code Migration app. From here, you'll create a new project.

00:13:09 You'll enter the following information for your new project. So we'll put a project description here.

00:13:16 You'll select the target release, select System Conversion,

00:13:23 and then select the destination that you want to run the check against.

00:13:29 Typically, you'll save this, but this will typically run for an hour and a half,

00:13:32 so we'll discard and we'll look at a sample project that we've already run.

00:13:39 So here, this is the initial page for the Custom Code Migration app.

00:13:45 You'll see, it's finished with warnings, come with the scope.

00:13:49 So you could see what's in scope for this project and what's out of scope.

00:13:56 We'll go ahead and go into Change Scope. Here you'll see all the packages that are part of the check

00:14:04 and you'll notice that there are two packages not in scope.

00:14:08 These packages actually have no objects within. You have the ability to add packages and remove as well.

00:14:20 If we go back and if you, once you finally... You can create a deletion transport for some.

00:14:26 And now we'll go to Analysis, here you'll see a high overview of the findings.

00:14:34 So next we'll analyze the findings. So here's a more detailed view of it.

00:14:45 Here we have different filters, right, from priority, check tiles,

00:14:48 simplification item catalog, SAP Note number, quick fixes, categories,

00:14:54 scope information, usage information, packages, object reference type, and object reference name.

00:15:04 Here, if you notice, let's go to quick fixes,

00:15:06 if you select any of this, it will update the whole dashboard

00:15:11 depending on what you filter against. And in here, you could see additional detailed information.

00:15:19 And if we go to the findings from here, you could see the different objects,

00:15:25 and then you can drill down into the object. Here, you'll get more detailed information,

00:15:32 you'll see the check title, check message, priority, object name, and the SAP Note.

00:15:38 From here, you can also click into the object and view it in a browser.

00:15:43 You can't make changes here, but you could display the source code.

00:15:46 And then you have the ability to open the SAP Note directly and see, you know,

00:15:52 what changes in terms of custom code you'll need to perform for this particular check object.

00:16:01 And that's it for the first demo. So now let's go ahead and continue to the next one.

00:16:12 So here, the next exercise that we want to discuss is

24

00:16:17 the ABAP Development Tools in Eclipse with quick fixes. For this exercise,

00:16:24 you'll you be using the same CAL solution 4. you'll perform the following activities for this step.

00:16:36 So first thing is you'll configure and schedule a local ABAP test cockpit run series.

00:16:44 Then you'll connect to the ABAP Development Tools, the ADT for Eclipse,

00:16:51 you'll review the ATC results. And then you're actually going to apply one quick fix

00:16:58 within the ADT. So here we also have a demo for this process as well,

00:17:06 for the ABAP Development Tools in Eclipse for quick fixes. And now let's go ahead and play the demo.

00:17:13 So you'll launch in the ADT, you'll connect into your SAP S/4HANA system.

00:17:22 Enter the password, you'll log in into the ADT for Eclipse.

00:17:32 First thing you want to do is come up to Window, Show View,

00:17:39 go down to Other, click on ATC Result Browser,

00:17:44 click Open. This will display the ATC run schedule that you

00:17:53 perform in your exercise. You'll go here, right click,

00:17:58 click on Analyze Result in ATC Problems View. And from here, you'll notice there is

00:18:11 an icon with a light bulb in red, and you'll just right-click and do quick fixes.

00:18:20 Here we have two options, to append pseudo code or replace.

00:18:23 We'll select replace from table, and click on Finish. And after the quick fix has been applied,

00:18:31 you'll go and click on the Activate button and it'll ask for a transport.

00:18:36 So we'll go ahead and create a new transport. Enter a description, we'll just do ATC Quick Fixes,

00:18:46 just click on OK. And once that's done,

00:18:55 we'll come back to the object and do a recheck. And if everything is successfully performed

00:19:04 before the quick fix, the results should come back

00:19:13 with an update. So here, instead of the errors,

00:19:22 now we've got warnings, and that's it for the quick fixes.

00:19:30 You'll be performing these exact same steps inside your exercises.

00:19:37 What's new in Custom Code Migration app? Here, we have a summary of the new features

00:19:46 within the SAP Fiori Custom Code Migration app. The SAP Custom Code Migration app is now available

00:19:55 in the SAP BTP, our SAP Business Technology Platform,

00:20:00 and can be easily set up and configured using the CIAS workflow.

00:20:06 The CIAS is the Cloud Integration Automation service, which is a set of guided interactive steps that enable

00:20:15 the customer to select, configure, and consume technical components on the SAP BTP.

00:20:23 We have a new advanced configuration in the custom code app as well,

00:20:27 where you can select your custom Z packages for analysis. We also,

00:20:35 inside the Fiori Custom Code Migration app, now support greenfield projects,

00:20:40 as well as our system conversion projects. The SAP Fiori Custom Code Migration app

00:20:49 now supports multiple projects for analysis, from SAP S/4HANA projects

00:20:57 to SAP BTP migration projects and classic custom code analysis projects.

00:21:06 You also have the ability to download the ATC check results from within the Fiori Custom Code Migration app

00:21:14 for upload into the SAP Readiness Check 2.0. This way you can view your ATC results

25

00:21:24 directly within the SAP Readiness Check report. And finally,

00:21:30 new complexity analysis dashboards are available within the Custom Code Migration app.

00:21:38 Here you can, you know, spot the top complex executables

00:21:42 and development packages in your custom code. You have the ability to identify candidates for redesign

00:21:50 to save adaptation efforts and future maintenance costs. And you have the ability to

00:21:58 remove custom or complex development packages from scope. For more information on the custom extensions

00:22:08 in SAP S/4HANA implementation, please refer to the following link,

00:22:13 A Practical Guide for Senior IT Leadership. Custom code checks and evaluation of results,

00:22:23 key takeaways. So finally,

00:22:26 here's a quick recap and key takeaways from the session. So from a Fiori Custom Code Migration app,

00:22:35 this is now available on the SAP BTP, the ABAP environment.

00:22:42 We have Cloud Integration Automation service available for quick and easy setup

00:22:49 of the Custom Code Migration app on SAP BTP. We now support greenfield projects, as well as, you know,

00:22:59 system conversion projects. And now you have advanced configuration where you can select

00:23:05 your custom code packages for analysis. And we now have

00:23:10 different dashboards for analysis of source code complexity.

00:23:17 And now we have the ability to integrate the ATC check results into the SAP Readiness Check 2.0.

00:23:27 And finally, from a quick fix perspective, which is available in the ABAP Development Tools in Eclipse,

00:23:35 we now have the ability to provide comments for quick fixes within the source code.

00:23:42 We now have new quick fixes for SD billing documents, and we have improved quick fixes for VBTYP.

00:23:54 So that's it for unit four. Thank you for your attention.

00:23:59 Now I hand it over to my colleague, Andreas Hauer, for the next section.

00:24:04 Thank you and see you again.

26

Unit 5

00:00:04 Hello, and welcome back to the openSAP course Gain Experience with a System

Conversion to SAP S/4HANA.

00:00:12 My name is Andreas Hauer, and I'm a chief enterprise architect

00:00:16 in the SAP S/4HANA Regional Implementation Group in EMEA. I will present to you unit five today

00:00:23 from my home office location close to Walldorf. In unit five, you will learn about the maintenance planner

00:00:30 and the impact on add-ons and business functions. So far, in the previous units,

00:00:35 you have already heard a lot about required preparation activities for the conversion.

00:00:41 So you might ask yourself what is the maintenance planner about,

00:00:45 and is this tool mandatory for a system conversion to SAP S/4HANA?

00:00:50 To answer this question, let us first have an overview of the maintenance planner.

00:00:56 The maintenance planner, as the successor of the well-known Maintenance Optimizer,

00:01:01 is the central planning tool that is hosted on the SAP Support Portal.

00:01:06 It supports all kinds of changes in the customer landscape, like update or upgrade of existing systems,

00:01:13 the conversion of an ECC system to S/4HANA, or also the installation of a new system.

00:01:22 For the maintenance planner, it's required that customer-specific data is uploaded

00:01:28 via the SLD and LMDB of your local solution manager into a customer-specific profile in the SAP Support Portal.

00:01:38 Consuming tools of the maintenance planner are, for example, the Software Provisioning Manager, to install a new system,

00:01:46 or the Software Update Manager for a conversion. Now, let's have a look what the maintenance planner

00:01:52 specifically provides for a system conversion to SAP S/4HANA. First of all, the maintenance planner is used

00:02:00 to check for installed software components, activated business functions, and add-ons.

00:02:07 In case there is no valid path defined for the conversion to the target S/4HANA stack,

00:02:13 the maintenance planner will prevent the conversion to SAP S/4HANA.

00:02:19 In the other case, if a conversion is possible, the maintenance planner will generate

00:02:24 the mandatory stack.xml file, and support the download of the software archives.

00:02:30 Both are consumed by the Software Update Manager later on. Last, not least, the maintenance planner also offers

00:02:38 multiple deployment options, for example, to implement the front-end system

00:02:42 embedded with the back-end system. Now, how can you start using the maintenance planner

00:02:49 to plan a system conversion to SAP S/4HANA? First, you need to make sure that you have an S-user

00:02:57 for the SAP Service Marketplace. In addition, you need to make sure that

00:03:02 your company's landscape data is available in the maintenance planner.

00:03:07 If you want to learn more about the required steps, please reach out to the blog,

00:03:12 which is outlined here on the slide. Once you have accessed the maintenance planner

00:03:18 with your S-user ID, simply select the tile Plan for SAP S/4HANA.

00:03:24 Then, choose the path converting an existing SAP ERP system to SAP S/4HANA.

00:03:31 Once you have done that, you need to provide the SAP ERP system

27

00:03:36 which you would like to convert, and you also need to provide the target S/4HANA version,

00:03:42 and the required support package stack. Last, not least, additional systems,

00:03:48 for example, if you want to co-deploy an SAP front-end server to the converted SAP S/4HANA system,

00:03:55 can be provided. Now, let's have a look why the maintenance planner

00:04:02 checks business functions in the source system. In unit two and unit three, you have heard from my colleagues

00:04:09 Ashuta and Astrid that the business function has a critical role in making

00:04:15 or breaking the conversion to SAP S/4HANA. The recent behind that is that, in S/4HANA,

00:04:24 a business function can have either the status ALWAYS_ON, ALWAYS_OFF, or CUSTOMER_SWITCHABLE.

00:04:31 In case a business function has been activated in the ERP system, and this business function is defined

00:04:38 as ALWAYS_OFF in the SAP S/4HANA system, there is a conflict,

00:04:44 and the maintenance planner will block the conversion to SAP S/4HANA.

00:04:49 Keep in mind that there are a few selected business functions classified as ALWAYS_OFF,

00:04:55 where the responsible SAP application development explicitly supports the deactivation,

00:05:02 even in a productive environment. If you want to learn more about these exceptions,

00:05:07 please reach out to the SAP Notes, which are mentioned here on the slide.

00:05:13 Apart from that, it's also important to know that activated business functions cannot be

00:05:21 deactivated anymore in a productive environment. This is also valid for business functions

00:05:28 which have been classified as reversible, as this status is only valid for non-production system.

00:05:37 In addition to the business functions, the maintenance planner also checks add-ons,

00:05:43 but which add-on types are considered by the maintenance planner,

00:05:46 and why does the maintenance planner check add-ons at all? To answer these questions, let us first have a look

00:05:54 which add-on types exist, and what the maintenance planner knows about

00:05:59 their release status for S/4HANA. First of all, there are the so-called SAP add-ons,

00:06:05 which are developed by SAP itself. These add-ons are modeled

00:06:10 in the Product and Production Management System, short, PPMS, which is an SAP internal master data repository

00:06:19 containing technical information about SAP software components and software products.

00:06:26 As the maintenance planner is using this PPMS system to check the release status of an add-on,

00:06:35 it exactly knows the status of an SAP add-on, and whether this SAP add-on is released,

00:06:41 or not for the target S/4HANA stack. Very similar are partner add-ons,

00:06:48 which are developed by partners, but part of the SAP price list,

00:06:53 these add-ons are as well modeled in the PPMS, and the status, the release status is known

00:06:59 to the maintenance planner. Partner add-ons, however,

00:07:04 which have been certified by the SAP Integration and Certification Center, short, ICC,

00:07:11 are not modeled in the PPMS. Accordingly, the maintenance planner does not know

00:07:16 about their release status. However, the maintenance planner is still able

00:07:23 to list certified add-ons separately if they are certified for the target release.

00:07:30 While other kinds of third-party add-ons are not known to the maintenance planner,

28

00:07:36 and it's in the responsibility of a customer to check the release status for SAP S/4HANA.

00:07:43 Now, why are add-ons checked in the source system? It's important to know that both SAP

00:07:51 and partner add-ons can only run on SAP S/4HANA if they have been released for it.

00:07:57 This is especially valid for productive usage. The result of the maintenance planner check

00:08:04 depends on the add-on support for SAP S/4HANA according to the PPMS,

00:08:10 the add-on type, and an existing license. Here, it is important to know

00:08:16 and to consider that there might be a difference between the licensing of an add-on in SAP ECC

00:08:23 and SAP S/4HANA. If you want to learn more on the role of add-ons

00:08:29 in making or breaking a conversion to SAP S/4HANA, please read the blog, which is outlined here on the slide.

00:08:39 Now, let's have a look on the impact the add-on type has for the add-on handling in the Software Update Manager.

00:08:48 And again, let's start with those add-ons which are known to the PPMS

00:08:54 and known the maintenance planner accordingly. Remember, those are the SAP add-ons

00:09:00 and the third-party add-ons, which are part of the SAP price list.

00:09:04 For these add-ons, the maintenance planner exactly knows about the release status for the target software stack.

00:09:11 If they are supported, the maintenance planner will provide an archive, or SAP file to the Software Update Manager.

00:09:19 If they are not supported, the maintenance planner will provide the information

00:09:24 to the Software Update Manager, so that the add-on can be uninstalled

00:09:28 or deleted during Software Update Manager execution. All other kinds of of third-party add-ons

00:09:35 independent of whether they are certified by the ICC or not, have a different behavior.

00:09:41 Here, the Software Update Manager expects an archive, or ACP file, to be provided by the customer.

00:09:49 Accordingly, it's important to contact your third-party vendor in time.

00:09:55 Also, keep in mind that for new SAP S/4HANA versions, a new version of the partner add-on typically comes later

00:10:03 than the general availability of the S/4HANA version itself. The reason here is very simple,

00:10:10 as development and testing of the partner add-on can only happen after the general availability of S/4HANA.

00:10:21 Now, how can you handle add-ons that are no longer relevant, but that are not released for SAP S/4HANA?

00:10:29 In general, the SAP tools, like the SAP Add-On Installation Tool,

00:10:35 or the Software Update Manager, are prepared for the deletion of add-ons.

00:10:41 Before an add-on can be deleted, you need to make sure that the data

00:10:46 and functionality is no longer required. And you also need to make sure that

00:10:51 an add-on vendor has enabled the deletion possibility. Here, it is important to note that partner add-ons

00:10:59 require an uninstallation procedure before they can get certified.

00:11:05 Once you have decided to delete the add-on, you typically deselect the add-on

00:11:11 in the maintenance planner, as part of your maintenance planning activities.

00:11:16 The Software Update Manager will then execute the deletion itself.

00:11:22 As an alternative, you can manually delete an add-on in the SAP Add-On Installation Tool.

00:11:29 Afterwards, you then typically delete the associated product instance

29

00:11:35 in the LMDB of your local solution manager. In case a third-party add-on blocks the conversion

00:11:44 to SAP S/4HANA, and is no longer supported by the vendor, a so-called configuration tool can be used.

00:11:53 Please keep in mind that the configuration tool requires at least version 0075 of the SAP Add-On Installation Tool,

00:12:03 and that the configuration tool cannot delete all add-ons. Here, an additional check is required.

00:12:11 If you want to learn more about the configuration tool, please reach out to the SAP Note,

00:12:18 and the configuration tool user guide, which are mentioned here on the slide.

00:12:23 And remember that the uninstallation of the add-on may result in a data loss,

00:12:28 so it's the customer's responsibility to check carefully. Now, let's have a system demo on how to use

00:12:36 the maintenance planner to prepare a system conversion to SAP S/4HANA, including the stack.xml file generation

00:12:44 and the selection of the required software archives. In the SAP Support Portal,

00:12:52 you select Maintenance, maintenance planner. This will bring you to the landing page

00:12:57 of the maintenance planner, from where you can access the maintenance planner itself.

00:13:05 Once the maintenance planner has been loaded, it comes up with a classic UI.

00:13:11 You can easily switch from this UI to a new, modernized UI. Once you have clicked that button under your user,

00:13:21 and switched to the new user interface, the maintenance planner will be loaded

00:13:26 with a modernized, convenient interface. Here, you click on the tile Plan for SAP S/4HANA.

00:13:34 On the upcoming screen, you choose your path by converting an existing SAP ERP system to SAP S/4HANA.

00:13:43 At the bottom of the page, you can find some prerequisites that are required for the conversion,

00:13:50 and also a high-level overview of the conversion process itself.

00:13:56 Once you have read, simply click on Next. Now, you need to select the back-end system

00:14:03 which you would like to convert to SAP S/4HANA. In my case, it's an ERP 6.0, Enhancement Package 6.

00:14:14 That's correct. Now, I will select the target version,

00:14:18 and also the target support package stack, in this case, 02.

00:14:23 The maintenance planner already pre-selects S/4HANA Server and the SAP Predictive Integrator,

00:14:29 which is heavily used for innovation scenarios. This is okay, so I click Next.

00:14:37 Now, I have the option to add an additional installation, in my case, a Fiori system should be co-deployed

00:14:47 on the converted back-end system. So I select Fiori for SAP S/4HANA, target stack 05,

00:14:55 and again, the maintenance planner pre-selects all possible UIs.

00:15:00 I will keep this for S/4HANA, HCM, MDG, and also travel management.

00:15:07 That is all fine. I simply click Next.

00:15:13 Now, the system gives me a summary of all the pre-check results.

00:15:18 For the add-ons, I can see that the system, that my source system, contains the following add-ons

00:15:23 that are not compatible with SAP S/4HANA. So if I continue with the conversion planning,

00:15:29 these add-ons are uninstalled, or deleted later on by the Software Update Manager.

00:15:35 That's exactly what I want. In addition, I can see that

30

00:15:40 there is one business function which will be deleted during the conversion to SAP S/4HANA.

00:15:46 The reason here is that the business function is not available at all in SAP S/4HANA.

00:15:52 So it's not an ALWAYS_ON or ALWAYS_OFF. It's simply not there anymore, and will be deleted.

00:15:57 Also, that is fine. I continue with the planning.

00:16:00 I get a pop-up that gives me, again, an overview of all warnings, or errors,

00:16:05 and if that's okay, I can continue. On this screen, I can see all changes

00:16:14 which I have defined so far. For each product, the system, the maintenance planner,

00:16:21 shows me which products will be deleted, or which products will be added.

00:16:27 You can see this with the simple icon. And that's it.

00:16:34 Now I have the chance to add an additional add-on, or to add some additional changes.

00:16:40 If this is not the case, and I'm fine with the change as it is defined so far,

00:16:46 I, again, simply click on Next. The maintenance planner now gives me the option

00:16:57 to choose all OS/DB-dependent files. As S/4HANA needs to be implemented on the HANA database,

00:17:04 I will select the HANA database-specific files for my operating system,

00:17:10 which is in this case a Linux system. So HANA database,

00:17:15 and of course I need the Software Update Manager, confirm the selection, and oops,

00:17:21 the maintenance planner gives me a warning. Two recommended files are not selected.

00:17:27 Okay, in this case, I will Cancel, and select the files.

00:17:32 For the host agent, I choose the latest version, and include IGS as well.

00:17:38 Again, confirm the selection. Another error comes up,

00:17:42 and the maintenance planner tells me that I should select APL.

00:17:46 In case I would like to read, I can follow the note directly from here.

00:17:51 APL here makes also sense because it's a predictive library, and as we have chosen prediction scenarios,

00:17:59 and might want to use innovative use cases, I select this file as well.

00:18:07 Once I have confirmed the selection, I continue with the next step.

00:18:18 Now, the maintenance planner is loading in the background all relevant software archives.

00:18:27 And I can select now which of these files I don't want to use,

00:18:35 for example, if I want to delete language-specific files that doesn't make sense for me in my installation.

00:18:44 If that's not the case, I simply continue, and I get the option to push all of these files

00:18:50 into a download basket. In the actual case, there are 236 objects

00:18:58 which have been added in the download basket, and which I can download later on.

00:19:03 Also, I have the option to download the stack.xml file, which will be needed

00:19:08 by the Software Update Manager for execution. Now, I can continue,

00:19:18 and get the so-called Maintenance Plan, which contains a summary of all the changes

00:19:24 I have prepared for the conversion. That's it with the maintenance planner.

00:19:32 I can now save it, and continue with my next activities. For this unit, we would like to hear about

00:19:44 the key takeaways before closing. Very important to keep in mind that

00:19:50 the maintenance planner is used to check installed software components,

00:19:55 activated business functions, and add-ons in the source system.

31

00:20:00 We have heard that the maintenance planner will prevent a system conversion in case there is no valid path defined.

00:20:09 Otherwise, in case the conversion is possible, the maintenance planner will provide the required

00:20:15 stack.xml file and also the software archives, which will be consumed by the Software Update Manager.

00:20:23 Very important, and keep that in mind, business functions with status ALWAYS_OFF are critical

00:20:30 and will block a conversion to SAP S/4HANA. Also, all add-ons need to be supported

00:20:37 for the target SAP S/4HANA stack. Add-ons that are not supported

00:20:43 need to be deleted or uninstalled. And remember that third-party add-ons are typically released

00:20:49 only after the availability of a new SAP S/4HANA version. That's it with unit five.

00:20:58 Thank you very much for listening in, and please stay tuned for unit six

00:21:03 with my colleagues Ashuta and Boris. Thank you very much.

32

Unit 6

00:00:04 Welcome to unit number six, Running Software Update Manager and Post-Processing

Steps.

00:00:10 My name is Boris Rubarth. I work as a product manager for SAP in Waldorf.

00:00:15 After we have discussed the maintenance planner and required preparation steps,

00:00:20 it's now about the execution of the technical conversion. The starting point is a question,

00:00:27 which tasks does Software Update Manager execute and which aspects do I have to consider?

00:00:35 The Software Update Manager is the kind of engine to execute the technical conversion

00:00:42 from the ECC system to SAP S/4HANA. Generally, like always, the task of the tool

00:00:49 is to update the software, provide new software components,

00:00:54 or update existing software components. And the second task is to do the data conversion.

00:01:00 So data conversion is moving the content from the old tables, from the old data model,

00:01:06 into the new tables belonging to SAP S/4HANA. This is, at least partially,

00:01:11 executed by the Software Update Manager. We have a simplified architecture picture here.

00:01:18 If the source system is already running on an SAP HANA database, which is not a requirement,

00:01:24 but if this is the case it is a complete in place procedure.

00:01:28 We keep the HANA database and we start the Software Update Manager

00:01:32 on an application server host, both are kept. Of course, it's possible to start this one step procedure as well

00:01:40 on a system not yet on SAP HANA database. In this case, the Software Update Manager would as well execute the database migration.

00:01:49 So migrating from the non-HANA to the HANA database as well. We call this DMO, database migration option,

00:01:57 of the SUM, the Software Update Manager. In this case, we have the source database host

00:02:03 and the target SAP HANA database host that has changed, but still the application server level is kept.

00:02:11 That's why we still call this an in-place procedure. There are requirements

00:02:16 to also change the application server level for a data center move or for applying new hardware

00:02:23 or even to move from on premise to a hyperscaler. For this, it is possible, in case the source is not yet on a HANA database,

00:02:32 to use what we call DMO with system move. DMO with system move will not only move the database

00:02:39 to a HANA database host, but also move the application server host.

00:02:44 You see a link here, and, of course, this approach is also documented

00:02:48 in the respective guides of the Software Update Manager. What else?

00:02:54 Well, as a preparation, what we need, of course, as discussed, is using the maintenance planner.

00:03:00 That will provide the stack.xml, the kind of recipe for the Software Update Manager,

00:03:05 and of course, the software archives for the new software components

00:03:10 and updated software components. That is a requirement.

00:03:14 Another requirement is that the simplification item checks were already executed in the source system.

33

00:03:20 The Software Update Manager will execute exactly the same reports

00:03:24 to check the consistency of the simplification item checks. That's why you should clarify all open items.

00:03:34 Actually, the Software Update Manager will execute these SI checks twice.

00:03:39 And if there's an issue, the Software Update Manager will stop

00:03:42 and not execute the technical conversion. These are mandatory preparations.

00:03:48 We have some optional activities. For example, you do not have to use the SAP readiness check,

00:03:54 but of course it's strongly recommended to use this as a comprehensive test

00:04:00 and project planning tool. Custom code check is technically not required.

00:04:08 The Software Update Manager will not care. So for a first sandbox conversion,

00:04:14 you may simply ignore the adaptation and analysis of custom objects.

00:04:19 Anyhow, you will do these adaptations after the conversion of the development system.

00:04:26 Other optional activities are features that the Software Update Manager is offering,

00:04:31 especially the prerequisite check that we have already had for a while.

00:04:35 But more important, the prerequisite check extended. That is a feature of the tool of the Software Update Manager,

00:04:44 it is optional but we strongly recommend this. And that's why I will introduce this on the next slide.

00:04:53 These checks of the Software Update Manager are of course also documented in the respective guides,

00:04:59 you find them on the landing page of the SAP software logistics tool set

00:05:05 in the SAP Support Portal. So, the prerequisite check extended.

00:05:10 Scenario is, you're not familiar with the system conversion. You have your first sandbox run.

00:05:16 You have used the maintenance planner to get the stack.xml. And now you start the Software Update Manager

00:05:22 that has a long uptime processing. Uptime means end users are still working on the system.

00:05:28 Then, the tool will check, and you may stumble across a check that is an error.

00:05:35 So, OS, operating system, or database version not sufficient. That is a blocker, you will have to take care of this.

00:05:42 Only then can you continue the procedure. And maybe the next blocker is you find inactive objects that you have to clarify,

00:05:50 otherwise you cannot continue the procedure. And then finally, you may run into simplification item checks that are not consistent,

00:05:58 and the tool will again block, you need time.

00:06:01 And all these times are blockers where you are not certain what other issues may come up.

00:06:06 That's why instead, for the very first run, we recommend using the prerequisite check extended.

00:06:13 It's the same tool. You just tell the tool,

00:06:16 well, I would like to start this prerequisite check extended with the same stack.xml.

00:06:21 And now if there is an issue, you will be notified, but the tool will not stop.

00:06:26 All those potential issues, the major blocks, are collected. The tool will not enter the downtime.

00:06:33 Instead, it will provide a list of those potential blockers. So you have a to-do list that you can work on

00:06:40 even in parallel and you know the major blockers. That's the benefit.

34

00:06:46 Now it could even be the case that the maintenance planner will not provide the stack.xml

00:06:51 because there are add-ons for which there is no version supported for your target SAP S/4HANA.

00:06:58 Even then, there is a close collaboration between the maintenance planner

00:07:02 and the Software Update Manager. The maintenance planner offers you,

00:07:07 although there's a blocking add-on, offers you to provide a specific stack.xml

00:07:12 that the Software Update Manager can use to explicitly run the prerequisite check extended only.

00:07:20 That means with this stack.xml, you cannot execute the technical conversion,

00:07:24 but you can use this test run to see the potential blockers and to work on them in parallel.

00:07:30 That's the benefit. The prerequisite check extended is offered on one

00:07:35 of the very first dialogs of the Software Update Manager. We call this the scenario strategy

00:07:41 that you can consider there. Now on this slide,

00:07:45 we already see the major block, Software Update Manager, a long uptime processing, some downtime,

00:07:51 parts that we will have a look at now. So green, and on this slide quite short,

00:07:58 in real time it's a longer uptime processing of the Software Update Manager, it will use the usual technologies

00:08:04 like the shadow system, shadow repository. We have the ramp down.

00:08:10 And then there is a block related to the activities of the Software Update Manager.

00:08:14 As already mentioned, we only have the migration if the source is not yet on SAP HANA.

00:08:21 Then we have the update, provide new software components

00:08:24 or updated software components. And the conversion from the perspective of data conversion.

00:08:32 Actually, the tool is only executing a part of this required data conversion.

00:08:38 You see a data conversion part that is part of the Software Update Manager activity

00:08:42 and another part that is to be executed afterwards. So data conversion,

00:08:48 moving content from old tables to the new tables of the new data model of SAP S/4HANA like ACDOCA.

00:08:55 This is partially executed by the Software Update Manager and partially to be executed afterwards.

00:09:01 There are some IMG activities. So after the SUM tool is finished,

00:09:05 the system is in a kind of intermediate state, not available for end users,

00:09:11 but potentially you will run the IMG activities like creating the FIN customizing on the new model

00:09:18 and then execute the FIN data migration. You see that the technical downtime is only partially

00:09:27 determined by the Software Update Manager. The overall technical downtime is longer.

00:09:31 There are some activities after the Software Update Manager that count to the technical downtime.

00:09:37 Overall, of course, for your project, the business downtime is relevant.

00:09:42 It's just the recommendation, whenever you discuss downtime,

00:09:47 be specific about whether you are talking about technical downtime or business downtime. Several aspects are, of course, influencing this downtime.

00:09:56 That's why we have a dedicated slide on this aspect here, properties of the source system that may impact the technical downtime.

00:10:04 You see here, the kind of starting point, the ECC system, uptime processing, if required, the migration.

35

00:10:11 Then in downtime we have data conversion of Software Update Manager and the data conversion as FIN IMG activities.

00:10:18 Until we reach this state, SAP S/4HANA. Of course, you can imagine the database size is an important factor.

00:10:26 The bigger the database, the longer the downtime. And another important part is the portion of tables

00:10:37 that are affected by the data conversion, depending on how intensively the system was used for,

00:10:43 for example, financial transactions. So the more tables are undergoing the data conversion,

00:10:50 of course, the longer the downtime will be. We start the Software Update Manager

00:10:55 on an application server host. And the performance of this host, where additional tools

00:11:00 are started by the Software Update Manager, is influencing the downtime as well.

00:11:05 Last aspect listed here is quality of data. You may wonder, quality of data,

00:11:11 why does it influence the downtime? You will see in your first run

00:11:15 that especially the FIN data conversion executed after the Software Update Manager will show up issues,

00:11:22 because the checks of SAP S/4HANA are more strict than the checks we had in the ECC source system.

00:11:29 ECC source system is consistent, but there are checks in this intermediate state.

00:11:35 You will have to work on those issues to clarify this, that takes time.

00:11:39 That's why the first downtime will be longer. And of course, for the productive conversion,

00:11:44 those issues are already solved and will not show up during the technical conversion. How about the estimation?

00:11:52 Meanwhile, we have some options, some tools here that will help you. The Planned Downtime Calculator is meanwhile a tile

00:12:01 in the SAP Readiness Check, and there is a block that is explaining

00:12:06 this rather new feature. We have the Technical Downtime Optimization app,

00:12:11 an offering in the SAP Support Launchpad, where you can upload the statistics of a conversion run and compare this,

00:12:22 and even get a calculation, whether there's optimization possible. And the third aspect here is data volume management,

00:12:31 an app in the SAP Support Launchpad as well, that may give you important hints on reducing the database size.

00:12:39 Remember, a system conversion is a one-to-one conversion, so the complete source database is converted.

00:12:46 You can reduce the database by archiving, for example. Apart from optimization and tuning,

00:12:52 there are additional approaches to reduce the downtime of a technical, of a system conversion.

00:13:00 We have a kind of metrics, a table, down below there's the link table in the SAP Support Portal

00:13:07 that lists all the possible approaches that are available with the Software Update Manager.

00:13:12 And we have the standard conversion, typically for systems lower than five terabytes,

00:13:19 this will be applicable. We have a rather new offering, downtime optimized conversion

00:13:24 that meanwhile you can use as an educated consultant. And, of course, we have SAP offerings like NZDT,

00:13:32 a service-based offering to reduce the downtime more drastically. Just mentioning this and referencing this table

36

00:13:39 where you find more information about availabilities, and the respective SAP Note explaining details on that.

00:13:48 A screenshot of the dialog of the Software Update Manager illustrates the options that are shown there.

00:13:55 Well, there are two screenshots. You see the one is, on the left-hand side, for the case

00:14:01 that the source is not yet on SAP HANA. There, we can use the uptime migration.

00:14:08 So moving migration partially through uptime, that's a small step, or downtime optimized conversion, that's a big step

00:14:15 with more effort to reduce the downtime. In case the source system is already on SAP HANA database,

00:14:21 then this uptime migration, of course, does not apply. We have no migration if the source is already on HANA.

00:14:28 So instead you can use nZDM, near zero downtime maintenance, and these little icons here will show you

00:14:36 a short explanation of those approaches, similar to the previous slide,

00:14:40 where we have this table available in the SAP Support Portal for you to learn more about those aspects.

00:14:50 For the project planning, of course, there are several aspects.

00:14:53 Picking out some of them, you will start with a sandbox,

00:14:56 probably a copy of the productive system. You may repeat the conversion run on the sandbox

00:15:02 to get familiar with the procedure, to iterate this, and to refine your project plan afterwards.

00:15:09 You will work on converting the development system. There, you will adapt your custom code

00:15:15 that you will still need and put this into a transport requests so that the subsequent systems

00:15:21 can simply use these transport requests. And you will consider dual maintenance

00:15:27 to have a converted development system and the original one for some emergency patches.

00:15:33 Quality assurance system, you will do some business function testing of new or adapted processes.

00:15:39 And for the conversion of the productive system, you will of course, consider a dress rehearsal here.

00:15:47 As an additional aspect here, I've listed a timeline. Let's assume that we have currently available

00:15:53 Software Update Manager 2.0 SP 11 that is available for download.

00:15:58 We call this, it's a maintenance phase, and you may start on a sandbox with this.

00:16:03 And then we offer a new SP version, SP 12 in this case, that is a phase in maintenance.

00:16:09 And that means SP 11 will switch to phase patch on request.

00:16:14 Patch on request means it's no longer available for download, this SP 11 version, but in case there's an incident

00:16:22 and we can still adapt or patch the code. You can imagine, after approximately four months,

00:16:30 there will be another SP version, SP 13. That means SP 12 is in phase patch on request

00:16:37 and SP 11 is then in phase out of maintenance. Out of maintenance means we are no longer able

00:16:45 to provide a patch that may be provided to you. And, of course, you would not like to use an SP version

00:16:53 of the Software Update Manager that is out of maintenance. So you will consider, during your project planning,

37

00:16:59 switching to a new SP version of the Software Update Manager,

00:17:03 so that you have at least some version that is in phase patch on request for your relevant systems.

00:17:10 For example, productive system, but maybe for others as well.

00:17:14 That's the idea. So you should not use a version

00:17:18 that is in phase out of maintenance. You can use this, you will still get support,

00:17:23 but, of course, it's a risk decision that you have to take. This maintenance strategy is attached

00:17:30 to the respective SAP Note on the software logistics tool set overall,

00:17:35 which is the bundle of several tools, not only Software Update Manager here.

00:17:41 After the Software Update Manager has finished, there are some post activities, larger and smaller ones.

00:17:47 FIN data conversion was already mentioned. It is, of course, explained in detail, for example,

00:17:53 in the SAP Note respective guide. Setup of SAP Fiori apps is a larger point here as well.

00:18:00 Changes to authorizations like some replicated transactions, new and changed authorization objects you will have to take care of.

00:18:09 Obsolete data handling is important related to old tables that are partially no longer required.

00:18:17 You cannot simply delete the complete content, SAP delivers the rules and the tools

00:18:22 to delete partially content from the old tables. Silent data migration is a concept that runs

00:18:29 after the conversion that does some data conversion in the background while you are already using the SAP S/4HANA system.

00:18:39 And then some selected basis tasks, for example, new workflow user and similar things.

00:18:46 Finishing up with a short system demo that we have here. So, the system demo is about...

00:18:54 I have already logged onto our application server, I'm here logged on with a user, root.

00:19:01 And what you will have to do as part of the exercises as well is the Software Update Manager was already provided.

00:19:09 So we switch to the respective directory, USR SAP, and then download.

00:19:16 In this folder, you will see that we have the SUM archive and the archive was already extracted here as well.

00:19:23 And we have the folder softdump, where the archives and the stack.xml are provided.

00:19:29 What you have to do as the user root is you have to register the Software Update Manager for the SAP host agent.

00:19:37 So the host agent knows where the SUM is located. This is done by executing a script.

00:19:43 You see here SUMSTART. That actually does not start the Software Update Manager,

00:19:47 it will start a script that configures the host agent. And after this config host agent option was used,

00:19:56 now the Software Update Manager can be started by the host agent. That means we will switch to the browser window

00:20:05 and start the Software Update Manager browser user interface with a URL

00:20:11 that you'll find in the exercise as well. We have to log on with the SID ADM user

00:20:16 and the respective password here to log onto the host agent.

00:20:21 And then the host agent will start the Software Update Manager tool.

00:20:26 Well, tool start required is the very first dialog in our case in the repeat phase.

00:20:32 This is due to our set up of the host for you. Normally, you would see this welcome message,

38

00:20:40 this dialog where you provide the stack.xml, the recipe. In our case, this is located as we have already discussed,

00:20:48 USR SAP, and then download. And in the download folder there's softdump.

00:20:54 We use the help here, the input help, to see there's only one XML that is selected.

00:21:01 With this one, you can specify the stack.xml and continue. Select roadmap is now this, what we call, scenario strategy.

00:21:10 We've seen this there before. After this scenario strategy

00:21:16 where we have chosen the standard approach, the tool will then show additional parameters

00:21:22 where we keep the archive authenticity check, We do not provide a customer buffer,

00:21:28 but we switch on the expert mode so that we see additional dialogs here.

00:21:33 Migration parameters is the point where we have to enter the migration key that is provided

00:21:38 in the handout for you. We choose Next,

00:21:42 and the following dialog will ask for the password of the user DDIC, as provided for you.

00:21:48 And after, we have provided this password and click Next, the Software Update Manager will scan the download directory.

00:21:57 And that's the end of our demonstration here. Key takeaways are the Software Update Manager

00:22:05 will execute the upgrade, will do the data conversion partially,

00:22:09 and if required, it will do the database migration. The prerequisite check extended allows you to identify major issues.

00:22:18 For reducing downtime, we have several approaches available. And DMO with system move offers a complete move of the system,

00:22:26 for example, to move to hyperscalers. The project planning must consider

00:22:30 that the Software Update Manager has its own maintenance strategy.

00:22:35 Thank you very much.

39

Unit 7

00:00:05 Hi everyone. I'm Rohit Khan.

00:00:07 I'm part of SAP Business Transformation Services group at SAP and I'm also part of SAP S/4HANA Regional Implementation Group

00:00:16 as a product expert. I'll be taking you through this unit seven of this openSAP course.

00:00:22 And in this unit, I'm going to talk about the activation of analytic engine

00:00:28 as well as configuration of embedded analytics in SAP S/4HANA on-premise system.

00:00:35 Well, this embedded analytics, of course, it's a very interesting topic.

00:00:39 And of course, for all the enthusiasts out there who would like to understand more

00:00:43 about analytics in SAP S/4HANA, this unit is for you.

00:00:48 And coming back to the embedded analytics, basically, you know, embedded analytics offers you some set of powerful tools

00:00:55 and powerful SAP Fiori applications that you can use, you know, to basically build new analytic content,

00:01:05 and also you can use these analytical SAP Fiori applications for your day to day transactions and so on.

00:01:11 So, yeah, as I said, sounds interesting. So let's start with the unit.

00:01:18 Okay, so how do I get started with these powerful SAP Fiori applications and tools, be it if I'm an end-user or I'm a key user

00:01:28 or analytical specialist, for example? how do I start with these tools like Query Browser,

00:01:34 Custom Analytical Queries, Design Studio, and so on. Well, the answer is very straightforward.

00:01:39 What you need to do is you need to configure first the Analytic Engine in SAP S/4HANA.

00:01:46 And this is the activity that you are going to perform in this unit of this openSAP course,

00:01:51 where you are going to activate the Analytic Engine and then also do the configuration

00:01:57 of, you know, these powerful features and tools so that you can use that.

00:02:04 And in order to, you know, configure the Analytic Engine, what do you need to do

00:02:08 is you need to follow the instructions as per these two SAP Notes

00:02:12 that you see here on your screen. The first note is a generic note,

00:02:16 that talks about the configuration in general, about, you know, configuring the Analytics Engine and so on.

00:02:22 Whereas the second note describes the actual configuration steps, you know,

00:02:27 that are necessary to enable the usage of the Analytic Engine as well as, you know, the usage of different tools

00:02:35 like Customer Analytical Queries, Query Browser, and so on. Now, this activity is to be done via a task list.

00:02:43 Okay, and with the task list activation, some other things will be done

00:02:48 like configuration of Analytic Engine, configuration of hierarchies,

00:02:52 configuration of design studio template and so on will be the part of this activity.

00:03:00 Coming back to the task list. Now task list is something, you know, it's again,

00:03:04 a very powerful feature, which you need to run in your SAP S/4HANA system.

00:03:09 And with the task list, you will have a certain set of steps that you need to perform

00:03:16 and with that, this activity will be done in your SAP S/4HANA system. And as I said, you know,

00:03:24 the task list activation is going to take some time and there are a lot of steps involved in that.

40

00:03:32 And so just to, you know, give you a brief overview so that you are comfortable with this,

00:03:37 I'll quickly show you a very short demo so that you can understand how this activity

00:03:42 is to be performed in the system. However, what you need to do is, you know,

00:03:48 you need to keep in mind that you download the hands-on exercise,

00:03:54 which is provided along with this unit and then you follow all the steps

00:03:58 as mentioned in that exercise document to do this end-to-end activation.

00:04:06 Okay, so having said that, let me quickly show you the short demo

00:04:09 so that you can understand how this task list really works. Okay, let's see the demo.

00:04:20 Okay, so let's start with transaction STC01. And now you need to put this task list that you see here,

00:04:29 SAP_BW_SETUP_INITIAL_S/4HANA. And next you are going to execute this task list.

00:04:50 And what you see in the task list are different steps. So we need to ensure that we execute all of these steps.

00:04:59 So we'll start with this green person icon, and you need to click on that, and you need to confirm

00:05:06 that you have read this note, just click on Confirm, move ahead, and you'll see it has turned green.

00:05:13 Next, you need to confirm or basically set the BW client, make sure that it is 100, save, come back.

00:05:24 And in the next step, you are going to select another task list.

00:05:29 Click on this icon, and click on Force Installation, save, and come back.

00:05:39 Now you need to run this task list in the background. And what'll happen is all of these task lists

00:05:47 will get executed in the background, and you should see the status

00:05:51 of each turning green, as you can see here.

00:05:57 Keep refreshing the task list so that you keep on getting the latest status

00:06:03 of the same. As you can see, it is turning green.

00:06:07 Or you can also keep an eye on the messages that are coming in the bottom of the screen.

00:06:15 You see, there is a list of messages already in the green. Keep refreshing.

00:06:20 So it is going to tell you the current status of the task list.

00:06:26 Now you can see there is an error. So what we need to do here

00:06:30 is we need to deselect this checkbox and then run the task list

00:06:38 in the background mode again. So we are going to deselect it

00:06:43 and then we will execute again in the background. So we'll resume the task list in the background.

00:06:52 And again, all the statuses will start filling in and you can see they are turning green.

00:07:00 Keep refreshing until the whole list turns green,

00:07:09 which means that the task list is now complete. Okay, so this was a very short demo, you know,

00:07:24 just to make you comfortable with this task list activation. So let's go ahead and move to the next slide,

00:07:31 which is talking about how do I get started with SAP S/4HANA embedded analytics.

00:07:37 Now as a prerequisite, you know, as I said, first thing first is that you should configure

00:07:42 the Analytic Engine in your SAP S/4HANA system. So that activity is done.

00:07:47 The next step is, of course, now, how do I use these powerful SAP Fiori applications and features,

00:07:54 which I briefly mentioned in my initial presentation. And of course they are all part

41

00:08:00 of your SAP S/4HANA embedded analytics. So to start that,

00:08:05 what you need to do is you need to follow this scope item called BGH.

00:08:12 And this scope item you can find in the Best Practices Explorer,

00:08:16 which is rapid.sap.com. You can go there as you can see here in this link.

00:08:22 And this scope item has a configuration guide. Okay.

00:08:27 And what do you need to do is you need to follow that configuration guide for first of all,

00:08:34 learning how to manually configure this set of powerful features in SAP S/4HANA.

00:08:39 And also how you can use this set of powerful features for a specific user.

00:08:47 I mean, if you are an end user, what are the kinds of Fiori applications

00:08:51 that are available to you? Or if you are an analytics specialist,

00:08:55 then what are the types of SAP Fiori applications that are meant for you?

00:09:02 So with this guide, there are a lot of benefits, of course, that you will gain from going through this guide.

00:09:09 Of course, one of the best gains is that, you know, you can learn about

00:09:12 how you can enable the real-time operational reporting on SAP S/4HANA system.

00:09:20 You will also get to know about, you know, how you can access SAP S/4HANA data

00:09:25 that is exposed as a CDS view in a uniform way, meaning that, you know,

00:09:31 you can expose the data of S/4HANA system through an external API,

00:09:36 which is built on top of your CDS view, and then you can use it externally as well.

00:09:41 That is one example. You will also, you know,

00:09:45 learn how this improved user experience, is basically going to help you in your day-to-day transactions.

00:09:57 And of course, you know, last but not least, you will also get to know how you can build

00:10:02 new analytic content in SAP S/4HANA to further improve, you know,

00:10:07 your business processes and so on. So, this is what your guide actually looks like.

00:10:15 And as you can see, this guide is called as the configuration guide.

00:10:18 And in this guide, it is going to describe all the general configuration steps and so on.

00:10:24 So let me quickly show you this particular guide so that you can understand.

00:10:31 Yeah, so this is the example of that guide and you can see this is

00:10:36 Technical Setup and Enablement for SAP S/4HANA Embedded Analytics. And if you come down,

00:10:43 you will find all the information that is needed for the manual configuration.

00:10:48 Or also if you would like to use these powerful SAP Fiori applications for end users

00:10:54 or for analytics specialists and so on. And that you can see here, you know,

00:10:59 it talks about all of that in great detail. So this is what I'm going to advise you.

00:11:05 What you need to do is after you have done the initial configuration of the Analytic Engine,

00:11:10 do follow this particular guide. You can download it from a rapid.sap.com.

00:11:17 And again, as I said, this guide is going to help you

00:11:19 to better understand about, you know, all of these powerful features and tools.

00:11:24 And you can also see it gives you all the technical representation

00:11:28 of the landscape as well. Okay, so let's switch back to the slides.

00:11:37 Alright, so now let's cover these offerings that I was talking about

00:11:41 that come along with embedded analytics. So primarily, these offerings are divided between, you know,

00:11:48 these offerings that are meant for the end users and the offerings that are meant

42

00:11:52 for the analytic specialists in your organization. Now, of course, end users are your business users.

00:11:59 And their primary job is to, you know, analyze the data and then act according to the insights,

00:12:05 meaning that, you know, they can find out from the data, if there is something that they would need to act upon.

00:12:12 So these powerful SAP Fiori applications have those features, which provide this kind of information

00:12:18 to these end users or the business users. And then they can, you know,

00:12:22 further act upon that insight. Coming back to analytics specialists, of course, you know,

00:12:29 for this group of users, embedded analytics provides, again,

00:12:32 a set of powerful SAP Fiori applications that they can use to build new analytic content

00:12:38 in SAP S/4HANA. So, what are these powerful applications?

00:12:45 I'm just going to cover that in my next slide. As you can see here,

00:12:49 these are some of the end user applications that are available for your users, business users

00:12:57 of considering overview pages, smart business KPIs, Analytical List Pages,

00:13:02 multidimensional reports, dashboards, and so on. So these are some of the, you know,

00:13:07 powerful SAP Fiori applications that are available for your business users.

00:13:13 For example, let's consider overview page. Now again, overview page is a very powerful application,

00:13:19 which gives the most important and relevant information to the user. And a user can then, you know,

00:13:27 act upon that information through this particular application itself.

00:13:33 And that information is displayed on the card that you see here. For example, you see these small, small boxes.

00:13:40 So all of these are basically cards and each card displays some, you know, relevant information,

00:13:45 which is relevant for that particular business role or for that particular user.

00:13:52 Similarly, you have a smart business framework apps and these apps basically enables the users to view

00:14:00 and analyze the data off one key performance indicator. Similarly, you have apps that are like Analytical List Page apps.

00:14:08 Okay, and you also have apps that provide you machine learning capability as well.

00:14:16 You know, again, as I said, all of this is there in your configuration guide under that scope item.

00:14:23 So you should download that and then, you know, go through in much detail.

00:14:30 Similarly, coming back to analytics specialist apps. So these are, again, some of the powerful, SAP Fiori applications,

00:14:39 which again, as I said helps analytics specialists to build new analytic content.

00:14:46 A very interesting app you can see here on your screen is custom CDS views.

00:14:49 Now again, this particular application is for analytics specialists to, you know, create a new custom CDS view

00:14:58 for their requirement. I mean, it's kind of a creation of a new data model

00:15:03 that probably might be used to build some new custom analytical query

00:15:08 or maybe that particular data model can also be exposed as an external API,

00:15:14 which could be consumed out of your SAP S/4HANA system. You know, so such kind of things you can do.

00:15:24 Similarly, you have a View Browser app. And in this application, you know, again,

43

00:15:31 this app will help the analytic specialists to search, browse, and find out, you know,

00:15:39 the SAP-delivered or even custom analytical queries. In addition, this also gives you the information

00:15:48 about all the released CDS views, for example, that are available in your system.

00:15:53 Or in fact, if you have developed a custom CDS view that also you can find out here in this View Browser app.

00:16:00 So again, as I said, a very important and, you know, powerful application to work with.

00:16:07 With the Manage KPIs and Reports app, you know, it's a single platform that you can use to create groups, KPIs,

00:16:16 reports, and applications that can be launched directly from the SAP Fiori launchpad. Similarly, you have applications like Custom Analytical Queries

00:16:34 to build new analytical queries and so on. So again, as I said, of course,

00:16:41 you need to visit that configuration guide document so that you can learn more in greater detail

00:16:46 about these powerful applications. Okay, so what I'm going to do now

00:16:53 is I'm going to again show you a very short demo about these powerful applications

00:16:58 that I just talk about so that you can understand how this thing really works in the live system.

00:17:06 So let's start with a demo. Okay, so let's start with the demo of the business user apps.

00:17:17 First one is Procurement Overview, which is of type overview pages app.

00:17:22 This app enables your business users to perform their daily tasks quickly and effectively

00:17:28 without the need to open many different reports and transactions.

00:17:33 The information is, you know, displayed on the set of actionable cards.

00:17:38 As you see here, all of these are the cards, and users can therefore focus on

00:17:43 the most important tasks that can enable them, you know, making the right decision and also a fast decision.

00:17:51 And also if there is something that is urgent and needs immediate action.

00:17:57 These cards show you the most important information, again, as I said, ranked according to the relevance.

00:18:04 For example, if you see this Monitor Purchase Contracts card, you can see the consumption and expiry date per contract.

00:18:12 For example, this is a contract here and then you can decide to change a contract

00:18:16 by selecting it if you feel like there is an action that needs to be done from your side.

00:18:22 In addition, you can also apply these global filters here on the top that you see.

00:18:28 And applying this global filter will apply this filter to the entire procurement overview,

00:18:36 let's say by supplier or by material group, for example. And then you can see all the urgent contracts,

00:18:42 purchase requisition or spend information according to the, you know,

00:18:48 selected criteria, filter criteria. For these graphical cards that you see here,

00:18:54 if you select this card, it will bring you more detailed analytic information.

00:19:03 The next app is our monitor purchase order items app. Now this app is of type, again, analytical list pages app.

00:19:11 And this app you can use to monitor the status of purchase order items

00:19:17 based on criteria such as material, supplier, quantity. Okay, and so on.

00:19:27 You can use a filter again to display the list of purchase order items

00:19:33 that you see here in the table. This list can be again modified again

00:19:38 by changing, you know, these filters, according to your own requirement.

00:19:43 And this app is only used for displaying the purchase order items only.

44

00:19:51 And by default, the list displays the overdue items,

00:19:56 meaning that the quantity that is still to be delivered and value still to be invoiced.

00:20:03 One other good thing with this app is that you can also use such features like chart only.

00:20:09 So you can only see the information in the form of a chart and then you can further click on it

00:20:15 and you can see the detailed information about the purchase order items.

00:20:20 One powerful feature that also comes with this app is the power of prediction,

00:20:27 which is proposed by SAP Predictive Analytics integrator. As you see here, predictive delivery.

00:20:33 And this will enable your users or business users to predict the delivery date of purchase order items.

00:20:42 And based on the predicted dates, your users then take necessary action.

00:20:49 Well, you will see this in the last unit of this course. The next app is your Overdue Purchase Order Items app.

00:21:01 Again, this app is SAP Smart Business generic drill down app. With this app,

00:21:09 the number of purchase order items with delivery dates in the past and those that are yet to be delivered

00:21:17 are basically calculated, as you see here.

00:21:22 You can also use this app to analyze delivery dates of purchase order items sent to supplier.

00:21:27 And that would be your key performance indicator. I will show you that in a moment.

00:21:33 And this app, as I said, you know, if you click on this refresh now,

00:21:38 it will bring up the latest calculation based on the live data .

00:21:43 So let's go in and what you see here, as I said, you can use this app,

00:21:48 as I said to analyze delivery dates of purchase order items sent to supplier, for example, now this supplier is your KPI.

00:21:55 So I have more KPIs like plant. So I can use another KPI, for example,

00:22:03 by purchasing group. So if I do this KPI,

00:22:06 I'll see that in this purchasing group, in this year 2020,

00:22:11 and these are my open PO net value. And what you see here in this orange color

00:22:15 is number of overdue items. And then I can further add another KPI and I can say, okay,

00:22:23 for this purchasing group, these number of overdue items, show me by plant.

00:22:29 So I'll be able to see this information by plant here that you can see.

00:22:34 And, you know, you can save this information also again,

00:22:38 in the form of a tile that will be displayed on your SAP Fiori launchpad.

00:22:48 Alright, so this was the demo to explain these powerful SAP Fiori applications.

00:22:54 And I'm sure you would have got some idea how these applications really help you in your day-to-day transactions and so on,

00:23:03 be it end user or be it analytic specialist. So with that, I have come to the end of my unit.

00:23:12 And just to recollect what we have learnt. In this unit we have learned how to configure

00:23:19 Analytic Engine in SAP S/4HANA. Again, if you want to use powerful features

00:23:26 of embedded analytics in SAP S/4HANA, you need to look for the best practice document,

00:23:32 which I just explained. Of course, the configuration that is needed to do this technical setup.

00:23:38 And of course, we also learned how, you know, these powerful SAP Fiori applications

00:23:44 are there for end users or for analytics specialists and so on.

45

00:23:50 Alright, so with this, I've come to the end of my unit.

00:23:55 And in the next unit, my colleague Jocelyn is going to cover how to set up SAP Fiori launchpad,

00:24:03 and how to activate initial business roles. So do look out for that.

00:24:10 Alright, with that, I'll say, thank you everyone for staying with me and bye-bye.

46

Unit 8

00:00:05 Welcome to unit eight on setting up SAP Fiori and activating initial business roles.

00:00:10 My name is Jocelyn Dart and I'm a user experience strategist

00:00:15 in the SAP S/4HANA customer care and regional implementation group. Let's start by answering the question,

00:00:22 why is adopting the SAP Fiori user experience essential to SAP S/4HANA?

00:00:28 Well you see, user experience drives organizational changes towards business outcomes.

00:00:33 Your organization will most likely have some UX value goals for SAP S/4HANA.

00:00:39 For example, they might want to make your business users more mobile, by doing more of their tasks on tablets and phones,

00:00:47 more insightful, by taking advantage of real-time operational analytics,

00:00:52 or more proactive, by introducing intelligent technologies, such as machine learning.

00:00:57 There are a wide number of UX value goals supported by standard use cases delivered in SAP S/4HANA.

00:01:04 The SAP Fiori user experience brings that new business value of SAP S/4HANA

00:01:09 to business users. For example, standard use cases in SAP S/4HANA include

00:01:15 the SAP Fiori launchpad and the apps themselves, which work on multiple device types.

00:01:21 Embedded analytics, as you saw in unit seven. And new business processes

00:01:25 such as group reporting, central procurement, predictive MRP, and many, many others,

00:01:29 which are only delivered in SAP Fiori. And, of course, there's the out-of-the-box

00:01:34 intelligent use cases for situation handling, machine learning, or robotic process automation.

00:01:39 And you'll see more of these in unit nine. Of course, you can also extend the standard use cases

00:01:44 with your own custom use cases deployed on S/4HANA or side by side in the Business Technology Platform.

00:01:53 Okay, so what major decision steps are needed to adopt the SAP Fiori user experience?

00:02:01 As you would expect, the major decision steps for adoption

00:02:03 are driven by your business. They need to decide who will change,

00:02:08 in other words, which business roles and users are in scope.

00:02:11 They will either need to understand the current as-is experience of their business users enough

00:02:17 so that they can decide what will change by envisioning the future,

00:02:21 using the UX value goals they have set. For example, if you want to make users more mobile,

00:02:26 what types of tasks would actually be more valuable to do on mobile devices

00:02:31 given the user's responsibilities and working environment? As a technical team, you will support them

00:02:37 by activating the business roles in scope so they can explore what is available

00:02:42 and decide how they will change. That is what launchpad features, content, and layout

00:02:47 should be deployed to business users to drive those same business outcomes.

00:02:51 Okay, so that given, what are the UX responsibilities of the technical team? Okay, so once your user, business stakeholders, and functional team

00:03:02 have decided which business roles are in scope, as a technical team,

00:03:06 you will need to rapidly activate the selected business roles in your sandbox environment

47

00:03:12 so that your team can explore them in action. Once your team have decided what they want to take forward to production,

00:03:20 you will need to refine the content and layout in your development environment, transport that through your system landscape,

00:03:27 and, of course, support your users throughout your different environments.

00:03:32 So what's the most efficient way to activate SAP Fiori for SAP S/4HANA?

00:03:37 So the good news here is instead of searching for what you need to configure, most configuration tasks

00:03:43 are brought to you in one place, which we call the task list.

00:03:46 There are two main task lists you should use to activate your initial SAP business roles as delivered,

00:03:53 ready for your team to explore them in your sandbox environment.

00:03:56 Use these tasks lists. You should be able to activate everything you need to explore

00:04:01 in less than a day. I'm serious.

00:04:04 The first is the Fiori foundation task list, which activates the Fiori launchpad itself

00:04:09 and its main features. For this task list,

00:04:13 there are a few prerequisite task lists, some of which you've already experienced in unit seven.

00:04:18 Such as turning on the embedded analytics engine and the enterprise search.

00:04:22 The second is the SAP Fiori rapid activation task list. With this task list,

00:04:28 you select the SAP business roles you want to explore and it activates en masse

00:04:33 the related SAP Fiori apps, classic UIs, the navigations between them and their launchpad layouts.

00:04:39 As an optional and highly recommended task you can generate a test user per business role.

00:04:46 By keeping the focus on what is delivered for a business user via their business role,

00:04:51 you can explore the apps and UIs as your user will see them. You will gain a swift understanding

00:04:57 of the launchpad layout for that user and by comparing roles,

00:05:01 you can see which features are controlled by authorizations. Okay, so let's have a look at the demo.

00:05:09 All right, so in here, I'm going to go into the task list transaction,

00:05:13 which of course is STC01. It's been around for a while

00:05:17 and I'm actually going to start with one of the last prerequisite task lists.

00:05:20 And this task list, SAP_CW_FIORI_ERP_ONE_CLIENT_SETUP, long name, is actually there

00:05:27 to set up your ABAP gateway as a Fiori front-end server.

00:05:30 So this is the configuration part. Each task list, you can see it has default task selected.

00:05:35 You can change that selection and each task has some documentation.

00:05:40 Some tasks have parameters that you need to check and set. So here's one, I don't have a virus scanner set up,

00:05:47 so I'm going to turn virus scanning off for now. I can always come back and just run

00:05:51 an individual task if I wish. Okay, so here's another one.

00:05:56 I'm going to adjust how much paralyzation I want. And remember, of course, these settings,

00:06:02 you can come back and change again later. You can also come back and run these task lists again

00:06:08 when you upgrade if the best practices have changed

48

00:06:12 or you've got new options in new release. This one here, I am setting some transport details.

00:06:19 So some things are going to be generated. So I want them to go on a Z development package

00:06:24 in my customer name space, and I'll just go through the list.

00:06:28 And of course, I've done this task list several times before.

00:06:31 So I know what I'm looking for, for the few things that I want to adjust and change.

00:06:35 We're going to give you these in the exercises, don't worry. We'll step you through it.

00:06:40 Okay, so the next thing I'm going to do here is I'm actually going to have a look and see what else I want to turn on.

00:06:50 Here's another place where I need to just say, put these things in a custom package.

00:06:56 And for the sake of convenience, I'm just putting everything in the same custom package,

00:06:59 but you can split them up. Okay, so last here,

00:07:05 I've got the option of maybe adding in an extra task. There's a couple of services that I want to turn on extra.

00:07:12 So I'm just going to set that up. And again, you can see here

00:07:16 that the parameters are different depending on what tasks you're doing.

00:07:19 In this case, I just need to add in the extra ICF notes that I want to turn on,

00:07:26 save that, come back to the task list, and then everything is ready to go.

00:07:31 Now what I'm going to do is just run the task list. That's it, hands off.

00:07:35 Just let it run through, and all being well, everything should run through and we get all green lights,

00:07:44 all green lights is always good. Okay, so let's have a look at what you've got at this stage.

00:07:49 So if I run the UI2/FLP transaction that just generates your launchpad URL.

00:07:55 At this stage, I've essentially got a blank launchpad entry page, no features.

00:08:00 So now we come to the Fiori foundation task list. Same principle, lot of tasks,

00:08:06 preselected for you as they will be foregoing for your first initial install.

00:08:12 You just need to work through them and adjust any of the ones that have parameters

00:08:17 to the parameters that you want to use. So here again, I've got some

00:08:21 that are going to generate some steps and I need to put them on a custom development package.

00:08:25 So I'm using the same Z Fiori development package for everything here, just for convenience.

00:08:31 It's useful even to have a look at these parameters, even if you're not going to change them.

00:08:36 And again, to have a look at the documentation as well. This one is quite useful because this is going to tell me

00:08:42 the authorization roles this will generate for me so that an administrator and a user has access to the launchpad

00:08:49 and all the main features. And I'll show you the administrator in a minute.

00:08:53 I'm going to add an optional, but highly recommended, one in 2020,

00:08:57 which of course is to turn on spaces and pages. Now you can still use groups in 2020,

00:09:03 but we will be deprecating them in a future release. So I'd rather turn them on now.

00:09:08 And as you can see here, I can actually configure whether I want to turn them on for

00:09:12 all clients or just specific clients. Remember, you can come back and run just a single task

00:09:17 in the task list at any time. Okay, so here I'm going to do the same thing.

00:09:22 Just start the task list in dialog, let it run through. This actually takes about 10 minutes.

49

00:09:27 I've sped it up a little bit. And you see here, I've got a warning, oh dear.

00:09:31 What do I do now? Well first thing, let's have a look at the warning,

00:09:33 see how serious it is. And it seems that this one's not too serious.

00:09:37 It says, right, you're going to need to re-execute that particular task.

00:09:41 We didn't quite get through it all. So here I am going through.

00:09:44 And this time I'm just going to deselect all the tasks. So skip all tasks and then just select the tasks

00:09:50 that I want to run again. And that was the Fiori,

00:09:57 the spaces and pages set up. If there's any dependent tasks,

00:10:01 it's just setting those on for me at the same time. So it's saying, well,

00:10:05 that needs to go on a transport request. So we'll grab that.

00:10:08 Okay, so here again, I just need to set my parameters, and then I can just run that particular task.

00:10:18 And once again, start the run in dialog. And now everything's gone through, it's all green.

00:10:24 If you want to look at your previous task lists, you can see them in transaction STC02.

00:10:29 Here, I'm logging on as the Fiori administrator, and you can see the basic features of the launchpad

00:10:34 are now working. The home navigation,

00:10:38 the search of business objects is there, notifications I've turned on,

00:10:43 there's settings in there. So that's all looking good, my themes, and so on.

00:10:48 And if I go to the app finder, here I can see my catalogs,

00:10:53 and also I can get to the SAP menu so I can search for my classic GUI transactions,

00:10:59 if I wish. Everything's working as a basic launchpad.

00:11:03 Onto the last one, which is the rapid content activation. So here I've got the choice of just adding,

00:11:11 cutting and pasting, a list of roles that I want to turn on. Typically I would have downloaded that list

00:11:17 from the Fiori apps library. So I'm just putting the list of the names in there.

00:11:22 I've got six in there. You can also, or as well,

00:11:26 add in any other business roles in the system. I'm going to select the recommended roles.

00:11:31 These are very useful because they're the ones that you can use to configure, adapt,

00:11:36 and extend SAP S/4HANA Fiori, changing Fiori. Which is really interesting when you get into extension.

00:11:44 Again, I've got some transport details. So I'm just going to add my package name in.

00:11:50 And again I'm just using the same package for convenience but you can split them up.

00:11:55 And, of course, the one thing I really like to do here. Yeah. Okay.

00:12:00 We're going to generate the roles for the prefix. You do actually need to generate the roles.

00:12:04 And the second thing here is I'm going to add my test users. I love this feature.

00:12:09 It makes testing so much easier and it's so much clearer when you can see what each individual role is doing.

00:12:17 So all I need to do is set a password that people can use for this test user.

00:12:23 And then I need to add in the role that I defined in the previous task list to give them access to the launchpad itself and the launchpad features.

00:12:32 So now I run this. Now this can take a little time,

00:12:35 depending on how many roles you've selected. So I'm going to start it in background.

00:12:40 And then I just wait for this to run and you can see it shows me where it's up to

50

00:12:45 and I can even set an auto refresh, or you can even go away,

00:12:48 come back into transaction STC02 and see what's going on.

00:12:53 Here, I've skipped to the end. You can see there's one little warning,

00:12:57 but I know that warning. It's not something I need to worry about.

00:13:00 It's fine. So I'm just going to go to the log

00:13:03 and see what's actually done. And here, you can see you're quite safe

00:13:07 to actually run these task lists again and again if you change your mind or you want to turn something on.

00:13:12 So it's going to generate the business roles for me, complete with all of the authorizations

00:13:17 that I need for each role and the users. So I've logged in here as the test user,

00:13:24 just to show you a little bit about what's happening. This is an optional exercise,

00:13:28 but it's always good to verify what you've done at the end. Just checking what they're seeing.

00:13:32 So you can see now with a real user, I can, for instance, see the default values

00:13:37 that are assigned to this user. I can see a range of apps that they're using,

00:13:41 and I can go into some of those apps and just explore a few standard floor plans

00:13:46 to make sure the main things are working. The vast majority of apps,

00:13:50 all you need to do is activate them. Very, very few apps have any

00:13:54 additional configuration at all. And of course, all of our Fiori elements floor plans

00:13:58 that many of you would know and love already, they're great to work with and good to test to see just

00:14:05 everything's working okay. Okay, so, having turned everything on,

00:14:12 how can I then refine the SAP Fiori for SAP S/4HANA user experience?

00:14:18 So in your development environment, you should treat the SAP business roles

00:14:23 as templates that you refine. SAP S/4HANA includes the launchpad content manager

00:14:30 that you can use to quickly create your own custom business roles,

00:14:34 using those SAP business roles as a starting point. If you want to add your own launchpad content,

00:14:40 you can do that using the launchpad app manager. And there's even a content activation task list to activate

00:14:47 the apps in your custom business roles. You can find demonstrations

00:14:52 and learn how to use all of these tools by reviewing our openSAP microlearning playlist videos

00:14:58 for SAP S/4HANA user experience. You will find the recommended videos in the further learning

00:15:04 in the download section of this course. Each video is 12 minutes or less.

00:15:10 You will even find a video showing how to create and assign your own launchpad layouts

00:15:15 using the entities spaces and pages. Remember to test your layouts and content as your businesses user.

00:15:23 Make sure it works for them. Once you are satisfied,

00:15:26 you can transport your content and layout to the rest of your system landscape using ABAP transport management.

00:15:33 So what types of tools support the UX in live systems? So your SAP S/4HANA solution comes with a variety of tools

00:15:41 to help you support your users, diagnose, and resolve issues from front-end browser

00:15:47 to back-end database. Arguably the most important are the about and app support launchpad features.

51

00:15:55 With these, your users can give you precise information on what they're using alongside the app behavior

00:16:00 that they are seeing. You will find many more tools and recommendations

00:16:05 in the SAP Fiori launchpad administration guide for your SAP S/4HANA release in the SAP Help Portal.

00:16:13 So what are our key takeaways? Okay, so UX adoption is a cross-functional responsibility

00:16:18 that is going to involve activities for many in your project team.

00:16:23 For instance, your business will need to scope your target business roles aligned

00:16:27 to your desired business outcomes. You as a technical team will need to efficiently activate

00:16:33 SAP Fiori and initial business roles as delivered in your sandbox environment. Use the task list,

00:16:39 you can do this in less than a day. After fit-to-standard analysis,

00:16:43 you'll need to refine the launchpad content in your development environment,

00:16:48 craft a default layout per custom business role to get your users started,

00:16:52 and transport that through to your production environment. And of course, then you need to support your users

00:16:58 on your change journey. Lots of tools and support mechanisms to help you do that.

00:17:03 Thanks so much for listening. Now go try it out for yourself.

00:17:07 And we'll see you back here in unit nine.

52

Unit 9

00:00:05 Welcome to the last unit of the openSAP course, Gain Experience with a System

Conversion to SAP S/4HANA.

00:00:11 We hope you have enjoyed the training so far. My name is Jorge Baltazar, and I will be the host of this unit,

00:00:17 where we will go through a quick start around Intelligent Enterprise features

00:00:20 available in SAP S/4HANA. Let's start by defining the current expected status

00:00:26 of your system. If you have followed the exercises in previous units,

00:00:30 by now you should have a fully converted SAP S/4HANA system and have already activated additional engines

00:00:36 like enterprise search, embedded analytics, and SAP Fiori. Once you've reached this status,

00:00:42 the situation poses the next big question, which is how can you get more value

00:00:47 out of your newly converted and configured SAP S/4HANA system?

00:00:52 To answer this question, you will find a very simple answer. Now that you have set up the foundations of SAP Fiori,

00:01:00 and you have already started experiencing this new user experience by consuming features like notifications,

00:01:06 or Fiori apps that leverage technologies like embedded analytics, enterprise search,

00:01:10 and floor plans like overview pages, it is time to enhance this user experience

00:01:15 by consuming additional features on top of the Fiori foundation

00:01:18 that allow you to provide extra intelligence to your business processes and your business users.

00:01:24 The technologies that allow providing intelligent features are Situation Handling, machine learning,

00:01:29 Intelligent Robotic Process Automation or IRPA, and chatbots, and each of these technologies

00:01:35 integrate or leverage features delivered via SAP Fiori, meaning that they either integrate fully

00:01:42 to an SAP Fiori app or they will use tools or services provided by the SAP Fiori framework to provide intelligence.

00:01:50 And now that we named and introduced these technologies, we need to answer an important question,

00:01:56 and that is where should you focus if you wish to start deploying intelligent technologies

00:02:01 in your business? Intelligent technologies in the context of SAP S/4HANA

00:02:07 tend to be associated with SAP Business Technology Platform and complex development efforts by default.

00:02:14 However, we would like to provide some clarity around these technologies.

00:02:18 For starters, complex development efforts might not be required if you focus on implementing IRPA,

00:02:24 Situation Handling, or machine learning, as there are some use cases that have already been delivered

00:02:30 in your SAP S/4HANA systems. Meaning you just need to turn them on,

00:02:35 configure, and consume. This helps prioritize which technologies

00:02:39 you might want to implement in your project. And the next question

00:02:44 will be around the required integrations with SAP Business Technology Platform.

00:02:49 The answer will be yes, this integration is needed, but not for all scenarios, as you will find, for example,

53

00:02:56 that Situation Handling is delivered embedded into your SAP S/4HANA systems.

00:03:01 On the other hand, consumption of IRPA scenarios requires integration to SAP Business Technology Platform,

00:03:07 as the deployment and development tools are delivered via cloud services.

00:03:13 And in the middle, you will find machine learning scenarios, which, depending on the use case,

00:03:18 may or may not require integrations with SAP BTP. This means that some machine learning algorithms

00:03:24 already exist in your SAP S/4HANA system, and you can consume them right away, while others,

00:03:31 the most complex algorithms, require integration with SAP BPT.

00:03:36 Taking these considerations into account, we will now dig deeper into these three technologies.

00:03:42 So let's start with Situation Handling and try to answer the question, what is Situation Handling?

00:03:49 By definition, Situation Handling is an intelligent engine available in SAP S/4HANA Cloud and on premise

00:03:56 that allows you to detect, track, and inform about critical events in your business

00:04:01 that require immediate attention. In order to do this, this engine evaluates the triggers

00:04:06 of the event, meaning, defining what happened, followed by evaluating the context of the trigger,

00:04:12 meaning, understanding what the event means. And lastly, it proposes a solution,

00:04:18 meaning, providing suggestions on what can be done to attend this event.

00:04:23 Situation Handling will provide not only event analysis, but also tools to monitor and adjust such events

00:04:29 and even integration features to further extend to your needs.

00:04:34 And now the next question will be how Situation Handling works. I will try to explain this at a very high level.

00:04:41 So, once Situation Handling is active, you will start running a business process

00:04:45 in your SAP S/4HANA system. As the process runs,

00:04:49 depending on your business process configurations, the system will start detecting any issues

00:04:54 in the ongoing process. And as issues are detected,

00:04:58 the system will start sending notifications to the required individual user or user groups,

00:05:04 and these notifications will be seen through the notifications area in your SAP Fiori launchpad.

00:05:10 Once each user or user group clicks on the notification in their Fiori launchpad, they will be redirected

00:05:16 to a specific app or overview page that provides details of the event.

00:05:22 And from this detailed view, the user can decide if they run a direct action or a corrective measure,

00:05:28 or if the event can be dismissed, allowing users to continue to monitor situations or adjust configurations as needed.

00:05:38 With this brief explanation, you might now be wondering, what do you need to set up this engine in your system?

00:05:44 For the basic setup of Situation Handling, activities will be divided into technical configurations

00:05:49 and functional configurations. In this training, we will focus

00:05:53 on running the technical configurations in the required CAL solution, which is solution four.

00:05:58 So make sure you have set up this image before you run the configuration steps.

54

00:06:04 For these technical configurations, you will first need to run the basic technical configurations

00:06:08 for Situation Handling. And once done,

00:06:11 you will assign specific SAP Fiori business roles to the functional users or to the end users

00:06:16 for them to explore, configure, and test some of the recommended scenarios,

00:06:21 which you will find here. To make it easier to understand,

00:06:26 we will now show a quick demo of the required technical configurations

00:06:30 for Situation Handling. You will first need to activate the notification

00:06:35 of data V4 services, and in this transaction, you will find the notification service for notification

00:06:43 and the situations of data V4 services. Both need to be active in the system.

00:06:49 Once you're done with this, you will then need to run the task list for content activation.

00:06:55 To run this task list, you will use the Fiori launchpad content manager variant

00:06:59 to activate standard and custom roles that we suggest you use for the activation.

00:07:04 So, you will start running the task list and you will first enter the name of the standard

00:07:09 and the custom role that we suggest you use. Once you enter this data into the task list,

00:07:15 you will then need to define or assign the package and the transfer requests that you will use

00:07:21 to activate the services in your system. You can use an existing transport or a new transport,

00:07:27 depending on what you want. And once you're done with this,

00:07:30 you will define the system alias for the OData service for task processing if it is found.

00:07:36 You can then start running the task list. It should take no time

00:07:39 and you will get all of this activated. Once this is done, you will next need

00:07:45 to activate the required notification providers via the transaction that we show here,

00:07:50 and you will need to make sure that the workflow notification provider

00:07:53 and the situation provider are both active, and also the demo notification provider.

00:07:59 With this, you will then need to activate a specific ICF node

00:08:03 for the notifications to work. You will do this via transaction SICF.

00:08:08 And then you will need to navigate to transaction SPRO, for which you will need to navigate to a specific path

00:08:14 in this configuration image. And you will then need to configure the notification hub

00:08:20 in your local gateway deployment. You will first need to activate

00:08:24 and maintain the push channels, which should be really straightforward,

00:08:28 as we show in this transaction, and later you will need to define the system aliases

00:08:34 for the back-end system and for the hub, for the local notification hub, which is also done

00:08:40 via the steps we're showing in this quick video. Once all of this is ready,

00:08:46 you will then need to run the test program to launch the notifications.

00:08:50 This will ensure that all the notifications generated by Situation Handling will be accessible

00:08:56 and will be visible to the end users. You will run this test program and then you will confirm

00:09:02 that the notifications are working in your Fiori launchpad. That way, when users start using Situation Handling,

00:09:09 they will get the notifications in their Fiori launchpad. And going through all these steps will ensure

00:09:16 that once your functional team configures and triggers an event via Situation Handling,

55

00:09:21 notifications should be visible in your Fiori launchpad. Let's now move to the next intelligent technology

00:09:29 and related question, which would be, what is SAP Intelligent Robotic Process Automation, or IRPA?

00:09:37 Intelligent Robotic Process Automation is a tool that allows you to automate repetitive

00:09:41 and time-consuming tasks via interactions with a robot. A robot is a piece of software that you install on your PC

00:09:49 or on a server, and it will simulate a human behavior and interactions with an application into modes.

00:09:55 Unattended, where the robot will run its tasks autonomously, requiring few to no human supervision.

00:10:04 For example, an autonomous robot that reads all purchase orders, which are sent to an e-mail inbox,

00:10:10 and once that e-mail is read, the robot retrieves information

00:10:13 from the e-mail or the attached files, and brings the data into an SAP S/4HANA system

00:10:18 to create the purchase order reference. And the second mode will be attended,

00:10:23 where the robot collaborates with humans in order to run a specific task.

00:10:27 For example, think of an insurance clerk who is called by a customer who has just had an accident.

00:10:34 In this situation, the insurance clerk might need to navigate through different systems

00:10:38 to get to the customer data. But by using a robot,

00:10:42 the insurance clerk can then run an automated list with all the many substeps needed to get the required data

00:10:48 from those multiple systems. With this brief description of the technology,

00:10:54 now you might be asking yourselves in which scenarios it will be recommended to use IRPA.

00:11:01 Overall, you will want to deploy IRPA robots when planning to automate manual and repetitive activities.

00:11:08 These activities should occur in high volume and may require interactions with multiple systems.

00:11:14 If this is the case, you can consider IRPA as an alternative to classic integrations between systems.

00:11:21 An example of the activities or processes that can be automated by IRPA robots are, for example,

00:11:27 logging into multiple SAP instances, collecting purchase requisitions,

00:11:31 and distributing these purchase requisitions to teams in shared service centers, or extracting data

00:11:38 through various connectors like Microsoft Excel, external apps, Web sites, third-party apps,

00:11:44 and enter data into an SAP S/4HANA system, or downloading structured data from various reports,

00:11:51 merging the data, and saving them in a shared drive. So the next question you might be asking now is

00:11:59 how would an SAP IRPA bot work in the context of an SAP S/4HANA implementation?

00:12:06 As we did earlier with Situation Handling, I will try to explain this at a very high level.

00:12:11 So first, a business process must be executed in the system. And at some point, while running this business process,

00:12:18 a repetitive task might be needed to be executed. At this moment, the robot will be invoked by the end user,

00:12:28 and next, the robot will proceed to simulate human interactions and behaviors with the applications.

56

00:12:35 And once those interactions conclude, the business process can continue by running the next steps

00:12:40 or come to a conclusion. All of this will happen while relieving an end user

00:12:46 from this repetitive and time-consuming task. And now you might be wondering how to set up IRPA

00:12:53 and the integrations in your system. To get IRPA bots running, you will need to go through a set

00:12:59 of technical and functional activities to enable the required architecture and deploy the robots

00:13:04 to your end user desktops. In this training, we will focus

00:13:08 on running the technical configurations in the required CAL solution, which is solution four.

00:13:13 So make sure you have set up this image before you run the configuration steps for this exercise.

00:13:20 For these technical configurations, you will need to set up some prerequisites,

00:13:24 like installing some mandatory Visual Studio libraries, and you will also need to set up an SAP BTP trial account,

00:13:31 along with the activation of the IRPA trial. Once this is done, you will run the required configurations

00:13:37 to deploy the bot, and once done, the robot will be ready for your functional team to test

00:13:42 and better understand these solution capabilities. To make it easier to understand,

00:13:49 we will now show a quick demo of the required technical configurations

00:13:53 for SAP Intelligent Robotic Process Automation. This will be an extensive exercise, so be aware

00:14:01 of the multiple steps required to set up and deploy the bot. For starters, you will first need to set up your BTP trial account.

00:14:09 And once this is done, you will need to activate the IRPA services.

00:14:14 Followed by assigning the IRPA security roles to the required users, and next, accessing the IRPA Factory.

00:14:24 When all of this is ready, you will then need to deploy the IRPA agent in your user's desktop,

00:14:30 and you will then need to deploy the standard bot content package to the agent.

00:14:36 And once all this is done, you'll be ready to test the bot. For this example,

00:14:42 you will first need to prepare a dataset in the provided Excel template,

00:14:47 and you will need to enter data for the required sales orders.

00:14:51 And once ready, once you enter all the data into the template,

00:14:55 you will need to copy the Excel file to the folder where the bot will read information.

00:15:00 With all of this ready, you will then need to run the bot, and at this moment is where you will raise your hands

00:15:05 and you will see that all human interactions with the software have been or are being generated,

00:15:11 are being placed by the bot, so there is no interaction

00:15:15 from you when all of this is happening. All human interactions are going to be automated

00:15:22 and you will see information being entered in the file. You will see new columns created

00:15:26 or new sheets created in this Excel file. And on success or error, you will find the files

00:15:32 that will provide the description on what occurred in case of errors, or the created objects in case of successful executions.

00:15:41 Once all of this is done, you can then go back to your SAP S/4HANA Fiori launchpad, and from the app,

57

00:15:48 Manage Sales Order, you can then make sure that the sales orders have been created correctly.

00:15:55 So, in this case, you can enter additional filters to get to the sales orders that were generated,

00:16:01 and you can then compare what you see in the screen of your Fiori application

00:16:05 with the information that you obtained in the Excel files for successful execution of the bot,

00:16:11 and you can even enter and get to see the details of the items that were added

00:16:16 to the sales order automatically by the bot. We now need to talk about machine learning,

00:16:24 so let's try to answer the first question, which is what is machine learning?

00:16:29 First of all, we can define machine learning as the capability of a computer to optimize results

00:16:35 by obtaining experience when running specific tasks. In this case, the term experience would refer to the data

00:16:42 we provide to a computer program. This type of learning means that the computer

00:16:47 is getting better and better at running specific tasks as we feed more and more data into it.

00:16:54 So, in the context of SAP S/4HANA, this means that some programs included

00:17:00 in your SAP S/4HANA system will start learning from the historical data in your system,

00:17:05 and this learning will help programs better predict, support, or automate business decisions.

00:17:12 Considering these definitions and context, you will find that machine learning scenarios in S/4HANA

00:17:18 are focused on predictive automation, recognition, recommendation, and classification scenarios.

00:17:24 And overall, all of these scenarios will be integrated to SAP Fiori, meaning that the consumption tool for the results provided

00:17:32 by the machine learning algorithms will only be visible for the end users via SAP Fiori apps.

00:17:40 Now that we know what machine learning is in the context of SAP S/4HANA, we now need to focus on the available tools.

00:17:48 In this case, we will focus on the tools already included and embedded into SAP S/4HANA,

00:17:53 so we will not discuss the scenarios that require integrations with SAP BTP.

00:17:59 In these embedded scenarios, you will find that the main tools to activate, configure,

00:18:04 and deploy machine learning are SAP Fiori apps. Those apps will be Intelligent Scenarios,

00:18:10 Intelligent Scenario Management, and Predictive Scenarios, and with these Fiori apps, you can then analyze data,

00:18:17 design machine learning models using the pre-deployed algorithms, and train those models so they are later consumed via SAP Fiori apps.

00:18:28 I know it might be difficult to visualize how this works, so let's make it simpler by going through a quick demo.

00:18:34 Please note that you will not find any exercises for this technology as there is not enough data available

00:18:40 in the CAL solution four to train the models correctly. To start with machine learning, you first need to log in

00:18:48 to your Fiori Launchpad and make sure that you have been assigned the role

00:18:52 for analytics specialist. Once you have been assigned this role,

00:18:56 you will be able to access the Predictive Models app. And inside the Predictive Models app,

00:19:02 you will then select the algorithm that you want to train or test.

58

00:19:07 Once you select the algorithm that you want to train or test, you will then select the model that's available,

00:19:13 and in this case, we will start a test train for this model. Once you click on Train, you will get to see the options

00:19:20 to define the model version description, and you will also find options to add filters.

00:19:26 These filters will modify the weights and vary training results,

00:19:31 and you can enter as many filters as you want. So here, we're showing the options

00:19:36 of all the filters available for this model, and we will only set up a specific value

00:19:41 for sales organization that we want to train this model for.

00:19:45 You will then click on Train, and then you will go to the model details where you find a list

00:19:50 of all the previous trainings that you have run. While the model is being trained, like in this example,

00:19:57 you will find the applied filters for the training. But in a fully trained model,

00:20:01 you will find a quality and prediction rating along with key influencers of the datasets,

00:20:07 which can help you understand how predictions work. Here, we're showing you multiple visualizations of these key influencers,

00:20:17 and you can train all your models by setting different filters, and this will allow you to obtain multiple versions of the model,

00:20:26 and better ratings and results when consuming the algorithms. Once you select the model version that well suits you,

00:20:32 you activate that and then you can start launching Fiori applications that will allow you to visualize those integrated machine learning capabilities

00:20:40 and you will then be capable of interpreting the results as needed. In this case, when we navigate to the app Quotation Conversion Rates

00:20:48 and we navigate to the list of quotations for a specific customer, you will then find the predicted quotation conversion rates,

00:20:56 which can help you decide which quotations you might want to prioritize.

00:21:05 Now that we have learned about the three main intelligent technologies in SAP S/4HANA,

00:21:10 you might want to know how many prebuilt intelligent scenarios are available in SAP S/4HANA.

00:21:17 To answer this question, in this slide, you will find the reference number

00:21:20 of the available scenarios. For example, for IRPA, there are more than 70 use cases

00:21:26 already available for deployment into your SAP S/4HANA 2020 system.

00:21:30 For Situation Handling, you will find over 65 use cases available in SAP S/4HANA 2020.

00:21:36 And for machine learning, you will find more than 15 use cases

00:21:40 ready to be deployed and consumed. So now you know a bit more about the technologies

00:21:46 and the number of available use cases. Now you might be wondering

00:21:50 if there are any additional recommendations that would allow you to jumpstart the adoption

00:21:55 of intelligent technologies. There is a programmatic approach to find out

00:22:00 for which business processes you might want to enable intelligent technologies,

00:22:05 and this is available by running the Process Discovery for SAP S/4HANA Transformation report.

00:22:11 To run this report, you will first need to extract data from your system by applying some Notes in your systems,

00:22:17 and once done, you will need to create a request and upload the extracted data from your system

00:22:22 in a zip file. Next, SAP will confirm your request

00:22:26 and create a summary with the analyzed data. And lastly, SAP will send the summary and instructions

59

00:22:33 on how to activate your Process Discovery solution account. You might be wondering, why would you receive an account?

00:22:42 But this is the interesting part of running this report. So we will explain this through a quick video.

00:22:50 Once you get the details of your account, you will then need to log in to your account

00:22:54 to see the results from the report. Here, we will start by logging into this sample report.

00:23:01 And once you have logged in, you will find critical KPIs you could improve by adopting new features or processes in SAP S/4HANA.

00:23:09 But most importantly, if you navigate to the Reports section, you will find a Process Automation opportunities report.

00:23:17 In this report, you will find a list of processes with automation potential and the recommended SAP Fiori, Situation Handling,

00:23:26 machine learning, and Intelligent Robotic Process Automation solutions you could leverage to deliver automation

00:23:33 and intelligence to your business. So, in this example, you can find out

00:23:37 that there have been some best practices that are recommended to be deployed in the system.

00:23:42 And for each best practice, there is also a suggested innovation technology

00:23:48 or automation technology like IRPA, Situation Handling, machine learning, or even SAP Fiori applications

00:23:56 that you could potentially use. We have now come to the end of the session,

00:24:03 but let's go through a brief summary of what we learned in this unit.

00:24:07 You now know that intelligent technologies are an integral part of SAP S/4HANA as they add automation

00:24:13 or intelligent capabilities to the system. You also learned that intelligent technologies

00:24:18 can be deployed using the embedded features in SAP S/4HANA, or side by side by leveraging SAP Business Technology Platform.

00:24:27 You also identified three technologies you can prioritize for deploying or exploring, which are Situation Handling,

00:24:34 Intelligent Robotic Process Automation, and embedded machine learning algorithms.

00:24:40 And last, you also learned about the programmatic approach to identify major automation opportunities in your system,

00:24:47 available by running the Process Discovery for SAP S/4HANA Transformation report.

00:24:53 We have now come to the end of this course. We hope you enjoyed the content and exercises,

00:24:59 and wish you luck in your assignments. Thanks for watching, and hope to see you soon.

www.sap.com/contactsap

© 2021 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 serv ices are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, 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/trademark for additional trademark information and notices.