ECC 6.0: Issues With Header Event to cancel Workflow

Ramki Maley rmaley at erpworkflow.com
Mon Mar 2 18:10:46 EST 2009


Issue resolved by activating Event Queue for the header event instance 
linkage.

Cheers,
Ramki.


Sheldon Oxenberg wrote:
> Alternative to putting a wait step (eg  requested start deadline of 1
> minute in a dummy step) just before the end of the workflow,
> you might also try putting a "wait for event" step (eg  the same PO
> Released event) just before the end of the workflow.
> 
> Regards,
> SHELDON OXENBERG
> CSC
> 
> 
> 
> 
>                                                                            
>              Rick Bakker                                                   
>              <rbakker at gmail.co                                             
>              m>                                                         To 
>              Sent by:                  "SAP Workflow Users' Group"         
>              sap-wug-bounces at m         <sap-wug at mit.edu>                   
>              it.edu                                                     cc 
>                                                                            
>                                                                    Subject 
>              02/23/2009 04:10          Re: ECC 6.0: Issues With Header     
>              PM                        Event to cancel Workflow            
>                                                                            
>                                                                            
>              Please respond to                                             
>                "SAP Workflow                                               
>                Users' Group"                                               
>              <sap-wug at mit.edu>                                             
>                                                                            
>                                                                            
> 
> 
> 
> 
> Ramki,
> 
> If I understand correctly, the last step in your workflow creates an
> event which will terminate that very same instance of the workflow.
> 
> You say that "the WF is complete by the time the system tries to
> process the terminating event" and also "the errors occurs only when
> the event is raised by the Workflow step (which calls the PO release
> BAPI)."
> 
> Although you said in your first post that you didn't detect any
> locking conflicts, that seems to me to be the most likely cause here -
> both the event and the workflow itself (finishing normally) are trying
> to terminate the workflow instance at the same time and that could
> lead to the workflow being placed in a state such that even
> subsequently generated Released events will have a problem.
> 
> Is there any way to call that BAPI so it doesn't generate the Released
> event?
> 
> Have you considered putting a wait step (eg requested start deadline
> of 1 minute in a dummy step) just before the end of the workflow?
> 
> regards
> Rick Bakker
> Hanabi Technology
> 
> On 2/23/09, Ramki Maley <rmaley at erpworkflow.com> wrote:
>> Rick, the errors occurs only when the event is raised by the Workflow
>> step (which calls the PO release BAPI).
>>
>> Regards,
>> Ramki.
>>
>> Rick Bakker wrote:
>>> 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
>>>>
>>> _______________________________________________
>>> 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
> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug



More information about the SAP-WUG mailing list