Message type: E = Error
Message class: SZDM_CC_CHKS_DETAILS - Detailed messages related to check classes
Message number: 103
Message text: Table &1 in metadata of Switch-BADI &2 (SLAPI-ID: &3) does not exist
The properties of Switch-BADI implementation are not correctly
maintained. For more information about this check, see
<DS:TX.SZDM_CC_GENERAL_ZDO>here.</>
The metadata object of the Switch-BADI implementation &V2& is maintained
as API &V3& in transaction SLAPI. Table &V1& is declared as accessed
table for this metadata object, however this table does not exist.
You can maintain the required properties in a
<DS:TX.SCTS_SLAPI_REPOSITORY>Repository for Meta Data of an API called
by an After-Import Method</>.
Check and make sure that the correct tables are specified which are
accessed by the Switch-BADI implementation.
To check and maintain the tables for the Switch-BADI implementation &V2&
, perform the following steps:
Call transaction SLAPI.
Select the line containing &V3&.
Choose "Used Database Tables".
Check table &V1& and adapt or remove it.
Check completeness of the tables and whether the attributes
<DS:DE.OB_LOCK_MODE>"Lock mode"</> and <DS:DE.OB_ACCESS_TYPE>"Access"</>
are correctly maintained.
Error message extract from SAP system. Copyright SAP SE.
SZDM_CC_CHKS_DETAILS103
- Table &1 in metadata of Switch-BADI &2 (SLAPI-ID: &3) does not exist ?The SAP error message "SZDM_CC_CHKS_DETAILS103 Table &1 in metadata of Switch-BADI &2 (SLAPI-ID: &3) does not exist" typically indicates that there is an issue with the configuration of a Business Add-In (BAdI) related to a switch framework in SAP. This error can occur in various scenarios, particularly when working with enhancements or customizations in the SAP system.
Cause: Missing Metadata: The error suggests that the system is unable to find the metadata for a specific table associated with a BAdI. This could be due to the BAdI not being properly activated or configured. Incorrect Switch Configuration: The switch framework may not be correctly set up, leading to the system not recognizing the BAdI or its associated tables. Transport Issues: If the BAdI or its metadata was transported from another system, there may have been issues during the transport process that resulted in missing objects. Version Mismatch: There may be a version mismatch between the BAdI
Get instant SAP help. Sign up for our Free Essentials Plan.
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...
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_DETAILS104
R3TR TABL or LIMU TABD &1: Table &2 cannot be set to read only.
What causes this issue? INCLUDE SZDM_CC_GENERAL_INTRO OBJECT DOKU ID TX Reason: In order to execute an upgrade in parallel with the productive applic...
SZDM_CC_CHKS_DETAILS105
R3TR TABU &1: Table &2 cannot be set to read only.
What causes this issue? INCLUDE SZDM_CC_GENERAL_INTRO OBJECT DOKU ID TX Reason: In order to execute an upgrade in parallel with the productive applic...
Click on this link to search all SAP messages.