s4h25 opensap: unit 05: maintenance planner, impact on add
TRANSCRIPT
openSAP_s4h25_Unit_5_Maintenance_Planner_Exercise.pdfs4h25 – Unit
05 Exercises
s4h25 openSAP: Unit 05: Maintenance Planner, Impact on add-ons and Business Functions
Exercise 1: Check stack.xml file whether any add-ons will be deleted during SUM execution
Exercise 2: Check in which version and on which system SAP FIORI FES FOR SAP S/4HANA 2020 will be installed
Exercise 3: Verify whether SAP Fiori
packages selected in the Maintenance Planner are included in stack.xml file
Logon Data ................................................................................................................... 3
Logon to system (SAP S/4HANA)................................................................................... 3
Exercise 1: Check stack.xml file whether any add-ons will be deleted during SUM execution4
Overview ....................................................................................................................... 4
Objective ....................................................................................................................... 4
Prerequisites ................................................................................................................. 4
Overview ....................................................................................................................... 7
Objective ....................................................................................................................... 7
Prerequisites ................................................................................................................. 7
Results: ......................................................................................................................... 9
Exercise 3: Verify whether SAP Fiori packages selected in the Maintenance Planner are included in stack.xml file .................................................................................................. 11
Overview ..................................................................................................................... 11
Objective ..................................................................................................................... 11
Prerequisites ............................................................................................................... 11
Prerequisites for the exercises
You need to have completed all exercises of Unit 01. You must have created your own instance of 1: “SAP ERP source system”
https://cal.sap.com/subscription?sguid=1a3556c0-0ee1-4a4c-8a5a- db08173df293
Logon Data Refer to the welcome page on the desktop of your SAP CAL instance.
User ID Password Client number
10steps2s4 <your SAP CAL instance master password>
100
https://cal.sap.com/subscription?sguid=1a3556c0-0ee1-4a4c-8a5a- db08173df293
4
ons will be deleted during SUM execution
Overview
Objective
Add-ons need to be supported for the target SAP S/4HANA stack. For SAP Add-ons and Partner Add-ons which are part of the SAP price list, the Maintenance Planner will check whether Add-ons identified in the source system are released for the target SAP S/4HANA stack or not. Add-ons which are not supported for the target SAP S/4HANA stack can possibly be deleted during the conversion. The result of your maintenance planner activities is summarized in a stack.xml file which will be consumed by the Software Update Manager (SUM).
NOTE: For all other Add-on types you need to get in touch with the 3rd party vendor to check the release status of the Add-on for the target SAP S/4HANA stack and you need to provide the SUM tool a corresponding archive or ACP file manually.
Prerequisites
For this exercise there is already a stack.xml file available on the remote Microsoft Windows desktop of your CAL instance. Please don’t change this stack.xml file and don’t use it for any other exercise or purpose. For Unit 06 a separate stack.xml file will be provided.
Exercise Description In this exercise you will verify in the stack.xml file whether the Maintenance Planner found any Add-on in the source system which is not released for the target S/4HANA stack and which will be deleted during SUM execution. You will perform the following tasks:
• Find and open the stack.xml
• Search for Add-on information in the stack.xml file
• Check whether any Add-on will be deleted during SUM execution
s4h25 – Unit 05 Exercise 1
5
What to Do What You Will See
1. Activate your instance of SAP CAL solution 1 and log on to RDP, Windows Remote Desktop. User: Administrator Password: <your instance master password for CAL solution1>
2. Right click on the MP_Stack_S4HAN A_2020_FPS00.xml file which you can find on the remote Microsoft Windows desktop and open it using Internet Explorer
s4h25 – Unit 05 Exercise 1
6
3. Browse through the MP_Stack_S4HAN A_2020_FPS00.xml file content and look out for the tag <to- be-deleted>. Within this tag you will find further information about add-ons to be deleted. For each such add-on you can find a tag called <product>.
4. Either continue directly with exercise 2 or suspend your instance of SAP CAL solution 1. Re- activate it once you continue with exercise 2. This is important to save cost.
Results:
s4h25 – Unit 05 Exercise 2
7
be installed
Objective
When planning a system conversion to SAP S/4HANA the Maintenance Planner offers the possibility to deploy additional systems, e.g. a SAP Fiori Frontend Server can be co- deployed directly on the converted S/4HANA system – the so called embedded deployment option for SAP Fiori.
According to your selections during the planning activities the Maintenance Planner will not only offer the required software archives for download but also include the “deployment instructions” into the stack.xml file which will be consumed by the Software Update Manager (SUM).
Prerequisites
For this exercise there is already a stack.xml file available on the remote Microsoft Windows desktop of your CAL instance. Please don’t change this stack.xml file and don’t use it for any other exercise or purpose. For Unit 06 a separate stack.xml file will be provided.
Exercise Description
In this exercise you will verify in the stack.xml file on which system the Fiori Frontend Server (FES) will be deployed and which version of SAP Fiori FES for S/4HANA will be installed. You will perform the following tasks:
• Find and open the stack.xml
• Identify which version and SP level of SAP Fiori FES for S/4HANA will be installed
• Check on which system the SAP Fiori Front-end server will be deployed
s4h25 – Unit 05 Exercise 2
8
What to Do What You Will See
1. Open a remote desktop connection and log on to your instance for SAP CAL solution 1. User: Administrator Password: <your instance master password for CAL solution1>
2. Right click on the MP_Stack_S4HAN A_2020_FPS00 file which you can find on the remote Microsoft Windows desktop and open it using Internet Explorer
s4h25 – Unit 05 Exercise 2
9
3. Browse through the MP_Stack_S4HAN A_2020_FPS00 file content and look out for the tag <sp- stack> in which SAP FIORI FES FOR S/4HANA is mentioned. Once you have found this element, you can identify the SP Level via the <caption> tag. The product’s release version itself is mentioned in the <version> element.
5. In the previously found <sp-stack> element continue to look out for the tag <sp-feature-stack>. Beyond, you will find another element called <application- system> where you can identify target system details via tags <sid> and <host>
6. Either continue directly with exercise 3 or suspend your instance of SAP CAL solution 1. Re- activate it once you continue with exercise 3. This is important to save cost.
Results:
• The following version and SP level of Fiori FES for S/4HANA will be installed:
s4h25 – Unit 05 Exercise 2
10
• The Fiori FES for S/4HANA will be installed on the following system:
s4h25 – Unit 05 Exercise 3
11
in stack.xml file
Objective
While defining the Fiori Frontend Server (FES) deployment type in the Maintenance Planner you can choose which Fiori packages shall be implemented on the FES.
According to your selections during the planning activities the Maintenance Planner will not only offer the required software archives for download but also includes the “deployment instructions” into the stack.xml file which will be consumed by the Software Update Manager (SUM).
Prerequisites
For this exercise there is already a stack.xml file available on the remote Microsoft Windows desktop of your CAL instance. Please don’t change this stack.xml file and don’t use it for any other exercise or purpose. For Unit 06 a separate stack.xml file will be provided.
Exercise Description
In this exercise you will verify in the stack.xml file whether all SAP Fiori packages which have been selected in the Maintenance Planner are listed in the stack.xml file and can be deployed during SUM execution. You will perform the following tasks:
• Find and open the stack.xml
• Check which Fiori packages are included in the stack.xml file
s4h25 – Unit 05 Exercise 3
12
What to Do What You Will See
1. Open a remote desktop connection and log on to your instance for SAP CAL solution 1. User: Administrator Password: <your instance master password for CAL solution1>
2. Right-click on the MP_Stack_S4HAN A_2020_FPS00 file which you can find on the remote Microsoft Windows desktop and open it using Internet Explorer
s4h25 – Unit 05 Exercise 3
13
3. Browse through the MP_Stack_S4HAN A_2020_FPS00 file content and look out for the tag <sp- stack> in which SAP FIORI FOR S/4HANA is mentioned. Once you found this element please verify if there is for each of the following products a <sp-feature-stack> element included:
• UI for SAP S/4HANA
• UI for MDG
• UI for TRV
4. You have completed all exercises of SAP CAL solution 1. If you want to check any further information in this system status, you can do so. Otherwise, it is no longer required, and we recommend that you terminate your SAP CAL solution 1 instance in order to save cost. Please note that an
s4h25 – Unit 05 Exercise 3
14
instance termination cannot be revoked, and you would be losing any configuration that you have done in that instance.
Results:
• The following Fiori packages are included in the stack.xml file:
s4h25 – Unit 5 Exercises
15
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 distr ibutors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from 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.
Coding Samples Any software coding or code lines/strings (“Code”) provided in this documentation are only examples and are not intended for use in a production system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules for certain SAP coding. SAP does not warrant the correctness or completeness of the Code provided herein and SAP shall not be liable for errors or damages cause by use of the Code, except where such damages were caused by SAP with intent or with gross negligence.
s4h25 openSAP: Unit 05: Maintenance Planner, Impact on add-ons and Business Functions
Exercise 1: Check stack.xml file whether any add-ons will be deleted during SUM execution
Exercise 2: Check in which version and on which system SAP FIORI FES FOR SAP S/4HANA 2020 will be installed
Exercise 3: Verify whether SAP Fiori
packages selected in the Maintenance Planner are included in stack.xml file
Logon Data ................................................................................................................... 3
Logon to system (SAP S/4HANA)................................................................................... 3
Exercise 1: Check stack.xml file whether any add-ons will be deleted during SUM execution4
Overview ....................................................................................................................... 4
Objective ....................................................................................................................... 4
Prerequisites ................................................................................................................. 4
Overview ....................................................................................................................... 7
Objective ....................................................................................................................... 7
Prerequisites ................................................................................................................. 7
Results: ......................................................................................................................... 9
Exercise 3: Verify whether SAP Fiori packages selected in the Maintenance Planner are included in stack.xml file .................................................................................................. 11
Overview ..................................................................................................................... 11
Objective ..................................................................................................................... 11
Prerequisites ............................................................................................................... 11
Prerequisites for the exercises
You need to have completed all exercises of Unit 01. You must have created your own instance of 1: “SAP ERP source system”
https://cal.sap.com/subscription?sguid=1a3556c0-0ee1-4a4c-8a5a- db08173df293
Logon Data Refer to the welcome page on the desktop of your SAP CAL instance.
User ID Password Client number
10steps2s4 <your SAP CAL instance master password>
100
https://cal.sap.com/subscription?sguid=1a3556c0-0ee1-4a4c-8a5a- db08173df293
4
ons will be deleted during SUM execution
Overview
Objective
Add-ons need to be supported for the target SAP S/4HANA stack. For SAP Add-ons and Partner Add-ons which are part of the SAP price list, the Maintenance Planner will check whether Add-ons identified in the source system are released for the target SAP S/4HANA stack or not. Add-ons which are not supported for the target SAP S/4HANA stack can possibly be deleted during the conversion. The result of your maintenance planner activities is summarized in a stack.xml file which will be consumed by the Software Update Manager (SUM).
NOTE: For all other Add-on types you need to get in touch with the 3rd party vendor to check the release status of the Add-on for the target SAP S/4HANA stack and you need to provide the SUM tool a corresponding archive or ACP file manually.
Prerequisites
For this exercise there is already a stack.xml file available on the remote Microsoft Windows desktop of your CAL instance. Please don’t change this stack.xml file and don’t use it for any other exercise or purpose. For Unit 06 a separate stack.xml file will be provided.
Exercise Description In this exercise you will verify in the stack.xml file whether the Maintenance Planner found any Add-on in the source system which is not released for the target S/4HANA stack and which will be deleted during SUM execution. You will perform the following tasks:
• Find and open the stack.xml
• Search for Add-on information in the stack.xml file
• Check whether any Add-on will be deleted during SUM execution
s4h25 – Unit 05 Exercise 1
5
What to Do What You Will See
1. Activate your instance of SAP CAL solution 1 and log on to RDP, Windows Remote Desktop. User: Administrator Password: <your instance master password for CAL solution1>
2. Right click on the MP_Stack_S4HAN A_2020_FPS00.xml file which you can find on the remote Microsoft Windows desktop and open it using Internet Explorer
s4h25 – Unit 05 Exercise 1
6
3. Browse through the MP_Stack_S4HAN A_2020_FPS00.xml file content and look out for the tag <to- be-deleted>. Within this tag you will find further information about add-ons to be deleted. For each such add-on you can find a tag called <product>.
4. Either continue directly with exercise 2 or suspend your instance of SAP CAL solution 1. Re- activate it once you continue with exercise 2. This is important to save cost.
Results:
s4h25 – Unit 05 Exercise 2
7
be installed
Objective
When planning a system conversion to SAP S/4HANA the Maintenance Planner offers the possibility to deploy additional systems, e.g. a SAP Fiori Frontend Server can be co- deployed directly on the converted S/4HANA system – the so called embedded deployment option for SAP Fiori.
According to your selections during the planning activities the Maintenance Planner will not only offer the required software archives for download but also include the “deployment instructions” into the stack.xml file which will be consumed by the Software Update Manager (SUM).
Prerequisites
For this exercise there is already a stack.xml file available on the remote Microsoft Windows desktop of your CAL instance. Please don’t change this stack.xml file and don’t use it for any other exercise or purpose. For Unit 06 a separate stack.xml file will be provided.
Exercise Description
In this exercise you will verify in the stack.xml file on which system the Fiori Frontend Server (FES) will be deployed and which version of SAP Fiori FES for S/4HANA will be installed. You will perform the following tasks:
• Find and open the stack.xml
• Identify which version and SP level of SAP Fiori FES for S/4HANA will be installed
• Check on which system the SAP Fiori Front-end server will be deployed
s4h25 – Unit 05 Exercise 2
8
What to Do What You Will See
1. Open a remote desktop connection and log on to your instance for SAP CAL solution 1. User: Administrator Password: <your instance master password for CAL solution1>
2. Right click on the MP_Stack_S4HAN A_2020_FPS00 file which you can find on the remote Microsoft Windows desktop and open it using Internet Explorer
s4h25 – Unit 05 Exercise 2
9
3. Browse through the MP_Stack_S4HAN A_2020_FPS00 file content and look out for the tag <sp- stack> in which SAP FIORI FES FOR S/4HANA is mentioned. Once you have found this element, you can identify the SP Level via the <caption> tag. The product’s release version itself is mentioned in the <version> element.
5. In the previously found <sp-stack> element continue to look out for the tag <sp-feature-stack>. Beyond, you will find another element called <application- system> where you can identify target system details via tags <sid> and <host>
6. Either continue directly with exercise 3 or suspend your instance of SAP CAL solution 1. Re- activate it once you continue with exercise 3. This is important to save cost.
Results:
• The following version and SP level of Fiori FES for S/4HANA will be installed:
s4h25 – Unit 05 Exercise 2
10
• The Fiori FES for S/4HANA will be installed on the following system:
s4h25 – Unit 05 Exercise 3
11
in stack.xml file
Objective
While defining the Fiori Frontend Server (FES) deployment type in the Maintenance Planner you can choose which Fiori packages shall be implemented on the FES.
According to your selections during the planning activities the Maintenance Planner will not only offer the required software archives for download but also includes the “deployment instructions” into the stack.xml file which will be consumed by the Software Update Manager (SUM).
Prerequisites
For this exercise there is already a stack.xml file available on the remote Microsoft Windows desktop of your CAL instance. Please don’t change this stack.xml file and don’t use it for any other exercise or purpose. For Unit 06 a separate stack.xml file will be provided.
Exercise Description
In this exercise you will verify in the stack.xml file whether all SAP Fiori packages which have been selected in the Maintenance Planner are listed in the stack.xml file and can be deployed during SUM execution. You will perform the following tasks:
• Find and open the stack.xml
• Check which Fiori packages are included in the stack.xml file
s4h25 – Unit 05 Exercise 3
12
What to Do What You Will See
1. Open a remote desktop connection and log on to your instance for SAP CAL solution 1. User: Administrator Password: <your instance master password for CAL solution1>
2. Right-click on the MP_Stack_S4HAN A_2020_FPS00 file which you can find on the remote Microsoft Windows desktop and open it using Internet Explorer
s4h25 – Unit 05 Exercise 3
13
3. Browse through the MP_Stack_S4HAN A_2020_FPS00 file content and look out for the tag <sp- stack> in which SAP FIORI FOR S/4HANA is mentioned. Once you found this element please verify if there is for each of the following products a <sp-feature-stack> element included:
• UI for SAP S/4HANA
• UI for MDG
• UI for TRV
4. You have completed all exercises of SAP CAL solution 1. If you want to check any further information in this system status, you can do so. Otherwise, it is no longer required, and we recommend that you terminate your SAP CAL solution 1 instance in order to save cost. Please note that an
s4h25 – Unit 05 Exercise 3
14
instance termination cannot be revoked, and you would be losing any configuration that you have done in that instance.
Results:
• The following Fiori packages are included in the stack.xml file:
s4h25 – Unit 5 Exercises
15
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 distr ibutors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from 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.
Coding Samples Any software coding or code lines/strings (“Code”) provided in this documentation are only examples and are not intended for use in a production system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules for certain SAP coding. SAP does not warrant the correctness or completeness of the Code provided herein and SAP shall not be liable for errors or damages cause by use of the Code, except where such damages were caused by SAP with intent or with gross negligence.