ECC 6.0: Issues With Header Event to cancel Workflow

[Rick Bakker]

Hello,

If I understand correctly, this error only occurs sometimes. Is there
any link that you've noticed between the cases where it happens? Does
it only happen when the event is generated outside the workflow, for
example?

regards
Rick Bakker
Hanabi Technology

On 2/21/09, Morris, Eddie <eddie.morris at sap.com> wrote:
> Hi Ramki,
>
> Since it is standard the parameter START_RECFB_SYNCHRON will not be
> used, just sometimes in custom code the parameter is set by accident so
> I thought it might be worth a try.
>
> Using the event queue sounds like the best option here.
>
> Regards,
> Eddie
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Ramki Maley
> Sent: 20 February 20, 2009 17:36
> To: SAP Workflow Users' Group
> Subject: Re: ECC 6.0: Issues With Header Event to cancel Workflow
>
> Eddie,
>
> I debugged the PO Release BAPI and verified that Function modele
> SWE_EVENT_CREATE is called with parameter START_RECFB_SYNCHRON set to
> Space.
>
> Regards,
> Ramki.
>
>
> Ramki Maley wrote:
> > Hi Eddie,
> >
> > Thanks for the response. I am not raising the event. This is standard
> > SAP 'Released' Event for PO (BUS2012). I probably should activate the
> > Event Queue for this event in order to avoid any conflicts.
> >
> > Regards,
> > Ramki.
> >
> > Morris, Eddie wrote:
> >> Hi Ramki,
> >>
> >> Do you raise the RELEASED event via custom code? Do you use
> >> SWE_EVENT_CREATE?
> >>
> >> If you raise the event via SWE_EVENT_CREATE please make note that the
> >> Function module SWE_EVENT_CREATE should not be called with flag
> >> START_RECFB_SYNCHRON = 'X'.
> >>
> >>
> >> Regards,
> >> Eddie
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf
> >> Of Ramki Maley
> >> Sent: 20 February 20, 2009 3:04
> >> To: SAP Workflow Users' Group
> >> Subject: ECC 6.0: Issues With Header Event to cancel Workflow
> >>
> >> 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
> >
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>