Recently
I saw a situation where object was not able to be included into the transport.
System was indicating that the objects is locked via pop-up message (TK117):
Object
XXX locked for request/task <SID>Kxxxxxx
Choose
‘Display object’ or ‘Cancel’.
However, the object was not locked by
any transport neither task. The transport that the error mentioned was released
and moved across the landscape long time ago.
To solve this issue, I went to t-code SE03
then in menu Requests/Tasks -> Unlock Objects (expert tool) and via this I
was able to unlock object.
Notice that 1st option – Unlock
Object List needs to be selected. Transport Request/Task input field needs
to be populated with the task no of the Transport Request in which the error
message indicates that it is locked in.
Behinds the scenes what this t-code is
doing is to remove a lock entry from table TLOCK (Change and Transport
System: Lock Table). The table basically holds all the objects that are locked
in the TRs. In my case for some reason while I released the TR the lock entry
wasn’t removed from the table. And it is not known to me what was that reason…
Doing further research about the error
I found also SAP Note 2537981 -
SE13 | TK117 | Request lock on nonexistent task/request, rep
ZSLA_DELETE_ORPHANED_TLOCK_2. The Note describes how to removed the lock entry
(so called orphaned lock) for LIMU TABT objects.
