Skip to Content
Technical Articles

SAP Note Simplification Item Check implementation problems

The SAP Note “2399707 – Simplification Item Check” is the feature note which helps customer to execute the simplification item check framework. Customer needs to implement this note before they run the check framework. Sometime the implementation has the problems. This post is focusing on some problems and show the solution to them.

 

1, The note context and system code are inconsistent

Symptom:

When you want to implement the new version of SAP Note 2399707, you always get the warning message for some objects as below:

“Not all corrections applied; see change display.

Some corrections already exist; see change display”

But after the note implemented with checked warning message, you also get the syntax error when you try to active all of objects. Or you got the run time error in ST22 when you run the check framework via SUM.

Sometime, the errors like:

  • /SDF/CL_RC_SIMPLE_CHK_DB=> PERFORM_CHECK: Field “LT_WHITELIST” is unknown
  • /SDF/CL_RC_MANAGER=>PERFORM_CONSISTENCY_CHECK: Field “LS_PPMS_PROD_VER_TARGET” is unknown

Affected objects:

  • /SDF/GEN_FUNCS_S4_RELEVAN_CHK
  • /SDF/CL_RC_CHK_UTILITY=>GET_TEXT_STR
  • /SDF/CL_RC_CHK_UTILITY=>SITEM_SKIP_STAT_UPDATE_SINGLE
  • /SDF/CL_RC_MANAGER=>PERFORM_CONSISTENCY_CHECK
  • /SDF/CL_RC_SIMPLE_CHK_DB=>PERFORM_CHECK
  • /SDF/RC_START_CHECK_F01
  • /SDF/RC_START_CHECK

Reason:

This is because the system code and note context are inconsistent.

The check framework code belongs ST-PI component. In ST-PI old version, you implemented the SAP Note 2399707, then upgrade the ST-PI, and did the adjustment for objects. And implement the new version of 2399707.

This issue most occur in after ST-PI SP level upgraded:

  • ST-PI 740 from >= SP08 to SP09 or higher.
  • ST-PI 2008_1_700 from >= SP18 to SP19 or higher.
  • ST-PI 2008_1_710 from >= SP18 to SP19 or higher.

Solution:

1, Open the class method /SDF/CL_RC_SIMPLE_CHK_DB->PERFORM_CHECK;

2, Go to the version management;

3, Retrieved the SP09 or SP18 upgrade version V2 or the version base on system;

And some system you can found the upgrade transport request as basis upgrade.

4, Do the same thing for all other objects but not “/SDF/RC_START_CHECK”. Because the report only contains the title warning.

5, SNOTE implement the note 2399707 again;

6, Ignore the report “/SDF/RC_START_CHECK” warning sine this is only title warning;

 

7, Active all of objects and complete the implementation.

 

 

2, Unable to read correction instruction when implementing the note

 

Symptom:

In case you experience issues in a system where SAP note 2399707 was already implemented, then you did do a SP update or release upgrade via SUM and afterwards try to implement SAP note 2399707 again.

The error message:

“Format of correction instructions 0020751258 212

0000092576 0091; unable to read corr. instruct.”

Reason:

This is an issue in the SUM tool which has been fixed with SUM 2.0 SP03.

 

Solution:

For systems which were upgraded in the past with older SUM versions, you can transport the objects of SAP note 2399707 implementation from a system which is not affected by this issue into the system which is affected by the issue. This will restore the TADIR entries of the objects. Afterwards (de)implementation of SAP note 2399707 is possible again. See also SAP note/KBA 2738153.

 

 

 

Additional Information

To learn more about how to perform simplification item check right and the relation to readiness check, you can follow below link:

https://blogs.sap.com/2018/03/26/sap-s4hana-simplification-item-check-how-to-do-it-right./

https://blogs.sap.com/2017/09/15/simplification-item-catalog-simplification-item-check-and-sap-readiness-check-for-sap-s4hana/

Be the first to leave a comment
You must be Logged on to comment or reply to a post.