Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TK - Transport Organizer
Message number: 028
Message text: Cannot delete (request locks still exist)
In request/task &V1&, which you want to delete, no objects are marked
as "locked" in the editor. Nevertheless request locks still exist for
task/request &V1&.
The function terminates.
Contact your system administrator, who must ensure that the request
locks (table TLOCK) correspond to the locked objects in your request.
If the error occurs repeatedly, send an error message to the SAP
Hotline.
Error message extract from SAP system. Copyright SAP SE.
TK028
- Cannot delete (request locks still exist) ?The SAP error message TK028 "Cannot delete (request locks still exist)" typically occurs when you attempt to delete a transport request in the SAP system, but there are still locks associated with that request. This can happen for various reasons, such as the request being in use, or it being locked by another user or process.
Causes:
- Active Locks: The transport request is currently locked by another user or process, preventing deletion.
- Incomplete Transport: The transport request may not have been fully processed or released, leading to locks remaining.
- User Sessions: A user session may still be holding a lock on the transport request.
- Transport Management System (TMS) Issues: There may be issues with the TMS that are causing locks to persist.
Solutions:
Check Locks: Use transaction code
SM12
to check for locks related to the transport request. You can filter by the transport request number and see if any locks are held by users.
- If you find locks, you can either wait for the user to release them or, if appropriate, you can delete the locks yourself (ensure you have the necessary authorizations).
Release the Transport Request: If the transport request is still in a "modification" state, ensure it is released properly using transaction code
SE09
orSE10
. Once released, you should be able to delete it.Check User Sessions: Use transaction code
SM04
to check active user sessions. If you find a session that is holding a lock on the transport request, you can ask the user to log off or terminate the session if necessary.Transport Organizer: Go to the Transport Organizer (transaction
SE09
orSE10
) and check the status of the transport request. If it is in a "modification" state, you may need to release it before deletion.System Restart: In some cases, a system restart may help clear any lingering locks, but this should be done with caution and typically as a last resort.
Consult Basis Team: If you are unable to resolve the issue, it may be necessary to consult your SAP Basis team for further assistance. They can help investigate deeper issues with the transport management system or database locks.
Related Information:
SE09
/ SE10
: Transport OrganizerSM12
: Display and Delete LocksSM04
: User SessionsBy following these steps, you should be able to identify and resolve the issue causing the TK028 error message.
Get instant SAP help. Sign up for our Free Essentials Plan.
TK027
Request/task &1 does not contain any objects
What causes this issue? The objects in request/task &V1& could not be read because it contains no objects.System Response Objects are not ne...
TK026
Objects can only be edited under &
What causes this issue? The selected objects can only be edited under the same task. Due to locks already in place, the objects can only be edited un...
TK029
You cannot enter "&1"
What causes this issue? An entry was made for object type &V1& (&V2&). This is no longer possible.System Response The entry is rejec...
TK030
Error saving request texts &1
What causes this issue? No new text can be entered in request/task &V1& in the logon language because a text already exists. The text for the...
Click on this link to search all SAP messages.