If you’re planning an upgrade to SAP S/4HANA, the SAP Readiness Check is a valuable tool to help you assess your system’s current state and identify any potential issues before the upgrade.
An accurate Readiness Check analysis starts with collecting important system information—such as usage statistics, custom code analysis, and configuration details.
This information is gathered using data collectors, which are ABAP-based tools that extract relevant data from your SAP system.
To set up the data collectors, refer to the SAP Notes outlined in the section below for step-by-step instructions.
Step 1: System preparation
Before implementing the required SAP Notes for the data collectors, make sure the following Notes are already applied in their latest versions:
SAP Note 1668882 – Note Assistant: Important notes for SAP_BASIS 730,731,740,750,751,752,753,754,755,756,757,758SAP Note 2971435 – SNOTE – Delta calculation issue when ‘mod unit’ positions are changed
These Notes help ensure your system is up to date and minimize the risk of errors during setup.
To make the implementation process easier, you can use the Note Analyzer tool available in the Note Assistant. For instructions and the input file, refer to SAP Note 3365856 – Note Analyzer Input File for SAP Readiness Check for SAP S/4HANA upgrades.
2758146SAP Readiness Check FrameworkSV-SCS-S4RRC_COLLECT_ANALYSIS_DATA
If SAP Note 2310438 has been implemented previously, it must be reverted prior to implementing SAP Note 2758146.
2399707Simplification Item Relevance & Compatibility ScopeCA-TRS-PRCKTMW_RC_SITEM_DATA_COLL
Enables simplification item relevance, compatibility scope analysis, and target S/4HANA version selection in RC_COLLECT_ANALYSIS_DATA. Implementation is mandatory. SAP Note 2502552 and the consistency check from this note are optional but recommended.
2903677Effort Drivers for Simplification ItemsCA-TRS-PRCKTMW_RC_EFD_DATA_COLL
This SAP Note offers the ability to include the effort driver analysis for simplification items with the initial effort ranking of Potentially High. The result is that effort ranking for some simplification items could be recalculated based on the scope and complexity of the system being analyzed.
2502552Consistency Check for Simplification ItemsCA-TRS-PRCKTMW_RC_SITEM_DATA_COLL
This SAP Note enables the optional data collection process for the consistency check. If you opt to include this data in your analysis, please ensure that you always use the latest version of this SAP Note. It is an addition to SAP Note 2399707. You must read and implement SAP Note 2399707 first and follow all steps, including the implementation of related SAP Notes listed in SAP Note 2399707.
3061414Integration AnalysisSV-SMG-MON-BPM-DCM–
This SAP Note details the steps required to enable successful execution of the Integration check data collectors. The check results provide insight into interfaces that could be impacted as part of an SAP S/4HANA upgrade project and provides guidance on mitigating the impact.
Please note that the data collector for this extended analysis is delivered starting with version 56 of SAP Note 2758146. SAP Note 3061414 only outlines the steps necessary for successful execution of the check, including required prerequisite SAP Notes.
2827612Innovation Potential DashboardSV-SCS-S4RTMW_RC_INNOVA_DATA_COLL
This SAP Note is responsible for enabling the optional Innovation Potential analysis, which populates the Innovation Potential dashboard with guidance on possible areas for future innovation based on current system usage statistics.
If the ST-PI component version in the landscape is less than or equal to ST-PI 2008_1_700 SP27, ST-PI 2008_1_710 SP27, or ST-PI 740 SP17, you need to implement the SAP Note 2827612 to enable innovation potential sub check.
2781766Custom Code Analysis via ATCBC-DWB-CEX–
Requires ATC setup and variant S4HANA_READINESS. See SAP Notes 2436688 and 3293011.
Step 2: Necessary authorizations
The user who is used to schedule the data collectors must have the following authorization:
Authorization object S_PROGRAM with values P_GROUP = RC_COLL and P_ACTION = SUBMIT, BTCSUBMIT, VARIANT.
The user ID used for scheduling the data collector for Custom Code Analysis must have the following authorizations:
Authorization object S_Q_ADM with values ACTVT = Add or Create (01), Change (02), Execute (16) and ATC_OBJTYP = Check run (01), Configuration (04)Authorization object S_Q_GOVERN with values ACTVT = Delete (06), Confirm (31) and ATC_OTYPGO = Exemption (01)
Step 3: Data Collection
Launch the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA).Choose Schedule Analysis to schedule the master job to collect data.Select the Download Analysis Data option in the data collection report once the collection process completes.Optional: Review the data collected in the compressed file.Optional: Alter the data collected as required to address any potential data protection concerns and then repackage the contents.Optional: Check the XML file content via the browser.
Step 4: Custom Code Analysis (Recommended)
Via the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA) in a non-productive system
Launch the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA).Choose the target release, select the Custom Code Analysis check, and deselect any other checks.Choose Schedule Analysis to schedule the master job to collect data.Select the Download Analysis Data option in the data collection report once the collection process completes.Choose Update Analysis at the top of the dashboard view to add the ABAP test cockpit export to the SAP Readiness Check analysis.
Note: The custom code analysis results of a non-production system can be uploaded to an existing SAP Readiness Check analysis created for a production system.
Manually via the ABAP Test Cockpit
Schedule an ABAP test cockpit run using the S4HANA_READINESS variant for the current product version (to create a baseline).Using the results from the previous step, maintain the baseline to exempt the findings. You can do this within the Manage Results screen in the ABAP Test Cockpit by selecting the relevant results and following the dropdown menu option: Maintain Baseline -> Add Selected Results To -> Exempt Findings.Schedule a second ABAP test cockpit run using the S4HANA_READINESS variant for the selected target release, ensuring the Consider Baseline setting is enabled.Export the results of the second ABAP test cockpit run by selecting the context menu option Export to -> File for SAP Readiness Check in the ABAP test cockpit result browser.Choose Update Analysis at the top of the dashboard view to add the ABAP test cockpit export to the SAP Readiness Check analysis.
Additional information:
To learn more about how to use SAP Readiness Check for S/4HANA upgrades, please refer to SAP Note 3059197 – SAP Readiness Check for SAP S/4HANA upgrades.
Â
​ If you’re planning an upgrade to SAP S/4HANA, the SAP Readiness Check is a valuable tool to help you assess your system’s current state and identify any potential issues before the upgrade.An accurate Readiness Check analysis starts with collecting important system information—such as usage statistics, custom code analysis, and configuration details.This information is gathered using data collectors, which are ABAP-based tools that extract relevant data from your SAP system.To set up the data collectors, refer to the SAP Notes outlined in the section below for step-by-step instructions.Step 1: System preparationBefore implementing the required SAP Notes for the data collectors, make sure the following Notes are already applied in their latest versions:SAP Note 1668882 – Note Assistant: Important notes for SAP_BASIS 730,731,740,750,751,752,753,754,755,756,757,758SAP Note 2971435 – SNOTE – Delta calculation issue when ‘mod unit’ positions are changedThese Notes help ensure your system is up to date and minimize the risk of errors during setup.To make the implementation process easier, you can use the Note Analyzer tool available in the Note Assistant. For instructions and the input file, refer to SAP Note 3365856 – Note Analyzer Input File for SAP Readiness Check for SAP S/4HANA upgrades.2758146SAP Readiness Check FrameworkSV-SCS-S4RRC_COLLECT_ANALYSIS_DATAIf SAP Note 2310438 has been implemented previously, it must be reverted prior to implementing SAP Note 2758146.2399707Simplification Item Relevance & Compatibility ScopeCA-TRS-PRCKTMW_RC_SITEM_DATA_COLLEnables simplification item relevance, compatibility scope analysis, and target S/4HANA version selection in RC_COLLECT_ANALYSIS_DATA. Implementation is mandatory. SAP Note 2502552 and the consistency check from this note are optional but recommended.2903677Effort Drivers for Simplification ItemsCA-TRS-PRCKTMW_RC_EFD_DATA_COLLThis SAP Note offers the ability to include the effort driver analysis for simplification items with the initial effort ranking of Potentially High. The result is that effort ranking for some simplification items could be recalculated based on the scope and complexity of the system being analyzed.2502552Consistency Check for Simplification ItemsCA-TRS-PRCKTMW_RC_SITEM_DATA_COLLThis SAP Note enables the optional data collection process for the consistency check. If you opt to include this data in your analysis, please ensure that you always use the latest version of this SAP Note. It is an addition to SAP Note 2399707. You must read and implement SAP Note 2399707 first and follow all steps, including the implementation of related SAP Notes listed in SAP Note 2399707.3061414Integration AnalysisSV-SMG-MON-BPM-DCM–This SAP Note details the steps required to enable successful execution of the Integration check data collectors. The check results provide insight into interfaces that could be impacted as part of an SAP S/4HANA upgrade project and provides guidance on mitigating the impact.Please note that the data collector for this extended analysis is delivered starting with version 56 of SAP Note 2758146. SAP Note 3061414 only outlines the steps necessary for successful execution of the check, including required prerequisite SAP Notes.2827612Innovation Potential DashboardSV-SCS-S4RTMW_RC_INNOVA_DATA_COLLThis SAP Note is responsible for enabling the optional Innovation Potential analysis, which populates the Innovation Potential dashboard with guidance on possible areas for future innovation based on current system usage statistics.If the ST-PI component version in the landscape is less than or equal to ST-PI 2008_1_700 SP27, ST-PI 2008_1_710 SP27, or ST-PI 740 SP17, you need to implement the SAP Note 2827612 to enable innovation potential sub check.2781766Custom Code Analysis via ATCBC-DWB-CEX–Requires ATC setup and variant S4HANA_READINESS. See SAP Notes 2436688 and 3293011.Step 2: Necessary authorizationsThe user who is used to schedule the data collectors must have the following authorization:Authorization object S_PROGRAM with values P_GROUP = RC_COLL and P_ACTION = SUBMIT, BTCSUBMIT, VARIANT.The user ID used for scheduling the data collector for Custom Code Analysis must have the following authorizations:Authorization object S_Q_ADM with values ACTVT = Add or Create (01), Change (02), Execute (16) and ATC_OBJTYP = Check run (01), Configuration (04)Authorization object S_Q_GOVERN with values ACTVT = Delete (06), Confirm (31) and ATC_OTYPGO = Exemption (01)Step 3: Data CollectionLaunch the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA).Choose Schedule Analysis to schedule the master job to collect data.Select the Download Analysis Data option in the data collection report once the collection process completes.Optional: Review the data collected in the compressed file.Optional: Alter the data collected as required to address any potential data protection concerns and then repackage the contents.Optional: Check the XML file content via the browser.Step 4: Custom Code Analysis (Recommended)Via the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA) in a non-productive systemLaunch the SAP Readiness Check data collection report (RC_COLLECT_ANALYSIS_DATA).Choose the target release, select the Custom Code Analysis check, and deselect any other checks.Choose Schedule Analysis to schedule the master job to collect data.Select the Download Analysis Data option in the data collection report once the collection process completes.Choose Update Analysis at the top of the dashboard view to add the ABAP test cockpit export to the SAP Readiness Check analysis.Note: The custom code analysis results of a non-production system can be uploaded to an existing SAP Readiness Check analysis created for a production system.Manually via the ABAP Test CockpitSchedule an ABAP test cockpit run using the S4HANA_READINESS variant for the current product version (to create a baseline).Using the results from the previous step, maintain the baseline to exempt the findings. You can do this within the Manage Results screen in the ABAP Test Cockpit by selecting the relevant results and following the dropdown menu option: Maintain Baseline -> Add Selected Results To -> Exempt Findings.Schedule a second ABAP test cockpit run using the S4HANA_READINESS variant for the selected target release, ensuring the Consider Baseline setting is enabled.Export the results of the second ABAP test cockpit run by selecting the context menu option Export to -> File for SAP Readiness Check in the ABAP test cockpit result browser.Choose Update Analysis at the top of the dashboard view to add the ABAP test cockpit export to the SAP Readiness Check analysis.Additional information:To learn more about how to use SAP Readiness Check for S/4HANA upgrades, please refer to SAP Note 3059197 – SAP Readiness Check for SAP S/4HANA upgrades.   Read More Technology Blog Posts by SAP articlesÂ
#SAP
#SAPTechnologyblog
