My problem was caused by an all-systems-crash that thrown off coherence, because data on dev, qas and prd were restored from different time situations. In particular there was some abap objects that were not inserted in change requests anymore while saving them, but they apparently weren’t in a cr. I found that those object were locked in a change request released task, so I cannot take them in a new change request.
As solution to the problem I used the transaction SE03, request/tasks – unlock objects (expert tools). All tasks containing the objects to rescue, not only the main change requests, must be unlocked. Then I could save workbench changes of those objects in a new cr.
