Terminating event in synchronous method.

Hi,
I am not using any BOR and its event in start event tab, but i want to use terminating event within a task, so can i do this?
Within this task i am using a BOR and its method, this is Synchronous method.
Now i want to use one terminating event also, so that this task completes either by successfully completing the method or by using terminating event.
Can i trigger this event from non-sap system?
Can i set container element from non-sap system? If yes how?
Thanks in advance,
Amar

I am not using any BOR and its event in start event tab, but i want to use terminating event within a task, so can i do this?
Ans. Yes...
Now i want to use one terminating event also, so that this task completes either by successfully completing the method or by using terminating event.
Ans. This is what a Job of Asynchronous task .. so create it as asynchronous...
Can i trigger this event from non-sap system?
Yes ... Use SAP_WAPI_CREATE_EVENT...
Can i set container element from non-sap system? If yes how?
Yes .... SAP_WAPI_WRITE_CONTAINER
Regards
Gautam

Similar Messages

Problem related to terminating event

Hello Friends,
A User has a workitem in his inbox which is in his inbox even after execution because terminating events defined on task have not taken place. How can I check that why terminating events have not taken place?
Thanks and Regards,
Vittalprasad

Imthiaz,
SAP exactly says the same which I said.
here is excerpt:
This function is used to define the terminating events of the task.
Tasks that refer to an asynchronous object method must always be defined with at least one terminating event. At runtime, the relevant work item is only terminated if one of the defined terminating events occurs.
Tasks that refer to a synchronous object method can also be defined with terminating events. At runtime, the relevant work item is generally terminated when the synchronous method has been successfully executed. But the work item is also terminated if one of the defined terminating events occurs.
I never mean to say that you are wrong or any one is wrong.
Like you said testing would be best.
Cheers
Jai

Terminating Event for BUS2017 Custom Method

Dear Experts,
I have an issue with the Terminating Event of the Workflow for BO : BUS2017. The event is getting triggered but receiver is not being picked.
I have created two events GR_103 and POST_105 in the Custom BO ZBUS2017 by delegating it to BUS2017. GR_103 is the triggering event for my workflow which I have triggered in the POST_DOCUMENT Method of the Implmentation for BADI : MB_MIGO_BADI.
GR_103 is triggered while doing MIGO (Goods Receipt) for Movement Type 103. My Workflow is triggered perfectly and then I have used a Dialog Asynchronous Task in which I have called the MIGO Transaction for Releasing the GR Blokced Stock using the Movement Type 105. I have created a Custom Method POST in the BO ZBUS2017 and I have used the FM: MIGO_DIALOG to call the MIGO. I am trying to raise the POST_105 event in the Method MB_DOCUMENT_BEFORE_UPDATE of the Interface IF_EX_MB_DOCUMENT_BADI. I have defined the Terminating Event for the asynchronous Task as POST_105.
Now the event POST_105 is triggered, but SWEL says 'No receiver entered'. Even the SWEINST shows the object data as the current Work Item along with Object Key, but still receiver not picked. When I try to trigger the same event in a test report by using call transaction, then the event triggers and work item gets completed without any issues.
Please advise.
Below is my terminating event code.
READ TABLE xmseg INTO wa_mseg INDEX 1.
CONCATENATE wa_mseg-mblnr wa_mseg-mjahr INTO l_objkey.
IF wa_mseg-bwart = '105' .
    CALL FUNCTION 'SWE_EVENT_CREATE'
      EXPORTING
        objtype           = 'BUS2017'
        objkey            = l_objkey
        event             = 'POST_105'
      EXCEPTIONS
        objtype_not_found = 1
        OTHERS            = 2.
ENDIF.
Regards,
Raju.

Have a COMMIT WORK after the function call. (At least test it - I am not sure if it will have some effects in your BADI - at least you will know whether the issue is about missing commit).
And please use SAP_WAPI_CREATE_EVENT instead of the old function you are using.
Also, make sure that the events will look exactly the same in event monitor SWEL when triggered from your code and when using test tool. Maybe there is some minor difference/mistake (object key, etc.) that you haven't noticed.
Regards,
Karri
Edited by: Karri Kemppi on Feb 7, 2012 8:14 AM

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 to Event Queue due to Work Item Lock

I have a dialog workflow task based on an asynchronous method defined with a terminating event. When the user executes the work item, the method generates the terminating event (via a V2 change document) but the work item is enqueued (locked) by the same user (locked when they execute the work item from SBWP) and therefore the terminating event goes into error and is placed in the event queue. The background job which processes the event queue does not redeliver the event so it stays in the event queue and the work item fails to complete. Other than dequeing the work item lock myself with a function call how do I get around this catch 22?

Hello Martin,
Actually, the locking happens whether I have the task as asynchronous or synchronous. The problem is the timing. If the user does not release the lock (by backing out of the dialog which is executed) prior to the terminating event attempting to enqueue and complete the work item then the event goes into error and is inserted into the event queue (and lingers there indefinitely, almost). Another issue with the asynchronous approach is that even if the user backs out of the dialog before the event actually attempts to complete the work item they will still see the work item in the inbox unless they click the refresh button when they get back to the inbox.
I have changed the task to synchronous but here is my scenario and another question.
The process being workflowed is the approval of service entrysheets (similar to an invoice if you are not familiar with External Services). In our process, there are a large number of documents being created and requiring approval by particular approvers. It is a normal scenario for an approver to have, lets say 25 documents in his inbox awaiting approval. It was not practical for him to have to navigate back and forth between his inbox and the approval task screen. Therefore, I give the users the option of (when executing a work item) having all the documents in his in-box (for this particular task) be presented in an approval list screen. They can then do a mass approval of the 25 documents with 1 click and 1 navigation. This list screen is also available to be executed outside workflow via a tcode. So, when the user executes the mass approval (either from the inbox or outside workflow) the work items are terminated via the terminating event assigned to the approval task.
A couple of issues remaining:
1) Given my example of 25 work items (user executes 1 work item from in-box
and I displayed all 25) being approved, when the user returns to the in-box, the 24
items remain in his inbox until he clicks the refresh button since these were not actually "executed" from the workflow engines point of view. However, these were terminated successfully because they were not "locked".
<b>Question:</b> Is there a way (user exit?) to trigger the inbox refresh automatically.
2) Now, the issue with the actual work item which the user executes from the inbox. As I mentioned, the work item is locked as soon as the user executes it and is not released until they back out of the dialog or logoff. So, here is what happens: If the terminating event is sent before the lock is released the event is sent to the event queue. If they then back out back to the in-box, its OK since I put some code in the SWO1 object type program (rememeber, its now synchronous) which will determine if they did the approval/rejection and the work item will complete and the event in the event queue will be deleted the next time the Event Queue Background job runs (it deletes any events for work items already in COMPLETED status). However, lets say they simply log off rather than backing up to the in-box or they don't do anything and are eventually logged off by timeout. In this case the code in the object type program to determine if the approval/rejection was done does not get executed (control does not return to the object type program) and the work item remains in "STARTED" status and remains in the users inbox and the event is in the event queue. So, now we have a work item that should be completed still sitting in the users in-box and the terminating event in the event queue. So the next time the user goes to their inbox the work item is still there. The interesting thing is that though this may be confusing to the user, if they then attempt to execute the work item, they will get a message: "Work item currently being completed by event" (Message SWF_RUN 644) and the event sitting in the event queue gets redelivered and completes the work item. To alleviate this problem I was thinking of adding a call to SAP_WAPI_WORKITEM_COMPLETE in the approval list screen after they do the approval but I'm guessing it wont work since it probably will try to enqueue the work item and it will still be locked.
Hopefully you haven't nodded off reading this rambling note...
Thank you,
Bob

Warning: "No terminating events defined for the task used"

Dear all,
I created a task with ABAP class and method as its object method. This task is a background task. The ABAP class inherits the IF_WORKFLOW interface but doesn't implement any method of the interface.
When I try to confirm the task settings in transaction SWDD, a message shows up "No terminating events defined for the task used" and I cannot continue the work. Does anybody have any idea what I should do?
Thanks + Best Regards
Jerome

Hi Jerome,
If you set a background task in your workflow, and if it is asynchronous, then you need some way to tell the template if it is finished and what happened. In this case you set terminating events - that is events which are published in the system as a result of your method (ie document.posted etc).
Either use a synchronous method for your task or set appropriate terminating events in your task setup.
Regards
Gareth

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

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

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

Regarding terminating events in workflows

Hi,
I know that terminating events are used with asynchronous methods. Can anyone tell me, why do we need to do so????
Thanks and Regards,
Ravi Varma

Hi
Check the links below
Workflow automates the steps and activities in a business process according to predefined procedures and rules.
Workflow presents information and documents to the appropriate knowledge worker or agent (another entity such as a program) to make a decision or perform an activity.
Workflow tracks each and every step in the process flow and maintains an ongoing status.
Workflow also collects and reports all of the metrics associated with the execution and completion of the process.
Check the below links u will get lot of info..
http://www.sap-press.com/product.cfm?account=&product=H950
Workflow
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
For examples on WorkFlow...check the below link..
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
Go through the following links on FORK :
http://help.sap.com/saphelp_nw04/helpdata/en/24/e2283f2bbad036e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8d/25f1e7454311d189430000e829fbbd/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/c5/e4a930453d11d189430000e829fbbd/content.htm
http://www.insightcp.com/res_23.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
For more reference on workflow: http://****************/Tutorials/Workflow/Workflow.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/04/9277a346f311d189470000e829fbbd/frameset.htm
Check these links.
http://www.sapgenie.com/workflow/index.htm
/people/ginger.gatling/blog/2005/12/01/link-workflow-business-objects-to-your-collaboration-tasks
http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm
http://www.sap-press.com/product.cfm?account=&product=H950
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
Workflow
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
For examples on WorkFlow...check the below link..
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
For examples on WorkFlow...check the below link..
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
Workflow tutorials with step-by-step and with screenshots are available at http://www.****************/Tutorials/Workflow/Workflow.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/42/c14a9b55103116e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/e4a930453d11d189430000e829fbbd/frameset.htm
http://www.sapgenie.com/workflow/
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2857887
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2855919
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2735228
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
Debug a workflow.
This has a step by step procedure :
http://fuller.mit.edu/workflow/debugging.pdf
www.erpgenie.com/sap/workflow/debugging.htm
http://www.erpgenie.com/workflow/debugging.htm?2b5de440
Workflow tutorials with step-by-step and with screenshots are available at
http://www.****************/Tutorials/Workflow/Workflow.htm
http://www.sapgenie.com/workflow/
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2857887
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2855919
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2735228
http://www.sapbrain.com/TUTORIALS/TECHNICAL/WORKFLOW_tutorial.html
Reward points for useful Answers
Regards
Anji

Terminating event deactivation

Hi ,
There is an terminating event of a task in a workflow builder which is activated .
Can someone please suggest some tcodes from where the terminating events are displayed and can be deactivated .
Also please let me know does the tcode SWETYPV display only triggering events
Thanks
Ankita

Hi there
Your question is a bit unclear. What do you want to do exactly.
For example say you have defined a task Change sales Order as ASYNCHRONOUS. This means that the workflow task won't complete until you raise a terminating event -- this event will be defined in the workflow.
So say a user OUTSIDE the workflow changes a sales order via VA02 you (or the transaction) needs to set an event SALES ORDER CHANGED.
This can be done via Change docs SWEC (not my favorite way but can be useful), or for a lot of standard SAP business objects via SWE3.
If you are lucky you might find an event already defined in the appropriate business object (look at transaction SWE3 as stated above) in which case just call the method you want to execute when the terminating event is raised by the transaction.
For custom (i.e non SAP standard transactions) you can raise an event quite easily using Function Module SAP_WAPI_CREATE_EVENT.
So when the action occurs that you want to use to terminate the workflow just include that FM in your method in a Business object or class.
Without knowing what you want to do it's a bit hard to be more helpful - if you explain the problem more clearly we can give some code examples.
Cheers
Jimbo

Task 20000051 : Terminating Event INPUTFINISHED

Hi,
I am using standard task 20000051 which has business object type IDOCAPPL with a terminating event INPUTFINISHED. Question is: even after the IDOC is processed successfully and set the IDOC staus to 53, workflow is still "In Process" status. What needs to do be done to set the WF automatically status to complete? Currently I set the status to "logically delete" which is a painful action every time.
Thanks in advance for your help.
Best, Nagarajan

Actually don't know. This is the standard task and being using as it is. Where do I see that the method is used to set the IDOC status.
Also I found that terminating event is getting triggered, I see the terminating event in the log. The only issue is WF is "In Process" status. What to do to set the status to complete automatically.
Here is what happened:
(1) IDOC went into error which triggered WF
(2) IDOC content was changed
(3) IDOC was re-processed successfully with IDOC status 53
(3)Terminating event was triggered
WF status still "in process". What to do?
Thanks
Nagarajan

Issue with Terminating Event - Reg

hi Gurus,
This might be a simple issue, but am not getting hold on a simple solution for my issue.
I'm working on ECC 6.0.
I have a custom workflow in which I have step1(A dialog task - Asynch) with a terminating event "COMPLETED" and then step 2 (A background task). once step1 is completed by user A, i am sending this WIACTUAL_AGENT to the step 2 in modifying some custom table data.
My issue is if user A finished the task(step 1) manually, then also the Term. event COMPLETED is getting triggered and hence the work item in user A's Inbox is disappearing. And then it's picking up user A as WIACTUAL_AGENT and sending to step 2. But, i need to distinguish or some how find out if the Termin. event occurred thru' execution of the workitem or manually performing the job. I looked into the workflow log for both the cases, and i don't find any clue with which i can differentiate that the Termin. event occurred thru' executing witem Vs. performing manually.
Anybody has any idea on how to find this out. Coz, depending on whether the action is done manually or thru' witem, i 'll be modifying the custom table data accordingly. Currently, for both the cases, when the Term. event occurs, the WIACTUAL_AGENT is same user A and hence it always is treating that the action is done thru' witem only, even though its done manually. This is because, when executed manually also, the step1 witem is ending with container element WIACTUAL_AGENT filled with user A and hence its proceeding with background task in step 2.
Any thoughts on how to tackle this issue. Your suggestions / input is really appreciated.
Thank you in advance. Pl let m

Hi Venu,
I have quickly created a sample workflow in my system.
Here is what I did:
1) Workflow will tigger to my inbox whenever Change master is created.
2) Created a custom task with object type ECM and method 'EDIT' with termination event 'Deleted'.
3) created fork step type with 2 branches and necessary branches 01.
4) one branch will execute the task created above
5) another branch will wait for the event "Deleted" of ECM
6) I have created a container element flag ( of type XFELD ).
7) In the wait event binding I am passing X to worklfow container element flag.
7) I have created change master from transaction CC01.
8) Received the worklfow and deleted the document via worklfow.
9) I checked the worklfow log and found that the flag container element is not populated
10) I have created one more change master from transaction CC01.
11) Received the worklfow but deleted the document outside the workflow.
12) I checked the worklfow log and found that the flag container element is populated with 'X' this time.
I think you can use that flag to differntiate whether the transaction was done outside worklfow or within the workflow.
Hope this helps.
Thanks.
Krishna.

Terminating event in synchronous method.

Similar Messages

Maybe you are looking for