How To Fix LRM_TADIR005 - Object &1 is locked in multiple requests &2 and &3

LRM_TADIR005 - Overview

• Message type: E = Error

• Message class: LRM_TADIR - Messages for ILM TADIR API

• Message number: 005

• Message text: Object &1 is locked in multiple requests &2 and &3

What causes this issue?

Object directory entries corresponding to the ILM object are locked in
different transport requests. Object directory entries for ILM1 and ILM2
must be recorded in a single request.
For example, this error occurs when ILM1 and ILM2 objects are manually
recorded in different requests.

System Response

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

How to fix this error?

Ensure that object directory entries for ILM1 and ILM2 are part of the
same transport request as follows:
Program ID Object Type Object Name
R3TR,,,, ILM1 ,, <OBJECT_CATEGORY><space><ILM_OBJECT_NAME>
R3TR,,,, ILM2 ,, <ILM_OBJECT_NAME>

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 LRM_TADIR005 - Object &1 is locked in multiple requests &2 and &3 ?

  The SAP error message LRM_TADIR005 indicates that an object (like a transport request or a development object) is locked in multiple requests. This typically occurs when there are concurrent attempts to modify or transport the same object, leading to a conflict.
  
  Cause:
  
  Concurrent Modifications: The object is being modified or transported in multiple requests at the same time.
  Transport Lock: The object is locked due to an ongoing transport process or a previous transport that did not complete successfully.
  Development Work: Multiple developers may be trying to work on the same object simultaneously, leading to a lock situation.
  
  
  Solution:
  
  Identify the Locks: Use transaction code SE03 (Transport Organizer Tools) to analyze the transport requests and identify which requests are locking the object.
  Release Locks: If you have the necessary authorizations, you can release the locks. This can be done through transaction SE03 or by using the transaction SM12 (Lock Entries) to find and delete the lock entries