Event is triggered once, but two workflow instances start

Hello all,
I have a workflow that is triggered by the event ISUSWITCHD.Created.
Unfortunately two workflows of the same version start on this event.
This event is triggered only once according to SWEL.
i have already copied the old workflow pattern (deactivated) and created a new pattern. Problem still exists.
There are no double entries in SWETYPV also.
Is this a Basis problem?
Any help is aprreciated,
Bye,
Holger
Edited by: Holger Reimer on Sep 20, 2010 9:43 AM

1. Go to the transcation SWE2 and check whether there is entry for the same workflow two times. If yes then check for what 
    other event the same workflow is being triggered.
    Create a check function module to test what was the actual triggering object.
2. If there is no such entry then check through out the code whether that worlflow is being called through a function module or  
   not. If that is being callde by a function module then the the SWELS cannot trace the triggering of the workflow and the
   workflow will be trigered.
    If such type of entry is still not there means  that the code does not contain any FM that will trigger the workflow then check 
    for it.
3.Go to the transcation PFTC.
   Give the workflow number and choose the workflow template. There you can check wherther any other event is assigned to  
   the workflow. If yes then trace that and deactivate the linkage if it is not required.
Thanks!

Similar Messages

  • Invoice output triggered once but sending multiple mails from the output

    Hello Experts,
    Need your help with a tricky issue in our system.
    We have an output type defined to send invoice output as email. Lately we have an issue with this.
    If we trigger the output in foreground it works fine. But when we create the invoices from batchjob it is triggering multiple emails for the same invoice. When we check the output in invoice it was triggered only once. Even in NAST also we have only one entry for these invoices. This issue is happening randomly not for all the invoices created through batch.
    To nailed down the issue we have added code to update the application log in the output program. It wil update the application log in SLG1 transaction when ever the output program was called. Surprisingly even for the cases where the mail triggered multiple times we have only one entry in the log. It means even though the mail sent multiple times, it is calling the output porgam only once.
    We are not able to replicate this issue even after mulitple trails.
    Please suggest how we can find the root cause for this issue. All the ideas are welcome.
    Thanks,
    Srini

    Hi
    The problem could be in SO_DOCUMENT_SEND_API1 or in the program called to send the mail
    SO_DOCUMENT_SEND_API1 places the mail in SOST (how many messages you can see there?)
    If you see only one message the problem could be in the program to send the mail
    Max

  • Getting WLI  Workflow Instance getting NULL.

    Hi All WLI Users,
    I am getting following problem while executing WLI workflow. After work
    flow gets triggered by an XML event and instantiated, after some time workflow
    instance becomes null.
    and the execution is aborted. Kindly give me a solution to this problem.
    Thanks
    Kiran

    Hi tony
    It won't be possible for us to send us the workflow, beacuse it has
    lots of interfaces
    like MQ series and TCP/IP adpater.
    But I can explain u in brief the workflow.
    Workflow sends message to HOST1 after getting successfull response
    from HOST1 it sends
    another request to HOST2 and waits for the response.
    Now this can iterate for say 200-500 times (depends on response
    from HOST1).
    Each message length is aroung 5000 bytes.During this iteration the
    instance somehow sets to NULL.
    I hope you can simulate the same at your end.
    Also note we also do XML transformation before sending the request.
    Thanks
    "tony lodge" <[email protected]> wrote in message
    news:[email protected]...
    Hi
    I recommend given this level of detail you open a case, what I amseeing
    looks like a valid bug. Please provide the sample workflow if possible
    Tony
    "Saurabh" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    The Versio ni am using is wlisp2.1 (service pack 2.1)
    and Exception Stack trace is as follows,
    <Mar 30, 2002 1:53:55 AM GMT-05:00> <Error> <T3Services> <Workflowtrace:Template=28003
    Template Definition=31003
    Instance=null>
    Workflow warning: com.bea.wlpi.common.WorkflowException: The system
    could
    not
    find the specified workflow instance: null.
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
    nce(WorkflowProcessorBean.java:537)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
    nceData(WorkflowProcessorBean.java:551
    atcom.bea.wlpi.server.workflow.Variable.setValue(Variable.java:92)
    atcom.bea.wlpi.server.workflow.Workflow.setVariable(Workflow.java:833)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.setVariableValue
    (WorkflowProcessorBean.java:1017)
    at
    com.bea.wlaiplugin.server.WLAIServiceImpl.execute(WLAIServiceImpl.java:211)
    atcom.bea.wlpi.server.workflow.action.ActionPlugin.execute(ActionPlugin.java:1
    23)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Start.activate(Start.java:168)
    at
    com.bea.wlpi.server.workflow.Workflow.start(Workflow.java:657)
    atcom.bea.wlpi.server.workflow.Workflow.instantiate(Workflow.java:617)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean$1.invoke(Workflo
    wProcessorBean.java:713)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.performWithError
    Handling(WorkflowProcessorBean.java:11
    32)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.instantiate(Work
    flowProcessorBean.java:709)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.in
    stantiate(WorkflowProcessorBean_h7kt4j
    _EOImpl.java:78)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.checkTrigger(EventProcesso
    r.java:358)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
    a:244)
    at
    com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
    ean.java:130)
    at
    weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
    atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
    at
    weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    <Mar 30, 2002 1:53:55 AM GMT-05:00> <Notice> <EJB> <Error markingtransaction
    for rollback: java.lang.IllegalStateException:
    Cannot mark the transaction for rollback. xid=4883:97fdb06e981bb8b8,status=Rolled
    back. [Reason=weblogic.transaction.interna
    l.TimedOutException: Transaction timed out after 89 seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    java.lang.IllegalStateException: Cannot mark the transaction for
    rollback.
    xid=4883:97fdb06e981bb8b8,
    status=Rolled back. [Re
    ason=weblogic.transaction.internal.TimedOutException: Transaction timedout after
    89 seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    at
    weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
    nsactionImpl.java:1486)
    at
    weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
    l.java:466)
    at
    weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
    ava:255)
    at
    weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
    5)
    at
    weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
    er.java:371)
    at
    weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
    java:756)
    at
    weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
    move(WorkflowProcessorBean_h7kt4j_EOIm
    pl.java:856)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
    cessor.java:510)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
    a:284)
    at
    com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
    ean.java:130)
    at
    weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
    atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
    at
    weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    javax.transaction.TransactionRolledbackException: EJB Exception: :weblogic.transaction.internal.TimedOutException:
    Transacti
    on timed out after 89 seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    at
    weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
    Impl.java:1122)
    at
    weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
    ansactions(ServerTransactionManagerImp
    l.java:441)
    at
    weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
    erImpl.java:1581)
    at
    weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
    sactionManagerImpl.java:404)
    at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
    rImpl.java:1547)
    at java.lang.Thread.run(Thread.java:484)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 89seconds
    >
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out
    after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    at
    weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
    tionImpl.java:1475)
    at
    weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
    ServerTransactionImpl.java:435)
    at
    weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
    at
    weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
    0)
    at
    weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
    er.java:371)
    at
    weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
    java:756)
    at
    weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
    move(WorkflowProcessorBean_h7kt4j_EOIm
    pl.java:856)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
    cessor.java:510)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
    a:284)
    at
    com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
    ean.java:130)
    at
    weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
    atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
    at
    weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ; nested exception is:
    weblogic.transaction.RollbackException: Transaction timed outafter 89
    seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out
    after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    weblogic.transaction.internal.TimedOutException: Transaction timed outafter 89
    seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    at
    weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
    Impl.java:1122)
    at
    weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
    ansactions(ServerTransactionManagerImp
    l.java:441)
    at
    weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
    erImpl.java:1581)
    at
    weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
    sactionManagerImpl.java:404)
    at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
    rImpl.java:1547)
    at java.lang.Thread.run(Thread.java:484)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 89seconds
    >
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out
    after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    at
    weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
    tionImpl.java:1475)
    at
    weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
    ServerTransactionImpl.java:435)
    at
    weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
    at
    weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
    0)
    at
    weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
    er.java:371)
    at
    weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
    java:756)
    at
    weblo

  • Subtype event not triggering and supertype event triggers twice!!!!!!

    Hi,
    We have created a subtype for object bus2030 and also an event created for that. My workflow should trigger whenever an inquiry is created.
    I've maintained this as triggering event in SWDD and done type linkage is SWE2 and everything looks fine.
    When i simulate or create event the WF is triggered but when create inquiry in VA11 WF does not triggers.
    I've checked SWEL for event trace but no event is triggered at all... Am i missing something... I've done almost everything that i used to do...
    Even synchronized buffer!!! nothing paid me a solution...
    Infact the same was working with 3.1i system but after migration to ECC6 we had to create new WF template for the same Process.
    Now I also see that the supertype bus2030-created event is triggered twice but, obviously no receiver type exists. But the zbus2030 event is not being triggered at all!!!!
    Kindly help me understanding my mistake...
    Regards,
    PB

    Hope you have already set the deletegation in SWO6.
    Now, event dont get triggered automatically, jus because they are defined in object. They have to be explicitly published in thesystem.
    Check for a suitable user exit in your transaction, which makes use of function module to create the event, from that you know how to proceed.
    If you dont find user exit, try other triggering techniques such as change documents, logistics, BTEs... etc.
    regards,
    Sandeep Josyula

  • Process Chain after EVENT - More than once

    Hi all, I would like to run a process chain after an event; everything works fine with the following model...
    PC1 >>
         >> some processes
         >> EVENT TRIGGER
    PC2 >>
         (after EVENT) runs ok after event ONLY if I SCHEDULE it
    After succesfully run, I've tried to run again immediatly PC1 again and it runs ok, even triggers mentioned EVENT, but PC2 never runs again until I manually SCHEDULE it.
    The answer is: how should I SCHEDULE the process chain PC2 so I'll "never" need again to SCHEDULE it when I want it to run after event triggered on PC1?
    Hope you can help me.
    Thanks a lot!
    Bernardo

    Hello,
    Both process chains are separated. At the model I described, at the end of PC1 event is succesfully triggered. After event is triggered at PC1, PC2 triggers correctly due it is scheduled as "after event".
    Everything works fine, then, if I trigger PC1 again it runs correctly; event is triggered succesfully but PC2 (that is scheduled as "after event") doesn't runs; this is because I haven't SCHEDULED it again (after the first succesfully run).
    What I want is not schedule PC2 after a succesfully run. Is there any way to reach that purpose?
    Thanks again!
    Bernardo

  • Remove Workflow Instance From Queue

    Hi Experts,
    We encounter a problem in UCM workflow. Somehow the content of some workflow instances is no longer exists in the system (Don't know why), but the workflow instances are still active. This cause the cps portlet fails to render the approval portlet.
    We have tried login as the workflow instance owner in UCM Admin page (http://host:16200/cs), and go to My Content Server > My Workflow Assignments, remove the offending workflow instance manually.
    However we don't know how much workflow instances are affected, we would like to remove all offending workflow instances by a single administrative account i.e. "weblogic", but we found that we are not able to do this as the Content Items In Workflow "workflow_name" does not include the offending workflow.
    Is there any SQL update to the data in the OCS schema to batch remove the workflow instances?
    Ziho

    Hi Jiri,
    Thanks for the suggestions, below are some more information on the issue.
    if you can afford that, the easiest way how to get rid of running workflow instances is to disable an re-enable the criteria workflow(s) that contain it. Be aware that you will lose all workflow statuses of the disabled workflows.We can't afford that as it is a production system
    Workflows, however, store workflow statuses on filesystem, so I'm not sure if database operations will be enough.I think so, we tried login as workflow owner, there is a function to "Remove workflow from queue" for specified workflow instance under All Active Workflows --> My Workflow Assignments. However after the removal of the workflow instances, we can't find any data modification in the OCS schema, related tables include WORKFLOWDOCUMENTS, WORKFLOWDOCATTRIBUTES, DOCUMENTS, DOCMETA, REVISIONS and REVCLASSES
    by doing so, the admin should see the items - not in My Workflow Assignment, though. You will need to click the name of the wokflow and then, you should see all the items in the particular workflowYes, the admin i.e. "weblogic" can view all active workflow instances WITH content associated with it, but offending workflow instances (i.e. the one WITHOUT content somehow) do not show up.
    We believe, if no things go wrong, that all active workflow instances can be found by running the following sql statement "select * from WORKFLOWDOCUMENTS;". However, in our case, workflow instances without content can be found using the same sql, but do not show up in UCM web UI login as "weblogic".
    Last, but not least, you should analyse how come an item in a workflow could be deleted.We encountered this during high load (Generated by Stress Test Tool), without login UCM web UI as admin role to delete content.
    the admin deleted the item in Repository Manager whilst it routed in a workflow.We tried using admin role to delete content in Repository Manager, it popup error when we tried to delete content which are in active workflow. We had to either Approve or Reject it before we can delete it (which I think the workflow maybe not in active state anymore, i don't know..)
    See if any other suggestion I can get. Thanks for the input.
    Thanks,
    Ziho

  • Workflow not starting and RFC status is 'User Switch Is Not Possible'

    Hi All,
    I am using ABAP classes to raise an event that triggers the workflow.
    When I am executing the workflow from SWUS or raising event from SWUE or SE24, the workflow is starting fine.
    But when I am raising the event from a Webdynpro application, the same event is raised, but the workflow is not getting triggerred.
    I could see a record in SWEL, but the workitem is not created.
    In SWEL, it is showing the RFC status as 'User Switch Is Not Possible'.
    When I go to SM58, I am able to re-execute the failed transaction and this time the workflow is getting triggered.
    The same workflow is working fine in D env. but not in T env.
    The event linkages are all same and I also used the COMMIT WORK statement after raising the event.
    Another problem is the RFC status is sometimes set to SYSFAIL and sometimes as 'System overloaded, repeat immediately by batch' other than 'User Switch Is Not Possible'.
    Please help.
    Thanks,
    Cay.

    Hi,
    call function module AUTHORITY_CHECK_RFC explicitly before a remote call to be able to treat a possible exception. If the authorization exists, the function module does not return an explicit result but, like all successfully executed function modules, sets sy-subrc to 0. If sy-subrc is not equal to zero then it could be the problem with the user authorization.
    I also think it could alos possible because of your Host name check whether any changes are done to host name.
    Regards
    Pavan

  • Workflow not starting for a customized Application

    Dear All
    It is a simple Applictaion but the Workflow not starting. when we submit the the form after filling up the form the error is showing as Check supervisor error. But the data in the system is showing the Correct supervisor. The Activity ins the Workflow details is showing as Stuck and Error.
    Regards
    Arifuddin

    Please post the details of the application release, database version and OS.
    It is a simple Applictaion but the Workflow not starting. What application?
    when we submit the the form after filling up the form the error is showing as Check supervisor error. What is the complete error message?
    But the data in the system is showing the Correct supervisor. The Activity ins the Workflow details is showing as Stuck and Error. Can you find any details about the error in the Workflow log file?
    Thanks,
    Hussein

  • Terminating Event Getting triggered more than once

    Hi All,
    I am facing a very peculiar problem in PR release workflow(item wise release, business object BUS2009).
    One of the requirements of the workflow is to send a mail to PR initiator once it is rejected by any of the approvers(4, in my case). The event associated with the cancellation of the workflow is REJECTION_START.
    The problem is that this event is being triggered more than once. One thing that i have observed is that if eg. second level of approver cancels it, the event is triggered twice. Likewise if third level of approver cancels it, it is being triggered thrice. Which leads to sending of 2 and 3 mails respectively to the PR initiators mailbox.
    Why is this happening? Ideally, only one event should have been triggered, and the triggering of the event should have been independent of PR approver's level. I am at my wits end regarding this.
    Any suggestions in this regard will be highly appreciated
    Regards
    Varsha Agarwal.

    If you check for 2nd level rejjection two release Code is associated so it triggers 2 times and same for 3rd level approval.
    I think you have to put some sort of filter using FM SAP_WAPI_WORKITEM_OBJECT
    in the attribute portion of yopur custom BO.
    The attribjute will check this FM and if it has entries that means already a Workflow has been triggered it should set the flag as X.
    Make use of this attribute in defining the start condition of this task thru
    SWB_COND.
    Thanks
    Arghadip

  • Event not triggering workflow always

    Hi,
    I have a parallel approval workflow which I trigger everytime I receive a decision from a UWL.it works fine but in some cases all the decisions are not received by the workflow.
    Steps: I receive the decision from UWL via a RFC
               I trigger the workflow with the decision using SAP_WAPI_EVENT_CREATE.
               However sometimes out of 5 decisions only 4 reaches and the workflow never completes since I wait till all the decisions  are received.
    After triggering the event I also update a table which shows correct values meaning the data is correctly passed from UWL.
    Not sure what can be the cause. Anyone any ideas.
    Thanks
    Papiya

    Hello,
    Either the event isn't being created, or the event is being created ad the workflow isn't triggering.
    Check tx SWEL (event trace, turn on with SWELS) to see if SAP_WAPI_CREATE_EVENT is creating the events.
    It will also show you if a workflow is triggered, and what the workitem id is. It will also show any errors.
    regards
    Rick Bakker
    Hanabi Technology

  • BTE 1030 - we use for AP documents, create an event that triggers a workflow

    Hello all,
    We use SAP's program RFBIBL00 to post AP documents.  We coded a function module that is called when BTE 1030 is reached.  Our FM creates an event that triggers a workflow.
    We are now doing some testing with an external vendor who is creating AP documents by doing an RFC  using function module BAPI_ACC_DOCUMENT_POST.
    It seems that this BTE, 1030, is not being triggered when the IDOC created by this function module posts the AP document.
    Has anybody else seen this issue and found a way to deal with it?
    Thanks
    Bruce

    AFAIK BAPI_ACC_DOCUMENT_POST and FI posting should trigger BTE 00001030 but BAPI_INCOMINGINVOICE_CREATE and AC interfacewould trigger BTE 00001050. (or is BAPI_ACC_DOCUMENT_POST also using AC interface, I will let you check it)
    Nevertheless call your FM triggered thru BTE 1030 also in a FM triggered thru BTE 1050. Also in the call check for update task
    function z_fi_00001050.
    call function 'TH_IN_UPDATE_TASK'
         importing
           in_update_task = in_update_task.
       if in_update_task eq 0 and i_xvbup eq 'X'.
         call function 'Z_FI_00001030' in update task
           exporting
             i_xvbup = ' '
           tables
             t_bkpf  = t_bkpf
             t_bseg  = t_bseg..
       else.
         call function 'Z_FI_00001030'
           exporting
             i_xvbup = ' '
           tables
             t_bkpf = t_bkpf
             t_bseg = t_bseg...
       endif.
    Regards,
    Raymond

  • Event geeting triggered but WI doesnt  proceed

    Hi All ,
      In my workflow , I have have a step which waits for the event 'TRIP.CHANGED' . And when the event is occured next step will be executed .
       I have came accross a strange situation wherein  the even is getting triggered but the next step is not executed . The workflow is still in the <b>WAIT</b> state .
       Previously it was working but now its not working .
      What could be the reason ?? Any thoughts ...
    Thanks ,
    Sonu M.

    Hi Sonu,
    You can go to transaction swu0 wherein if you give your business object and the event you can see your particular workflow is linked or not.
    If it is linked that means it will show you a green light if not it will give you a red light.
    If it has a green light it is linked successfuly if not plz chek the bindings.
    Else if this all thing is working you might have done some other changes which hasnt reflected so go to transaction swu_obuf and sycronize it.(it might work)
    I had the same problem in my workflow , but i changed that wait for event condition and did some other check,so now it is working.You can also possibly change that condition and check some other condition.
    Regards,
    Prajakta.

  • Event gets triggered Two times everytime

    Dear Experts,
    I am using an event Changed of BOR LIKP(Outbound Delivery). It gets triggered twice. I am unable to find the reason. Please help.
    -Pritam

    Hi,
    Check this [Thread1|Event and Business obejct triggered  twice; & [Thread2|the workflow gets trigerred thrice...;.
    Regards,
    Surjith

  • Events being triggered more than once

    HI All,
    I am using SAP Business One 2007 A SP:01 PL:07
    I have created a form using SAP Business One UI API Version 2007 A 8.0.When i open the form first time all item events and menu events are working properly..
    When i close the form and open it again all the menu and items events get fired twice.Again i close and reopen the form all Item and Menu events are triggered thrice on a single click.
    Any help to solve this problem will be highly appreciated.
    Warm Regards,
    Prerna

    Hello,
    Maybe You using a global variable for the form. Try to swicth to local variable and use sbo_application.form.GetForm(pval.formtypeex, pval.formtypeCount), or check you application really closes the window (window menü, and see the list of opened forms).
    Try to use EventSpy, which is a part of the SDN tools, you can download from /docs/DOC-8857#section6
    Regards,
    J

  • Workflow instances problem

    My problem is that in workflow i am sending workitem for manager approval.If manager rejects the workitem it goes to employee back for correction and resubmission.But what is happening once workitem is send to employee for correction the current workflow instance is completed and when user changes the report and resubmits it a new workflow instance will be created.This all increases load on the working system.
    Can we keep the same workflow instance working till report is rejected or accepeted and then only workflow instance is completed.

    I think you can make use of Function module
    SAP_WAPI_WORKITEMS_TO_OBJECT
    in a virtual attribute that will check whether any existing wflow is already triggered for it. If yes set the Flag(Virtual attribute) value as X. Make use of this attribute in th Start ciondition of the wflow in SWB_COND Tcode.
    Now in your workflow the approval step should be inside a loop that loops until the request is approved. Inside the loop the approval step should be in fork with 2 parallel branch and 1 necessary. In 1 branch put approval step and in other branch put the Wait for event step.
    Thanks
    Arghadip

Maybe you are looking for

  • I recently installed OS 10.8, and now my mail and calendar accounts want to default to my sister and her email address?

    Here is my situation: My sister and I have shared an Apple ID ever since I bought my sister an iPhone on my cell phone account. We each have Mac laptops and had no problem syncing to separate Gmail/Exchange accounts but still share an Apple ID for co

  • Can i use events for anything i want?

    hi i've got a doubt about events. i am using events to send information between objects, so that the objects don't need to know who they are sending the information to. so i created my own events, listener and listenermulticaster but i have the feeli

  • Mail wouldn't quit in 10.4.7

    But thanks to an earlier thread, I looked at the third-party JunkMatcher filter and removing it solved the problem. Instructions are at http://junkmatcher.sourceforge.net/Howto/Installation/index.html#Uninstall

  • Workpace - Web Dynpro Projects vs. DC Projects

    Hello, When creating a DC Project out of the DTR (development track) on the Development configuration perspective, those Projects do not show up on my workspace folder like a regular Web Dynpro projects does. How do I get these DC projects into my wo

  • Personal domain and regular .Mac site

    I would like to create my own personal website (like usual on .Mac in my personal area) and then also post another domain I own to my .Mac area. How does it know which site to "publish" to? Or can you only have one website in iWeb '08? Thanks.