How To Fix SZDM_CC_CHKS_DETAILS040 - Classification conflict &3, table &2, API &1

SZDM_CC_CHKS_DETAILS040 - Overview

• Message type: E = Error

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

• Message number: 040

• Message text: Classification conflict &3, table &2, API &1

What causes this issue?

The check is performed to ensure lock mode consistency for ZDO
enablement. For more information about ZDO and required properties see
<DS:TX.SZDM_CC_GENERAL_ZDO>here.</>
In this case the specification for an API to be called by an
after-import method (AIM) is checked, for which tables are read or write
accessed. For each of these tables it is specified whether and how data
security against write access is achieved by choosing a corresponding
<DS:DE.OB_ACCESS_TYPE>"Access"</> and <DS:DE.OB_LOCK_MODE>"Lock mode"</>
combination.
A conflict is identified with the values "&V3&", where the first part
means the values of the <DS:DE.OB_ACCESS_TYPE>"Access"</>/
<DS:DE.OB_LOCK_MODE>"Lock mode"
</> combination, and the second part means the central configuration
value.

How to fix this error?

Check whether the specified <DS:DE.OB_ACCESS_TYPE>"Access"</>/
<DS:DE.OB_LOCK_MODE>"Lock mode"</> combination is appropriate for the
table &V2& when accessed by an after-import method assigned to the
checked API &V1&.
To check the specification for the API, perform the following steps:
Call transaction SLAPI.
Select the line containing "&V1&".
Choose "Used Database Tables".
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. Lock mode "Undefined" is considered as not
yet ZDO-enabled and is therefore not valid for ZDO either.
If you, as a responsible person for the API &V1&, think the values are
appropriate but the conflict is still not resolvable, contact the
upgrade team.
To contact the upgrade team create an incident on component
BC-UPG-DTM-TLA and list the API &V1& and the table &V2& for which this
issue appears together with the specified
<DS:DE.OB_ACCESS_TYPE>"Access"</>/<DS:DE.OB_LOCK_MODE>"Lock mode"</>
combination and classification &V3&.

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_DETAILS040 - Classification conflict &3, table &2, API &1 ?

  The SAP error message SZDM_CC_CHKS_DETAILS040 indicates a classification conflict in the context of SAP's classification system. This error typically arises when there is a mismatch or inconsistency in the classification data being processed, particularly when using the Classification API.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Inconsistent Data: There may be inconsistencies in the classification data for the object being processed. This could be due to missing or incorrect entries in the classification tables.
  
  
  Incorrect API Usage: The API being called may not be used correctly, leading to conflicts in the classification data.
  
  
  Data Integrity Issues: There may be issues with data integrity, such as duplicate entries or incorrect relationships between classes and characteristics.
  
  
  
  Configuration Issues: The classification system may not be configured correctly, leading to conflicts when trying to classify objects.
  
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Classification Data: Review the classification data for the object in question. Ensure