How To Fix SATC_CI_MODE_MSGS099 - It is recommended to apply baseline for checks with stable identity only

SAP Error Message - Details

• Message type: E = Error

• Message class: SATC_CI_MODE_MSGS - ATC/Code Inspector: exemption handling

• Message number: 099

• Message text: It is recommended to apply baseline for checks with stable identity only

What causes this issue?

It is recommended to apply the baseline features only to analyzers that
provide findings with strong identity. In contrast findings with weak
identity shall not used for the base line.
One or more check do not meet this criteria. Please be aware that the
baseline features might not work (well) for such checks.
&NOTE&
Baseline is a technique to suppress findings typically in legacy code.
As long as the code remains unchanged the baseline shall suppress the
finding. As soon the code gets change the baseline effect shall get
revoked. This requires that a finding has a strong identity. Include &
line number do not satisfy this requirement. Typically an analyzer with
strong identity computes a checksum for the affected statements.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SATC_CI_MODE_MSGS099 - It is recommended to apply baseline for checks with stable identity only ?

  The SAP error message SATC_CI_MODE_MSGS099 typically relates to the SAP Code Inspector (SCI) and indicates that it is recommended to apply a baseline for checks that involve stable identities. This message is often encountered when performing static code checks in ABAP programs.
  Cause:
  The error message suggests that the checks being performed may not yield consistent results due to the dynamic nature of the code being analyzed. Specifically, it implies that the checks are being run in a mode that does not guarantee stable identities, which can lead to unreliable results. This is particularly relevant for checks that depend on the structure or behavior of the code that may change over time or in different contexts.
  Solution:
  To resolve this issue, you should consider the following steps:
  
  
  Apply a Baseline: 
  
  Create a baseline for the checks you are performing. A baseline is a reference point that allows the Code Inspector to compare the current state of the code against a known good state. This can help ensure that the checks are stable and reliable.
  You can create a baseline by running the Code Inspector in a mode that allows you to save the results of the checks and use them for future comparisons.
  
  
  
  Review Check Settings:
  
  Review the settings of the checks you are running. Ensure that you are using checks that are appropriate for the type of code you are analyzing. Some checks may be more suitable for certain types of code than others.
  
  
  
  Use Stable Identity Checks:
  
  Focus on checks that are known to provide stable results. This may involve selecting specific checks that are designed to work with stable identities or avoiding checks that are known to be problematic in dynamic contexts.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation for the Code Inspector and the specific checks you are using. This can provide insights into how to configure the checks properly and what best practices to follow.
  
  
  
  Update SAP System:
  
  Ensure that your SAP system is up to date with the latest patches and updates. Sometimes, issues with tools like the Code Inspector can be resolved with system updates.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional guidance on using the Code Inspector effectively.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Training and Documentation: Consider reviewing training materials or documentation related to the Code Inspector to better understand its features and best practices.
  
  By following these steps, you should be able to address the error message SATC_CI_MODE_MSGS099 and improve the reliability of your code checks in SAP.