This blog is for Conversion from ECC6/EHP6 to S/4HANA 1809FPS0 – t3 of the conversion steps to be done in sequence below. Blog can also be referred for S/4HANA 1809FPS1. Maintenance Planner (MP) checks your components, add-ons, active business functions and industry solutions to ensure compatibility with the SAP S/4HANA 1809FPS0. This is a mandatory step that creates the stack file used during the t5 – SUM tool process. We will focus on Sandbox type system with co-deployed (embedded) gateway.
Download the Maintenance Planner User Guide for reference
Please find other blogs as follows:
S/4HANA SQUARE ONE
|NEW INSTALLATION||PART1 – MP||PART2 – Installation
||PART3 – BP Activation
||PART4 – Fiori Activation|
|S/4HANA 1809||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0|
||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0|
||fps2 fps0||fps2 fps0||fps2 fps1 fps0
|S/4HANA 1511||fps2 fps1|
Please login to Maintenance Planner to access system assigned to your S-user. Please ensure landscape data is uploaded to SAP support portal via LMDB of SAP Solution Manager. The system that you are converting has to be defined in OSS under your customer ID. The diagram below shows the Maintenance Planner cloud service and how it integrates with Customer system.
System data is uploaded to the Customer Profile via SLD and LMDB; in the Maintenance Planner changes are defined and stack.xml and download basket are prepared. Consuming tools are Software Provisioning Manager Software (SWPM), Software Update Manager (SUM). etc.
From LMDB the data is uploaded to customer profile in SAP support portal using Solman daily job – Landscape Fetch. If there is issue in replicating you may be asked to apply Note 2186164 – Problem in replicating systems to Maintenance Planner. Also apply min SPAM 69 in source system.
TIP: Maintenance planner separates data based on Customer Number. So ensure you use same customer number to define system in sapnet using the S-user id belonging to this same Customer number.
It is recommended to connect your system to Solution Manager but if it is not yet connected or if it is not updating Maintenance Planner (MP) correctly, please use this workaround to Add System in MP.
Logon to the S/4HANA backend system in client 000. Enter tCode SPAM -> Utilities -> Generate system info XML -> download file.If the above menu option is not available, run report RSLANG20 as per Note 2645566 – Option SPAM->Utilities->Generate System info XML is missing
Logon to Maintenance Planner, Explore Systems
Click on (1) Add System and choose file systeinfo_<SID>.xml and confirm upload
Your system should be available in Maintenance Planner as shown above (2) E6D.
TIP: For Central HUB deployment follow the above steps to Add the Front End Server to Maintenance Planner. However it is recommended to install embedded Fiori Front End.
Click on E6D System above. If the status of Verify is ERROR you will have to click and answer questions that come up.and then Save/Activate. Please click on Plan below:
TIP: In case your system is at a stack level below minimum, DMO/SUM tool will stop with error at PREP_INPUT_CHECK/SUMCHK. The release note 2625407 has details on minimum netweaver stack level required. The stack.xml should be created only after this.
We will create stack.xml. In Maintenance Planner click on tile Plan for SAP S/4HANA.
Select Convert Existing ERP system to SAP S/4HANA System.
Select the Existing ERP system E6D, Target version S/4HANA 1809, Target stack 01 (01/2019) FP and select Target Product Instances.
In the next screen please select Additional Systems. It is recommended to select Fiori FrontEnd Server Co-deployed with Backend. Click on Next.
You may get messages for different types of messages as shown below and may not be able to proceed further only after showstopper issues are resolved. Some may require OSS message to be opened.
TYPE 1: ADD-ONS
TYPE 2: UNINSTALLABLE ADD-ONS
For Uninstalling Add-Ons please refer Note 2011192 – Uninstallation of ABAP add-ons The individual Add-on notes are indicated above.
TYPE 3: BUSINESS FUNCTIONS ALWAYS OFF IN 1809
Please refer Note 2240359 – SAP S/4HANA: Always-Off Business Functions There are attachment files with details of Business Functions for every S/4HANA release.
The RULE is if in the Source system the Business Function is ON and in the Target system the Business Function is Always off then it is a showstopper and Conversion is not possible.
For Business Functions always ON please refer Note 2240360 – SAP S/4HANA: Always-On Business Functions
TYPE 4: BUSINESS FUNCTIONS DELETED BY TOOL
The Business Function LOG_EHS_PSS_CONC4PSS would be deleted during the upgrade. You may also like to check if Note 2369043 – SFW: S/4HANA 1610 installations with inconsistent SFW_ACTIVE_B2 content applies.
TYPE 5: 3RD PARTY COMPONENTS
TYPE 6: INDUSTRY SOLUTIONS
Please refer SAP Note 2214213 for supported industry solutions
TYPE 7: COMPONENTS NOT CHECKED
The above provides information is provided at the end, if the system has JAVA technical system connections.
If there were no showstoppers, you will be able to proceed …
Select Linux on x86_64 64 bit, Confirm Selection
Click on Stack Ind files NON-ABAP below
Deselect the languages not applicable as below and click on Next.
TIP: Before you click on Push to Download Basket, in the next screen, you may like to empty the download basket for your S-000 user so that any files added to the download basket are meant for this task and will help to ensure that only the required files are included.
In the next screen click on Download Stack XML, Download Stack Text File, Download PDF and Export to Excel to download the files to your desktop. Out of these you will have to ftp the stack.xml file to the server. It will look something like this – MP_Stack_2000540583_20181011_.xml
In the pdf file downloaded above, in the Planned Changes section there is a link provided that takes you directly to Service Marketplace to download the media.
TIP: After the sandbox upgrade, for upgrading the landscape please download stack.xml for entire landscape – DEV, QAS, PROD, etc as Maintenance Planner may have slight changes over time.
Download all the media into /sapmedia/download. You need the files below for the installation, please check if these are in download folder: SUM20SP03_1-80002456.SAR – or latest version of Software Update Manager.
TIP: To save time needed for scanning files, move files S4HANAOP103_LOAD* to a separate folder like /sapmedia/1809_EXP.
OTHER FILES NEEDED:
In addition you will require file crlbag.p7s from https://tcs.mysap.com/crl/crlbag.p7s
When uploading this file to media please include the stack.xml file as this is not included in download.
TARGET DATABASE (HDB):
You need HANA database (min SPS03 Rev 33 for fps0 and rev 36 for fps1)please download the files below from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDITION => SAP HANA DATABASE 2.0
You also need to download latest version of the HANA client from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDITION => SAP HANA CLIENT 2.0
If you want to install LiveCache you will require the HANA database LCAPPS plugin from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDIT 1.0 => HANA LCAPPS => SAP HANA LCAPPS 1.00
Download all the media and separate the following into separate directories for convenience under /sapmedia (min rev 33 for fps0 and min rev 36 for fps1)
SOURCE DATABASE HDB:
You may have to upgrade database to min HANA 2 SPS3 Rev33. May be a 2 step upgrade..
Ref Note 2372809 – Guideline for Upgrading a SAP HANA 1.0 to SAP HANA 2.0 System
Check which plugins are installed in HANA Database using studio, Administration=> Overview.
TIP: In case the HANA database has AFL plugin installed you will need the corresponding AFL plugin file, download it together. If you download later on, and the available download for HANA server changes to a higher patch even within rev 33, you cannot just download AFL available at that time when AFL is at available at higher level. It is recommended to download the needed plugins at same time. Also evaluate the need for plugins and uninstall using hdblcm of the currently installed release before upgrade if not needed.
SOURCE DATABASE DB6 (DB2 FOR LINUX, UNIX AND WINDOWS):
Upgrade to DB6 version 10.5 FP8 or higher as per Note 2644872
SOURCE DATABASE ORA:
Upgrade to Oracle version 12 or higher as per Note 2644872
SOURCE DATABASE MAXDB:
Upgrade to SAP MaxDB version 7.9.08.32 or higher as per Note 2644872
SOURCE DATABASE MSS:
Upgrade to MS SQL Server 2012 or higher as per Note 2644872
SOURCE DATABASE ASE:
Upgrade to SAP ASE Version 16.0 SP02 patch level 07 or higher as per Note 2644872
Please refer Product Availability Matrix for all other database types
The Development, Quality, and Production systems are converted at different times. So the stack file can have slightly different component levels although same stack level is selected. So output the stack.xml for the Quality and Production System at same time and freeze the landscape for adding components.
The option of System Track does not work for System Conversions and Upgrade and should not be used..
COMPONENT FOR INCIDENTS:
You can open OSS messages using component BC-UPG-MP
Thank you. Hope you enjoyed the blog !
Product Expert – S/4HANA