Skip to Content
author's profile photo Former Member
Former Member

Update Terminate Dump in WorkFlow

I have a workflow for PO release which was getting triggered on event RELEASESTEPCREATED of BUS2012(PO). Now one day in my Production Environment started giving Update Terminate after releasing and saving the PO is Tcode Me29n , upon analysis, I came to know that in workflow trace(SWEL) BUS2012 event RELEASESTEPCREATED was getting triggered twice and for the first trigger workflow was running perfect but for the 2nd entry it was giving error in agent determination via rule number 20000027..and it was giving short dump (update terminate) after reading dome forums and notes i came to know that culprit was the entry in SWEC

(Events for Change Doc.). This entry was for Purchasing Doc object EINKBELEG Business Object BUS2012 event RELEASESTEPCREATED and trigger was "OnCreate" . this entry was triggering workflow 2nd time and that time the workflow container elements remained blank and Rule was giving errors which intern was giving Update termination DUMP.

Now I deleted this culprit entry from SWEC and my workflow is getting triggered only once And perfectly and everyone is happy. But my question is in my production system same behavior was there from long time but i mean triggering workflow twice for same PO document on release. but till now it had not given Update termination dump this started suddenly. and even in my DEV and QA servers stil culprit entry is there and it is creating 2nd erroneous entry which is going into error due to blank Container elements getting passed in rule but still it is not giving dump (express update terminate or in (ST22)...what could be the reason.. and in production system also it started giving dump

Suddenly while problem was there for long time. I suspect some of the system setting from

Basis side might have changed but my basis are saying nothing has changed..so what could be

the reason is this problem in workflow side or basis settings side??

Thanks and Regards

Munish Singh

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 23, 2008 at 11:48 AM

    Nothing changed ... Right!

    Does the update termination log not say where the termination occurred? I'd start by checking if the program that caused the termination has been changed, then the programs that are called by this program. It is of course strange that everything is fine in DEV and QA, but there could be an explanation for this, e.g. the problem could be caused by, or at least related to, something that is client-specific and not transportable.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      >

      > Nothing changed ... Right!

      >

      > Does the update termination log not say where the termination occurred? I'd start by checking if the program that caused the termination has been changed, then the programs that are called by this program. It is of course strange that everything is fine in DEV and QA, but there could be an explanation for this, e.g. the problem could be caused by, or at least related to, something that is client-specific and not transportable.

      Check that some smart cookie hasn't limited the authorisation for WF-BATCH in the system where the dump is occurring, and get you BASIS dudes to check table sizes.

      Cheers

      Gareth

  • Posted on Jan 28, 2008 at 08:18 AM

    Hi MS,

    this could have occured if any number ranges are changed, or the indexes for PO tables are not refreshed.

    BASIS guys can help you with this.

    Also check SM13 Tcode to understand the dump better

    Aditya

    Edited by: Aditya Varrier on Jan 28, 2008 1:48 PM

    Add a comment
    10|10000 characters needed characters exceeded

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.