How To Fix TR105 - & locked; correction lock cannot be transferred

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 105

• Message text: & locked; correction lock cannot be transferred

What causes this issue?

The long-term lock (correction lock) set for the object to be deleted
could not be transferred to the other requests within the linked
(correction/transport/..) requests.
Reason:
A request also containing the object to be deleted is being processed
and therefore has a temporary lock (editing lock).

System Response

The object is not deleted and remains locked.

How to fix this error?

Call transaction SM12. This transaction gives you an overview of the
temporary locks. You can now find out the name of the user who put the
temporary lock on the specified correction.
Contact the owner of the temporary lock.
Once the temporary lock on the other correction has been removed, you
can try again to delete the correction.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TR105 - & locked; correction lock cannot be transferred ?

  The SAP error message TR105, which states "Locked; correction lock cannot be transferred," typically occurs in the context of transport requests in SAP. This error indicates that a transport request is locked, preventing it from being transferred to another system (e.g., from development to quality assurance or production).
  Causes:
  
  Locked Transport Request: The transport request is locked because it is currently being edited or has not been released properly.
  User Lock: A user may have locked the transport request by editing it or by not releasing it correctly.
  Transport Organizer Issues: There may be issues with the transport organizer or the transport management system.
  Incomplete Release: The transport request may not have been fully released, which is necessary for it to be transferred.
  
  Solutions:
  
  
  Check Lock Status:
  
  Use transaction code SE01 or SE09 to check the status of the transport request. Look for any locks associated with the request.
  
  
  
  Release the Transport Request:
  
  If the transport request is still in a modifiable state, ensure that it is released properly. You can do this by selecting the transport request and choosing the "Release" option.
  
  
  
  Unlock the Transport Request:
  
  If the transport request is locked by a user, you may need to unlock it. This can be done by:
  
  Using transaction code SE01 or SE09 to find the transport request and unlock it.
  If necessary, contact your SAP Basis administrator to unlock the request.
  
  
  
  
  
  Check for Active Changes:
  
  Ensure that there are no active changes in the transport request that need to be addressed before it can be released.
  
  
  
  Transport Management System (TMS) Check:
  
  Verify that the Transport Management System is functioning correctly. Sometimes, issues with TMS can lead to transport requests being locked.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error. SAP frequently updates its knowledge base with solutions for common issues.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SE01: Transport Organizer
  SE09: Workbench Organizer
  SE10: Customizing Organizer
  
  
  Transport Request Types:
  
  Workbench requests (for development objects)
  Customizing requests (for configuration changes)
  
  
  SAP Basis Role: If you are not able to resolve the issue, it may be necessary to involve your SAP Basis team, as they have the necessary authorizations and tools to manage transport requests and locks.
  
  By following these steps, you should be able to resolve the TR105 error and successfully transfer your transport request.