Skip to Content
Author's profile photo Sushil Aher

S/4HANA Conversion 2nd Step – Code and Compatibility Check


As discussed in previous blog the digital transformation path for S/4HANA has various steps and it’s very important to validate and pass thru each step of the road map to achieve the successful S/4 conversion project.

Just a recap to earlier blogs, in previous blog of S/4HANA – Path to Digital Transformation we learnt about what all options to adopt the S/4HANA and started discussing about the option of system conversion.

Note: 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

Below is the high level plan for the S/4HANA conversion program, we already covered the 1st step in the blog How to use Maintenance Planner for S/4HANA Conversion.


The 2nd step in the road map is to do the code and compatibility check.

The code and compatibility check has three sub tasks which are important from the conversion perspective

  1. Review the simplification list for SAP S/4HANA
  2. SAP S/4HANA conversion pre-checks
  3. Custom code analysis

Simplification List review

The simplification list for SAP S/4HANA is useful for the customers to understand the functional level details with S/4HANA and changes to the individual transactions, applications and solutions. Few of the functionality are combined, few of the functionality are made obsolete and some equivalent functionality is enabled with S/4HANA, some cases there is enhancement to the existing functionality.

The list is available with the required changes in PDF and XLS format for customer reviews for better planning and estimation for the S/4HANA conversion programs


The Simplification List is integrated with the custom code check tool. This tool provides a detailed report about where the custom code on your SAP Business Suite system does not comply with the scope and data structures of SAP S/4HANA

Note: The involvement of functional and technical team is very important in this phase of activities

The next step is the system pre-checks

Pre-checks are important to identify the required steps and make sure the system is compatible for the conversion process

The pre-checks are very important and should be completed before starting the next phase of activities and running the SUM tool. The output of pre-checks is the list of items which needs to be addressed before the actual conversion process is started.

Basically pre-check is ran twice on the overall process, first time as manual pre-check and second time during SUM execution. If there are errors in pre-check phase in SUM tool then the SUM tool will stop and conversion is aborted, due to this it is very important to run the pre-check as manual run ahead of time.

Note: It’s very important and mandatory to run maintenance planner before starting pre-checks phase. Please refer blog How to use Maintenance Planner for S/4HANA Conversion on how to run maintenance planner

Pre-check process

During the pre-check phase it’s important to implement the SAP note 2182725 and related notes in all the source systems which are in scope for the conversion (The note needs to be implemented in Sandbox, Dev, QA, Prod and any other systems which is part of conversion project)

The SAP notes contains a report, “R_S4_PRE_TRANSITION_CHECKS” which needs to be run manually in the source system to do the pre-check activity

Best Practices to follow for running the pre-checks:

  1. Make sure the manual activities as per SAP note 2182725 are completed. Import all the notes which are mentioned as part of manual activities
  2. Follow the sequence of runs for the report “R_S4_PRE_TRANSITION_CHECKS”
  3. Make sure to run the report in Simulation Mode (P_Test) mode
  4. All the errors which are reported as part of Check Class Consistency Check option should be fixed before you run the Pre-Transition Check Option
  5. Make sure to run the maintenance planner and have stack xml downloaded and kept at server level



In order to address all the pre-check errors you need to review various SAP notes and raise OSS message with SAP with individual components. For some of the issues, you need to upgrade individual components to certain supported version.

e.g: The ECC DIMP component needs to have minimum release 999 SP 99. Check the below SAP note

2310116 – Report R_S4_PRE_TRANSITION_CHECKS return errors on ECC-DIMP

The overall check result return code must be lower or equal to 4. Otherwise the Software Update Manager (SUM) will not be able to perform the conversion of your system.

Note: The involvement of Basis, ABAP technical and functional team is very important in this phase of activities

The next step in the conversion process is to do the custom code analysis

Custom Code Analysis

For the SAP system conversion to SAP S/4HANA, any modification/simplifications made to SAP objects need to be considered in your customer objects.

The Custom Code Migration work list helps to provide the details of all customer objects and provide the reference to simplified SAP objects and links to information about how to adopt these customer objects.

Few of the pre-requisite and requirement for custom code analysis:

  1. The source system version should be NW 7.0 to 7.40 which is called as SAP business suite system during conversion process
  2. Only ABAP stack with Unicode system
  3. To setup the custom code migration work list, you need to have separate NW 7.5 system against which the custom code analysis will be performed. This system is called as evaluation system
    1. To save some cost and time, you can utilize the evaluation system from SAP Cloud Appliance Library (CAL) hosted on AWS cloud as this is the temporary setup
  4. You have completed the maintenance planner tasks and pre-check tasks mentioned above

Please refer the below setup diagram which shows the required setup to run the custom code work list for migration


The custom code analysis is basically set of activities which need to perform with proper pre-requisites and sequence; at high level below are the steps which are explained in detail in the blog Custom Code Analysis Setup

Below are the high level steps for the custom Code Analysis Setup

  • Evaluation System Implementation: Implement the NW 7.5 ABAP stack
    • To save some cost and time, you can utilize the evaluation system from SAP Cloud Appliance Library (CAL) hosted on AWS cloud as this is the temporary setup
  • Download and Import Simplification database list into evaluation system
  • Implement SAP note 2185390: Custom Code Analyzer tool
  • Download and Import Custom Code Analyzer list from source system
  • Compare the custom code analyzer results against the simplification DB
  • Adapt the simplification items for diff applications

Note: In this exercise the ABAP development/technical team along with Basis team plays very critical role.

This is the 2nd step in your S/4HANA conversion project.

With this we have completed the S/4HANA Conversion – Code and Compatibility Check

The next step in the S/4HANA conversion road map is Source and Target System Checks

Reference Links:

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Monika Patel
      Monika Patel

      Thanks for great blog.
      One Question - in Pre-Check Report RUN of report R_S4_PRE_TRANSITION_CHECKS  is providing a STACK.xml (output of Maintainance planner run)  mandatory??

      When I tried running Report R_S4_PRE_TRANSITION_CHECKS  in one of our ECC system in Simulation MODE for Pre-Transition Check Option  with BLANK input in STACK.xml field , the report  did run & gave errors, warning along with green/cleared components.

      However I am wondering where would the report pick "Target" version from  -- from implemented SAP NOTE or from STACK.xml?

      The output  for ECC-DIMP is as below. The line "check-requires minimum target release....."  is the reason of above question

      48) Software component ECC-DIMP.
      The check class is CLS4H_ECC_DIMP (application component IS-A).
      The check requires the minimum target release S4CORE 100 SP 0000.
      Method GET_PREPROCESSING_CHECK_RESULT: execution time 5 seconds (= 0 minutes) - thereof ABAP execution time 4698
      milliseconds (= 5 seconds).