Corrupt Sub WF definition.

[Khanna, Manish]

Mike,

Thanks for the information. However it's unlucky on our side that the
corrupt definition moved to production.

 

What is happening right now is

1.	Runtime version is intact in our Development and Production; as
a result the workflow is running fine.
2.	It was recently when there was a need to enhance the business
process and hence we discovered that the definition is corrupt in all
the systems.
3.	What is happening is when I try to open the template in SWDD, it
gives a short dump in program SAPLSWDD with the following info

************************************************************************
****************************************************

When changing or deleting one or more lines of the internal table

"\PROG=SAPLSWDD\DATA=ALL_LINES_TAB[]" or when inserting in the table

 "\PROG=SAPLSWDD\DATA=ALL_LINES_TAB[]", 0 was used as

the line index. An index less than or equal to zero is not

allowed.

 

The error can occur when using the following options:

1. "INDEX idx" for specifying the line number in the table

 "\PROG=SAPLSWDD\DATA=ALL_LINES_TAB[]"

   where you want to change, insert or delete.

2. "FROM idx" for specifying the start index when deleting a line

   area from or inserting a line area into the table

 "\PROG=SAPLSWDD\DATA=ALL_LINES_TAB[]".

3. "TO idx" for specifying the end index when deleting a line

   area from or inserting a line area into the table

 "\PROG=SAPLSWDD\DATA=ALL_LINES_TAB[]".

************************************************************************
*******************************************************

 

We are facing the same error in all the systems. 

 

Regards,

Manish

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike.Nickson at boots.com
Sent: Thursday, March 09, 2006 5:12 AM
To: SAP Workflow Users' Group
Subject: Re: Corrupt Sub WF definition.

 


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/7d712019/attachment.htm