Question:
Hello friends,
Quite often, I get the message
The current work item has the status Logically deleted.
Why does this occur?
What can I do to rectify it?
Thanks
Dana
Answer:
A typical situation would be that you've got a fork where not all branches are necessary. As soon as the necessary number of branches are completed the unprocessed Work Items in the other branches will be put to 'Logically deleted', since their completion isn't required any more.
_________________
Regards
Trygve
Answer:
Hi Trygve,
Thanks for the reply.
I finally figured out why it is occuring.
I created a custom method Approve for ZBUS2089 for a Trip approval workflow using the function module BAPI_TRIP_CHANGE_STATUS.
I released the method prior to releasing the object type ZBUS2089.
Now I set the status of the method to implemented and the ZBUS2089 to released.
That removed the problem of "Work item Logically deleted"
But still I haven't figured out why is it so?
Thanks
Dana
Answer:
I see the problem recurring again.
What could be the reason?
Please help.
Thanks
Dana
Answer:
Hi Trygve,
You are right.
Now the problem is resolved.
There is a parallel processing (FORK) in the workflow. One path has the wait for event Changed and the other path has Trip status change. Whenever there is a status change the Wait for event changed is triggerd. The Changed event is triggered before the change status task is completed. Hence the incomplete task is automatically set to the logically deleted.
I solved it by replacing the wait for event changed with wait for event created. Because actually when the Initiator changes the Trip he is actually triggering the Created event.
Thanks
Dana