Workflow WS00000038 not complete

[holger_salt]

Hi,

I am setting up the PR workflow WS00000038. Workflow is triggered and the first task (workitem to liberate the pr) is just fine. The correct agent is found and receives the workitem in his inbox.

But when the agent executes the workitem (Task TS00007986) and releases the purchase requision, the workflow does not continue to the next step and comes to an end.

The exits in this task in the workflow are events which are triggered (e.g. BUS2009.REJECTED, BUS2009.RELEASED)

All the following tasks already are set as general tasks, also users were assigned through customizing.

The events are visible in SWEL, why does the workflow not react to them? It reacts to the initial event BUS2009.RELEASESTEPCREATED, so the settings for event receiving in general seem to be allright in the system.

Any help is appreciated. thanks

[holger_salt]

Thank you to all that tried to help me.

Problem solved: Workflow does come to an end now and finishes in status "complete".

It seems, that the workflow customizing (SWU3) had not been fully activated. My guess would be that there is a correlation with " configure RFC destination" or "backgroundjob for event queue". Was the first workflow pattern on the system and SAP Basis had not configured SWU3 before...

[Former Member]

Hi Holger,

You don't have to use event queue if you're not expecting tens of thousands of events at once.

I always leave it out when configuring new systems for workflow.

Kind regards, Rob Dielemans

[holger_salt]

There is no error message whatsoever. The purchase requisition is rejected in this case and triggers

WS65400027.

Graphical protocoll:

Neither of the outcomes is used, not when rejected, not when released.

And this rejection was already acknowledged by workflow WS65400027, that workflow shows status completed.

[Former Member]

Hi,

It looks like the workflow isn't working correctly. Activate the event log, SWEL and check if the terminating event occurs correctly. Next check in the workflow builder if these events are one of the terminating events, also check ST22 to see whether a short-dump occurs when it tries to terminate the workitem, maybe a badi implementation is screwing up standard behaviour.

If no one has tinkered with the standard workflow, nor with the behaviour (badi/exits/enhancements) then I suggest to execute function module SWD_WFD_REPLICATE_FROM_9999 and enter the standard workflow template in IM_TASK, in rare cases a transport can corrupt the definition of the workflow. If this does not help, then you should raise an error message with SAP.

Kind regards, Rob Dielemans

[anjan_paul]

Hi,

Please share the screenshot of techincal workflow log.

Thanks

[holger_salt]

Hi,

thanks for your answer. Yes, there always starts a new workflow, after a release.

But after three releasesteps the pr is finally released and I still have three active workflows (i.e. not in status completed, but started). Shouldn't they be in status complete after the pr is released?

The first task to release the pr (TS0007986) has four exits, all are ending events, like BUS2009.REJECTED. Neither is taken by the workflow.

[Former Member]

Hi,

What is the desired next step? Ususally these standard workflows only exist per releasestep, so if it is released and a new releasestep is created then a new workflow for this release will be started.

Please check your release strategy to find out if how it should behave.

Kind regards, Rob Dielemans