Do you have any question about this error?
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
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.
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.
SZDM_CC_CHKS_DETAILS040
- Classification conflict &3, table &2, API &1 ?Get instant SAP help. Start your 7-day free trial now.
SZDM_CC_CHKS_DETAILS039
Classification conflict &4, table &3, object &1, type &2
What causes this issue? The check is performed to ensure lock mode consistency for ZDO enablement. For more information about ZDO and required proper...
SZDM_CC_CHKS_DETAILS010
No static table classification found for table &1 of package &2
What causes this issue? This table has no static ZDM classification but might need one, as it belongs to a package which contains other tables with a...
SZDM_CC_CHKS_DETAILS041
Classification conflict &4, table &3, XPRA report &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 proper...
SZDM_CC_CHKS_DETAILS042
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 proper...
Click on this link to search all SAP messages.