How To Fix SCTS_AIM060 - Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4

SCTS_AIM060 - Overview

• Message type: E = Error

• Message class: SCTS_AIM - Messages for the AIM meta data repository

• Message number: 060

• Message text: Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4

What causes this issue?

For each after import method (AIM), the owner has to declare all tables
the AIM reads from or writes to. Furthermore, for each of these tables,
the owner of the AIM or XPRA has to declare if and how the content of
these tables is protected against write access by the productive
application running in parallel with the ZDO upgrade. The owner provides
this information by assigning a "LOCK_MODE" to each of these tables. The
possible values of the LOCK_MODE and their meanings are described
<DS:DE.OB_LOCK_MODE>here.</>

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

If different AIMs or XPRAs declare access to the same table and use
different values of LOCK_MODE then the system will compute a common
value which is suitable for both AIMs or XPRAs. Some combinations of
LOCK_MODE values are, however, incompatible to each other. In this case,
the system will report an error.
The pairs of compatible and incompatible lock modes can be depicted in
the following matrix:
||' '| X | P | R | U | W
------------------------------------
' '||' '| ! | ! | ! | ! | !
X || ! | X | P | R | U | !
P || ! | P | P | R | ! | ! (! represents a pair of
R || ! | R | R | R | ! | ! incompatible lock modes)
U || ! | U | ! | ! | U | !
W || ! | ! | ! | ! | ! | W
In the current case, table &V1& is declared with two incompatible lock
modes (&V2& and &V3&). The conflicting value is declared for the AIM of
transport object type &V4& (see transaction SOBJ, navigate to the method
declarations, select button "AIM details" and navigate to "used database
tables").

System Response

In a ZDO upgrade, the tables cannot be correctly classified. This can
lead to a failure of the upgrade.

How to fix this error?

Adjust the LOCK_MODE values for table &V1&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCTS_AIM060 - Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4 ?

  The SAP error message SCTS_AIM060 indicates a lock mode conflict for a specific database table. This error typically arises when there are concurrent attempts to access or modify the same database table in a way that is not allowed due to the current lock settings. Here’s a breakdown of the components of the error message and potential solutions:
  Cause
  
  Lock Mode Conflict: The error occurs when two or more transactions are trying to access the same table with incompatible lock modes. For example, one transaction may be trying to write to the table while another is trying to read it, or two transactions may be trying to write to the table simultaneously.
  AIM (Application Interface Management): The error is related to the Application Interface Management (AIM) and indicates that there is a conflict in the access modes for the specified table.
  SOBJ-type: The SOBJ-type refers to the type of object that is being accessed,