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
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 useIn a ZDO upgrade, the tables cannot be correctly classified. This can
lead to a failure of the upgrade.
Adjust the LOCK_MODE values for table &V1&.
Error message extract from SAP system. Copyright SAP SE.
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,
Get instant SAP help. Sign up for our Free Essentials Plan.
SCTS_AIM059
Lock mode conflict (&2 <-> &3) for table &1 with SLAPI-entry &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. If an AIM calls an A...
SCTS_AIM058
No lock modes adjustment P -> X needed. No tables with lock mode P found.
What causes this issue? During a ZDM upgrade, some database tables can be accessed by both the productive application and the after-import methods (A...
SCTS_AIM061
Lock mode conflict (&2 <-> &3) for table &1 with SLAPI-entry &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. If an AIM calls an A...
SCTS_AIM062
Lock mode is undefined for table &1 in metadata of API &2.
What causes this issue? The metadata object of an API &V2& to be called by an after-import method (AIM) has been created. Table &V1& ...
Click on this link to search all SAP messages.