SAP-WUG Digest, Vol 39, Issue 61

yogesh patil yogeh at hotmail.com
Tue Feb 26 15:25:15 EST 2008


Hi Sue,
          sorry i  dont know why it doesnot show up when i reply with my official email id..anywyas..you can try the following 

1.Check whether the 'RESULT' container element in the Business object method is set  to 'T' or 'F' in either case...after reading the values from the table..

2.check whether the date type of the element' result' in the method  is same as the one that u bind back to the task container...and back to the WF container.. and also check the import /export paramater check box is appropriately checked in the method...parameters section...

Hope this helps..

Thanks,
Yogesh

> From: sap-wug-request at mit.edux`
> Subject: SAP-WUG Digest, Vol 39, Issue 61
> To: sap-wug at mit.edu
> Date: Tue, 26 Feb 2008 14:48:55 -0500
> 
> Send SAP-WUG mailing list submissions to
> 	sap-wug at mit.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mailman.mit.edu/mailman/listinfo/sap-wug
> or, via email, send a message with subject or body 'help' to
> 	sap-wug-request at mit.edu
> 
> You can reach the person managing the list at
> 	sap-wug-owner at mit.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SAP-WUG digest..."
> 
> 
> Today's Topics:
> 
>    1. RE: Condition step not working in Workflow (Sue Doughty)
>    2. RE: Result Processing not working in Workflow (Sue Doughty)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 26 Feb 2008 14:15:30 -0500
> From: "Sue Doughty" <Sue.Doughty at odfl.com>
> Subject: RE: Condition step not working in Workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> 	<082C942F46528B44B5463D3C2A1FF0F40E4E660C at corp-m-exch2.corp.odfl.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> Yogesh,
> 
>  
> 
> Did you mean to send a response?  I see nothing in your email.
> 
>  
> 
> 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 <mailto:sue.doughty at odfl.com> 
> 
> ________________________________
> 
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Yogesh Patil
> Sent: Tuesday, February 26, 2008 1:36 PM
> To: SAP Workflow Users' Group
> Subject: RE: Condition step not working in Workflow
> 
>  
> 
>  
> 
> 
> 
> ****************************
> 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/20080226/b9d5b8b4/attachment-0001.htm
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 26 Feb 2008 14:48:11 -0500
> From: "Sue Doughty" <Sue.Doughty at odfl.com>
> Subject: RE: Result Processing not working in Workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> 	<082C942F46528B44B5463D3C2A1FF0F40E4E66A2 at corp-m-exch2.corp.odfl.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> Thank you for response.
> 
>  
> 
> I've tried refreshing the buffers and logging off and back on.  
> 
>  
> 
> I should know how to search SAP-WUG, but I don't know how.  Would you
> please point me in the right direction?
> 
>  
> 
> 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 Shai Eyal
> Sent: Tuesday, February 26, 2008 2:08 PM
> To: sap-wug at mit.edu
> Subject: Subject: Condition step not working in Workflow
> 
>  
> 
> Hi Sue,
> 
>  
> 
> I had several issues that sounds like that. I can guess you work with
> ECC6 BASIS level 9 or 11.
> 
> Please try the buffer refresh. Even log off and login again and try.
> 
>  
> 
> If you still can't get it working run search of SAP-WUG ; I posted
> message with OSS note describing ECC 6.0 "surprises".
> 
> BTW, pay attention that you don't have case-sensitive problem.
> 
>  
> 
> Eventually it'll work - good luck,
>  
> 
> Regards,
> Shai Eyal
> 
> SAP Logistics senior consultant
> SAP Workflow specialist
> Mobile: 972-52-5816633
> 
>  
> 
> ----- Original Message ----
> From: "sap-wug-request at mit.edu" <sap-wug-request at mit.edu>
> To: sap-wug at mit.edu
> Sent: Tuesday, February 26, 2008 19:07:00
> Subject: SAP-WUG Digest, Vol 39, Issue 59
> 
> Send SAP-WUG mailing list submissions to
>     sap-wug at mit.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>     http://mailman.mit.edu/mailman/listinfo/sap-wug
> or, via email, send a message with subject or body 'help' to
>     sap-wug-request at mit.edu
> 
> You can reach the person managing the list at
>     sap-wug-owner at mit.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SAP-WUG digest..."
> 
> 
> Today's Topics:
> 
>   1. RE: Do we need triggering event for single task?
>       (Vinod Viswanathan)
>   2. AW: Do we need triggering event for single task?
>       (Schmidinger, Heinz (Oerlikon BZ))
>   3. Re: Maximum node number reached in process execution (endless
>       loop?) (Mike Pokraka)
>   4. RE: RFC status error while triggering a Workflow
>       (Khatawate, Deepak N (ACCENTURE))
>   5. Condition step not working in Workflow (Sue Doughty)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 26 Feb 2008 16:19:04 +0530
> From: "Vinod Viswanathan" <Vinod.Viswanathan at in.fujitsu.com>
> Subject: RE: Do we need triggering event for single task?
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>  
> <5AC5F6D093559448A9E0D8AB279EF31D0538CBF6 at PUNE-MAIL1.india.rapidigm.com>
>     
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Sandy,
> 
>     My pleasure.  Then the only solution I have for this is by
> triggering events unless of course some standard transactions allow a
> standard task id to be mentioned.  
> 
>     If you agree to link your standard task to triggered events, just go
> to SWETYPV, give the Task ID instead of the workflow id and enable the
> type linkage flag 
>     manually.
>     OR
>     In the task that you create, mention the particular event as one of
> the triggering event of the task.
> 
>     Hope this answer is relevant to your question.
> 
> Best Regards,
> Vinod Viswanathan
> Workflow Consultant
> Fujitsu Consulting - Pune
> Phone: +91 20 40722000 Extn:2370
> 
> 
> ________________________________
> 
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Sandy
> Sent: Tuesday, February 26, 2008 3:40 PM
> To: SAP Workflow Users' Group
> Subject: Re: Do we need triggering event for single task?
> 
> 
> Hi Vinod.
> Thanks for your answer.
> I knew that FM SAP_WAPI_START* or others.
> I just want to know the best approach to execute single workflow task.
> 
> 
> On Tue, Feb 26, 2008 at 5:21 PM, Vinod Viswanathan
> <Vinod.Viswanathan at in.fujitsu.com> wrote:
> 
> 
> 
>     Hi Sandy,
>     
>     There are some functionalities where the workflow or its task
> can
>     directly be specified and need not be triggered using
>     an event.
>     
>     A workflow or task can explicitly be called using a standard FM
> also.
>     
>     If the single step is a custom step, it is possible to execute
> it
>     using a background job too.
>     
>     Hope this answers your question.
>     
>     Best Regards,
>     Vinod Viswanathan
>     Workflow Consultant
>     Fujitsu Consulting - Pune
>     Phone: +91 20 40722000 Extn:2370
>     
> 
>     -----Original Message-----
>     From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
> On Behalf
>     Of Sandy
>     Sent: Tuesday, February 26, 2008 2:33 PM
>     To: SAP Workflow - MIT
>     Subject: Do we need triggering event for single task?
>     
>     Hi All.
>     I need your opinion on whether we need triggering event for
> workflow
>     single task. Especially if this single task is called within
> ABAP
>     program.
>     I agree we need a trigerring event if we use workflow but I'm
> not so
>     sure the best approach for single workflow task.
>     
>     Thanks in advance
>     
>     
>     
>     _______________________________________________
>     SAP-WUG mailing list
>     SAP-WUG at mit.edu
>     http://mailman.mit.edu/mailman/listinfo/sap-wug
>     
> 
> 
> 
> 
> -- 
> *-- Maorriyan --*
> 
> SAP Workflow
> SAP Security
> UWL Admin
> SAP HR OM 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20080226/25353c83/a
> ttachment-0001.htm
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 26 Feb 2008 14:06:52 +0100
> From: "Schmidinger, Heinz (Oerlikon BZ)"
>     <heinz.schmidinger at oerlikon.com>
> Subject: AW: Do we need triggering event for single task?
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>     <4072E0D0EEA33240A4E39DB04A4AE9E0B9B101 at ad02bz0101.dom02.net>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Sandy,
> 
> 
> 
> if you start a task using f.m. SAP_WAPI_start-* or you fire an Event
> using SAP_WAPI_CREATE_EVENT, the result will be the same at least.
> 
> 
> 
> In my opinion you get more flexibility into your coding if you fire an
> event.
> 
> In this case you can easy change the started Task only by customizing
> the Event-Binding.
> 
> 
> 
> Regards
> 
> Heinz
> 
> 
> 
> ________________________________
> 
> Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag
> von Sandy
> Gesendet: Dienstag, 26. Februar 2008 10:03
> An: SAP Workflow - MIT
> Betreff: Do we need triggering event for single task?
> 
> 
> 
> Hi All.
> I need your opinion on whether we need triggering event for workflow
> single task. Especially if this single task is called within ABAP
> program.
> I agree we need a trigerring event if we use workflow but I'm not so
> sure the best approach for single workflow task.
> 
> Thanks in advance
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20080226/ad4e050a/a
> ttachment-0001.htm
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 26 Feb 2008 15:31:41 -0000 (UTC)
> From: "Mike Pokraka" <wug at workflowconnections.com>
> Subject: Re: Maximum node number reached in process execution (endless
>     loop?)
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>  
> <62247.212.157.1.1.1204039901.squirrel at workflowconnections.com.mail.aais
> p.net.uk>
>     
> Content-Type: text/plain;charset=iso-8859-1
> 
> Hi Bill,
> 
> Your workflow has an endless loop somewhere. What's causing the
> confusion
> is that the workflow system treats this as a transaction error and rolls
> back the state to the last successfully completed step before the
> sequence
> that resulted in the loop.
> 
> A way around this is to re-execute the current step of the WF and have a
> look at the log straight away to see the subsequent steps before they
> are
> rolled back again.
> 
> Cheers,
> Mike
> 
> On Thu, February 21, 2008 10:04 pm, Bill Holbrook wrote:
> >
> >
> >  Hello All,
> >
> > I am on R/3 4.7 and am running a workflow where I am getting the
> > following error message Maximum node number reached in process
> execution
> > (endless loop?) Message no. WL392. At present, a maximum of 10000
> nodes
> > are allowed in one workflow - see settings for workflow runtime system
> > or basic data of the workflow definition. During execution of the
> > confirmation for work item 22322832, the node counter was increased to
> > value 10001 while step number 274 was being processed.
> >
> >
> >
> >
> >
> > The workflow is going through a fork and after executing the last step
> > in the fork the workflow will wait like it is exceeding the maximum
> > number of nodes but it is not. The workflow error points to a step
> > farther down in the workflow but the log does not show any steps being
> > executed from the fork to the point of the step where error is
> pointing.
> >
> >
> > Originally the workflow was just one big workflow but since then I
> have
> > broken it up with a subflow.
> >
> >
> > Any Help ?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 26 Feb 2008 15:43:34 -0000
> From: "Khatawate, Deepak N (ACCENTURE)" <Deepak.Khatawate at bp.com>
> Subject: RE: RFC status error while triggering a Workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>  
> <2019246BF83D0F46A0376FF2A463F712096CF090 at BP1XEUEX021-C.bp1.ad.bp.com>
> Content-Type: text/plain;    charset="us-ascii"
> 
> Hi Shrinivas,
> Check transaction sm58 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Vinod Viswanathan
> Sent: Tuesday, February 26, 2008 2:57 AM
> To: SAP Workflow Users' Group
> Subject: RE: RFC status error while triggering a Workflow
> 
> 
> 
> Hi Shrinivas,
> 
>   Please check the following in this order:-
> 
>   1.  Were you able to check the event linkages(SWETYPV) etc.?  Please
> check the same if it the type linkage flag is 
>       activated.  
>   2.  Also try testing the workflow independently using SWUS.  for all u
> know it may be getting stuck in the first step 
>       because of some error in the first step.
>   3.  Try triggering the event by executing FM SWE_EVENT_CREATE and
> check if the error persists.
>   
>   Please check the same and see if it helps.
> 
> Cheers,
> vinod
> 
> 
> --- Shrinivasa Padubidri Shenoy
> <ShrinivasaP_Shenoy at infosys.com> wrote:
> 
> > 
> > Hi,
> > 
> > I am trying to trigger a custom workflow from EP in Newly set up ECC 
> > 6.0 system.
> > Problem here is, Business object Event is getting triggered in R/3 
> > with custom workflow as reciever, but the workflow is not going to the
> 
> > first step. The event trace (SWEL) gives following information,
> > 
> > Action Receiver started correctly
> > RFC Status Logon not possible (error in license
> > check)
> > 
> > I have checked the configuration in SWU3, all were fine, also the RFC 
> > WORKFLOW_LOCAL_100 tested successfully. The ECC6.0 has the permanent 
> > license (Training).
> > Also this problem happens intermittently !
> > For some time it is working fine, some other time its giving the same 
> > RFC error.
> > 
> > Please let me know why this has happened? How can it be solved? Please
> 
> > reply ASAP.
> > 
> > Thanks,
> > Shrinivas
> > 
> > 
> > 
> > **************** CAUTION - Disclaimer
> > *****************
> > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended 
> > solely for the use of the addressee(s). If you are not the intended 
> > recipient, please notify the sender by e-mail and delete the original 
> > message. Further, you are not to copy, disclose, or distribute this 
> > e-mail or its contents to any other person and any such actions are 
> > unlawful. This e-mail may contain viruses. Infosys has taken every 
> > reasonable precaution to minimize this risk, but is not liable for any
> 
> > damage you may sustain as a result of any virus in this e-mail. You 
> > should carry out your own virus checks before opening the e-mail or 
> > attachment. Infosys reserves the right to monitor and review the 
> > content of all messages sent to or from this e-mail address.
> > Messages sent to or from this e-mail address may be stored on the 
> > Infosys e-mail system.
> > ***INFOSYS******** End of Disclaimer
> ********INFOSYS***>
> _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > 
> 
> 
> Something that can't be re-cycled is Wasted Time.
> 
> 
> 
> ________________________________________________________________________
> ____________
> Never miss a thing.  Make Yahoo your home page. 
> http://www.yahoo.com/r/hs
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Tue, 26 Feb 2008 12:06:28 -0500
> From: "Sue Doughty" <Sue.Doughty at odfl.com>
> Subject: Condition step not working in Workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>  
> <082C942F46528B44B5463D3C2A1FF0F40E4E649B at corp-m-exch2.corp.odfl.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> We are on 4.7, ECC 6.0
> 
> 
> 
> I have a sub-workflow that executes a loop until a result flag is set to
> T.  It executes a method that reads a table with some information.  If
> the record is found, the result is set to T, if not it is set to F and
> the result container is set in the method.  The next step is a condition
> to check the result.  If T, the loop and sub-workflow are completed, if
> F, it waits and tries again after five minutes.
> 
> 
> 
> My problem:  If the method executes and the result is T, the workflow
> works as designed.  If the method returns a result of F, the workflow
> stops at that step and does not move to the condition step to check the
> result.
> 
> 
> 
> I can see that the method is returning the result container.  If the
> Result = T, I can see that the Result container is sent back to the
> sub-workflow.  When I look at the step in the log, it says that the
> background item was created, started, work item processing is complete
> and the result processing is done with no errors.
> 
> 
> 
> If the Result is F, I can see that the method is returning the result
> container, but the workflow container does NOT get set to the Result.
> When I look at the step in the log, it says that the background item was
> created; started and work item processing is complete with no errors,
> BUT the Result Processing is NOT done.
> 
> 
> 
> What am I missing?  Why is the Result processing being done for one
> result but not the other?
> 
> 
> 
> 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
> 
> 
> 
> ****************************
> 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/20080226/978243b1/a
> ttachment.htm
> 
> ------------------------------
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> 
> End of SAP-WUG Digest, Vol 39, Issue 59
> ***************************************
> 
>  
> 
> 
> Send instant messages to your online friends
> http://uk.messenger.yahoo.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.
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080226/9a27eb68/attachment.htm
> 
> ------------------------------
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> 
> End of SAP-WUG Digest, Vol 39, Issue 61
> ***************************************

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080226/d13f7c37/attachment.htm


More information about the SAP-WUG mailing list