Workflow Fails After Upgrade to ECC 6.0 (Joanne Johnson)

[Shai Eyal]

Joanne,

Lately I upgraded twice to ECC6 and indeed the workflow suffer from problems. However most are resolved in support package 15.
I'd advice reviewing note 571302 - Collective note relating to transports in workflow .
Try to check your workflow definition because the error you describe should already appear there.
In addition, in case you have two clients in your development system (one for customization+developent and one with data) verify everything is copied correctly (use t.code SCC1).
In addition, check synchronization though I'm quite sure you did that.

BTW, are other workflows work well ?
 
Regards,
Shai Eyal
SAP Logistics senior consultant
SAP Workflow specialist




------------------------------

Message: 3
Date: Wed, 20 Jun 2007 09:43:36 -0400
From: "Joanne Johnson" <JoanneJohnson at jo-annstores.com>
Subject: Workflow Fails After Upgrade to ECC 6.0
To: <sap-wug at mit.edu>
Message-ID: <4678F6C8020000AF00008DC5 at corp.jo-annstores.com>
Content-Type: text/plain; charset=US-ASCII

Hello all,

I created a custom workflow last year while we were in SAP v4.7.  We are currently in the process of upgrading to ECC 6.0 (Basis pkg level SAPKB70011).  This workflow no longer works in 6.0.  It fails with an error message OL383 "The source and target structure have a different number of fields".   I get this problem whether the workflow was created in 4.7 and not worked until 6.0 or if it was created and worked in 6.0.

I researched this error message and found a number of OSS Notes that imply that there are lots of workflow problems in ECC 6.0 but none of them refer to the BOR I am using (BKPF).  I did have several notes applied in 6.0 to prevent potential problems (OSS Note 887076 - Incorrect Binding After Upgrade and executed pgm ZRSWD_BINDING_RESTORE and OSS Note 1043988 - Short Dump When Workflow Restarted) however, they made no impact on the error.

I think the problem is a binding problem because the method that is failing is the IMPORT_FROM_BOR_CONTAINER however, when I test this method, it seems to work ok.  There are no syntax errors anywhere in the workflow or in the business object BKPF or ZBKPF.

I also noticed that BOR BKPF has a new method in 6.0 called BKPF.GetARLData but that's related to ArchiveLink Data so I don't think that's causing the problem since I'm not executing that method.

Does anyone have any suggestions or insight?  Thanks for the help.

Joanne Johnson
Jo-Ann Stores, Inc.






------------------------------
***************************************


      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/ 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070620/661bcd05/attachment.htm