2968380 - SAP Readiness Check for SAP S/4HANA - troubleshooting guide

Issue

• Refer also to: 2951527 - Dropdown list empty for target release S/4HANA or BW/4HANA
• Keep in mind that Readiness Check report is supported for version upgrades, not for FPS or SP level updates.
• Example Scenarios:
• If your system is already on the latest version (ex. S/4HANA2023) there will be no available version to select as a target. The latest available version can be verified from the catalog content from https://me.sap.com/sic/overview with your S-User.
• If your system is on S/4HANA2020 version, you will not see subsequent SP levels from the target drop downlist for S/4HANA2020. Only the versions available for upgrade such as S/4HANA2021 or later will be available.

1. Implement the SAP Note 1668882 and 2971435 if they are missing.
2. De-implement SAP Note 2758146.
3. During de-implementation, if any of object of the SAP Note 2758146 is not deleted in the customer system, then delete those objects manually in SE24 or SE80.
4. Implement SAP note 2758146 again in the latest version.

Please see KBA 3221283  for the more detailed steps.

When implementing SAP Note 2758146, there are warning objects from SNOTE.

• Make sure to manually activate all the objects with yellow warning message to implement the objects in the latest version. As documented in SAP Note 2913617 - SAP Readiness Check for SAP S/4HANA
  
  If you’re updating the implementation of an SAP Note, you may see a screen indicating some of the objects already exist. We recommend selecting the checkbox in the Apply Changes column for those objects with a yellow triangle in the Status column. Otherwise, inconsistencies could occur with the implementation of the correction instructions.

When implementing SAP Note 2758146, there is an error "Name ana_sys_add_info.xsl is not unique, Name fui-site.css is not unique" or "Characteristics of object 'M_TEXT_P' not valid".

• 3308795 - Error message "Name <MIME objects> is not unique" or "Characteristics of object 'M_TEXT_P' not valid" happens when implementing SAP note 2758146 for S/4 HANA Readiness Check

Syntax error dump when executing program RC_COLLECT_ANALYSIS_DATA

Category               ABAP programming error

Runtime Errors         DBSQL_SQL_ERROR

Except.                CX_SY_OPEN_SQL_DB

ABAP Program           RC_COLLECT_ANALYSIS_DATA

Application Component  SV-SMG-CM

Short Text

SQL error "SQL code: 305" occurred while accessing table "DF14L".

• Implement SAP Note 2758146 version 114 or higher to fix this issue.

Syntax error dump when executing program RC_COLLECT_ANALYSIS_DATA

Category               ABAP programming error

Runtime Errors         XML_FORMAT_ERROR

Except.                CX_XSLT_FORMAT_ERROR

ABAP Program           TMW_RC_DOWNLOAD_ANALYSIS_DATA

Application Component  SV-SMG-CM

Short Text

The read XML document had an invalid format.

• Implement SAP Note 2758146 version 113 or higher to fix this issue.

RC report RC_COLLECT_ANALYSIS_DATA terminated with a runtime error DATA_OFFSET_NEGATIVE.

Category                     ABAP programming error
Runtime Errors             DATA_OFFSET_NEGATIVE
Except.                        CX_SY_RANGE_OUT_OF_BOUNDS
ABAP Program              /SSA/EIM
Application Component SV-SMG-MON-BPM

• 3006484 - RC_COLLECT_ANALYSIS_DATA ends with dump DATA_OFFSET_NEGATIVE

After implementing SAP Note 2332472 there is a syntax error Type "ABAP_BOOL" is unknown

• 3392898 - Fix syntax error of abap_bool in class CLS4SIC_SLL_CLS_COMCO

Syntax error dump when executing program RC_COLLECT_ANALYSIS_DATA

Category Installation error
Runtime Errors CALL_FUNCTION_NOT_ACTIVE
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC

Short Text
The function module is not active or does not contain any code.

Error analysis
An exception has occurred which is explained in more detail below. The
exception is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC' 

An attempt was made to execute the CALL FUNCTION statement in program
"RC_COLLECT_ANALYSIS_DATA". The name of the function module to be called is
"/SDF/FDQ_CHECK_PREREQUISITES".
""/SDF/FDQ_CHECK_PREREQUISITES" cannot be found in its function group though.

1. Execute transaction SE37.
2. Select Menu "Utilities" and choose "Repair Function Group".
3. Enter function group "/SDF/FDQ_ASSESSMENT" in the form field.
4. Execute.
5. When the repair procedure has been finished, reimplement SAP Note 2758146 in the latest version.
6. When implementing the SAP Note 2758146, it should be implement without any errors. If there are yellow warning objects, you have to activate all of them by manually ticking all boxes (refer to issue #3). This will ensure they are overwritten to the latest.

Syntax error dump when executing program RC_COLLECT_ANALYSIS_DATA

Category Installation error
Runtime Errors CALL_FUNCTION_NOT_ACTIVE
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC

Short Text
The function module is not active or does not contain any code.

Error analysis
An exception has occurred in class "CX_SY_DYN_CALL_ILLEGAL_FUNC"

An attempt was made to execute the CALL FUNCTION statement in program
"RC_COLLECT_ANALYSIS_DATA". The name of the function module to be called is
"/SDF/BPM_7X_S4RC20_GET_KPIS".
""/SDF/BPM_7X_S4RC20_GET_KPIS" cannot be found in its function group though.

• Follow the solution outlined in SAP Note 3205320 - Repair report for syntax errors preventing implementation of SAP Note 2745851 - Business Process Improvement Content for "SAP Readiness Check 2.0"

When scheduling RC_COLLECT_ANALYSIS_DATA it recommended to implement the SAP Note 2769657 which is now obsolete.

Message:

"Prerequisite up-to-date SAP Note 2769657 for interface is not installed"

• The message is likely due to a previous version of the readiness check having been displayed. This indicates that there were errors during the implementation/update of SAP Note 2758146. Therefore, De-implement the SAP Note 2758146 completely and re-implement it again afterwards in its latest available version.
  During the implementation you may face the situation documented as issue 3 under the General scope. Ensure to select the relevant checkboxes as described, respectively.
• For additional instructions on how to re-implement SAP Note 2758146, refer to KBA 3322169 - Error "The system is already a SAP S/4HANA system. This is not supported" when running the Readiness Check Report for S/4HANA upgrades

Category               ABAP programming error
Runtime Errors         RAISE_EXCEPTION
ABAP Program           RC_COLLECT_ANALYSIS_DATA
Application Component  SV-SMG-CM

Exception condition "SMDB_CONTNET_NOT_FOUND" triggered  

• The dump is caused because SUPPORT_PORTAL connection is not setup. This will cause SIC cannot be downloaded from SUPPORT_PORTAL. Manually download SIC content and upload in your system by referring to SAP KBA 2951527.

Category               ABAP programming error
Runtime Errors         SYNTAX_ERROR
ABAP Program           RC_COLLECT_ANALYSIS_DATA
Application Component  SV-SMG-CM

• This dump is caused by implementation errors with SAP Note 2758146.

• The resolution is provided in SAP KBA 2894402.

Issue

Error "The check could not be performed" in the Business Process Discovery tile when uploading RC_COLLECT_ANALYSIS_DATA analysis file to SAP for Me.

• Please implement the latest version of SAP Note 2745851
• Ensure your ST-A/PI version is 01V SP00 or later
• After rerunning the report if your error persists open a case with SV-SCS-S4R

Memory dump TSV_NEW_PAGE_ALLOC_FAILED in program /SSA/EKP or /SSA/EKF or /SSA/EKW.

•  2874082 - Readiness Check 2.0/BSR: memory dump TSV_NEW_PAGE_ALLOC_FAILED
  
  In most of KBAs above the solution it to remove a specific KPI from the list at the startscreen of RC_COLLECT_ANALYSIS_DATA. You might need to repeat this several times for different KPIs. In order to get more details about the removed KPIs, you can perform an analysis in ST13 TBI_REPORTS with limited selection criteria (i.e. selecting just one week of data, restricting selection only for some company codes, some plants, etc).
  Please refer to the guidelines in this KBA: 2197502 - BPMon: How to test & execute data collection manually in ST13: TBI_REPORTS
  If you do not want to remove the KPI because you really need to get this KPI in your report, or if you also get a dump in TBI_REPORTS (meaning you there is too much data in the system) you should perform archiving of the data before running the report again.

RC_COLLECT_ANALYSIS_DATA child job TMW_RC_BPA_DATA_COLL fails with either error PXA_NO_FREE_SPACE or TSV_NEW_PAGE_ALLOC_FAILED

• This error is related to memory dumps caused by large KPIs.
• The resolution steps are outlined in KBA 2818045.

Job RC_COLLECT_ANALYSIS_DATA or TMW_RC_BPA_DATA_COLL fails with an error_message. In the job log, you will find a line that indicates "ST-A/PI Release 01U_731 lower 01V."

• The minimum required ST-A/PI version is 01V. Please upgrade ST-A/PI version to 01V or higher and try again.

• In addition to implementing the latest version of SAP Note 2745851, there are recommended code corrections based on your ST-A/PI SP version. Please verify if they are implemented.

• We recommend to implement the newest version of ST-A/PI collective SAP Notes: 

  ST-A/PI Release	SAP Notes
  ST-A/PI 01V SP3	3393415 - ST-A/PI 01V SP3: Advance Corr. BP Analytics - PPIs for ERP 3404710 - Corrections for ST-A/PI 01V SP3 (framework) For HANA Systems in addition 3393435 - ST-A/PI 01V SP3: Advance Corr. BP Analytics - PPIs for ERP (S/4HANA)
  ST-A/PI 01V SP2	3321793 - ST-A/PI 01V SP2: Advance Corr. BP Analytics - PPIs for ERP 3345108 - Corrections for ST-A/PI 01V SP2 (framework) For HANA Systems in addition 3321856 - ST-A/PI 01V SP2: Advance Corr. BP Analytics - PPIs for ERP (S/4HANA)
  ST-A/PI 01V SP1	3261488 - ST-A/PI 01V SP1: Advance Corr. BP Analytics - PPIs for ERP 3270847 - Corrections for ST-A/PI 01V SP1 (framework) For HANA Systems in addition 3261489 - ST-A/PI 01V SP1: Advance Corr. BP Analytics - PPIs for ERP (S/4HANA)
  ST-A/PI 01V	3194251 - ST-A/PI 01V SP0: Advance Corr. BP Analytics - PPIs for ERP 3159166 - Corrections for ST-A/PI 01V SP0 (framework) For HANA Systems in addition 3194259 - ST-A/PI 01V SP0: Advance Corr. BP Analytics - PPIs for ERP (S/4HANA)

Syntax error dump when executing program RC_COLLECT_ANALYSIS_DATA

Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program /SDF/CL_S4RC20================CP
Application Component SV-SMG-SDD

Short Text
Syntax error in program "/SDF/CL_S4RC20================CP ".

Error analysis
The following syntax error was found in the program
/SDF/CL_S4RC20================CP :
"Method "ADDTOJSON" is not declared or inherited in class "/SDF/CL_S4RC"
"20". -"

• Please see KBA 3283120.

Error/issue/dump is triggered with child job TMW_RC_BPA_DATA_COLL.

Check the job log from SM37 for more information. Then follow the resolution of the respective symptom.

• 2897369 - Job TMW_RC_BPA_DATA_COLL canceling with message "Job also canceled due to process termination. See the system log"
• 2818045 - Memory dump in the job TMW_RC_BPA_DATA_COLL
• 2874082 - Readiness Check 2.0/BSR: memory dump TSV_NEW_PAGE_ALLOC_FAILED

Issue

• SAP KBA 3479180 SAP S/4HANA Readiness Check Financial Data Quality Child Job Long Running

In RC_COLLECT_ANALYSIS_DATA in an SAP ERP 6.0 system:

• The Scope Selection is missing "Financial Data Quality Check" (FDQ) as a selection option, even though required SAP Notes are implemented (i.e. SAP Note 2758146, SAP Note 2972792, RTCCTOOL report shows required FDQ Notes are implemented and in green status). 
  
  

• The option to select Expert Mode is also not available. 

• The Financial Data Quality Check is only supported for SAP ERP 6.0 systems (see SAP Note 2913617).
• The Financial Data Quality Check should not appear in the Scope Selection of an SAP S/4HANA Finance (SAP Simple Finance System).
• In the SAP ERP 6.0 system, de-implement and re-implement SAP Note 2758146 in the latest version.

Transport errors in program CL_RC_FDQ* when transporting finance notes in S/4HANA systems.

• 3333027 - Transport errors with SAP Note 2972792 in program CL_RC_FDQ*

Running RC_COLLECT_ANALYSIS_DATA having FDQ checks selected was canceled with a runtime error

Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Except.                CX_SY_REF_IS_INITIAL
ABAP Program           RAGS_RC_FDQ_HANDLER
Application Component  SV-SMG-DVM

Access using a 'ZERO' object reference is not possible.
 What happened?
     Error in the ABAP Application Program
     The current ABAP program "RAGS_RC_FDQ_HANDLER" had to be terminated because it
      has
     come across a statement that unfortunately cannot be executed.

• De-implement SAP Note 2758146 and re-implement again in the latest version. In case of issues see row below for how to deal with activation errors.

Job(s) TMW_RC_FDQ_DATA_COLL as well as parent job RC_COLLECT_ANALYSIS_DATA were canceled.

In the joblog you may find error message internal session terminated with a runtime error SAPSQL_PARSE_ERROR

For the runtime error a dump was written:

Category ABAP Programming Error

Runtime Errors SAPSQL_PARSE_ERROR
Except. CX_SY_DYNAMIC_OSQL_SEMANTICS
ABAP Program CL_RC_FDQ_FI_AA_MONITOR=======CP
Application Component SV-SMG-DVM

• 3186098 - Error in CL_RC_FDQ_FI_AA_MONITOR=======CP during job TMW_RC_FDQ_DATA_COLL

Financial Data Quality child job "TMW_RC_FDQ_DATA_COLL" cancels with message "Table BKPF is empty" & "Job canceled after system exception ERROR_MESSAGE".

• When table BKPF is empty, there is no data to analyze from FDQ perspective. This means there is no reason to activate the FDQ check, so execute the Readiness check analysis excluding the FDQ option. Keep in mind that the FDQ check should be scheduled in your active client, not in client 000. The table can also be checked from SE16 in the client you plan to execute the RC report.

Financial Data Quality tile is empty.

• Verify if configuration steps documented in SAP Note 2972792 are completed first. 
• If during the SAP Note 2972792 implementation there are yellow warnings from SNOTE they need to be manually activated to get the latest version of the code. 
• If the child job "TMW_RC_FDQ_DATA_COLL" finishes quickly with log message like "Buffered data less than 30 days..." delete the buffer by following below steps. This will delete the buffer and allow a fresh analysis for FDQ.
1. Execute RC_COLLECT_ANALYSIS_DATA
2. Select ONLY option "Financial Data Quality".
3. Click the button Delete Buffered Data for Selected Items. This deletion will only be applied to Financial Data Quality and other option will not be affected.
   
4. After deleting the buffered data start the FDQ analysis and upload the data to RC report. 

Issue

1. Delete old Sizing results with report /SDF/HDB_SIZING_CLEAN (refer to SAP Note 1872170)

2. Clear Buffer:

1. Run report RC_COLLECT_ANALYSIS_DATA in SE38

2. Select the checkbox for Hana Sizing

3. Click Delete Buffered Data for Selected Items button

3. Schedule job to collect data again and upload

The following message is displayed in the long text error message during the implementation of Note 3304656.

No queue calculation because of a missing maintenance certificate
Message No. TN808

Diagnosis
Attempted to define a queue that contains OCS Package SAPK61700QCPSAPAPPL delivered by SAP. This failed as no valid maintenance certificate was found in the system.

Procedure
Install a valid maintenance certificate and repeat the queue calculation.

Background Information
As of 2009, maintenance certificates are required to be able to install and maintain SAP software with the Add-On Installation Tool and Support Package Manager. These maintenance certificates can be requested with SAP Solution Manager and are distributed to the systems automatically.
For more information, see the SAP Support Portal under http://service.sap.com/maintenancecertificate and SAP Note 1240265.
Component SV-SMG-LIC is also available for reporting an problems or any further questions.

1. Renew the Maintenance Certificate following KBA 3485445 - TCI Note cannot be implemented due to no valid maintenance certificate.

Issue

• 2847830 - SAP Readiness Check 2.0 "add-on Compatibility" and "Active Business Functions" tiles are empty

Issue

• 2919704 - Background Job of Readiness Check terminates because of  error message being raised from underlying API's

• 2937003 - S/4 Hana Readiness Check for Business Partner gives an error after implementing SAP Note #2811183

Category ABAP programming error
Runtime Errors CALL_FUNCTION_NOT_FOUND
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC

Short Text
Function module "CVI_READINESS_CHECK" not found

What happened?
An attempt was made to call function module "
This cannot be found in the library though.

• Steps to enable Customer Vendor Integration have not been taken or the system does not have SAP_APPL
• Review the SAP Note 3010669 and perform the manual steps.