Skip to Content

Workflow step is not getting executed

Hi all,

I have designed a workflow in which I have a Decision step. after taking the a decision then it is taking so much time to execute the next step which is a background step.

The waiting time is varying from time to time some times it is getting executed in 20 min, some time it is taking 1 hr no fixed time.

I have used SAP_WAPI_DECISION_COMPLETE function module and I am passing space to the DO_COMMIT becuse of this the workitem is getting completed but it is not going to the next step. This fm is called under a button Approve of a WD application. after completeing the entire cycle of the WD application we are using the statement COMMIT WORK but still the execution is not going to the next step.

In this regard , please, can any body share their views and ideas.

And it is mandatory that only after the webdynpro application execution finishes they want to COMMIT the work.

One more thing while searching forums I found like there are terms like DB COMMIT and simple COMMIT WORK what is the difference between them .

Thanks&Regards

Pavan

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on May 19, 2009 at 07:11 PM

    Hello,

    "after taking the a decision then it is taking so much time to execute the next step which is a background step."

    Is it taking a long time to execute the step, or to begin executing the step?

    What does that background step do?

    regards

    Rick Bakker

    Hanabi Technology

    Add a comment
    10|10000 characters needed characters exceeded

    • Thanks Rick

      Here the case is , the decision workitem is getting completed and then after some time all of a sudden the background step starts getting executed and then executes the entire workflow and workflow gets completed.

      There is no dump, no error , every thing is fine,

      The step itself gets into the ready, started state after some time.

  • author's profile photo Former Member
    Former Member
    Posted on May 20, 2009 at 10:39 AM

    I hope you are passing the DECISION_KEY parameters properly. This parameter should be the WI_RESULT value that gets stored for each option in the decision task container.

    Thanks

    Arghadip

    Add a comment
    10|10000 characters needed characters exceeded

    • Rick Bakker Pavan Chand Bhamidipati

      Hello,

      I wasn't asking about the commit.

      In the first post you said:

      "The waiting time is varying from time to time some times it is getting executed in 20 min, some time it is taking 1 hr no fixed time."

      And in the latest post you said:

      "but no matter it is not moving to the next step"

      Which one is true?

      And anyway, commiting the result of a decision step is not, I think, something that can be delayed.

      regards

      Rick Bakker

      Hanabi Technology

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.