Start Condition related to upgrade ECC 6

[Sue Doughty]

We also have this issue, but it happens on condition steps.  It only happens intermittently.  

 

For some reason an attribute of the business object that we are comparing is blank.  I've put an instantiation step at the beginning of the workflow and we still have it happen intermittently.  I finally added a container operation to move the attribute to a container after the instantiation step and changed the condition to look at the container.  That has seemed to fix it - so far!!  

 

We are on ECC 6.0, Service Pack 13.  Is there anything that I'm missing?

 

Regards,

Sue T. Doughty

SAP Workflow Specialist

Old Dominion Freight Line, Inc.

500 Old Dominion Way

Thomasville, NC 27360

Phone:  (336) 822-5189

Toll Free (800 ) 432-6335, ext. 5189

Email:  sue.doughty at odfl.com

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Gambier
Sent: Wednesday, September 24, 2008 7:14 AM
To: SAP Workflow Users' Group
Subject: RE: Start Condition related to upgrade ECC 6

 


Stefaan,
 
This might related to a bug I found with condition binding in ECC 6 that's to do the 'new' syntax added for unicode conversion in SWD_CONDEF table (see OSS Note 1228836). 
 
ECC 6 expects extra piece of syntax in the LEFTEXPR or RIGHTEXPR fields along the lines of {TYPE = ... } so that the expression can be understood in unicode terms but unfortunately the upgrade process from old 4.6c Workflows to new ECC Workflows does not account for this at all (and never will). This caused us no end of grief with condition steps trying to compare a date attribute on a BOR Instance and a constant string value, e.g. '31.12.9999'. Without this new syntax the condition becomes invalid nt he way that you have described.
 
Thankfully I found a neat little trick to get around this without too much fuss. If you go into the WF definition, click on the binding, change nothing but hit the green tick in the binding screen the WF Builder adds the missing {TYPE=...} syntax in SWD_CONDEF but doesn't tell you. The current definition may pick this up at the moment as a syntax error before you do this. If this syntax error goes away by performing this little trick then I think you will have solved your issue :)
 
Try it out and see if it works. If it does, you should probably activate the WF definition again and transport it. Note that this change is version dependent so it won't have effect on running instances of older versions.
 
Regards,
 
Mike GT

________________________________


Date: Wed, 24 Sep 2008 12:43:01 +0200
From: stefaan.vermeulen at gmail.com
To: SAP-WUG at mit.edu
Subject: Start Condition related to upgrade ECC 6



Hi,

 

While testing in a new upgraded development from 46c to ECC6 I encountered the following.

A WF related to BUS2007 Maintenance orders gives every time an exception "Operator 'EQ': The value of the left operand cannot be determined"

in the event trace and doesn't get triggered.

 

The condition is: &Maintenance order.PM planning plant& = BEP1

 

Nothing was changed to the workflow, BO ZBUS2007 , delegation or event linkage, everything is still active and error free.

In the old development it still works.

 

The checks I have done:

-Deleted to condition and recreated this, same problem.

-I saw that FM : SWB_2_CHECK_FB_START_COND_EVAL is used in SWB_COND(ECC6), I replaced this by the old FM SWB_CHECK_FB_START_COND_EVAL, same problem.

-I created new test-wf's and used the same and even other fields to check before triggering, the same problem.

 

I didn't found a related problem in the archives, any suggestions ?

 

Thanks,

Stefaan.

 

 

________________________________

Win £3000 to spend on whatever you want at Uni! Click here to WIN! <http://clk.atdmt.com/UKM/go/111354032/direct/01/> 



****************************
CONFIDENTIALITY NOTICE: The information contained in this message may be confidential, privileged, proprietary, or otherwise legally exempt from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this message, any part of it, or any attachments. If you have received this message in error, please delete this message and any attachments from your system without reading the content and notify the sender immediately of the inadvertent transmission. Thank you for your cooperation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080924/739c637c/attachment.htm