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.
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
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.
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
Get instant SAP help. Sign up for our Free Essentials Plan.
SZDM_CC_CHKS_DETAILS099
R3TR OBJA &1: Table &2 accessed by an API 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 SLAPI implementation &v1& has spec...
SZDM_CC_CHKS_DETAILS098
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 implementat...
SZDM_CC_CHKS_DETAILS101
Table &1 in metadata of SL API &2 does not exist in this system.
What causes this issue? The properties of an API called by an after-import method (AIM) might be incorrectly maintained. In transaction SLAPI, you ha...
SZDM_CC_CHKS_DETAILS102
Table &1 in metadata of XPRA &2 (SLAPI-ID: &3) does not exist
What causes this issue? The properties of an XPRA report are not correctly maintained. For more information about this check, see <DS:TX.SZDM_CC_G...
Click on this link to search all SAP messages.