How To Fix SZDM_CC_CHKS_DETAILS102 - Table &1 in metadata of XPRA &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: 102

• Message text: 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_GENERAL_ZDO>here.</>
The metadata object of the XPRA report &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 API.
To check and maintain the tables for the XPRA report &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_DETAILS102 - Table &1 in metadata of XPRA &2 (SLAPI-ID: &3) does not exist ?

  The SAP error message you are encountering, specifically "SZDM_CC_CHKS_DETAILS102 Table &1 in metadata of XPRA &2 (SLAPI-ID: &3) does not exist," typically indicates that there is a problem related to the metadata of a specific XPRA (a type of program in SAP that is used for data migration or adjustments during upgrades) and its associated tables.
  Cause:
  
  
  Missing Table: The error suggests that a required table (denoted by &1) is missing from the metadata for the specified XPRA (denoted by &2) and SLAPI-ID (denoted by &3). This could happen due to:
  
  Incomplete installation or upgrade of the SAP system.
  Corruption in the database or metadata.
  A previous upgrade or support package that did not complete successfully.
  
  
  
  Incorrect Configuration: There may be configuration issues or inconsistencies in the system that prevent the XPRA from accessing the necessary metadata.
  
  
  Version Mismatch: The XPRA may be looking for a table that is not present in the current version of the system, possibly due to an upgrade or patch that was not applied correctly.
  
  
  Solution:
  
  
  Check for Missing Tables: Verify if the table mentioned in the error message actually exists in the database. You can do this by using transaction SE11 (Data Dictionary) to check for the existence of the table.
  
  
  Re-run the XPRA: If the table is missing, you may need to re-run the XPRA or the relevant upgrade steps. This can sometimes resolve issues related to missing metadata.
  
  
  Check Upgrade Logs: Review the upgrade logs for any errors or warnings that might indicate why the table is missing. This can provide insights into what went wrong during the upgrade process.
  
  
  Restore from Backup: If the table is critical and cannot be recreated, consider restoring it from a backup if available.
  
  
  SAP Notes: Search for relevant SAP Notes that might address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  
  
  Contact SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP Support for assistance. Provide them with the error message details and any logs you have reviewed.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE38 (ABAP Editor), and SP01 (Spool Request) for troubleshooting.
  Documentation: Review the official SAP documentation related to the specific XPRA and the version of SAP you are using.
  System Checks: Perform system checks to ensure that all components are functioning correctly and that there are no other underlying issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.