Terminating Event in PO Release Workflow. Workitem is not terminating

Hi WF Experts,
                        I have done Purchase Order Release Workflow with 10 level release With 2 days dead line. Since standard release supports only 8 level release i have opted for Role Resolution Via User Exit 9 . and i am picking release codes from ztable.
I was working fine till now.But suddenly end users are facing problem that workitem is not terminating even after they have released the PO.
What could be the issue what is the terminating event for PO Release workitem.
Please suggest me how to resolve this issue.
Regards,
Hari

Hi Hari,
Please check if the following links helps:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/sap%252bworkflow%252bevents
http://help.sap.com/saphelp_nw04/helpdata/en/c5/e4b590453d11d189430000e829fbbd/frameset.htm
Hope this helps!
Regards,
Saumya

Similar Messages

  • The task TS20000166 in PO release workflow( WS20000075 ) is not terminating

    Dear Experts ,
    The task TS20000166 in PO release workflow( WS20000075 ) is not terminating after release the PO .
    In the WS20000075 ,the event RELEASESTEPCREATED is triggeing and move to the next step.The next step is 'Release of purchase order'  , the task TS20000166  is not terminating after release of PO .So Workflow is not move to next step i.e  TS20000168.
    I have noted TS20000166  is having three terminating event ( RELEASED,RESET,SIGNIFICANTLYCHANGED ) but still it is not terminating.
    Is it Clear.If you want more details please let me know .Please help me.
    Thanks and Regards
    Rajesh

    Dear Raj,
    Please check agent assignment. And also check graphical mode error and check how many events fire one after one. Because for rejecting there is one more workflow u have to activate but i dont think so u have to activate it after realease . In agent assign ment check workflow with normal agent assignment dont use release stretargy then check it again if it is working fine then it must be problem of agent assignment step.
    Reagrds,
    Gurprit Bhatia

  • 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

  • Getting two same workitems in PO release workflow for 2 level

    Hi experts,
    I am working in PO Release workflow upto two level of release.
    But while triggring my workflow by creating PO I get two same workitem.One of the two has correct Release Code(I have checked that in workflow log) and another has Release Code with no value.If I execute one of them Its working fine.But 2nd one still remains in inbox.I think my workflow has been triggred twice while I am creating a PO.
      Can someone suggest, where is the problem?
    Thanks,
    Manas

    Hi,
      According to your instruction I have got 5 event trace.
    BUS2012     RELEASESTEPCREATED     14.02.2008     16:31:57     WS99900003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    QCYBUS2012     CREATED     14.02.2008     16:31:57          @AI@     No receiver entered
    BUS2011     QUOTATIONCREATED     14.02.2008     16:31:57          @AI@     No receiver entered
    BUS2012     RELEASESTEPCREATED     14.02.2008     16:31:57     WS99900003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    FREBUS2012     CREATED     14.02.2008     16:31:57          @AI@     No receiver entered
    I have given you the details of the event traces.
    Here I notice RELEASESTEPCREATED event occurs twice.
    Can you please suggest why this is happening?
    Thanks,
    Manas.

  • Event Linkage Getting Disabled In PO release Workflows : Plz help

    hi all
    i am working on PO Release Workflow
    my problem is when I create PO and save it , the event  linkage in SWETYPV gets disabled
    plz help me its urgent.
    regards
    ravish

    Hi
    If you have an error in the event linkage (could be a binding error, or an error in your business object), the event linkage will deactivated (the standard customizing).
    You can change this behavior through transaction SWE2 -> double click on your event linkage -> change the "Behavior Upon Error Feedback". (I think you can change this globally but I'm not quite sure where)
    In my book best practice here will be;
    1. Use the event queue
    2. Set the "Behavior Upon Error Feedback" flag to something like "Keep linkage but flag as having an error" - I'm not on the system so I'm not quite sure what it's called
    By doing this you make sure that you will collect your event in the event queue, in case of an error.
    or
    In the detail screen of SWETYPV there's an option called Bahaviour upon error in receiver, if you change this to option 3 then the linkage won't be disabled in cases of errors.
    Sometimes you want the event linkage to be disabled in cases of errors, espescially when the only reason that an error can occur is a very serious one.

  • PR item level Release WorkFlow

    Hi Experts,
                      I have activated PR item level release WorkFlow  WS00000038. My MM consultant has configured release strategy with ME51N. The Work flow works fine On releasing it sends notification work item to initator but on release Refusal it don't send notification work item to initator. Can anyone guide me how to resolve this issue.
    TS00007986 SINGLERELEASE
    4 Outcomes of release
    1) Positive Confirmation
    2) Negative Confirmation
    3) Confirmation Release Cancelled
    4) Purchase requisition item significantly changed
    Now 1) posative confirmation is working fine.
    but when we reject release then in that case also the workflow log it is going in undefined output that is significantly changed.
    can anyone help me to resolve this issue.
    Regards,
    Hari

    Hi Hari,
    When you reject a PR, 2 events are getting triggered (Significantly changed and rejection_started). You check this in Transaction SWEL by rejecting PR.
    The reason why output is going to Significantly changed branch is in SWEL you can see that 1st Significantly changed  event is getting triggered and then Rejection_started.
    Solution1: Deactivate the Significantly changed event in termination events tab.
    Solution2: Create an attribute(Database object) for your business object. This attribute should be of type EBAN-BANPR. Check if BANPR = 08 and then send the rejection mail.
    I hope this clears your doubt.
    Please Revert back to me if you have any queries.
    Regards,
    Gautham Paspala

  • Is there no contract rejected task in contract release workflow ? (BUS2014)

    I'm trying to trigger my workflow when a contract is rejected but I can not see any 'rejected' task or step in default contract workflow.
    How can I be able to do this ?
    Here is the copy of default cotract workflow (WS20000079);
    And here is the tasks of BUS2014;
    Thanks for any help.

    Hi Mustafa
    The standard WF WS20000079 uses task TS20000172 to send the decision. It has three terminating events from BUS2014 (RELEASED, RESET and SIGNIFICANTLYCHANGED).
    Which event gets triggered when you "reject" a contract in your system? (check in SWEL (switch on the trace first using SWELS))
    Regards,
    Modak

  • PO release workflow - regarding.

    Hello !
       I am into the development of PO release workflow.
       I use custom task for releasing the purchase order(BUS2012-SINGLE RELEASE).
       I have configured RELEASE STEP CREATED and CHANGED event to trigger the workflow
       When purchase order is created, workflow triggers via RELEASE STEP CREATED event  and go to the first approver.When first approver has released, the work item goes to second approver via CHANGED event and not via RELEASE STEP CREATED.
       Following are terminated events , I have configured :
    WIOBJECT_ID     BOR Object Type     BUS2012     RELEASED     Purchase Order Release PO
    WIOBJECT_ID     BOR Object Type     BUS2012     RELEASESTEPCREATED     Purchase Order Release Step Created
       Please suggest how to make the workflow to re-trigger via  RELEASE STEP CREATED instead of CHANGED event once the first approver have released it.
    Thanks and regards,
    S.Suresh

    Hello Gautam Maini !
                 Thank you so much for your reply.
                 I have already activated RELEASESTEPCREATED event at SWEC.
                 The problem I face is that the work item of first agent does not completes though the PO is released.I have configured terminating event as RELEASED.Due to buffer problem or some other reason, the terminating event's binding properties looks so contradictory.I have posted the screen shot of the same at
    http://img19.mediafire.com/205f136394986473f8b76798935c80b1f5794a496734421d23384bb33713f8886g.jpg
                 In the table , SWFDEVINST, RELEASED event and SIGNIFICANTLY CHANGED event is updated after the PO release by first agent.
                  Once the PO is released by first approver , CHANGED event gets fired instead of RELEASED event.(observed at SWEL).
                  At workflow log, I get message as follows :
                              Message Text         Execution interrupted
                              Exception                0
                              Error Type               0
                              Area                 SWF_RUN
                              Message                611           
                  Please suggest solution for the problem for which I will be grateful.
    Thanks and regards,
    S.Suresh

  • Issue in PO Release Workflow WS20000075

    Hi All,
    We have activated Std. PO release Workflow WS20000075 for two step release levels. When New PO created with release strategy this workflow will trigger and send workflow items to Agents to release Purchase Order. Up to this it's working fine.
    But the problem occurs to trigger Workflow again after PO price change. We have release change indicator with 5% variance of price. That means when some one changes the Price or Quantity and if the total values variance more than 5% of price variance then Release strategy will activate again in PO. But in this case Workflow WS20000075 not sending workflow items again to the agents.
    Is there any workflow setting causing the issue?

    Hi Sivaparvathy ,
    As far I can understand in SWEL event trace for the second time the event is getting triggered but there is no appropriate receiver for that event. Can you please specify the event name. If it is any event other than RELEASE for eg lets say if it is CHANGE, in the workflow WS20000075 header you will have to bind the workflow with this event and activate linkage for this particular event as well(without changing the previous configuration for PO release event). So that the workflow is triggered for this event as well..
    Hope this helps
    Regards
    Anik

  • Payment Release Workflow

    Hi Folks,
             We are working on Payment Release workflow in AR module.
             Once the invoice is posted, workflow is able to block the payment, but not sending mails to the agent for approval.
             For testing, i have entered a dummy userid as the agent and checking for the mails.
             How can we debug or monitor to check why the agent is not getting mails in SBWP.
             Pls suggest how to solve the problem.
    Thanks in advance,
    Shyam.

    Hello,
    Okay, let me correct that for you:
    "We are working on Payment Release workflow in AR module.
    Once the invoice is posted, workflow is able to block the payment, but not sending WORKITEMS to the agent for approval.
    For testing, i have entered a dummy userid as the agent and checking for the WORKITEMS.
    How can we debug or monitor to check why the agent is not getting WORKITEMS in SBWP.
    Pls suggest how to solve the problem."
    Have you looked in SWI5 to see if it is listed for the user there? Check that there are no excluded agents.
    The solution is likely that you haven't set the task to General Task, as already suggested.
    regards
    Rick Bakker
    hanabi technology

  • Payment release workflow thru F-53 Transaction  help needed

    Hi gurus,
    I am trying for payment release workflow using F-53 which is the client requirement. As there is no parking option in the transaction i created a custom event "parked" in the transaction .I tried using BTE. but i m not able to find the right product no in infosystems of BTE for the transaction F-53. Is there any way for payment approval workflow.
    Thanks and Regards,
    Kumar

    Hi Kumar,
    Actually, what you may do is setup a workflow for automatic payment with approval/rejection process which would trigger a BAPI for f-53 process.
    And keep the below items in mind before finalize:
    a. F110 will not clear any blocked invoices.
    This is the default setting, as a security for the blocked items stay in the system
    (blocks are always there with a reason).
    b. In F-53 you can control what you want to clear (not automatic),
    therefore some blocks can be redefined allowing F-53 to clear SPECIAL-BLOCKED items
    You may find more options too.
    Thanks
    MKS

  • Regarding PR Release workflow:

    My pr release workflow is 8 levels.
    1st level is working fine( getting workitem to sap inbox of 1st level approver and releasing from his inbox)
    when it comes to second level it is automatically releasing from me54n.(am not getting any workitem to sap inbox of 2nd level of approver)
    and it is not showing in workflow log also.(total skipping second level)
    3rd level is working fine.
    can you pls tell me the solution.
    thanx in advance.

    hi
    thanx for ur reply.
    in workflow log i saw 1 st level succesfully completed.(this is loop 1 in workflow log)
    then after is going 3rd level(this is loop 2 in workflow log)
    total 2nd level is skipping(is not showing in workflow log)
    because 2nd level is automatically releasing in me54n so it is going directly to 3rd level as a loop 2.
    pls check below attached docuent.
    That is the code i used inside business object to getting agents.
    first agent getting correct only -1st level
    second agent is skipping when debugging time(because 2nd level is automaticcay released in ME54N)
    third agent is getting correct only- it is showing as a second level
    so pls tell me a solution how to control automatic release in me54n for 2nd level?????
    best regards,
    seetha

  • PR release workflow - issue in mulitple level approval

    Hi Experts,
    I have developed a new workflow for PR release strategy.
    Business object: BUS2105 ( Purchase Requistion )
    Triggerring event: ReleaseStepCreated
    Step1: Workflow started ( Releasestepcreated)
    Step2: Approve PR ( Agent1)
    Step2a
    If yes --> Released to next level (Agent 2 )
    Step2b
    If No --> Rejected and notified initiator
    If Yes --> Notify intiator and exit
    Step3b.
    If no --> based on next release code and release
    group get the next level agent and go to
    step2
    Step4: Workflow ends.
    Issue:
    For single step PR release, workflow is working fine.
    When PR created with multiple level release, a workflow triggers and notifies the 1st level agent, when the agent releases the PR at 1st level and saves it , workflow is not proceeds to further steps to find the next level agent.
    Here i am using the FM to fetch the approvers and assigning the same for release codes.
    Please guide me...

    Hi
    ''workflow is not proceeds to further steps''... do you mean that RELEASESTEPCREATED event is not triggered for next step ?
    you can check this in SWEL that whether event is getting triggered after first release.
    If yes then the issue is in configuration of release strategy where for all release code you need to mark workflow parameter 1.

  • PR overall release workflow

    Hi All,
    I am working on PR overall release workflow (WS20000077) and had activated workflow for PR rejection 'wf_pur_rejo' (WS65400029). When i create a PR using ME51N workitem gets created. When we reject the PR by executing the workitem i receive the workitem for rejection also. Everything is fine till here.
    But when i try to execute the workitem (Purchase Requisition XXXXX Rejected) i get an <b>error 'No Administrator found for the task'</b> and i observed that in workitem log it is shown in READY STATE. This happens for some user ids and it works fine with some other user ids.
    Can any please tell me where i am going wrong and if i am then eloborate on what should i be doing?
    Thanks in advance,
    Regards,
    Lakshmi Narayana.S

    I have got it, ran the Transaction SWU_OBUF to synchronize the buffers and re-logged into SAP. Now the problem is solved.
    Regards,
    Lakshmi Narayana.S

  • (Solved) Workflow System Verification Step 4: workitem could not be created

    Hello all
    We're on R/3 4.7 and I'm trying to get workflow runtime environment up and running. I've already passed through the automatic customizing (SWU3), all is green!
    When starting the verification workflow I get a mail in my SAP Workplace inbox telling me something about error WL 410.
    In the workflow log I can see this (had to translate it from german, so please bare with me if wording in english is not absolutely correct):
    green -> Start event received
    green -> (sub-)workflow created
    green -> workflow started
    green -> SWW_WI_ERROR_MESSAGE_SEND_S    
    red   -> Callback vom Workitem ausgeführt
    red   -> GET_DEADLINE
    red   -> SWW_WI_STATUS_CHANGE
    Clicking on the first red light pops up a message telling me something like that:
    Workflow 'Workflow-System-Verification' Step n° 4: Workitem could not be created
    The long text message of this and the workflow protocol tells nothing more.
    Anyone out there able to help me on this issue?
    Kind regards,
    Renaud

    Hello Alan
    Yes, this nearly made me crazy. Posted a customer message to SAP concerning this in parallel last week and also sent them some screenshots. They also advised me to move unit H from (non standard) dimensionless to dimension "time". This corrected it as already mentioned before.
    I did several workflow activations before and never had any problems with automatic customizing and the verification workflow... until I came across this system here. Also on all other systems known to me the unit H was never dimensionless. Double checked it last week as well. Probably someone else fiddled around in CUNI without knowing what he or she was doing? Will probably never find it out. I just hope that this was an exception! Else...
    Some extra points would be great of course )
    Thanks and kind regards,
    Renaud

Maybe you are looking for