How To Fix SZDM_CC_CHKS_DETAILS052 - Inconsistent metadata for XPRA report &1 (SLAPI-ID:&2)

SZDM_CC_CHKS_DETAILS052 - Overview

• Message type: E = Error

• Message class: SZDM_CC_CHKS_DETAILS - Detailed messages related to check classes

• Message number: 052

• Message text: Inconsistent metadata for XPRA report &1 (SLAPI-ID:&2)

What causes this issue?

The properties of an XPRA report &V1& maintained as API &V2&are
inconsistent. For more information about required properties, see
<DS:TX.SZDM_CC_GENERAL_ZDO>here.</>

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

In order to see the detailed messages for the XPRA report &V1&
properties, perform the following steps:
1) Call transaction SLAPI.
2) Select the line containing &V2&.
3) Choose "Check" button.
You need to correct the XPRA report's properties according to the check
issues.

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_DETAILS052 - Inconsistent metadata for XPRA report &1 (SLAPI-ID:&2) ?

  The SAP error message SZDM_CC_CHKS_DETAILS052 indicates that there is inconsistent metadata for an XPRA (eXtended Program Run) report in the system. This error typically arises during the execution of an XPRA report, which is used for data migration or system upgrades.
  
  Cause:
  The inconsistency in metadata can be caused by several factors, including:
  
  Incomplete Upgrade or Migration: If an upgrade or migration process was interrupted or not completed successfully, it may lead to inconsistencies in the metadata.
  Corrupted Data: Corruption in the database or in the transport requests can lead to metadata inconsistencies.
  Missing or Incorrect Configuration: If the configuration settings for the XPRA report are incorrect or missing, it can trigger this error.
  Version Mismatch: If there are discrepancies between the versions of the components involved, it may lead to metadata inconsistencies.
  
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Check the XPRA Report: Identify the specific XPRA report mentioned in the error message (indicated by