How To Fix SZDM_CC_CHKS_DETAILS098 - R3TR OBJA &1: Table &2 read by Switch Badi &3 cannot be set to read only.

SAP Error Message - Details

• Message type: E = Error

• Message class: SZDM_CC_CHKS_DETAILS - Detailed messages related to check classes

• Message number: 098

• Message text: R3TR OBJA &1: Table &2 read by Switch Badi &3 cannot be set to read only.

What causes this issue?

INCLUDE SZDM_CC_LAT_DET_INTRO_PROC OBJECT DOKU ID TX
In this case<(>,<)> the owner of the Switch-BADI implementation &v3& has
specified that the Switch Badi implementation accesses table &v2& and
that this table shall be read-only for the productive application during
the ZDO upgrade. (See ABAP transaction SLAPI. Choose the "Position..."
button to find your Switch-BADI implementation metadata definition &v1&.
Select this entry and choose "Used Database Tables".)
INCLUDE SZDM_CC_LAT_DET_RO_IMPOSSIBL OBJECT DOKU ID TX

How to fix this error?

As an alternative to setting the complete table to read-only the
application needs to make sure that only the key ranges accessed by the
Swich-BADI implementation has become read-only while all other table
entries are still writeable for the productive application.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SZDM_CC_CHKS_DETAILS098 - R3TR OBJA &1: Table &2 read by Switch Badi &3 cannot be set to read only. ?

  The SAP error message SZDM_CC_CHKS_DETAILS098 indicates that there is an issue with a Business Add-In (BAdI) implementation that is trying to set a table to read-only, but the system has detected that this is not allowed for the specific context or configuration.
  Cause:
  The error typically arises in the following scenarios:
  
  BAdI Implementation: The BAdI implementation is attempting to modify a table that is not allowed to be modified in the current context. This can happen if the BAdI is designed to read data but is trying to write or change it.
  Switch Configuration: The switch configuration for the BAdI may not be set correctly, leading to conflicts in how the data is accessed or modified.
  Data Locking: There may be a data locking issue where the table is being accessed in a way that conflicts with its intended use.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check BAdI Implementation:
  
  Review the BAdI implementation code to ensure that it is not trying to modify the table in question when it should only be reading it.
  Ensure that the BAdI is implemented correctly according to the specifications provided by SAP.
  
  
  
  Review Switch Configuration:
  
  Check the switch configuration for the BAdI. Ensure that the switch is activated and configured correctly to allow the intended operations on the table.
  You can use transaction SICF to check the status of the BAdI and its related switches.
  
  
  
  Debugging:
  
  If you have access to the development environment, you can debug the BAdI implementation to see where the error occurs. This can help identify if there are any logical errors in the code.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation for the specific BAdI and the tables involved. This can provide insights into the expected behavior and any restrictions that may apply.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. Provide them with the error message details and any relevant context.
  
  
  
  Related Information:
  
  BAdI (Business Add-In): A way to enhance SAP applications without modifying the original code. BAdIs allow developers to add custom functionality.
  Switch Framework: A mechanism in SAP that allows for the activation or deactivation of certain features or enhancements in the system.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE18 (for BAdI definitions) and SE19 (for BAdI implementations) to manage and troubleshoot BAdIs.
  
  By following these steps, you should be able to identify and resolve the issue related to the error message SZDM_CC_CHKS_DETAILS098.