Attribute not set correctly for BUS2038/INPROCESS

Berthold Wagner BerthelWagner at web.de
Fri Jan 13 07:27:20 EST 2006


Hi,

yes I'm using a simple start condition.
I double checked everything. All looks fine, table entries are okay,
SWB_COND okay, workflow header okay. When I test the condition with the same
object where the workflow is triggered wrongly the condition says " The
evaluation of the condition gives the result 'False'".
I think this must be a SAP error. I have to report this to OSS. Thanks for
your support 

cheers

Berthold

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Andy.M.Catherall at csplc.com
Sent: Donnerstag, 5. Januar 2006 10:34
To: SAP Workflow Users' Group
Subject: RE: Attribute not set correctly for BUS2038/INPROCESS

Hi Berthold

I'm assuming you are using a simple conditional start-condition, rather
than a custom check Function Module:

* Is the binding between the event and the workflow correct?

* When you look at the values of these variables in the [incorrectly]
started workflow, what do you see? Are they correctly set, or blank?

* Is the Start Condition correct in both SWB_COND and when viewed through
the workflow builder? Personally, I've experienced 'oddities' with SWB_COND
in the past. Look in transaction SWETYPV for your event linkage, open that
up and confirm that the "SWB_CHECK_FB_START_COND_EVAL" function module has
been included in the 'Check Function Module' field.

* Finally, you can look at tables SWBRULECOM, SWETYPECOU and SWETYPEENA,
the latter two being the same information as that seen in Transaction
SWETYPV.


Hope this helps
Andy



|---------+---------------------------->
|         |           "Berthold Wagner"|
|         |           <BerthelWagner at we|
|         |           b.de>            |
|         |           Sent by:         |
|         |           sap-wug-bounces at m|
|         |           it.edu           |
|         |                            |
|         |                            |
|         |           29/12/2005 14:31 |
|         |           Please respond to|
|         |           "SAP Workflow    |
|         |           Users' Group"    |
|         |                            |
|---------+---------------------------->
 
>---------------------------------------------------------------------------
---------------------------------------------------|
  |
|
  |       To:       "'SAP Workflow Users' Group'" <sap-wug at mit.edu>
|
  |       cc:
|
  |       Subject:  RE: Attribute not set correctly for BUS2038/INPROCESS
|
 
>---------------------------------------------------------------------------
---------------------------------------------------|




Hi,

My problem is not that the workflow is not started but it is started
although it should not be started because of the start condition

cheers

Berthold
      -----Original Message-----
      From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
      Behalf Of Yogesh Chopra
      Sent: Donnerstag, 29. Dezember 2005 10:06
      To: SAP Workflow Users' Group
      Subject: RE: Attribute not set correctly for BUS2038/INPROCESS

      Hi! Berthold

      If workflow is not getting triggered in event INPROCESS then you have
      to manually trigger that even in one of user exit. I faced same
      problem in my previous parking document workflow FIPP. Use function
      module to trigger workflow in the INPROCESS event.

      Thanks and Best Regards
         Yogesh Chopra
      Yogesh.Chopra at axonglobal.com

            -----Original Message-----
            From: BerthelWagner at web.de [mailto:BerthelWagner at web.de]
            Sent: Thursday, December 29, 2005 4:55 PM
            To: sap-wug at mit.edu
            Subject: Attribute not set correctly for BUS2038/INPROCESS



            Hello workflowers,


            I have a problem with a workflow for BUS2038. I use several
            events for triggering the workflow (CREATED/CHANGED/INPROCESS)
            and for each event the same start condition checking two custom
            own attributes. Everything is fine with CREATED and CHANGED and
            the workflow is only started when the condition is okay. With
            INPROCESS instead one of my custom own attributes is not
            considered and the workflow is even when one of the conditions
            is not okay. When I set a breakpoint in the program of the
            business object for the determination of one of the attributes
            (which is a user status) and create the event via SWUE I see
            that the breakpoint is reached for CREATED and CHANGED but not
            for INPROCESS. Any Ideas?


            cheers Berthold



                                                     
                                                     
                                                     
 Verschicken Sie romantische, coole und witzige      
 Bilder per SMS!                                     
 Jetzt bei WEB.DE FreeMail:                          
 http://f.web.de/?mc=021193                          
                                                     






                                          
                                          
                                          
                                          
                                          
 The content of this email is             
 confidential and for the                 
 addressee only. If you are not the       
 addressee of this                        
 email (or responsible for the delivery   
 of this message                          
 to such person) you may not copy,        
 forward, disclose                        
 or otherwise use it or any part of it in 
 any form                                 
 whatsoever. If you have received this    
 email in error                           
 please email the sender by replying to   
 this message                             
 and delete this message thereafter.      
                                          
 Opinions, conclusions and other          
 information in this                      
 message that do not relate to the        
 official business                        
 of our Company shall be understood as    
 neither                                  
 given nor endorsed by it.                
                                          


       _______________________________________________
      SAP-WUG mailing list
      SAP-WUG at mit.edu
      http://mailman.mit.edu/mailman/listinfo/sap-wug





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

This e-mail is confidential and may contain privileged information.  If you
are not the addressee or if you have received the e-mail in error,  it may
be unlawful for you to read, copy, distribute, disclose or otherwise use the
information which it contains.

Under these circumstances, please notify us immediately by returning this
mail to 'mailerror at csplc.com' and deleting this e-mail from your system.

Any views expressed by an individual within this e-mail do not necessarily
reflect the views of Cadbury Schweppes Plc or its subsidiaries.  Whilst we
have taken reasonable steps to ensure that this e-mail and attachments are
free from viruses,  recipients are advised to subject this mail to their own
virus checking, in keeping with good computing practice.

Cadbury Schweppes is making a donation to help Crisis open doors for
homeless people instead of sending corporate Christmas cards this year.
Please click here to receive our Christmas greetings.

http://www.crisis.org.uk/festive-card/cadbury-schweppes  

Visit our website at www.cadburyschweppes.com

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

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug





More information about the SAP-WUG mailing list