PUBLIC Version 3.1 / May 2019

PUBLIC

Version 3.1 / May 2019

SAP Batch Job - Health Status With SAP Solution Manager 7.2 Support Package Level 08

2

TABLE OF CONTENTS

1 INTRODUCTION ............................................................................................................................... 3

1.1 Concept of Batch Job - Health Status ............................................................................................ 3

1.2 Benefits of Batch Job - Health Status............................................................................................. 3

2 SETUP .............................................................................................................................................. 4

2.1 Prerequisites.................................................................................................................................... 5

2.1.1 Relevant SAP Notes ..................................................................................................................... 5

2.1.2 Managed System .......................................................................................................................... 5

2.1.3 SAP Solution Manager System.................................................................................................... 5

2.1.3.1 BW Client ................................................................................................................................... 5

2.1.3.2 SolMan Setup executed .............................................................................................................. 5

2.1.3.3 SAPSUPPORT user in Solution Manager ................................................................................... 5

2.1.3.4 Check changeability of Repository and cross-client Customizing ................................................. 7

2.1.3.5 Check System Change Options .................................................................................................. 7

2.1.3.6 Specific Users, Roles and authorizations in SAP Solution Manager 7.2 ....................................... 9

2.1.3.7 Role Z_SAP_BW_CCMS_SETUP .............................................................................................. 9

2.1.3.8 Role Z_JSM_HC_USER ........................................................................................................... 11

1.1 ACTIVATION WITH SAP SOLUTION MANAGER........................................................................... 12

1.1.1 SAP Notes providing latest corrections for activation report .................................................. 13

2.1.4 Activate SAP Business Information Warehouse objects ......................................................... 13

2.1.4.1 Activation using report RAGS_JSM_CONFIG_CUSTOMIZE ..................................................... 13

2.1.4.2 Alternative: Activation using report RS_BCT_SM_SETUP_JSM_HC ......................................... 13

2.1.4.3 Activation results ...................................................................................................................... 14

2.1.5 Maintain table for target-source mapping for aggregation and data reorganization .............. 15

2.1.6 Check if the Extractor Framework (EFWK) and housekeeping job are working ..................... 16

2.1.7 Check E2E Resources used by the Extractor Framework ....................................................... 18

2.1.8 Activate data extraction process in Extractor Framework (EFWK) ......................................... 19

2.1.9 Web Service Activation .............................................................................................................. 21

2.1.10 Check Batch Job - Health Status Report .................................................................................. 21

3 TROUBLESHOOTING .................................................................................................................... 22

3.1 Problems during activation process............................................................................................. 22

3.1.1 Error during activation of BW objects....................................................................................... 22

3.1.1.1 Problem with EFWK Administration Work Center ...................................................................... 23

3.1.1.2 JM extractors are missing in the list of available extractors........................................................ 23

3.2 Problems after activation process ................................................................................................ 24

3.2.1 No data available for the Batch Job - Health Status Report ..................................................... 24

3

1 INTRODUCTION

The SAP Batch Job - Health Status check is an analytical functionality within SAP Solution Manager. It provides reporting dashboards based on key performance indicators (KPI) related to job execution data collected from selected managed SAP systems. These KPIs provide an overall picture about the actual system workload caused by background processing in order to identify possible optimization potential in specified managed systems connected to the SAP Solution Manager. The reporting dashboards make use of the SAP Business Information Warehouse (BW) component available in SAP Solution Manager as an SAP Netweaver 7 system and offer views on different aggregation levels and timeframes. The SAP Batch Job - Health Status Batch Job - Health Status is based on a dashboard which can be used for regular, ad-hoc analysis or even in situations where you face serious issues in your job scheduling landscape (i.e. bottleneck situations). Starting with Solution Manager SP08, a dedicated ABAP Job - Health Status (cross system) Dashboard is predelivered.

1.1 Concept of Batch Job - Health Status

The Batch Job - Health Status uses the Extractor Framework (EFWK) of SAP Solution Manager Diagnostics (SMD) to extract and to aggregate job execution data from managed systems and simple job / BW process chain monitoring data collected from the managed systems into InfoCubes located in the BW component of SAP Solution Manager. All jobs in selected managed systems with a final status (“finished” or “cancelled”) are considered for the Batch Job - Health Status and collected on an hourly basis, the available aggregation for job execution data from daily for weekly and monthly views is done once a day automatically. The available data can be displayed via the predefined Dashboard. A set of extractors are available to extract job execution data from the managed systems. This set contains an extractor for taking only the job execution header information from table TBTCO into account, while another is combining data from job execution header (TBTCO) and job execution item (TBTCP) table (see figure1).

Figure 1 Batch Job - Health Status Concept

Dashboards (BW Report) InfoCube Data Source

Daily View on Jobs 0SM_JSM_H Table TBTCO in managed systems

Daily View on Jobs (Step) 0SM_JSM_H Table: TBTCO and TBTCP in managed systems

Weekly View on Jobs 0SM_JSM_D Aggregated from InfoCube 0SM_JSM_H

Weekly View on Jobs (Steps) 0SM_JSM_D Aggregated from InfoCube 0SM_JSM_H

Monthly View on Jobs 0SM_JSM_W Aggregated from InfoCube 0SM_JSM_D

Monthly View on Jobs (Steps) 0SM_JSM_W Aggregated from InfoCube 0SM_JSM_D

1.2 Benefits of Batch Job - Health Status

The dashboards answer the following questions:

• Which jobs have cancelled?

• Is there a system bottleneck, causing job delays?

4

• Is batch job processing working at all, i.e. do we have a normal number of finished jobs?

• Which jobs have highest runtime and do they deteriorate?

Figure 2: Dashboard Example for Job Health Status

The graphical views enable an easy overview about the job execution status and distribution in the managed systems. The tabular views provide more detailed information via drilldown functionality. In addition, these tabular views can also be exported as MS excel files. With such reports, the M Health Check provides you an overview about the job scheduling situation and system workload caused by background jobs in the managed systems, thus enhances the transparency of the existing job schedule and jobs which are causing problems or which can be improved.

2 SETUP

The following activation steps can be either performed directly in the productive SAP Solution Manager system or the activation steps can be applied first in the development SAP Solution Manager system and get afterwards transported (via quality assurance system) to the productive SAP Solution Manager.

DISCLAIMER:

Please use this Setup Guide for Batch Job - Health Status at your own risk. All our recommendations regarding the activation of this functionality are based on our general experience and maybe are not valid for your specific implementation, especially when you are already using the SAP BW component in SAP

5

Solution Manager. In this case, please consult and involve the people already working with BW in the target system to make sure that all functions in BW keep working.

2.1 Prerequisites

2.1.1 Relevant SAP Notes

Please refer to SAP Note 2319931. This is a collective note for the Batch Job - Health Status of the SAP Solution Manager 7.1 and the SAP Solution Manager 7.2.

2.1.2 Managed System

RFC user assigned to READ and TMW RFC connections from Solman in the managed system:

2.1.3 SAP Solution Manager System

2.1.3.1 BW Client

The Batch Job - Health Status is implemented in software component BW Content (BI_CONT or ST-BCO). If there is no BW client maintained in your system, please define it in the SAP Solution Manager Configuration. In general, it is recommended using the same client as BW client as is used as Solution Manager client. The client assignment cannot be changed later on after the initial configuration.

2.1.3.2 SolMan Setup executed

SOLMAN_SETUP “Mandatory Configuration” & “Managed System configuration” for managed system(s) in scope executed

2.1.3.3 SAPSUPPORT user in Solution Manager

Combine the roles from template user SM_TECH_ADM (created in SOLMAN_SETUP: Cross Scenario Configuration -> Mandatory Configuration -> System Preparation step 5) and template user BPO_ADM_XXX (created in SOLMAN_SETUP: Business Process Operations -> Basic BPO Configuration -> Step 6). In addition, the following roles shall be added to that user.

• SAP_SM_SCHEDULER_CONFIG

• SAP_SM_JMON_CONF

• SAP_SM_ROLECMP_ALL

• SAP_SM_SMUA_ALL

• SAP_SMWORK_CONFIG

• SAP_SM_CRM_UIU_SOLMANPRO_ADMIN

• SAP_SMWORK_JOB_MAN

• SAP_SM_CRM_UIU_SOLMANPRO_PROC

• SAP_SM_CRM_UIU_SOLMANPRO_CHARM

• SAP_SM_BPMON_REPORTING

• SAP_SM_CRM_UIU_FRAMEWORK

• SAP_SM_CRM_UIU_SOLMANPRO

• SAP_SYSTEM_REPOSITORY_DIS

6

• SAP_SM_FIORI_LP_EMBEDDED

• SAP_SM_RFC_ADMIN

• SAP_SM_USER_ADMIN

• SAP_SM_S_RFCACL

• SAP_SETUP_SYSTEM_PREP_DISP Info: BW is previously known as BI. Both BW and BI refer to the SAP Business Information Warehouse.

7

2.1.3.4 Check changeability of Repository and cross-client Customizing

Note: In a productive system the settings for the Repository and cross-client Customizing might not be changeable. If this is the case, the activation steps have to be performed in the development system first. The changed objects have to be transported to the productive system in a second step.

Before starting the activation process, the changeability of the Repository and cross-client Customizing has to be checked. Modifications of these items must be allowed, because several changes affecting cross-client topics are applied to the system configuration during the activation. Make sure that in transaction “SCC4” the settings for the selected BW client are set to status “Changes to Repository and cross-client Customizing is allowed” (see figures 5 & 6). Otherwise change it. After completing the activation process it can be reset to its original status.

Figure 3 – Double click on the selected BW client in transaction “SCC4”

Figure 4 – Changes to Repository and cross-client Customizing should be allowed

2.1.3.5 Check System Change Options

Note: In a productive system the settings for System Change Options might not be changeable. If this is the case, the activation steps have to be performed in the development system first. The changed objects have to be transported to the productive system in a second step.

8

In order to ensure objects related to the BW Reporting functionality can be activated, three namespaces have to be set to status “modifiable” in transaction “SE03”. Following the node “Set System Change Option”, you have to check if the namespaces “/B10/” (Generation Namespace for SAP BI Content), “/BI0/’ (Business Information Warehouse – SAP Namespace) and “/BIC/” (Business Information Warehouse: Customer Namespace) are modifiable. If not, change them to “modifiable” (see figures 7 & 8).

Figure 5 – Transaction SE03 used to set system change options

Figure 6 – Check if relevant BW namespaces are modifiable - If not, change them accordingly

9

2.1.3.6 Specific Users, Roles and authorizations in SAP Solution Manager 7.2

Please configure the necessary roles / authorizations via transaction PFCG as described below. These minimum authorizations are needed in order to activate Batch Job - Health Status and get a picture of the results. In case the authorization configuration cannot be done in productive systems, please first do the configurations in development system and then transport the changes to the productive systems. For the activated BW objects, please use the BW Transport Connection available in the BW Administration Workbench (RSA1).

2.1.3.7 Role Z_SAP_BW_CCMS_SETUP

• Create role Z_SAP_BW_CCMS_SETUP from standard role SAP_BW_CCMS_SETUP.

• Extend authorizations: extend the object class AAAB, object S_TCODE, field TCD with RSRV, SICF and SU53.

Figure 7 – Screen shot: Role Z_SAP_BW_CCMS_SETUP (1)

• Extend authorization: fill object class BC_A, object S_TABU_DIS, field DICBE with *.

10


• Insert authorization: fill object class BC_Z.


• Insert authorization: fill object S_APPL_LOG, field ACTVT with 03, field ALG_OBJECT with RSRV

and ALG_SUBOBJ with Dialog.


11

2.1.3.8 Role Z_JSM_HC_USER

The following role must be manually created in the customer namespace, since there is no corresponding standard role available. The role assigns the necessary authorizations for the database access during the activation of Batch Job - Health Status.

Figure 11 – Screen shot: Role Z_JSM_HC_USER (1)

• In addition to the set-up in release 7.1, the object S_RS_ADMWB / 63 / CONT_ACT has to be added to the role Z_JSM_HC_USER. Fill the field ACTVT with 03, field RSADMWBOBJ with CONT_ACT.

Figure 12 – Screen shot: Role Z_JSM_HC_USER

Profile S_DEVELOP

• This profile is necessary for activating the Batch Job - Health Status.

12

1.1 ACTIVATION WITH SAP SOLUTION MANAGER

The following sections describe the activation process of the Batch Job - Health Status in SAP Solution Manager step by step. Activation steps are valid in release 7.1 and 7.2. If any problems arise during activation, please refer to the Troubleshooting chapter at the end of the document. Report RAGS_JSM_CONFIG_CUSTOMIZE supports the different steps of the activation. Note: The activation of BW objects is performed in BW client, all other steps in Solution Manager client.

13

1.1.1 SAP Notes providing latest corrections for activation report

The following SAP Notes provide the latest corrections for the activation report RAGS_JSM_CONFIG_CUSTOMIZE. It is highly recommended to implement the corrections before the activation is performed. If all or some of the activation steps were performed already, follow the instructions in the SAP Notes to update the settings in the Solution Manager.

SAP Notes:

• 2249196 - Catch-up run of extractor extract data only for the last one hour

• 2252512 - Data in the hourly cube should be kept longer to enable issue analysis

2.1.4 Activate SAP Business Information Warehouse objects

2.1.4.1 Activation using report RAGS_JSM_CONFIG_CUSTOMIZE

In order to activate the necessary BW objects for the Batch Job - Health Status execute the report RAGS_JSM_CONFIG_CUSTOMIZE by checking “BW Content Activation and entering RFC destination to BW (this will create a background job for report RS_BCT_SM_SETUP_JSM_HC).

Figure 13 – Screen shot: Report RAGS_JSM_CONFIG_CUSTOMIZE

2.1.4.2 Alternative: Activation using report RS_BCT_SM_SETUP_JSM_HC

Alternatively report RS_BCT_SM_SETUP_JSM_HC can be executed in background or dialog mode with transaction SE38. It may take a few minutes until the execution completes.

If you execute the report in dialog mode, the following selection screen is displayed (figure 15), please leave the entry field empty and press the execution button (F8) to start the activation process:

Figure 104 – Screen shot: Report to generate BW objects

Info: If you run the report in Dialog Mode instead of running it in the background, there will be a pop-up with warning message “Active BI Content might be overwritten. Continue?” In this case click “Yes” to continue. In addition, there may be a popup for “Select Source Systems”, just click on “yes” to continue (it has no effect in our case).

14

2.1.4.3 Activation results

Once all objects are configured you should receive message “All steps successfully performed” as shown in figure 16. If the activation was done in background the information can be found in the spool of the job which executed report RS_BCT_SM_SETUP_JSM_HC.

Figure 115 – Screen shot: successful messages after activation of BW objects

Note: to verify the RFC connection to BI client for the field “RFC to BW”, you can check the relevant entry in table “E2E_WA_CONFIG” (do selection with TYPE “SAP_BID”, double-click on the selected item, and then check the STRING). The result can be checked in the Data Warehousing Workbench:

• Go to Data Warehousing Workbench via transaction code RSA1;

• Select the “InfoProvider” on the left side;

• Expand the “SAP Solution Manager”, then expand the subtree “SAP Solution Manager - Job Scheduling

Management”;

• You will see the JM objects, similar as shown in the screen shot below.

15

Figure 126 – Screen shot: Data Warehousing Workbench

2.1.5 Maintain table for target-source mapping for aggregation and data reorganization

In this step we maintain the aggregation levels for the housekeeping job in table E2E_BI_AGGREGATE, as well as maintain the table E2E_BI_DELETE for deletion jobs. This step is only required for Batch Job - Health Status on Jobs (Daily/Weekly/Monthly view).

The tables E2E_BI_AGGREGATE and E2E_BI_DELETE are maintained by executing report RAGS_JSM_CONFIG_CUSTOMIZE.

Figure 17 – Screen shot: execute report RAGS_JSM_CONFIG_CUSTOMIZE

Note: to verify the RFC connection to BI client for the field “RFC to BW”, you can check the relevant entry in table “E2E_WA_CONFIG” (do selection with TYPE “SAP_BID”, double-click on the selected item, and then check the STRING).

16

The standard job data life time in the InfoCubes related to the Batch Job - Health Status are configured by the report in table E2E_BI_DELETE in the following way:

Figure 18 – Screen shot: Reorganization parameters

with

0SM_JSM_H $DELTA=8$ (8 days)

0SM_JSM_D $DELTA=30$ (1 month)

0SM_JSM_W $DELTA=180$ (6 months)

Explanation of the above example:

“0CALDAY” stands for the current day, for example 09.07.2018. If “DELTA = 8”, this means the threshold date is current day minus 8 days (01.07.2011). In this case, all data in 0SM_JSM_H that is older than 01.07.2011 will be deleted. This configuration ensures that the data at lowest level will only be available for 8 days, so that the data volume will be kept low.

These entries can be changed any time manually according to your special needs.

2.1.6 Check if the Extractor Framework (EFWK) and housekeeping job are working

The Batch Job - Health Status on Jobs has three dashboards views with different aggregation levels and timeframes (i.e. daily view, weekly view, monthly view) based on the data collected by the extractors. To enable this functionality, the EFWK and housekeeping jobs must be working to start the automatic aggregation and reorganization process.

Please follow the steps below to check the jobs in transaction SM37 in the SolMan client. If the jobs are not scheduled in the system yet, schedule and activate them.

17

The report E2E_EFWK_RESOURCE_MGR starts extraction cycle of EFWK and executes due data extractor according to scheduling; this job should run every minute.

Figure 19 – Screen shot of SM37: check BW Extractor job

This job should be scheduled during configuration of SAP Solution Manager. It starts data extraction process from configured managed systems and saves data in the Batch Job - Health Status hourly InfoCube 0SM_JSM_H.

• The housekeeping report E2E_HK_CONTROLLER performs data aggregation and reorganization within the EFWK regarding the configuration in the underlying tables E2E_BI_AGGREGATE and E2E_BI_DELETE; this job should run daily (e.g. one time shortly after midnight):

18

Figure 20 – Screen shot of SM37: check the housekeeping job

For more information about the aggregation levels and data reorganization, please refer to the sections 2.2.3.

2.1.7 Check E2E Resources used by the Extractor Framework

In this step you need to check table E2E_RESOURCES which contains RFC resources available for data extraction within EFWK with transaction SE16. Normally all systems should be defined here that have been configured in managed system setup in the configuration of SAP Solution Manager. If an entry is missing you can manually create it as well, but maybe you should check before the managed systems setup.

Figure 21 – Screen shot: check E2E Resources

19

The naming convention for the RFCRESOURCE is “SM_SIDCLNT000_READ” (replace “SID” with the system ID, the “000” with the client number). Please make sure that the list includes the needed system, as well as the entries “NONE”, “SOLMANDIAG” and “SOLMAN_DIALOG_WORKPROCESSES”.

Note: if BW client is different from Solution Manager client (i.e. RFC destination to BI is not “NONE”), then there should be an entry in this table for RFC destination to BW client under RFCRESOURCE (see field “String” in table E2E_WA_CONFIG where type = SAP_BID).

Information about the field RESOURCECAP:

It defines the maximum number of dialog work processes which can be used for data extraction purposes.

2.1.8 Activate data extraction process in Extractor Framework (EFWK)

In this step, we have to configure the system specific data extraction process for the Batch Job - Health Status by updating table E2E_ACTIVE_WLI for active worklist items within the EFWK. This table contains the scheduling information for all extractors being executed.

For Job Daily/Weekly/Monthly view, we have to add the scheduling of the Batch Job - Health Status extractors here to trigger data transfer between SAP Solution Manager and managed systems. We recommend scheduling either the extractor for job or for job step execution data for one specific system you want to include in the Batch Job - Health Status. The extractor for job execution data only collects information from table TBTCO; the extractor for job step execution data collects job step data in addition, by joining the tables TBTCO and TBTCP.

20

• Within the JM Work Center, go to tab “Administration” in the left window, the select option “Manage

Data Collection for Analytics” in the right window to enter the EFWK Work Center.

Figure 22 – Screen shot: Maintain extractors

• As shown in the screen shot below, filter by “*jsm*” in the Extractor Overview list. Select the corresponding extractor; then click on the change button to enter the change mode.

Figure 23 – Screen shot: select the extractor to be activated

• Click on the “Activate” button for the reports you want to use, then the extractor is activated, which is indicated by the light bulb in the “Active Status” column.

21

Figure 24 – Screen shot: activate the extractor

2.1.9 Web Service Activation

Before the web template for Batch Job - Health Status can be used in the system, the “BEx (Business Explorer)” and “Mime (MIME in Web Reporting)” Web services have to be activated. For this call transaction “SICF”.

At this point, all activation steps have been executed successfully.

2.1.10 Check Batch Job - Health Status Report

After extractor execution, the Batch Job - Health Status can be executed via “Business Process Monitoring” Work Center – Configuration Dashboard Builder. Navigate to “Business Process Operations – Batch Job – Health Status”:

Figure 13: Batch Job Health Status Dashboard

22

3 TROUBLESHOOTING

When activating or working with the Batch Job - Health Status, you could sometimes face technical issues for which we want to provide you – according to our experience – a short description how to handle and solve it. If you face technical issues which are not included in this chapter, please feel free to create a customer message on component SV-SMG-PSM, providing a detailed description of your issue.

3.1 Problems during activation process

3.1.1 Error during activation of BW objects

Symptom:

As described in section 2.3.6, you executed report RS_BCT_SM_SETUP_JSM_HC in the BW client in order to generate BW objects for the Batch Job - Health Status. After the execution, the report returns error messages as shown in the following screen shot.

Figure 29 – Screen shot: Error messages from the report to generate BW objects

Solution:

In the transaction RSOR, manually activate the InfoArea 0SM_JSM and all the related objects in the process.

23

3.1.1.1 Problem with EFWK Administration Work Center

Symptom:

You want to perform the step described in section 2.3.10, but the EFWK Administration work center is not working.

Solution:

Directly change the “ACTIVE” field in the table E2E_ACTIVE_WLI via transaction SE16. Set this field to “X” to activate the extractors.

3.1.1.2 JM extractors are missing in the list of available extractors

Symptom:

You want to activate the JM Extractors as described in section 2.3.10. The EFWK Administration work center is working, however the JM extractors are missing in the list of available extractors.

Solution:

There are some steps missing in managed system setup of the Solution Manager. Perform the following steps:

Execute transaction SOLMAN_SETUP in the Solution Manager system. Go to ‘Managed System Configuration’, select the relevant managed system and press ‘Configure System’. In step 8 ‘Configure Automatically’ select ‘Extractors Setup’ and press ‘Execute Selected’ (see below picture). This will refresh the available extractors for the managed system relevant for the product version.

Figure 30 – Screen shot: Setup extractors for the managed system

In case of errors check the details of the error message.

24

3.2 Problems after activation process

3.2.1 No data available for the Batch Job - Health Status Report Symptom: The Batch Job - Health Status has been set up, but you do not see the results in the report because there is no data in the InfoCube. Solution:

1. Start Solution Manager Administration Work Center, select the tab “Infrastructure”.

Figure 31 – Screen shot: Check Extractor Status (1)

Then select “Framework” -> “Extractor Framework”.


In the Extractor Overview list, filter by “*JSM*”. Select the related extractor, and check the status.


As next step, select the related extractor, check the status.

2. In case the extractor is “banned”, you may check if the problem can be solved by releasing the extractor.

25

3. If the problem persists or in case of error status you can check the extractor logs and extractor details by clicking on the extractor entry.


4. Try to analyze and solve the problem based on the content of the error logs.

5. After you have solved the problem, deactivate and reactivate the extractor so that the extractor will be restarted.

www.sap.com/contactsap

© 2019 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and 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/copyright for additional trademark information and notices.

https://www.sap.com/copyright

PUBLIC Version 3.1 / May 2019

Documents

Transcript of PUBLIC Version 3.1 / May 2019