New Precheck for SAP S/4HANA 1709 Conversion

In this blog post I will briefly review both old and new conversion pre-check reports, their implementation and execution aspects.

As of the SAP S/4HANA release 1709, the conversion pre-check report R_S4_PRE_TRANSITION_CHECKS, originally available with SAP note 2182725, has been replaced with a report /SDF/RC_START_CHECK, delivered as a part of the SAP simplification item check. The old conversion pre-check, delivered with the SAP note 2182725, is still valid for SAP S/4HANA releases 1511 and 1610. Depending on the target release version, SUM calls for either the old or new version of the conversion pre-check.

The conversion pre-check covers the most important areas of the system to be transitioned to SAP S/4HANA. SUM will not allow system conversion in case of any error or abortion messages. You have to resolve these issues, as well as review all warning messages, before you can proceed with the system conversion to SAP S/4HANA.

R_S4_PRE_TRANSITION_CHECKS – how the old report works

The older ABAP check report R_S4_PRE_TRANSITION_CHECKS is delivered with the SAP note 2182725 together with further 25 notes listed in the description of the head note. It is still valid and should be used if your target S/4HANA release version is 1511 or 1610.

The notes implementation doesn’t require any additional activity in the system and check could be executed once implementation has been completed. Once executed, you can review the results in the on-line mode. The simulation mode doesn’t require stack.xml file available, so you could run the check before you start the actual SAP S/4HANA conversion project. When executed in client 000, the check shows results for all clients in the system.

Results for all software components are displayed in bulk together. It is possible to filter the results by the message category – success, warning, error and/or abortion. For larger systems, you can expect several thousand messages in the output.

SDF/RC_START_CHECK – what comes with the new report

The newer version of the pre-conversion check is delivered with the SAP note 2502552, which has to be implemented on top of the SAP note 2399707 which delivers the original version of the S/4HANA simplification item check report /SDF/RC_START_CHECK. When launched, the report will inform you if any updates are available, so you could install by the note re-implementation.

Once implemented, you should start with the simplification item check for the target release version of the SAP S/4HANA. Once the simplification item check has been executed, you may proceed with the conversion pre-check by executing consistency check for all or selected items only. The pre-check results are displayed next to the relevance field. After you have executed both checks for the first time, you can display the last check results at any time without executing the check again.

Technically, the contents of the consistency check are similar to the older R_S4_PRE_TRANSITION_CHECKS report. /SDF/RC_START_CHECK report gives you a list of the same messages, check IDs and reference notes. Comparing to the older report, it shows diagnosis for simplification items relevant for your conversion, it doesn’t require separate simplification item check anymore, as well as it allows pre-check results output per individual simplification item.

On the implementation side, the advantage of the newer /SDF/RC_START_CHECK report is that the simplification item check and conversion pre-check are delivered with two single SAP notes, so updates could be easily implemented. In comparison, the older R_S4_PRE_TRANSITION_CHECKS report is delivered with 26 main notes, which may bring over 50-80 notes on your system, when implementing them. It may also cause some complications, when trying to update it or part of it.

Another important difference on the implementation side comes from the requirement of having SAP Note Transport-based Correction Instructions (TCI) enabled on the system you are trying to analyze. TCI cannot be implemented using the Note Assistant. Instead, you would require BASIS specialist involvement.

The implementation of the TCI is explained under the note reference 2187425 and comes with some other corrections listed in the note 2502552.


Once you have implemented and executed the conversion pre-check report, based on the report output, you may proceed with the preparation activities for your SAP S/4HANA conversion. Run the report again when the required preparation activities have been completed, to make sure you have no more pre-check error and/or abortion messages preventing you from the system conversion. Please keep in mind, that conversion pre-check is only one of required activities on your road to SAP S/4HANA.

In case you have any questions or would to have something added or adjusted, please leave your comments and ideas below the blog in the comments section.

webinar sap s/4hana datavard near-zero downtime

Leave a Reply

Your email address will not be published. Required fields are marked *