How To Fix SZDM_CC_CHKS_DETAILS100 - R3TR CLAS &1: Table &2 defined for Switch Badi can't 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: 100

• Message text: R3TR CLAS &1: Table &2 defined for Switch Badi can't 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 &v1& 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
SFW_SW_&v1& or SFW_BF_&v1& respectively. 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 should 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_DETAILS100 - R3TR CLAS &1: Table &2 defined for Switch Badi can't be set to read only. ?

  The SAP error message SZDM_CC_CHKS_DETAILS100 typically indicates an issue related to the configuration of a Business Add-In (BAdI) in the context of a switch framework. This error occurs when a class (R3TR CLAS) is defined for a switch BAdI, but the associated table (Table &2) cannot be set to read-only. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause
  
  Switch BAdI Configuration: The error usually arises when there is a misconfiguration in the switch BAdI setup. The system expects certain tables to be read-only, but they are not configured correctly.
  Implementation Issues: If the BAdI implementation is trying to modify data in a table that is supposed to be read-only, this error will occur.
  Inconsistent Data: There may be inconsistencies in the data or the way the BAdI is defined, leading to the system being unable to enforce the read-only status.
  
  Solution
  
  Check BAdI Implementation: Review the implementation of the BAdI to ensure that it does not attempt to modify any data in the specified table. If modifications are necessary, consider whether a different BAdI or approach is more appropriate.
  Review Switch Configuration: Ensure that the switch configuration for the BAdI is set up correctly. Check the transaction SWT2 to verify the switch settings and ensure that the BAdI is correctly activated.
  Table Definition: Verify the definition of the table in question. Ensure that it is correctly defined in the context of the switch BAdI and that it is intended to be read-only.
  Transport Requests: If the changes were made in a development environment, ensure that all relevant transport requests have been properly released and imported into the target environment.
  Consult Documentation: Refer to SAP documentation or notes related to the specific BAdI and switch framework for any additional guidance or known issues.
  
  Related Information
  
  Transaction Codes: Use transaction codes like SE18 (for BAdI definitions) and SE19 (for BAdI implementations) to analyze and modify BAdI settings.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional context.
  Debugging: If necessary, use debugging tools to trace the execution of the BAdI and identify where the error is being triggered.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.