<div>Mike,</div>
<div> </div>
<div>Thanks for you're suggestion, I regenerated the binding without very much succes, like I described initially I even started with the binding for the BO from scratch in a test WF with the same problem.</div>
<div> </div>
<div>Seems to be related to another problem.</div>
<div> </div>
<div>regards,Stefaan.</div>
<div> </div>
<div> </div>
<div><br><br> </div>
<div><span class="gmail_quote">2008/9/24, Mike Gambier <<a href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><br>Stefaan,<br> <br>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). <br> <br>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.<br>
<br>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, <strong>change nothing</strong> 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 :)<br>
<br>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.<br>
<br>Regards,<br> <br>Mike GT<br><br>
<hr>
<br>Date: Wed, 24 Sep 2008 12:43:01 +0200<br>From: <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:stefaan.vermeulen@gmail.com" target="_blank">stefaan.vermeulen@gmail.com</a><br>To: <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
Subject: Start Condition related to upgrade ECC 6
<div><span class="e" id="q_11c9416d841985a4_1"><br><br><br>
<div>Hi,</div>
<div> </div>
<div>While testing in a new upgraded development from 46c to ECC6 I encountered the following.</div>
<div>A WF related to BUS2007 Maintenance orders gives every time an exception "Operator 'EQ': The value of the left operand cannot be determined"</div>
<div>in the event trace and doesn't get triggered.</div>
<div> </div>
<div>The condition is: &Maintenance order.PM planning plant& = BEP1</div>
<div> </div>
<div>Nothing was changed to the workflow, BO ZBUS2007 , delegation or event linkage, everything is still active and error free.</div>
<div>In the old development it still works.</div>
<div> </div>
<div>The checks I have done:</div>
<div>-Deleted to condition and recreated this, same problem.</div>
<div>-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.</div>
<div>-I created new test-wf's and used the same and even other fields to check before triggering, the same problem.</div>
<div> </div>
<div>I didn't found a related problem in the archives, any suggestions ?</div>
<div> </div>
<div>Thanks,</div>
<div>Stefaan.</div>
<div> </div><br></span></div>
<hr>
Win £3000 to spend on whatever you want at Uni! <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://clk.atdmt.com/UKM/go/111354032/direct/01/" target="_blank">Click here to WIN!</a></div><br>_______________________________________________<br>
SAP-WUG mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br>