How To Fix SZDM_CC_CHKS_DETAILS103 - Table &1 in metadata of Switch-BADI &2 (SLAPI-ID: &3) does not exist

SAP Error Message - Details

• 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

What causes this issue?

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</>.

How to fix this error?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 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 implementation and the switch configuration, leading to inconsistencies.
  
  Solution:
  
  Check BAdI Activation: Ensure that the BAdI is activated in the system. You can do this by navigating to the BAdI definition in transaction SE18 and checking its status.
  Review Switch Configuration: Go to transaction SFW5 to review the switch configuration. Ensure that the switch is activated and that the BAdI is correctly assigned to the switch.
  Check Transport Logs: If the BAdI was transported, check the transport logs for any errors or warnings that might indicate issues with the transport.
  Re-implement or Adjust BAdI: If the BAdI implementation is missing or incorrect, you may need to re-implement it or adjust the implementation to ensure it aligns with the switch configuration.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  Debugging: If the issue persists, consider debugging the code to identify where the error is being triggered and gather more context about the missing metadata.
  
  Related Information:
  
  Transaction Codes: 
  
  SE18: BAdI Definition
  SE19: BAdI Implementation
  SFW5: Switch Framework
  
  
  SAP Notes: Search for SAP Notes related to BAdI and switch framework issues. You can use the SAP Support Launchpad to find relevant notes.
  Documentation: Review SAP documentation on BAdIs and the switch framework for best practices and configuration guidelines.
  
  If the problem continues after following these steps, it may be beneficial to reach out to SAP support for further assistance.