Start form triggered by call transaction hangs in ready status

[Former Member]

Hi,

I have a custom workflow that is triggered by a start form, which obviously has a transaction code assigned to it (ZTF_WS....).

When executing the start form manually the workflow proceeds as expected.

However, I am trying to execute the start form transaction via a "call transaction '....' using [bdcdata].... construct.

Sadly the workflow hangs, although it gets triggered ultimately by the scheduled job RSSWERRE or can be set active via transaction SWIA.

The RSSWERRE triggering is probably good enough but it would be nice if things were a bit more immediate.

Any ideas?

Thanks.

Nigel.

[Former Member]

Do you explicitly trigger the workflow in your custom transaction or do you raise an event? I have a feeling this might be happening because the workflow template (WS9...) is not set as a General Task.

[Former Member]

Thanks, Abdullah.

The trigger for the workflow is a start form, which SAP assigns a transaction code to. The task is general. When starting the transaction (i.e. the start form) in the foreground all is well, but when I try and initiate it via call transaction 'ZTF....' from my custom program (as explained in my initial query), the workflow starts properly but hangs in READY status.

I have managed to get round this by following the call transaction in my custom program with a call to function SAP_WAPI_EXECUTE_WORKITEM which kicks the workflow into gear, so all is well.

All that is left is a curiosity re. the ready status issue, but it isn't worth keeping this discussion subject open for that.

Best regards.

Nigel.

[former_member185167]

Hello,

"although it gets triggered ultimately by the scheduled job RSSWERRE"

That means there was a temporary error, which usually means there is a locking problem.

BDCs can be problematic, especially when called in background mode.

regards

Rick Bakker / hanabi technology

[Former Member]

Hi,

I'd still be interested to know why the workflow is hanging when the start transaction / form is 'called' rather than executed manually, but meantime I've fixed the issue by picking up the most recent subflow type in READY status for this workflow from table SWWWIHEAD and using the workflow identifier as input to function module SAP_WAPI_EXECUTE_WORKITEM. Anything that slips through the net for wahtever reason can be picked up by the scheduled RSSWERRE.

Cheers.

Nigel.