BIBO Blog: "Cannot lock request DTP* of table 0Material for deletion (Message no. RSMPC178)"

Scenario

Consider following situations

DTP load for DSO is running more than its due time i.e. (taking more time to load data) and hence stays in yellow state for a long time and you want to stop the load to the DSO by changing the status of the loading request from yellow to red manually, but you deleted the ongoing background job for the DTP load.
A master data load through DTP failed as the background job for DTP failed with a short dump and you want to start a new DTP load but you cannot as there is a message saying “The old request is still running”. You cannot change the status for the old request to red or green as there is message “QM-action not allowed for master data”. You cannot delete the old request due to the message “Request cannot be locked for delete”.

Solution

1. When old request in Scenario 1 & 2 is in yellow status and you are not able to change / delete the request, it’s actually in a pseudo status. This request sits in table RSBKREQUEST with processing type as 5 in data elements USTATE, TSTATE and this 5 is actually "Active" status which is obviously wrong.One of the possible solutions is to ask a basis person to change the status to 3 in both USTATE and TSTATE and then it allows reloading the data. Once the data is successfully loaded, you can delete the previous bad request even though it is still in yellow. Once the request is deleted, the request status gets updated as "4" in table RSBKREQUEST.

2. There is one more alternative solution, wherein you can manually change the status of the old request to red or green by using the function module RSBM_GUI_CHANGE_USTATE.

Following are the steps to change the QM Status of a yellow request to red/green by using RSBM_GUI_CHANGE_USTATE

3. In Some cases, Check in SM37 also and make sure it's finished or cancelled and not active. then check in SM12 and release the lock directly, if any.

1. Select Request Id from target.