This blog is for Conversion from ECC6/EHP6 to S/4HANA - t3 of the conversion steps to be done in sequence below. Maintenance Planner (MP) checks your components, add-ons, active business functions and industry solutions to ensure compatibility with the SAP S/4HANA. 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.
Please login to Maintenance Plannerto 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.
TIP2: 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.
TIP3: 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. But in this case please ensure all Add-Ons and Business Functions are correctly recognized.
TIP4: 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.
PART 2: PLAN FOR S/4HANA
We will create stack.xml. In Maintenance Planner click on tile Plan for SAP S/4HANA.
TIP: The other way to try to do this is using tile Explore Systems and then select the instance. Please do not use this option as it is most likely the Front End Server will not be considered. Select Convert Existing ERP system to SAP S/4HANA System.
Select the Existing ERP system E6D, Target version of S/4HANA, Target stack FPS 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. If there is a showstopper message with Red exclamation, you may not be able to proceed further. You may have to create OSS ticket.
The REASON for this 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. However there are exceptions to this - few Business Functions as mentioned in Note 2240359 for example Business Function ISR_RETAIL_RMA.
The above WARNING message shows that the component is not checked. It also states that the technical system does not have java technical system connections.
If there were no showstoppers, you will be able to proceed ... Select Linux on x86_64 64 bit, Confirm SelectionYou have to also select the files for the Source OS/DB
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: SUM20SP08_1-80002456.SAR - or latest version of Software Update Manager.
TIP: To save time needed for scanning files, move files S4HANAOP104_LOAD* to a separate folder like /sapmedia/1809_EXP.
PART 3 - ADD 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 SPS04 Rev 44 for 1909 fps2 )please download the latest version 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) IMDB_SERVER20_48_0-80002031.SAR IMDB_CLIENT20_004_202-80002082.SAR IMDB_LCAPPS_2048_0-20010426.SAR
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.
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