Start Condition related to upgrade ECC 6

Wed Sep 24 19:44:41 EDT 2008

Sue,

By any chance is your condition binding trying to make use of an attribute from an instance attribute fetched from your main object? e.g. document->user->name (where to find the value of 'name' you have to first fetch the instance called 'user' from instance 'document').

Sometimes trying to get a value in this way causes grief at runtime if the middle instance attribute in such a chain ends up being null, e.g. ex_object_not_found is raised. This error may only manifest itself from time to time depending on the data involved and would not picked up as a syntax error in the definition.

Or, perhaps the condition trying to use a virtual attribute of an object where the code behind it may occasionally raise ex_property_not_found? This kind of thing cause some grief at runtime, particularly with binding because it is treated as a show-stopping error.

Mike GT

Subject: RE: Start Condition related to upgrade ECC 6Date: Wed, 24 Sep 2008 14:29:11 -0400From: Sue.Doughty at odfl.comTo: sap-wug at mit.edu

Hi Mike,

When we have the problem, we are using standard events.  The events sit in the event queue up to six minutes before they are delivered.  When the workflow starts, it has a wait step for 10 seconds and then a task to instantiate the object.  Even after all of that, we sometimes get the error where it is not seeing the EESUBGROUP attribute of the object.  It doesn’t happen all the time, just once or twice a month.  That is what is so frustrating….I cannot put my finger on what might be happening.

Today, I have done what Jake said about checking that the SWC_SET_ELEMENT CONTAINER macro is being run and it is, but not to the “OBJECT-“ field name – it’s being done to a field name in the Data statement of the code.  I don’t know if that would make a difference, but I’ve changed it to SWC_SET_ELEMENT CONTAINER ‘EESubgroup’ OBJECT-EESUBGROUP instead of SWC_SET_ELEMENT CONTAINER ‘EESubgroup’ EESUBGROUP (where EESUBGROUP is defined in the Data statement).  I’ll see if that clears up the problem.

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 PokrakaSent: Wednesday, September 24, 2008 1:09 PMTo: 'SAP Workflow Users' Group'Subject: RE: Start Condition related to upgrade ECC 6

Hi Stefaan, 

This error usually results when there is no object instance. Is this a newly created object? If so, it’s possible that the event is firing before the object has made itself at home in the database – particularly if it’s a custom event. 

Cheers, 
Mike

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Stefaan VermeulenSent: 24 September 2008 11:43To: SAP-WUG at mit.eduSubject: 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.

__________ Information from ESET NOD32 Antivirus, version of virus signature database 3467 (20080924) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature database 3468 (20080924) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature database 3468 (20080924) __________The message was checked by ESET NOD32 Antivirus.http://www.eset.com

**************************** 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. 
_________________________________________________________________
Make a mini you and download it into Windows Live Messenger
http://clk.atdmt.com/UKM/go/111354029/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080924/0762bd57/attachment.htm