Corrupt Sub WF definition.

[Mike.Nickson@boots.com]

Manish

I had the same (or similar) problem here.

I could access the workflow OK in the development client, but if I 
referred to the workflow in any other client (PFTC, SWI1 etc) then I would 
get a short dumps.

Luckily this did not get as far as our production system.

Our problem was related to a condition node in the workflow that was 
corrupted in some way, but SAP fixed it for me.

We were getting CALL_FUNCTION_REMOTE_ERROR dumps at the rate of 1 per second as the 
program was looping . . . Is this what you are getting ?

Mike





"Khanna, Manish" <manish.khanna at amd.com>
Sent by: sap-wug-bounces at mit.edu
08/03/2006 01:34
Please respond to "SAP Workflow Users' Group"

 
        To:     "SAP Workflow Users' Group" <sap-wug at mit.edu>
        cc: 
        Subject:        Corrupt Sub WF definition.


Hi,
 
I've found a peculiar problem.
 
We have a logistic invoice approval workflow having a main process and an 
approval 'sub workflow'. For some issue I need to look at the 'sub 
workflow' definition but SWDD and PFTC give short dump when trying to 
display the workflow definition.
 
I tried in our production system also, but the issue remains.
 
Interestingly the workflow is running fine, which means the runtime 
version is intact.
 
How can I recover the WF definition???
 
Regards,
Manish_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060309/cf6a0d50/attachment.htm