Multiple terminating events

Hi All,
Is it possible to have multiple terminating events, what i mean is:
I created WF template with multiple steps. All steps are using the same task (Approve/Reject) and in the task itself I also define a terminating event.
- At the first step, I trigger an event to terminate the step1 and it can complete the first step
- but at the 2nd step, looks like the second workitem doesn't create a new instance linkage for the terminating event. So when I call another event to terminate it, it says no receiver found.
Pls advise, thanks

I don't understand why you are causing an event within the same loop. None of that code makes sense. In general, a dynamic event should be created and registered before the loop with the event structure and the event should be destroyed after the loop is complete.
As far as your other VIs, you should use a feedback node or unregistered shift registers to hold your value for C instead of using a local variable. Look up a Functional Global Variable.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

Purchase Order Workflow - dialog step not receiving terminating event

Hi,
We have a scenario wherein based on the release groups and release strategies, different peope need to release the PO's.
I have been able to develop the workflow for this successfully, but here is where I am facing an issue.
After the PO has been created, based on the release group and strategy, it gets routed to the appropriate 1st approver. On their approval, the PO gets routed to the 2nd approver. Once the 2nd approver approves, the dialog step doesnt get completed and is still waiting for the terminating event. Event trace shows that the event is getting published, but there is no workitem to receive the terminating event. I am not sure why this is occuring for only 2nd approver onwards whereas for the 1st approver, the terminating event is received by the workitem.
I am using start conditions for my workflow to ensure only 1 instance of the workflow is triggered for a rel groups and rel strategy and release code, else I am multiple instances each time an approver approves the PO. I am not sure if the start conditions are causing this issue with the terminating events not being received with the workitems.
Any assistance is welcome.
Thank you,
Satish

From the information provoided it seems you are using PO that is subjected to Release of PO for multiple Release Code and each Release Code Release is being done by one approver. If that is the case then I think the Terminating event should get caught. Please check whether the Terminating event that is getting triggered is specific to the Release Code or not.
Thanks
Arghadip

Multiple life events on a same day

I am using Oracle OAB's SSHR and processing life events related to termination and termination reveral.
I reverse the termination of one employee and again terminated him so he has an open life event. Now his Hire and Term dates are same and so the system gives me error- :User Intervention Required: multiple life events occured on a same day".
How can I process his open life event?
Thanks if you can answer asap.

Hi,
you don't need any technical expertise for it. However, if you are using OAB for managing benefits, I suggest going through with the functional expert to understand he setup there and what life event should take precedence.
Steps : Navigate to Collapse Life Events form (I think it's Total Compensation -> General -> Additional Setup)
Give the winning life event name as whatever life event you want to take precedence (newhire or termination) and provide both the life event names on the right side. Choose the option @Void potentials"(or something like that) for the code and the winning life event date for the date.
Regards,
Vinayaka

BSP Terminating event not triggering

Hello Friends,
We have a scenario, where a BSP application is triggered from a Workflow, for a certain approval, and after the user clicks on Approve button on the BSP Page, the BSP would write to the workflow container using SAP_WAPI_WRITE_CONTAINER and then we call SWF_WSC_CALLBACK_LAUNCH.
This used to work, but after an almost Fatal incident with our system, we are not able to get this to work.
We can see in the workflow log that the container is written, but the terminating event is not triggered, and the workflow doesn't move forward
Is there a setting that we're missing..??
Thanks,
Tat.

Have you tried:
call function 'SAP_WAPI_DECISION_COMPLETE'

Terminating Event Not Triggering

HI Guys,
I have added a custom task to call MRBR screen and set a Terminating Event for this task. It is a Asynch Method.
Through SAP_WAPI_CREATE_EVENT i am calling the terminating event but my task is not getting terminated.
I checked in SWEL i could see evnt log for my terminating event without Receiver type.
Kindly help me to sort out this issue.
Regards,
Dheepak

Hi
Where have you written the code for triggering the termination event?
Also in your task have you created an entry:
WIOBJECT_ID FIPP TerminatingEvent Name.
When everything is done properly in SWEL you would see the receiver as workitem.
Thanks and Regards
Aman

Use multiple day event in Calendar region

I am using a Calendar region in my application. One issue i have run into is, some of my events are multiple-day events, such as a conference. The calendar application does not seem to be able to deal with multiple-day events. It takes one date as the date. There doesn't seem to be any way of dealing with multiple day events. In my case, I have 2 date fields in my table associated with my calendar - a starting date, and an ending date.
Has anyone found a way to deal with this situation? I don't want to have a separate entry for each date of the event. I'd like to be able to use my start date, and ending date fields.
Thanks,
John

Scott,
I took the SQL you used in your trigger and substituted my table names and fields. I am getting 3 errors. Here is what my code looks like after the substitutions (my table names are 'meetings_tbl' and 'meetings_tbl_cal'):
CREATE OR REPLACE TRIGGER ai_meetings
AFTER UPDATE OR INSERT ON meetings_tbl
FOR EACH ROW
DECLARE
l_date_diff NUMBER;
BEGIN
IF UPDATING THEN
DELETE FROM meetings_tbl_cal WHERE m_id = meetings_tbl.m_id;
END IF;
l_date_diff := meetings_tbl.meeting_end - meetings_tbl.meeting_start;
FOR x IN 0..l_date_diff
LOOP
INSERT INTO meetings_tbl_cal
(m_id, meeting_date)
VALUES
(meetings_tbl.m_id, TO_DATE(meetings_tbl.meeting_start + x));
END LOOP;
END;
I am getting 3 errors:
1) PL/SQL: ORA-00904: "MEETINGS_TBL"."M_ID": invalid identifier
2) PLS-00357: Table,View Or Sequence reference 'MEETINGS_TBL.MEETING_END' not allowed in this context
3) PL/SQL: ORA-00984: column not allowed here
Maybe I'm not supposed to substitute ':NEW' with 'MEETINGS_TBL' ??
Thanks for your help!
John

Copy of task TS50000075 and EXTSRV - termination event not working

Hi,
We have done copy of TS50000075 and extended business object EXTSRV to ZEXTSRV
this was done to call function module ISR_CALL_FOR_CHANGE to open up adobe form in edit mode
it works well but the task is not terminated
if termination event is put just like TS50000075 like WIOBJECT, ZEXTSRV COMPLETED then workitem never ends and always stays in inbox
ZEXTSRV COMPLETED event is not triggered when the workitem is completed in the UWL
even if we trigger this event programatically , it does not find receiver and the task stays in-process
if termination event is put as _WORKITEM PROCESSED then it bahves like synchronous task ie even if the workitem is clicked and form is not completed, the workitem ends. so the user can click it only once
also i've tried following
1 - used the function module to complete the workitem in QISR BADI. but the workitem ID is not available inthe BADI. If I try to export it from business object method and import in BADI, it doesnt work
2 - find active workflows and derive workitem id and complete workitem using FM SAP_WAPI_WORKITEM_COMPLETE
     this FM doesnt work , step becomes logically deleted which is not desirable
3 - find active workflows and derive workitem id and complete workitem using other FM SAP_WAPI_SET_WORKITEM_COMPLETD
     work item is complete but there is workflow error - cannot determine succesor node
4 - find active workflows and derive workitem id and change a particular container element
    check this container element in complete workitem condition in activity step of dialog step of workflow of this task-
     workitem stays inprocess
    check this container element in parellel wait step to complete the workitem-
     parellel step executes but fork is not complete, workflow doesnt proceed
kindly help in this matter. the workitem does not get completed at all even if we force complete, workflow goes in error of - cannot determine succesor node.
is there anything specific to the EXTSRV-PROCESS method which makes the TS50000075 task to trigger EXTSRV-COMPLETED and end the workitem ?
help is much needed in this case
thank you,
b

Hi,
You need to see the event in SWEL, otherwise it will never work with workflow. Make sure that the event monitor is on (in transaction SWELS).
I cant see the event in SWEL. The vent monitor is on because if I create event in SWUE, it shows up.
How you actually create the event now?
There is BADI QISR which is always called to handle user action of PDF form. I have written the function modue to create event in the user action
>If i trigger it using funciton module -- then it doesnt find any receivere so it doesnt terminate the task. it is seen in SWEL with no receiver found. do i still need to do commit work ?
You need the COMMIT WORK always if you trigger the event in any program&function or whatever.
ok ill try doing commit work after the create event function module
Test your event with transaction SWUE. Make a test case first in a way that the task is waiting in the inbox/UWL. Then create the event in SWUE. Now, if the task gets completed, you will know that that event itself is working and your terminating event configuration is done properly. If this works, your only problem is in the event creation itself. And for that you need to tell exactly how you create the event. If you do it with your own custom code, use SAP_WAPI_CREATE_EVENT and don't forget to have COMMIT WORK after the function call.
I am doing exactly like you said. but it doesnt work ie even if I create the event in SWUE, the workitem doesnt get completed.
This event is seen in SWEL with no receivere found
I am able to infact set the workitem to complete using WAPI funciton module to complete teh task in the BADI.
but the workflow goes in to error saying , next node cannot be determined
Regards,
Karri

Terminating event 'Created' in ABAP OO context

Hi,
I need a little help here. A lot of times I have used terminating event ‘Created’ for different BOR types – and asynchronous tasks where users are asked to create an object using call transaction from a work item.
Now I am struggling with the same in ABAP OO and have an issue:
The goal is to have a terminating event raised on a custom class - and received by a work item if a customer is fully created, that is the general part, the company code part and the sales area part.
Raising the event is working great. I have put in a class in trx. SWEC together with a function module which set the class as object type if the condition is fulfilled.
Then in trx. SWED I have entered another function module to set the key for class together with object_por-catid = ‘CL’.
Then when a customer master record is created I can see in the event trace that the event is raised with the correct key.
No I want to receive the new object into my asynchronous dialog task. I define the event as terminating event – and in the code call transaction XD01.
When the work item is created I find a waiting event linkage in trx. SWE3 – of cause without key; this is unknown until after creating.
But after executing the workitem and raising the event the workitem does not receive the event and is therefore not completed.
Is this approach not possible in ABAP OO – or do I miss something in the class definition / coding?
The event is defined as public instance – I have not coded any event handler method.
Thanks,
Claus.

Hello Claus,
Interesting question, unfortunately not with a simple answer.
The issue is that you are waiting for an instance event without a key. Your object raises an event with a key => No match.
If you raise the created event without a key, you won't be able to match up two near-simultaneous creations with their corresponding work items. Same thing if you wait for a static event.
So how does SAP do it with BOR events? By breaking the rules of course!
They do some hidden trickery to bypass this problem by doing an 'Export to Memory' of the work item ID, and the CREATED event raising code bypasses the usual event linking mechanisms and looks for it's creator by retrieving the memory variable. I don't have the exact spots of code in my head, but a bit of debugging should find it.
So what can you do? Given that you have full control of the class you could do something similar and maybe also create some kind of temporary key consisting of the Work Item ID and raise an event with that, or you could maybe skip the transaction concept completely and run the create GUI entirely within your WF step - maybe a custom screen gathering the initial data and then create the object via BAPI. Time to get creative!
Hope that helps,
Mike
Edit: Or you could do the quick and dirty solution and just use the BOR events for the step and instantiate the class during the binding back to WF...

Terminating event and abap oo class

Hi, gurus,
I 'd like to know how the terminating event works.
for example, i define a custom abap oo class (which has been implemented the interface of IF_WORKFLOW), and i want to use it as the terminating event of a standard task.
could you please tell me how does it works?
1. there must be an instance defined in the container of the task?
which must be instanciated in the run time?
2. then in another abap report, i simply raise the event defined as the terminating event, using the same key, then the pending task will be terminated?
could you pls provide more information on this ?
thanks and best regards.
Jun

Hi Jun Zhang,
An event that is used to stop a workflow or task, or change the behavior of an already started workflow is called Terminating Event.
If the event linkage is active and the linkage rules are satisfied, the status of the work item is set to COMPLETED.
Defining Event Linkage Terminating event linkage consists of 2 parts.
Type linkage which specifies business object type, event name, generic name for event receiver (WORKITEM for terminating events of tasks or EVENTITEM for wait for event steps)
Instance linkage which identifies the particular receivers (I.e. work item Ids) per object instance.
Terminating event linkages can be seen in SWE3.
For terminating events, along with Business object and Event a Container Element should be specified that holds the Object Instance.
Terminating Event for Workflow is available from Release 6.10 only. This is defined in Basic Data of Workflow Builder.
Binding Definition is optional for Terminating Events. Binding can be defined b/n event container and workflow container to pass event information to the workflow if required. That is the only way of passing information from an asynchronous method to the task that started it.
Thanks and Regards,
Prabhakar Dharmala

Use abap class event as terminating event

Hi,
The class is say ZCL_WF_CLASS and the event END_WF.
What needs to be done to have this event used correctly as a terminating event of a workflow? Does this event require a parameter to hold the workitem id (or workflow id), as currently this event has no parameters?
Previous developer has developed the class and event and installed as a terminating event but the workflow is going into error not terminating correctly. I believe the incorrect development of the event and/or its use in the workflow is the issue. Note that nowhere is this event currently raised in any code of the workflow.
Cheers,
Ross

Hello,
Unless I'm mistaken, a terminating event for a workflow is just like any wait-for event in a workflow.
It can be based on any object or class and it can be used in various ways - to terminate a branch or terminate the workflow, for example.
The workflow listens out for the event and checks if there is a matching key. You could base it on the key of a workflow object but it makes more sense to base it on an object or class that's used in the workflow - e.g. the POSTED event of an object would be used to terminate a workflow seeking approval for the posting of an object.
It definitely won't work if the event has no parameters. I guess if you do base it on the workflow object then you would use the top-level workitem id. Try it with a test workflow and SWUE to generate the event.
regards
Rick Bakker
hanabi technology

ECC6.0 WebDynpro(ABAP) - raising terminating event

Hi, in ECC6.0 I have a custom WDA application with a custom workflow. The workflow is launched via an event that is raised in the WDA application. However, at one point workflow sends a link to one of the WDA pages, whereby the user clicks a button which raises what should be a terminating event for the workflow task. However, while this event is raised, as confirmed in SWEL, it doesn't terminate the task. The event is raised through a WDA assistance class. The object type, event and object key are all being set properly during the raising of the event. Viewing the event in SWEL confirms the proper setting of the key fields. So why isn't the step terminating?
Thanks in advance,
Kevin

Hi,
If the object that is waiting for event has no instance, the task will not be terminated when the event is created in the system (As I said). So now the reason is clear for you.
>The event is raised through a WDA assistance class
I am not sure what you mean by this. You raise the event from the WDA assistance class? Or you raise an event for the assistance class? (Or perhaps both?).
If you raise the event for the assistance class, you should have an instance of that class in the workflow container (which you would then bind from workflow container to the task container). So, now the question is: do you have an instance of the assistance class in the WF container (when you look it from log)? Or is it initial also?
Actually I don't really even understand how you have managed to combine the WDA assistance class and WF class? How do you actually start the workflow (with which kind of event)? Whatever event it is, it should most likely instantiate some class/object in the workflow. Then in your problematic task you should most likely use this same class in the terminating event (unless there is something really fancy in your workflow).
Regards,
Karri

Read workitem Container Value in Terminating event Check Function Module

Hi
I have some problems reading work item data / values of a work item container element in a check function module on a terminating event Do any of you know if this is possible, and if so, how its done ?
In My scenario I have created a multiline approval step for my business document, one task pr Line Owner. The Event Approved is defined as a terminating event for this task, and the line owner is passed to the task container.
Now, when I raise the event, with the line owner as an event parameter, I would like to check if the line owner on the raised event, matches the line owner in the task container in question in a check fm. But here I faced the problem, that only event data, and not work item data, are passed to the Check Function module.
Regards,
Morten Nielsen

Hello Morten, hello Arghadip,
in the instance linkage's check function module (entered via transaction SWEINST) you'll have the workitem-id in the system event parameter EVTRECEIVER_ID
With this number you can use the frame work in order to read the work item container.
This is a sample coding, how you access the correct work item container using SAP Enterprise and it's new OO frame work, which checks on the terminating event of BUS2105.Released the correct release code for a work item.
INCLUDE <cntn01>.
INCLUDE <SWFCNTN01>.
INCLUDE RSWEINCL.
*** Read workitem instance and container from event
       DATA: wi_id            TYPE swwwihead-wi_id.
       swc_get_element EVENT_CONTAINER evt_receiver_id wi_id.
       IF sy-subrc <> 0.
          MESSAGE E015(ZPREL) WITH evt_receiver_id
                                       RAISING wrong_call.
       ENDIF.
       DATA: lv_wi_handle    TYPE REF TO if_swf_run_wim_internal.
       DATA: ls_context      TYPE sww_wimctx.
       DATA: lv_wi_container TYPE REF TO if_swf_cnt_container.
*    - set context
       ls_context-do_commit = ' '.
       ls_context-called_btc = 'X'.
       ls_context-exec_user = sy-uname.
       ls_context-fbname     = 'Z_CHECK_RELEASE_CODE'.
       CLEAR lv_wi_handle.
       CALL METHOD cl_swf_run_wim_factory=>initialize( ).
       CALL METHOD cl_swf_run_wim_factory=>find_by_wiid
               EXPORTING
                  im_wiid             = wi_id
                  im_read_for_update = ' '
*                 im_enqueue_owner    = fb_name
*                 im_wait_for_enqueue = 'X'
                  im_context          = ls_context
               RECEIVING
                  re_instance         = lv_wi_handle.
*** This check is only done for workitem linkage TS90100081
       IF lv_wi_handle->m_sww_wihead-wi_rh_task <> 'TS90100081'. "#EC_SYNTEXT
          EXIT. "Let event pass, as this is an instance linkage to another workitem
       ENDIF.
       DATA: releaseCode_wi        TYPE t16fc-frgco.
*    - read releaseCode from workitem container
       lv_wi_container = lv_wi_handle->get_wi_container( ).
*    - perform binding event container -> workitem container
       swf_get_element lv_wi_container 'RELEASECODE' releaseCode_wi.
      DATA: e             TYPE REF TO cx_swf_run_wim.
      CATCH cx_swf_run_wim INTO e.
         RAISE WORKFLOW_RUNTIME_ERROR.
   ENDTRY.
*** From here on, the variable releaseCode_WI hold the
*** container element RelaseCode of the work item, that
*** is going to be terminated...
*** Further coding from here as appropriate...
Best regards,
Florin

Terminating event -- No active receiver found

Hi -- on an Integration project I just need a workitem that stays active until explicitly closed via an event..
It's easy enough to create a triggering event which starts a process.
I've followed all the rules (as far as I can see) to create a terminating event but it doesn't work.
I've created a test Bus Obj ZZJIMBO which simply has a key of the SAP user ID.
I've defined 3 events
STARTSYN ====> Synchronous
STARTASY =====> Asynchronous
FINISHED ======> terminating
Using SAP_WAPI_CREATE_EVENT the STARTSYN and STARTASY are triggered and the relevant processes start - both for the synchronous and asynchronous tasks.
However on raising the FINISHED event the system just errors with NO Active receiver found.
All the binding etc is fine and SWU0 doesn't find any problems.
Looking at the instance table (transaction SWE3)
I see that the eventid is the same as the current workitem but the object key is empty
object key <empty>
eventid    000000250100
The only possibility I can see is that my Business object doesn't really have "instances" like say a sales order as it only exists at run time.
Would I have to say trigger the event finished using something like the Work item itself which does have a valid individual instance -- I can extend the WORKITEM bus obj and add an event FINISHED to it instead.
I can get the workitem id via the container so that shouldn't in theory be a problem to "instantiate" the Workitem (or ZWORKITEM) business object.
I really hoped to have all the events in the SAME business object however.
Any ideas
Cheers
jimbo

Hi James.
1. Yes, I think the workitem in runtime would expect the triggering event should be from the instance of the object either from
        a. standard workitem relevant obejct instances like _WORKITEM, ATTACHOBJECTS, RULERESULT
       b. or the associated BO in the task i.e WIOBJECT_ID
2. However as you say >>I really hoped to have all the events in the SAME business object however>>. I can suggest the following
       a. create a parallel fork to the step which is creating your workitem
       b. In this parallel branch create step 'Wait for Event; and refer it to your ZZJIMBO.FINISHED.
      c. define necessary branches required to complete the fork as 1. meaning, if any one of the branch ends flow will continue to next step in main workflow.
So, when the event ZZJIMBO.FINISHED is raised with the correct instance which was used in workflow. 'Wait for event' will receive it and this branch will end and eventually other branch will get logically deleted. You can put some flag in the 'Wait for event' branch using which u can understand whether the workitem is completed in normal way or through exeption.
Hope this helps !!
Regards
Krishna Mohan

Terminating Event Terminating all work items

System : Solution Manager
Business object : BUS2000116
1. I have multiline container element for Agent.Agents are Dynamic not static.Approval from all agents is required.
2. Work flow desing
a.Defination of Agent : ABAP Dictionary type SWP_AGENT with Multiline
b. FORK with two steps , One step Required
c. One part of FORK has WAIT FOR EVENT "REJECTED" Event and other has Activity with Agent "_underline []Agent()Index of: Agent _underline"
d. Under the Miscellaneous tab Multiline line element Agent.
e. Terminating event for this activitiy is APPROVED Event, which I have defined in business object.
Let say in Program [Custom tab for standard transaction CRMD_ORDER] I have three agents I am getting Three work item in the workflow log with different Agent.
PROBLEM:
When any user open the workitem from SAP Inbox and APPROVE it[ Custom button on standard screen CRMD_ORDER], Program raises Event APPROVED by using Function Module "SWE_EVENT_CREATE". But it set other two work items also in Completed status.
concatenate 'US' sy-uname into v_creator.
        call function 'SWE_EVENT_CREATE'
          exporting
            objtype                       = c_objtype    "BUS2000116
            objkey                        = objectkey    "Key field Which is GUID from CRMD_ORDERADM_H table
            event                         = gs_event      "APPROVE"
           creator                       = v_creator
            take_workitem_requester       = 'X'
          START_WITH_DELAY              = ' '
          START_RECFB_SYNCHRON          = ' '
          NO_COMMIT_FOR_QUEUE           = ' '
          DEBUG_FLAG                    = ' '
          NO_LOGGING                    = ' '
          IDENT                         =
         importing
           event_id                      = v_eventid
           receiver_count                = v_count
        TABLES
          EVENT_CONTAINER               =
         exceptions
           objtype_not_found             = 1
           others                        = 2
        if sy-subrc <> 0.
          message id sy-msgid type sy-msgty number sy-msgno
                  with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        endif.
Please let me know what could be the reason?
Thanks in Advance.

I think instead of using a event you can use a container element. You want to make sure that the users performs the approving action properly. If the user does that inside your code you set this container element as X. You pu the approval step inside a loop that checks whether the container element is X. Also another important thing you need to put the parallel approval step along with the loop inside a subworkflow.
Thanks
Arghadip

Terminating Event with Decision Step

Hi,
In our purchase requisition approval workflow, I need to have a decision step in which to prompt approver to either approve the req. or reject the requisition. In this decision step, I need for it to have terminating events for "SIGNIFICANTLYCHANGED", "RELEASE", "REJECT" and "RESET".
First, I copy the generic decision task 8267 to my my own custom decision task. Then I added a BUS2009 in the container, releasecode and other needed elements. In this custom decision task, I was able to add these terminating events that has been defined in the BUS2009. I was able to setup binding, except the one binding
Terminating Event ->   Task
&_EVT_OBJECT&      ->   &_WI_OBJECT_ID&
Since the &_EVT_OBJECT& for the terminating event is BUS2009. And the custom decision task &_WI_OBJECT_ID& is DECISION business object. They're incompatable business object. So I replaced that binding with
Terminating Event     -> Task
&_EVT_OBJECT&    ->   &PURCHASE_REQ&
After all the configuration has been setup. I created a new purchase requisition. Upon the RELEASESTEPCREATED event, it create a custom decision workitem in my agent's inbox. When I triggered the "RELEASE" event, it is however not terminating my custom decision workitem. The workitem still sits in the agent's inbox waiting to be execute.
Is it possible to setup terminating events for decision step? Any kind of suggestions or inputs would be greatly appreciated.
Thank you.
Jennifer Tran
System Analyst

I will suggest you to create a fork with 2 parallel branch and 1 necessary branch. Put the approval step in 1 branch and the wait for Release step event in another branch in this way you can suffice your requirment.
Thanks
Arghadip

Multiple terminating events

Similar Messages

Maybe you are looking for