Introduction

In previous blog of S/4HANA adoption we learnt about what all options to adopt the S/4HANA and started discussing about the option of system conversion.


As discussed earlier, the system conversion option is available for such customer who wants to convert their current system into an SAP S/4HANA system


Let’s quickly go over the high level plan for S/4HANA conversion project as shown below,


/wp-content/uploads/2016/06/1_973058.jpg

Maintenance Planner:

The first step in S/4HANA conversion is to analyse the source system using the Maintenance planner tool.


When you open the SAP Maintenance Planner for your system landscape you will see below screen with the list of available systems under “Explore Systems”.


/wp-content/uploads/2016/06/2_973059.jpg


Select the system from the list which you are planning for S/4HANA conversion


/wp-content/uploads/2016/06/3_973060.jpg


In this case I am selecting the system EC1 which got some errors in verification and data sync with Solution Manager


The sync errors are resolved by ignoring the software components as these components are not present in my source system and can be ignored


/wp-content/uploads/2016/06/4_973064.jpg


/wp-content/uploads/2016/06/5_973065.jpg

/wp-content/uploads/2016/06/6_973066.jpg


After rectifying all the errors my system is ready for planning the S/4HANA conversion


/wp-content/uploads/2016/06/7_973067.jpg

Start the Planning activity as shown below,


/wp-content/uploads/2016/06/8_973068.jpg


/wp-content/uploads/2016/06/9_973069.jpg

This is the benefit of running maintenance planner at the start of S/4HANA conversion project. At start of the project you will come to know if your system is ready for conversion or not and what all things which needs to be completed before system made ready for S/4HANA conversion


As per below error screen, there are certain add-ons and business functions available in my system which are not supported by S/4HANA and these issues needs to be addressed before we can select the S/4HANA conversion


/wp-content/uploads/2016/06/10_973073.jpg


Check SAP note 2214409 and 2011192 for further details on how to handle the non-supported add-ons for S/4HANA


I am able to resolve all the dependency and made sure the business functions information is available in solution manager so that it will be selected during the conversion process


After rectifying the above error the system is ready for the S/4HANA conversion project


It’s very important to resolve the add-on errors as all the add-on’s are not supported by S/4HANA. Also, this is very important step as part of early planning in S/4HANA conversion projects as it will give clear understanding in terms of if your environment is eligible for conversion scenario or you need to go for new Implementation and then do the data migration/conversion


Note: Solution manager plays very vital role in S/4HANA conversion projects and it’s very important to have Solution manager properly setup and right data is sync between source system and solution manager


Select plan a conversion to SAP S/4HANA option to start the process and download all required media files for S/4HANA conversion


/wp-content/uploads/2016/06/11_973074.jpg

/wp-content/uploads/2016/06/12_973075.jpg

This is the 1st step in your S/4HANA conversion project.


Once the maintenance planner is successfully run we need to go to the second and important step of code and compatibility check.


Code and compatibility check phase is sub divided into 3 different steps, which we will learn in next blog of Code and Compatibility Checks!


Reference Links


The System Conversion to SAP S/4HANA, on-premise edition 1511 – Technical procedure and semantic adaption tasks


SAP S/4HANA Flipbook

SAP Business Suite 4 SAP HANA

https://websmp203.sap-ag.de/~sapidb/011000358700000309032009E/

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Frank Wagner

    Hello Sushil,

    thanks for your blog!

    I just wanted to point your attention to some new features of the current Maintenance planner. Here we have on the entry screen a new tile “Plan for SAP S/4HANA – Installation / Conversion”. With that it is possible to plan your way to SAP S/4HANA more specifically. Accordingly the screens look now a bit different.

    Maintenance Planner – SAP Help Portal Page

    Kind Regards,

    Frank

    (0) 
  2. Ahmad Tarmizee Kamarul Zaman

    Hello Sushil,

    Nice blog. I have some question :

    1) What was the action taken by you when refer to note 2214409 ?

    2) What was the target shipment level for your S4HANA conversion ?

    Kind Regards
    Tarmizee

    (0) 
    1. Sushil Aher

      Hi Ahmad,

      The error which I got was basically for FIORI apps which were installed in my source system. You need to remove these FIORI apps in order for maintenance planner to work properly.

      Please refer SAP notes 2034588, 2200415, 2011192 for more information

      My target version was initial shipment for S/4 1511

      (0) 
  3. Ahmad Tarmizee Kamarul Zaman

    Dear All,

    It seems SAP updated the Maintenance Planner page with additional menu “Plan for SAP S/4HANA” that can be used for install and conversion to S/4HANA. New user guide also available.

    Note 2240359 and blog SAP S/4HANA, on-premise edition 1511 FPS2: Remarks regarding Business Functions also much helpful.

    Best Regards

    Tarmizee

    (0) 
  4. Sunil Maheshwari

    Hello Sushil,

    I would to know if Maintenance planner can be used to evaluate  source system and also to evaluate Pre transition checks and custom code check for migration of ECC To S4HANA 1605 Finance.

    As I understand Maintenance Planner,  Pre transition checks and custom code check analyzer is for migration from ECC To S4HANA EM.

    Best Regards,

    Sunil Maheshwari

    (0) 
    1. Frank Wagner

      Hello Sunil,


      with the Maintenance Planner you can plan your software update to target releases (for example S/4HANA EM or S/4HANA Finance). In The S/4HANA context the Maintenance Planner is checking supported Add-Ons and supported Busienss Functions.

      The Pre-Checks and the Custom Code Checks are separate conversion steps and not executed within the Maintenance Planner. More or less they can be executed on Business Suite start release


      For the first version of S/4HANA (SAP S/4HANA Finance) the logic is a bit different. Here the SAP S/4HANA Finance related pre-checks are part of the S/4 software delivery and executed on S4 Test system. As an outlook for 1610. Here we are planning to integrate the FIN specific steps better in the common logic.


      More Details:


      Best Regards,

      Frank

         

      (0) 

Leave a Reply