Corrupt Sub WF definition.

[Khanna, Manish]

I didn't find transaction SWDS.

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of jerry martinek
Sent: Thursday, March 09, 2006 9:48 AM
To: SAP Workflow Users' Group
Subject: Re: Corrupt Sub WF definition.

 

Hi,

Are you accessing the sub WF directly or inderictly via the main WF? We
had a similar problem that we solved by accessing the sub-WF directly
and then regenerating it. 

Also have you tried accessing the WF via SWDS?

Jerry

Content-Type: multipart/alternative; boundary="=_alternative
004875AB8025712C_=" --=_alternative 004875AB8025712C_= Content-Type:
text/plain; charset="iso-8859-1" Content-Transfer-Encoding:
quoted-printable Manish I had the same (or similar) problem here. I
could access the workflow OK in the development client, but if I=20
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=20 corrupted in some way, but SAP fixed it for me. We
were getting CALL=5FFUNCTION=5FREMOTE=5FERROR dumps at the rate of 1
per= second as the=20 program was looping . . . Is this what you are
getting ? Mike "Khanna, Manish" Sent by: sap-wug-bounces at mit.edu
08/03/2006 01:34 Please respond to "SAP Workflow Users' Group" =20 To:
"SAP Workflow Users' Group" cc:=20 Subject: Corrupt Sub WF definition.
Hi, =20 I've found a peculiar problem. =20 We have a logistic invoice
approval workflow having a main process and an=20 approval 'sub
workflow'. For some issue I need to look at the 'sub=20 workflow'
definition but SWDD and PFTC give short dump when trying to=20 display
the workflow definition. =20 I tried in our production system also, but
the issue remains. =20 Interestingly the workflow is running fine, which
means the runtime=20 version is intact. =20 How can I recover the WF
definition??? =20 Regards,
Manish=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
SAP-WUG mailing list SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug --=_alternative
004875AB8025712C_= Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable 
Manish 

I had the same (or similar) problem = here. 

I could access the workflow OK in th= e 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 o= ur production system. 

Our problem was related to a conditi= on node in the workflow that was
corrupted in some way, but SAP fixed it fo= r me. 

We were getting 
CALL=5FFUNCTION=5FREMOTE=5FERROR dumps at the rate of 1 per second a= s
the program was looping . . . Is this what you are getting ? 

Mike 




	"Khanna, Manish" <ma= nish.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: &nbs= p;      "SAP Workflow Users' Group" <sap-wug at mi=
t.edu> 
        cc: &nbs= p;       
        Subject:=        Corrupt Sub WF definition.



Hi, 
  
I've found a peculiar problem. 
  
We have a logistic invoice approval workf= low 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, bu= t the issue remains. 
  
Interestingly the workflow is running fin= e, which means the runtime
version is intact. 
  
How can I recover the WF definition??? 
  
Regards, 
Manish=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



--=_alternative 004875AB8025712C_=-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060309/aa24953f/attachment.htm