dialog workitem is logically deleted

[bhakti2]

hi

this is rather simple workflow, with approval dialog step of user decision.

the dialog workitem is seen as logically deleted in the workflow log.

we are not able to make out why it is getting logically deleted.

there is nothing in the workflow log that can give us any clue. we checked swel, st22, sm58 etc....

how can we find out why the dialog workitems are getting logically deleted ??

thanks

B

[Former Member · Accepted solution]

Is only the dialog step / work item logically deleted? Is the workflow (the header work item) itself still in process? Or has the whole workflow been logically deleted?

It could be of course possible that somewhere (outside of the workflow - user-exit, BADI, Z-program, etc.) is some code which directly terminates the work item (e.g. with function SAP_WAPI*CANCEL*). This might be difficult to trace down...

Kind regards,

Karri

[bhakti2 · Accepted solution]

hi Karri

only the dialog step is getting logically deleted and the status of workflow is set to Completed

if it is some other processing outside of the workflow, then what should be the user id with which the step has been executed ? it would no tbe wf-batch, am i right? it would be the user who has executed the code that resulted in logically deleting the workitem ?

thanks

bhakti

[Former Member · Accepted solution]

>only the dialog step is getting logically deleted and the status of workflow is set to Completed

Now this is a really crucial point of information. When the whole workflow gets completed (someone completes it in a way or another) the work items that are still not processed (basically in "ready" or in "process" status) will get logically deleted. Most likely there is nothing "wrong" in your decision step.

Open the technical WF log, and pay attention to the first (="header") work item. Can you find the reason why the workflow was completed? You should put your effort of finding the reason why the workflow gets completed. The decision step work item getting into logically deleted status is just a consequence for the workflow getting completed.'

Kind regards,

Karri

[bhakti2 · Accepted solution]

hi Karri,

thanks for the critical point of workflow status completed

im focussing on reason why wf got completed

i found the message SWF_RUN, 611, Execution Interrupted

I am tyring to explore this message

i've just refreshed buffer and regeenrated the busines object and waiting for more such instances to occur

this has been very common problem and there are too many workflow instances with this problem

thank you

bhakti

[pokrakam]

What does the log read for the item? And the WF?

[bhakti2]

hi Mike

im trying to dig into the workflow log

i find that the logicaly deleted stage has the creator userid and not wf-batch as user

and like Karri said i find at header level this message SWF_RUN 611 to figure out how the workflow got completed at header level

ive put some screenshots here

thanks

bhakti

[pokrakam]

Looks like it was deleted by design - e.g. a parallel fork completing may look like this. Any events? Is there a header event to complete the WF?

You say you checked SWEL - is the correct logging switched on (filters in SWELS).

The other more difficult to trace possibility is that it was programmatically cancelled by a custom program or BAdI by e.g. SAP_WAPI_WORITEM_CANCEL, maybe do a where-used on this FM.

[bhakti2]

hi Mike

there is no parellel fork

there isno terminating event to complete the workflow

i checked in swel, there is no filter in swels

yes there is a z-report that using FM to complete workitems programmatically.

it is a mass approval report where the decision workitems are processed using std FM

but it gives an approve or reject decision and i tried that but i couldnt simulate the exact problem in dev system (this is happening in UAT system)

it is happening for every 4th or 5th workflow for in the system, its really getting serious

thank you

bhakti

[pokrakam]

Could you maybe post the chonological view (long button across the top) of the whole WF execution?

Also, I see the deletion occurs 3s after creation, so I suspect something in the process that triggers the workflow kicks off something that cancels it. Is the report being run?

Also, "there isno terminating event to complete the workflow" - are you checking the events at workflow header level? (Header -> version specific -> Events)

[bhakti2]

hi Mike,

below is chronological view

yes the time 3 seconds is varying for different instances, we are studying any pattern

the report is run by user so doesnt seem likely

but we are checking by confirming with the user

also there are some other ways in which the workitem is being completed using funciton module

so we are checking the precisely

there are no events at header level

the culprit seems to be that events have not been used for completing workflows using FM

thank you

bhakti

[pokrakam]

I think your analysis is pretty much on the money.

In particular "also there are some other ways in which the workitem is being completed using funciton module"

--> I think that is your most likely cause. Something special about the process is triggering something which calls one of these.

[anjan_paul]

Hi,

   Variuos reason may be there. You have to check in your design. ForK step complete, Process control step, terminatin event etc .  Check and share    screenshot of design of worklfow step

[bhakti2]

hi Anjan

terminating event - not there for the dialog workitem

parellel fork - there is no parellel fork in the workflow

wait event - no wait event, no parellel fork

deadline  - no deadline or any other process control

im putting the screenshot

thank you

[bhakti2]

screenshots of design of the dialog workitem