How To Fix SZDM_CC_CHKS_DETAILS042 - Classification conflict &4, table &3, Switch-BADI &1, API &2

SZDM_CC_CHKS_DETAILS042 - Overview

• Message type: E = Error

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

• Message number: 042

• Message text: Classification conflict &4, table &3, Switch-BADI &1, API &2

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 a Switch-BADI implementation &V1& 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 "&V4&", 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 &V4& is appropriate for
the table &V3& when accessed by the Switch-BADI implementation &V1&.
To check the specification for the Switch-BADI implementation &V1&,
perform the following steps:
Call transaction SLAPI.
Select the line containing &V2&.
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 Switch-BADI &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 Switch-BADI implementation &V1&, the API
&V2& and the table &V3& 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 &V4&.

Error message extract from SAP system. Copyright SAP SE.

SZDM_CC_CHKS_DETAILS042 - Details

• The SAP error message SZDM_CC_CHKS_DETAILS042 indicates a classification conflict in the context of a Business Add-In (BADI) implementation. This error typically arises when there is a mismatch or inconsistency in the classification data being processed, often related to the specific BADI implementation or the API being used.
  
  Cause:
  
  Data Inconsistency: The error may occur due to inconsistent or incorrect classification data in the relevant tables.
  BADI Implementation Issues: If the BADI implementation is not correctly handling the classification data, it can lead to conflicts.
  API Misuse: If the API being called does not align with the expected data structure or classification, it can trigger this error.
  Switch Configuration: The switch for the BADI might not be activated or configured correctly, leading to conflicts in the classification process.
  
  
  Solution:
  
  Check Data Consistency: Verify the classification data in the relevant tables. Ensure that all required fields are populated correctly and that there are no inconsistencies.
  Review BADI Implementation: Examine the