ECC 6.0: Issues With Header Event to cancel Workflow

[Rick Bakker]

Hello,

The error "no workflow configuration for..." seems to be a bit of a catch-all.
Is there any other information?

Maybe this SDN thread will be of interest:

https://www.sdn.sap.com/irj/scn/thread?messageID=5166086&tstart=0

regards
Rick Bakker
Hanabi Technology

On 2/19/09, Ramki Maley <rmaley at erpworkflow.com> wrote:
> System ECC 6.0 SAPKA70015 / SAPKB70015
>
> This is a new implementation that recently went live. I have a PO approval
> Workflow in which the last step is a Synchronous Background Task that
> releases the PO after the necessary approval steps. Please note that the
> approval step is not in any Fork and is the very last step. I have defined
> the 'Released' event to cancel the WF at the header level in the WF Builder
> (SWDD) in order to cater to approval outside workflow. When the Released
> event is created by WF-BATCH in the BG step, the WF is complete by the time
> the system tries to process the terminating event,. However I noticed that
> the Released event in some cases is being flagged as in error and put in
> event queue. I switched on the trace for the event and monitored it. The
> event trace sometimes shows 'No Receiver Entered' for some instances (which
> is perfectly fine) and Error for the rest. The message does not show any
> locking conflicts.  Redelivering the event creates the same error message
> (No configuration for workflow WS900XXX version n). Please see the attached
> picture for example entries from WF Log and Event Log.
>
> Any pointers in stopping the Events being written to the queue would be
> greatly apreciated.
>
> Regards,
> Ramki.
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>