<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Rick,<BR>
sorry for the typo...<BR>
all i am trying to say is if she is using a Loop until step then she has to do a container operation step and check the same in the condition.<BR>
<BR>
<BR>
<BR>
Thanks,<BR><BR>yogesh "not a failure but a low aim is a crime"<BR><BR>> From: sap-wug-request@mit.edu<BR>> Subject: SAP-WUG Digest, Vol 39, Issue 81<BR>> To: sap-wug@mit.edu<BR>> Date: Thu, 28 Feb 2008 12:14:42 -0500<BR>> <BR>> Send SAP-WUG mailing list submissions to<BR>> sap-wug@mit.edu<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> or, via email, send a message with subject or body 'help' to<BR>> sap-wug-request@mit.edu<BR>> <BR>> You can reach the person managing the list at<BR>> sap-wug-owner@mit.edu<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of SAP-WUG digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. RE: SAP-WUG Digest, Vol 39, Issue 78 (Sample, Rick)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Thu, 28 Feb 2008 11:13:36 -0600<BR>> From: "Sample, Rick" <Rick.Sample@gbe.com><BR>> Subject: RE: SAP-WUG Digest, Vol 39, Issue 78<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <1897E92A96C47648A6574CB9A51C64070558071F@SEBEV1PW.graybar.com><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> This is incorrect if you are trying to catch the RESULT parm from<BR>> method->task!<BR>> swc_set_element container 'RESULT' 'T'. Will set a "container element".<BR>> <BR>> <BR>> swc_set_element container RESULT 'T'. Will set the METHOD RESULT<BR>> parameters to be caught by Task.<BR>> <BR>> <BR>> Rick Sample<BR>> SAP Business Workflow Developer<BR>> Graybar, Inc.<BR>> 11885 Lackland Dr.<BR>> St. Louis, MO. 63146<BR>> 314-573-5822<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of yogesh patil<BR>> Sent: Thursday, February 28, 2008 10:41 AM<BR>> To: sap-wug@mit.edu<BR>> Subject: RE: SAP-WUG Digest, Vol 39, Issue 78<BR>> <BR>> <BR>> <BR>> Sue,<BR>> <BR>> Since you are checking the condition in a loop ,i think you have to do<BR>> a container operation with assign "after "the method you are calling<BR>> for getting T or F of the result element and then check for the<BR>> Condition(the workflow container used in the container operation) in the<BR>> condition step. it should work.<BR>> <BR>> for exampe!<BR>> <BR>> method get_result.<BR>> <BR>> if <BR>> swc_set_element container 'RESULTt' 'T'.<BR>> else.<BR>> swc_Set_element container 'RESULT' 'F'.<BR>> <BR>> endmethod.<BR>> <BR>> Do a container operation in the wf definition.<BR>> <BR>> set the workflow container for EX..FLAG = RESULT(from task container)<BR>> <BR>> and then in the next step check for the <BR>> WF container FLAG in the condition.<BR>> <BR>> <BR>> <BR>> <BR>> Please let me know if this works..<BR>> <BR>> Thanks,<BR>> <BR>> <BR>> yogesh.<BR>> <BR>> > From: sap-wug-request@mit.edu<BR>> > Subject: SAP-WUG Digest, Vol 39, Issue 78<BR>> > To: sap-wug@mit.edu<BR>> > Date: Thu, 28 Feb 2008 10:31:04 -0500<BR>> > <BR>> > Send SAP-WUG mailing list submissions to<BR>> > sap-wug@mit.edu<BR>> > <BR>> > To subscribe or unsubscribe via the World Wide Web, visit<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > or, via email, send a message with subject or body 'help' to<BR>> > sap-wug-request@mit.edu<BR>> > <BR>> > You can reach the person managing the list at<BR>> > sap-wug-owner@mit.edu<BR>> > <BR>> > When replying, please edit your Subject line so it is more specific<BR>> > than "Re: Contents of SAP-WUG digest..."<BR>> > <BR>> > <BR>> > Today's Topics:<BR>> > <BR>> > 1. RE: Condition step not working in Workflow (Sue Doughty)<BR>> > 2. RE: Condition step not working in Workflow (Sue Doughty)<BR>> > 3. RE: Condition step not working in Workflow (Sample, Rick)<BR>> > <BR>> > <BR>> > ----------------------------------------------------------------------<BR>> > <BR>> > Message: 1<BR>> > Date: Thu, 28 Feb 2008 08:23:51 -0500<BR>> > From: "Sue Doughty" <Sue.Doughty@odfl.com><BR>> > Subject: RE: Condition step not working in Workflow<BR>> > To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> > Message-ID:<BR>> > <082C942F46528B44B5463D3C2A1FF0F40E5BB199@corp-m-exch2.corp.odfl.com><BR>> > Content-Type: text/plain; charset="us-ascii"<BR>> > <BR>> > Hi Mike,<BR>> > <BR>> > The step actually completes. The next step (condition checking for T<BR>> or<BR>> > F) does not start if the result of the method is F, but the condition<BR>> is<BR>> > executed if the result of the method is T.<BR>> > <BR>> > I'll give your suggestion a try.<BR>> > <BR>> > Regards,<BR>> > Sue T. Doughty<BR>> > SAP Workflow Specialist<BR>> > Old Dominion Freight Line, Inc.<BR>> > 500 Old Dominion Way<BR>> > Thomasville, NC 27360<BR>> > Phone: (336) 822-5189<BR>> > Toll Free (800 ) 432-6335, ext. 5189<BR>> > Email: sue.doughty@odfl.com<BR>> > -----Original Message-----<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> Behalf<BR>> > Of Mike Pokraka<BR>> > Sent: Thursday, February 28, 2008 7:54 AM<BR>> > To: SAP Workflow Users' Group<BR>> > Subject: RE: Condition step not working in Workflow<BR>> > <BR>> > Just to confirm the obvious: Does the step actually complete? (Status<BR>> > Completed)<BR>> > If it just completes and the next step doesn't start then your WF<BR>> > definition couldbe corrupt. Put the two steps into a test WF and see<BR>> if<BR>> > that works.<BR>> > <BR>> > On Wed, February 27, 2008 6:20 pm, Sue Doughty wrote:<BR>> > > Hi Mike,<BR>> > ><BR>> > > I changed the data type to SY-INPUT and still get the same results.<BR>> > ><BR>> > > Thank you for the suggestion though. I'm willing to try anything. I<BR>> > > hope that it is not something so simple that I'll feel really stupid<BR>> > > when I find it. :-)<BR>> > ><BR>> > > Regards,<BR>> > > Sue T. Doughty<BR>> > > SAP Workflow Specialist<BR>> > > Old Dominion Freight Line, Inc.<BR>> > > 500 Old Dominion Way<BR>> > > Thomasville, NC 27360<BR>> > > Phone: (336) 822-5189<BR>> > > Toll Free (800 ) 432-6335, ext. 5189<BR>> > > Email: sue.doughty@odfl.com<BR>> > ><BR>> > > -----Original Message-----<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > Behalf<BR>> > > Of Mike Pokraka<BR>> > > Sent: Wednesday, February 27, 2008 12:13 PM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Condition step not working in Workflow<BR>> > ><BR>> > > Hmm, not too sure then. I thought I'd mention as it would be worth<BR>> > > checking. Also make sure your data type is valid for the values. Try<BR>> > > changing it to SY-INPUT just to make sure.<BR>> > ><BR>> > > On Wed, February 27, 2008 4:11 pm, Sue Doughty wrote:<BR>> > >> Hi Mike,<BR>> > >><BR>> > >> Thanks for your reply.<BR>> > >><BR>> > >> I am not using a result parameter even though I tried that when it<BR>> > did<BR>> > >> not work the way I had it at first. Neither way works. I can see in<BR>> > >> the workflow log that my export parameter (ImageFound) is being<BR>> > >> populated with the correct 'T' or 'F' value, but the Results<BR>> > > processing<BR>> > >> step is not being executed with an F value - it only executes when<BR>> > the<BR>> > >> export parameter contains a 'T' value.<BR>> > >><BR>> > >> I can't use a virtual attribute because the input parameters to the<BR>> > >> method change with each call to the method (i.e., doctype and<BR>> > >> imagedate).<BR>> > >><BR>> > >> Regards,<BR>> > >> Sue T. Doughty<BR>> > >> SAP Workflow Specialist<BR>> > >> Old Dominion Freight Line, Inc.<BR>> > >> 500 Old Dominion Way<BR>> > >> Thomasville, NC 27360<BR>> > >> Phone: (336) 822-5189<BR>> > >> Toll Free (800 ) 432-6335, ext. 5189<BR>> > >> Email: sue.doughty@odfl.com<BR>> > >> -----Original Message-----<BR>> > >> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > > Behalf<BR>> > >> Of Mike Pokraka<BR>> > >> Sent: Wednesday, February 27, 2008 10:44 AM<BR>> > >> To: SAP Workflow Users' Group<BR>> > >> Subject: Re: Condition step not working in Workflow<BR>> > >><BR>> > >> Hi Sue,<BR>> > >> Are you using a standard return parameter or a result parameter?<BR>> > >> ("Result<BR>> > >> parameter" checkbox on your method properties).<BR>> > >> Result parameters behave differently, T/F must be defined within<BR>> the<BR>> > >> data<BR>> > >> dictionary and become separate outcomes of the method.<BR>> > >> Also, perhaps a virtual attribute might be easier if this is all<BR>> that<BR>> > >> the<BR>> > >> method does...<BR>> > >><BR>> > >> Cheers,<BR>> > >> Mike<BR>> > >><BR>> > >> On Tue, February 26, 2008 5:06 pm, Sue Doughty wrote:<BR>> > >>> We are on 4.7, ECC 6.0<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> I have a sub-workflow that executes a loop until a result flag is<BR>> > set<BR>> > >> to<BR>> > >>> T. It executes a method that reads a table with some information.<BR>> > > If<BR>> > >>> the record is found, the result is set to T, if not it is set to F<BR>> > > and<BR>> > >>> the result container is set in the method. The next step is a<BR>> > >> condition<BR>> > >>> to check the result. If T, the loop and sub-workflow are<BR>> completed,<BR>> > >> if<BR>> > >>> F, it waits and tries again after five minutes.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> My problem: If the method executes and the result is T, the<BR>> > workflow<BR>> > >>> works as designed. If the method returns a result of F, the<BR>> > workflow<BR>> > >>> stops at that step and does not move to the condition step to<BR>> check<BR>> > >> the<BR>> > >>> result.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> I can see that the method is returning the result container. If<BR>> the<BR>> > >>> Result = T, I can see that the Result container is sent back to<BR>> the<BR>> > >>> sub-workflow. When I look at the step in the log, it says that the<BR>> > >>> background item was created, started, work item processing is<BR>> > > complete<BR>> > >>> and the result processing is done with no errors.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> If the Result is F, I can see that the method is returning the<BR>> > result<BR>> > >>> container, but the workflow container does NOT get set to the<BR>> > Result.<BR>> > >>> When I look at the step in the log, it says that the background<BR>> item<BR>> > >> was<BR>> > >>> created; started and work item processing is complete with no<BR>> > errors,<BR>> > >>> BUT the Result Processing is NOT done.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> What am I missing? Why is the Result processing being done for one<BR>> > >>> result but not the other?<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> Regards,<BR>> > >>><BR>> > >>> Sue T. Doughty<BR>> > >>><BR>> > >>> SAP Workflow Specialist<BR>> > >>><BR>> > >>> Old Dominion Freight Line, Inc.<BR>> > >>><BR>> > >>> 500 Old Dominion Way<BR>> > >>><BR>> > >>> Thomasville, NC 27360<BR>> > >>><BR>> > >>> Phone: (336) 822-5189<BR>> > >>><BR>> > >>> Toll Free (800 ) 432-6335, ext. 5189<BR>> > >>><BR>> > >>> Email: sue.doughty@odfl.com<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> ****************************<BR>> > >>> CONFIDENTIALITY NOTICE: The information contained in this message<BR>> > may<BR>> > >> be<BR>> > >>> confidential, privileged, proprietary, or otherwise legally exempt<BR>> > >> from<BR>> > >>> disclosure. If the reader of this message is not the intended<BR>> > >> recipient,<BR>> > >>> or an employee or agent responsible for delivering this message to<BR>> > > the<BR>> > >>> intended recipient, you are hereby notified that you are not<BR>> > >> authorized to<BR>> > >>> read, print, retain, copy or disseminate this message, any part of<BR>> > > it,<BR>> > >> or<BR>> > >>> any attachments. If you have received this message in error,<BR>> please<BR>> > >> delete<BR>> > >>> this message and any attachments from your system without reading<BR>> > the<BR>> > >>> content and notify the sender immediately of the inadvertent<BR>> > >> transmission.<BR>> > >>> Thank you for your cooperation.<BR>> > >>><BR>> > >>> _______________________________________________<BR>> > >>> SAP-WUG mailing list<BR>> > >>> SAP-WUG@mit.edu<BR>> > >>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >>><BR>> > >><BR>> > >><BR>> > >> _______________________________________________<BR>> > >> SAP-WUG mailing list<BR>> > >> SAP-WUG@mit.edu<BR>> > >> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >><BR>> > >><BR>> > >> ****************************<BR>> > >> CONFIDENTIALITY NOTICE: The information contained in this message<BR>> may<BR>> > > be<BR>> > >> confidential, privileged, proprietary, or otherwise legally exempt<BR>> > > from<BR>> > >> disclosure. If the reader of this message is not the intended<BR>> > > recipient,<BR>> > >> or an employee or agent responsible for delivering this message to<BR>> > the<BR>> > >> intended recipient, you are hereby notified that you are not<BR>> > > authorized to<BR>> > >> read, print, retain, copy or disseminate this message, any part of<BR>> > it,<BR>> > > or<BR>> > >> any attachments. If you have received this message in error, please<BR>> > > delete<BR>> > >> this message and any attachments from your system without reading<BR>> the<BR>> > >> content and notify the sender immediately of the inadvertent<BR>> > > transmission.<BR>> > >> Thank you for your cooperation.<BR>> > >><BR>> > >> _______________________________________________<BR>> > >> SAP-WUG mailing list<BR>> > >> SAP-WUG@mit.edu<BR>> > >> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >><BR>> > ><BR>> > ><BR>> > > _______________________________________________<BR>> > > SAP-WUG mailing list<BR>> > > SAP-WUG@mit.edu<BR>> > > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > ><BR>> > ><BR>> > > ****************************<BR>> > > CONFIDENTIALITY NOTICE: The information contained in this message<BR>> may<BR>> > be<BR>> > > confidential, privileged, proprietary, or otherwise legally exempt<BR>> > from<BR>> > > disclosure. If the reader of this message is not the intended<BR>> > recipient,<BR>> > > or an employee or agent responsible for delivering this message to<BR>> the<BR>> > > intended recipient, you are hereby notified that you are not<BR>> > authorized to<BR>> > > read, print, retain, copy or disseminate this message, any part of<BR>> it,<BR>> > or<BR>> > > any attachments. If you have received this message in error, please<BR>> > delete<BR>> > > this message and any attachments from your system without reading<BR>> the<BR>> > > content and notify the sender immediately of the inadvertent<BR>> > transmission.<BR>> > > Thank you for your cooperation.<BR>> > ><BR>> > > _______________________________________________<BR>> > > SAP-WUG mailing list<BR>> > > SAP-WUG@mit.edu<BR>> > > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > ><BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > ****************************<BR>> > CONFIDENTIALITY NOTICE: The information contained in this message may<BR>> be confidential, privileged, proprietary, or otherwise legally exempt<BR>> from disclosure. If the reader of this message is not the intended<BR>> recipient, or an employee or agent responsible for delivering this<BR>> message to the intended recipient, you are hereby notified that you are<BR>> not authorized to read, print, retain, copy or disseminate this message,<BR>> any part of it, or any attachments. If you have received this message in<BR>> error, please delete this message and any attachments from your system<BR>> without reading the content and notify the sender immediately of the<BR>> inadvertent transmission. Thank you for your cooperation.<BR>> > <BR>> > <BR>> > <BR>> > ------------------------------<BR>> > <BR>> > Message: 2<BR>> > Date: Thu, 28 Feb 2008 09:53:03 -0500<BR>> > From: "Sue Doughty" <Sue.Doughty@odfl.com><BR>> > Subject: RE: Condition step not working in Workflow<BR>> > To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> > Message-ID:<BR>> > <082C942F46528B44B5463D3C2A1FF0F40E5BB327@corp-m-exch2.corp.odfl.com><BR>> > Content-Type: text/plain; charset="us-ascii"<BR>> > <BR>> > Hi Mike,<BR>> > <BR>> > I tried creating the dummy method that just takes in the T or F and<BR>> > returns the T or F that was sent in like you said....got same results.<BR>> > <BR>> > I tried creating a new workflow with the new dummy task and a new<BR>> > condition step (that reads the workflow container that is updated from<BR>> > the method looking for the T or F)....got same results.<BR>> > <BR>> > I tried change T and F to Y and N....got same results.<BR>> > <BR>> > I can see the output container from the method in the workflow log.<BR>> > But, if the condition is false, the output container from the method<BR>> is<BR>> > not returned to the workflow container and the condition step is not<BR>> > executed. If the condition is true, the output container from the<BR>> > method is returned to the workflow container and the condition step is<BR>> > executed. <BR>> > <BR>> > I have an OSS note open with SAP. I can see where they have come into<BR>> > the system and tested it, but as of yet, have not gotten a response<BR>> from<BR>> > them.<BR>> > <BR>> > I am totally befuddled!!!<BR>> > <BR>> > Regards,<BR>> > Sue T. Doughty<BR>> > SAP Workflow Specialist<BR>> > Old Dominion Freight Line, Inc.<BR>> > 500 Old Dominion Way<BR>> > Thomasville, NC 27360<BR>> > Phone: (336) 822-5189<BR>> > Toll Free (800 ) 432-6335, ext. 5189<BR>> > Email: sue.doughty@odfl.com<BR>> > <BR>> > -----Original Message-----<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> Behalf<BR>> > Of Mike Pokraka<BR>> > Sent: Thursday, February 28, 2008 7:54 AM<BR>> > To: SAP Workflow Users' Group<BR>> > Subject: RE: Condition step not working in Workflow<BR>> > <BR>> > Just to confirm the obvious: Does the step actually complete? (Status<BR>> > Completed)<BR>> > If it just completes and the next step doesn't start then your WF<BR>> > definition couldbe corrupt. Put the two steps into a test WF and see<BR>> if<BR>> > that works.<BR>> > <BR>> > On Wed, February 27, 2008 6:20 pm, Sue Doughty wrote:<BR>> > > Hi Mike,<BR>> > ><BR>> > > I changed the data type to SY-INPUT and still get the same results.<BR>> > ><BR>> > > Thank you for the suggestion though. I'm willing to try anything. I<BR>> > > hope that it is not something so simple that I'll feel really stupid<BR>> > > when I find it. :-)<BR>> > ><BR>> > > Regards,<BR>> > > Sue T. Doughty<BR>> > > SAP Workflow Specialist<BR>> > > Old Dominion Freight Line, Inc.<BR>> > > 500 Old Dominion Way<BR>> > > Thomasville, NC 27360<BR>> > > Phone: (336) 822-5189<BR>> > > Toll Free (800 ) 432-6335, ext. 5189<BR>> > > Email: sue.doughty@odfl.com<BR>> > ><BR>> > > -----Original Message-----<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > Behalf<BR>> > > Of Mike Pokraka<BR>> > > Sent: Wednesday, February 27, 2008 12:13 PM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Condition step not working in Workflow<BR>> > ><BR>> > > Hmm, not too sure then. I thought I'd mention as it would be worth<BR>> > > checking. Also make sure your data type is valid for the values. Try<BR>> > > changing it to SY-INPUT just to make sure.<BR>> > ><BR>> > > On Wed, February 27, 2008 4:11 pm, Sue Doughty wrote:<BR>> > >> Hi Mike,<BR>> > >><BR>> > >> Thanks for your reply.<BR>> > >><BR>> > >> I am not using a result parameter even though I tried that when it<BR>> > did<BR>> > >> not work the way I had it at first. Neither way works. I can see in<BR>> > >> the workflow log that my export parameter (ImageFound) is being<BR>> > >> populated with the correct 'T' or 'F' value, but the Results<BR>> > > processing<BR>> > >> step is not being executed with an F value - it only executes when<BR>> > the<BR>> > >> export parameter contains a 'T' value.<BR>> > >><BR>> > >> I can't use a virtual attribute because the input parameters to the<BR>> > >> method change with each call to the method (i.e., doctype and<BR>> > >> imagedate).<BR>> > >><BR>> > >> Regards,<BR>> > >> Sue T. Doughty<BR>> > >> SAP Workflow Specialist<BR>> > >> Old Dominion Freight Line, Inc.<BR>> > >> 500 Old Dominion Way<BR>> > >> Thomasville, NC 27360<BR>> > >> Phone: (336) 822-5189<BR>> > >> Toll Free (800 ) 432-6335, ext. 5189<BR>> > >> Email: sue.doughty@odfl.com<BR>> > >> -----Original Message-----<BR>> > >> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > > Behalf<BR>> > >> Of Mike Pokraka<BR>> > >> Sent: Wednesday, February 27, 2008 10:44 AM<BR>> > >> To: SAP Workflow Users' Group<BR>> > >> Subject: Re: Condition step not working in Workflow<BR>> > >><BR>> > >> Hi Sue,<BR>> > >> Are you using a standard return parameter or a result parameter?<BR>> > >> ("Result<BR>> > >> parameter" checkbox on your method properties).<BR>> > >> Result parameters behave differently, T/F must be defined within<BR>> the<BR>> > >> data<BR>> > >> dictionary and become separate outcomes of the method.<BR>> > >> Also, perhaps a virtual attribute might be easier if this is all<BR>> that<BR>> > >> the<BR>> > >> method does...<BR>> > >><BR>> > >> Cheers,<BR>> > >> Mike<BR>> > >><BR>> > >> On Tue, February 26, 2008 5:06 pm, Sue Doughty wrote:<BR>> > >>> We are on 4.7, ECC 6.0<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> I have a sub-workflow that executes a loop until a result flag is<BR>> > set<BR>> > >> to<BR>> > >>> T. It executes a method that reads a table with some information.<BR>> > > If<BR>> > >>> the record is found, the result is set to T, if not it is set to F<BR>> > > and<BR>> > >>> the result container is set in the method. The next step is a<BR>> > >> condition<BR>> > >>> to check the result. If T, the loop and sub-workflow are<BR>> completed,<BR>> > >> if<BR>> > >>> F, it waits and tries again after five minutes.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> My problem: If the method executes and the result is T, the<BR>> > workflow<BR>> > >>> works as designed. If the method returns a result of F, the<BR>> > workflow<BR>> > >>> stops at that step and does not move to the condition step to<BR>> check<BR>> > >> the<BR>> > >>> result.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> I can see that the method is returning the result container. If<BR>> the<BR>> > >>> Result = T, I can see that the Result container is sent back to<BR>> the<BR>> > >>> sub-workflow. When I look at the step in the log, it says that the<BR>> > >>> background item was created, started, work item processing is<BR>> > > complete<BR>> > >>> and the result processing is done with no errors.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> If the Result is F, I can see that the method is returning the<BR>> > result<BR>> > >>> container, but the workflow container does NOT get set to the<BR>> > Result.<BR>> > >>> When I look at the step in the log, it says that the background<BR>> item<BR>> > >> was<BR>> > >>> created; started and work item processing is complete with no<BR>> > errors,<BR>> > >>> BUT the Result Processing is NOT done.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> What am I missing? Why is the Result processing being done for one<BR>> > >>> result but not the other?<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> Regards,<BR>> > >>><BR>> > >>> Sue T. Doughty<BR>> > >>><BR>> > >>> SAP Workflow Specialist<BR>> > >>><BR>> > >>> Old Dominion Freight Line, Inc.<BR>> > >>><BR>> > >>> 500 Old Dominion Way<BR>> > >>><BR>> > >>> Thomasville, NC 27360<BR>> > >>><BR>> > >>> Phone: (336) 822-5189<BR>> > >>><BR>> > >>> Toll Free (800 ) 432-6335, ext. 5189<BR>> > >>><BR>> > >>> Email: sue.doughty@odfl.com<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> ****************************<BR>> > >>> CONFIDENTIALITY NOTICE: The information contained in this message<BR>> > may<BR>> > >> be<BR>> > >>> confidential, privileged, proprietary, or otherwise legally exempt<BR>> > >> from<BR>> > >>> disclosure. If the reader of this message is not the intended<BR>> > >> recipient,<BR>> > >>> or an employee or agent responsible for delivering this message to<BR>> > > the<BR>> > >>> intended recipient, you are hereby notified that you are not<BR>> > >> authorized to<BR>> > >>> read, print, retain, copy or disseminate this message, any part of<BR>> > > it,<BR>> > >> or<BR>> > >>> any attachments. If you have received this message in error,<BR>> please<BR>> > >> delete<BR>> > >>> this message and any attachments from your system without reading<BR>> > the<BR>> > >>> content and notify the sender immediately of the inadvertent<BR>> > >> transmission.<BR>> > >>> Thank you for your cooperation.<BR>> > >>><BR>> > >>> _______________________________________________<BR>> > >>> SAP-WUG mailing list<BR>> > >>> SAP-WUG@mit.edu<BR>> > >>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >>><BR>> > >><BR>> > >><BR>> > >> _______________________________________________<BR>> > >> SAP-WUG mailing list<BR>> > >> SAP-WUG@mit.edu<BR>> > >> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >><BR>> > >><BR>> > >> ****************************<BR>> > >> CONFIDENTIALITY NOTICE: The information contained in this message<BR>> may<BR>> > > be<BR>> > >> confidential, privileged, proprietary, or otherwise legally exempt<BR>> > > from<BR>> > >> disclosure. If the reader of this message is not the intended<BR>> > > recipient,<BR>> > >> or an employee or agent responsible for delivering this message to<BR>> > the<BR>> > >> intended recipient, you are hereby notified that you are not<BR>> > > authorized to<BR>> > >> read, print, retain, copy or disseminate this message, any part of<BR>> > it,<BR>> > > or<BR>> > >> any attachments. If you have received this message in error, please<BR>> > > delete<BR>> > >> this message and any attachments from your system without reading<BR>> the<BR>> > >> content and notify the sender immediately of the inadvertent<BR>> > > transmission.<BR>> > >> Thank you for your cooperation.<BR>> > >><BR>> > >> _______________________________________________<BR>> > >> SAP-WUG mailing list<BR>> > >> SAP-WUG@mit.edu<BR>> > >> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >><BR>> > ><BR>> > ><BR>> > > _______________________________________________<BR>> > > SAP-WUG mailing list<BR>> > > SAP-WUG@mit.edu<BR>> > > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > ><BR>> > ><BR>> > > ****************************<BR>> > > CONFIDENTIALITY NOTICE: The information contained in this message<BR>> may<BR>> > be<BR>> > > confidential, privileged, proprietary, or otherwise legally exempt<BR>> > from<BR>> > > disclosure. If the reader of this message is not the intended<BR>> > recipient,<BR>> > > or an employee or agent responsible for delivering this message to<BR>> the<BR>> > > intended recipient, you are hereby notified that you are not<BR>> > authorized to<BR>> > > read, print, retain, copy or disseminate this message, any part of<BR>> it,<BR>> > or<BR>> > > any attachments. If you have received this message in error, please<BR>> > delete<BR>> > > this message and any attachments from your system without reading<BR>> the<BR>> > > content and notify the sender immediately of the inadvertent<BR>> > transmission.<BR>> > > Thank you for your cooperation.<BR>> > ><BR>> > > _______________________________________________<BR>> > > SAP-WUG mailing list<BR>> > > SAP-WUG@mit.edu<BR>> > > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > ><BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > ****************************<BR>> > CONFIDENTIALITY NOTICE: The information contained in this message may<BR>> be confidential, privileged, proprietary, or otherwise legally exempt<BR>> from disclosure. If the reader of this message is not the intended<BR>> recipient, or an employee or agent responsible for delivering this<BR>> message to the intended recipient, you are hereby notified that you are<BR>> not authorized to read, print, retain, copy or disseminate this message,<BR>> any part of it, or any attachments. If you have received this message in<BR>> error, please delete this message and any attachments from your system<BR>> without reading the content and notify the sender immediately of the<BR>> inadvertent transmission. Thank you for your cooperation.<BR>> > <BR>> > <BR>> > <BR>> > ------------------------------<BR>> > <BR>> > Message: 3<BR>> > Date: Thu, 28 Feb 2008 09:29:50 -0600<BR>> > From: "Sample, Rick" <Rick.Sample@gbe.com><BR>> > Subject: RE: Condition step not working in Workflow<BR>> > To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> > Message-ID:<BR>> > <1897E92A96C47648A6574CB9A51C6407055805CD@SEBEV1PW.graybar.com><BR>> > Content-Type: text/plain; charset="us-ascii"<BR>> > <BR>> > Hi Sue (a.k.a. Ms. Befuddled. LOL)<BR>> > <BR>> > This is interesting. Before you through in the towel do you mind<BR>> > checking a few things?<BR>> > <BR>> > 1: <BR>> > Try changing your data to just CHAR1 type for all values in your test<BR>> WF<BR>> > / method, <BR>> > GET_ELEMENT_CONTAINER the values to same data type in method at<BR>> > beginning of method, (inspect that you can actually get values)<BR>> > SET_ELEMENT_CONTAINER to same on export, (inspect you are actually<BR>> > setting the values)<BR>> > ensure all bindings are setup.<BR>> > <BR>> > 2:<BR>> > You are in ECC6? If so, the below may be a long shot, but worth<BR>> > remembering anyway. Because I had a similar sounding issue on<BR>> conversion<BR>> > from 4.6c to ECC6. Bindings have new options. (Nice to know after the<BR>> > fact eh!)<BR>> > <BR>> > 4.6c by default, if you have bindings setup for task->WF but DO NOT do<BR>> a<BR>> > SET_ELEMENT_CONTAINER in method it will NOT overwrite your WF values<BR>> > even though the binding are setup. <BR>> > * This, in my option, is the way it should have worked in the first<BR>> > place! You have a binding with null value...it should set null values!<BR>> > Period!<BR>> > Developers job to explicitly GET/SET in the code. (Not bindings!) Just<BR>> > my .02 worth. <BR>> > <BR>> > ECC6, by default, WILL overwrite empty / initial values unless you<BR>> > change the bindings to ignore empty/initial values.<BR>> > <BR>> > I do not like the extra options on bindings. Just a personal<BR>> preference<BR>> > I suppose. So, what I now do is GET/SET all values in/out of<BR>> > task-method. <BR>> > That way, I don't have to squirrel through code AND bindings to figure<BR>> > out what is getting passed back if empty / initial values. If I want<BR>> to<BR>> > pass back an empty value, I set the value to empty in the method. I<BR>> find<BR>> > it more confusing to use the extra binding options. (Also, you can't<BR>> add<BR>> > a "comment" on binding to remind yourself as to the whys, as you can<BR>> in<BR>> > code)<BR>> > <BR>> > 3:<BR>> > If using ECC6, verify you are have all same data types for the values<BR>> > you are passing around. <BR>> > I know in 4.6c you can create the containers to a data type, but it<BR>> > always pass char 255 strings no matter what. i.e. if you import via<BR>> > GET_ELEMENT_CONTAINER, you got a string. Not a type data value you set<BR>> > in WF or Task. (Can't remember if ECC6 does this. Don't have it in<BR>> front<BR>> > of me at the moment!)<BR>> > <BR>> > 4:<BR>> > Verify that the method is not terminating on your F condition before<BR>> it<BR>> > gets a chance to set the value. <BR>> > <BR>> > If these are not the issue, and you would like more assistance, feel<BR>> > free to ask. (I have an inch of breathing room to spare today!)<BR>> > <BR>> > Rick Sample<BR>> > SAP Business Workflow Developer<BR>> > Graybar, Inc.<BR>> > 11885 Lackland Dr.<BR>> > St. Louis, MO. 63146<BR>> > 314-573-5822<BR>> > <BR>> > -----Original Message-----<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> Behalf<BR>> > Of Sue Doughty<BR>> > Sent: Thursday, February 28, 2008 8:53 AM<BR>> > To: SAP Workflow Users' Group<BR>> > Subject: RE: Condition step not working in Workflow<BR>> > <BR>> > Hi Mike,<BR>> > <BR>> > I tried creating the dummy method that just takes in the T or F and<BR>> > returns the T or F that was sent in like you said....got same results.<BR>> > <BR>> > I tried creating a new workflow with the new dummy task and a new<BR>> > condition step (that reads the workflow container that is updated from<BR>> > the method looking for the T or F)....got same results.<BR>> > <BR>> > I tried change T and F to Y and N....got same results.<BR>> > <BR>> > I can see the output container from the method in the workflow log.<BR>> > But, if the condition is false, the output container from the method<BR>> is<BR>> > not returned to the workflow container and the condition step is not<BR>> > executed. If the condition is true, the output container from the<BR>> > method is returned to the workflow container and the condition step is<BR>> > executed. <BR>> > <BR>> > I have an OSS note open with SAP. I can see where they have come into<BR>> > the system and tested it, but as of yet, have not gotten a response<BR>> from<BR>> > them.<BR>> > <BR>> > I am totally befuddled!!!<BR>> > <BR>> > Regards,<BR>> > Sue T. Doughty<BR>> > SAP Workflow Specialist<BR>> > Old Dominion Freight Line, Inc.<BR>> > 500 Old Dominion Way<BR>> > Thomasville, NC 27360<BR>> > Phone: (336) 822-5189<BR>> > Toll Free (800 ) 432-6335, ext. 5189<BR>> > Email: sue.doughty@odfl.com<BR>> > <BR>> > -----Original Message-----<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> Behalf<BR>> > Of Mike Pokraka<BR>> > Sent: Thursday, February 28, 2008 7:54 AM<BR>> > To: SAP Workflow Users' Group<BR>> > Subject: RE: Condition step not working in Workflow<BR>> > <BR>> > Just to confirm the obvious: Does the step actually complete? (Status<BR>> > Completed)<BR>> > If it just completes and the next step doesn't start then your WF<BR>> > definition couldbe corrupt. Put the two steps into a test WF and see<BR>> if<BR>> > that works.<BR>> > <BR>> > On Wed, February 27, 2008 6:20 pm, Sue Doughty wrote:<BR>> > > Hi Mike,<BR>> > ><BR>> > > I changed the data type to SY-INPUT and still get the same results.<BR>> > ><BR>> > > Thank you for the suggestion though. I'm willing to try anything. I<BR>> > > hope that it is not something so simple that I'll feel really stupid<BR>> > > when I find it. :-)<BR>> > ><BR>> > > Regards,<BR>> > > Sue T. Doughty<BR>> > > SAP Workflow Specialist<BR>> > > Old Dominion Freight Line, Inc.<BR>> > > 500 Old Dominion Way<BR>> > > Thomasville, NC 27360<BR>> > > Phone: (336) 822-5189<BR>> > > Toll Free (800 ) 432-6335, ext. 5189<BR>> > > Email: sue.doughty@odfl.com<BR>> > ><BR>> > > -----Original Message-----<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > Behalf<BR>> > > Of Mike Pokraka<BR>> > > Sent: Wednesday, February 27, 2008 12:13 PM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Condition step not working in Workflow<BR>> > ><BR>> > > Hmm, not too sure then. I thought I'd mention as it would be worth<BR>> > > checking. Also make sure your data type is valid for the values. Try<BR>> > > changing it to SY-INPUT just to make sure.<BR>> > ><BR>> > > On Wed, February 27, 2008 4:11 pm, Sue Doughty wrote:<BR>> > >> Hi Mike,<BR>> > >><BR>> > >> Thanks for your reply.<BR>> > >><BR>> > >> I am not using a result parameter even though I tried that when it<BR>> > did<BR>> > >> not work the way I had it at first. Neither way works. I can see in<BR>> > >> the workflow log that my export parameter (ImageFound) is being<BR>> > >> populated with the correct 'T' or 'F' value, but the Results<BR>> > > processing<BR>> > >> step is not being executed with an F value - it only executes when<BR>> > the<BR>> > >> export parameter contains a 'T' value.<BR>> > >><BR>> > >> I can't use a virtual attribute because the input parameters to the<BR>> > >> method change with each call to the method (i.e., doctype and<BR>> > >> imagedate).<BR>> > >><BR>> > >> Regards,<BR>> > >> Sue T. Doughty<BR>> > >> SAP Workflow Specialist<BR>> > >> Old Dominion Freight Line, Inc.<BR>> > >> 500 Old Dominion Way<BR>> > >> Thomasville, NC 27360<BR>> > >> Phone: (336) 822-5189<BR>> > >> Toll Free (800 ) 432-6335, ext. 5189<BR>> > >> Email: sue.doughty@odfl.com<BR>> > >> -----Original Message-----<BR>> > >> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > > Behalf<BR>> > >> Of Mike Pokraka<BR>> > >> Sent: Wednesday, February 27, 2008 10:44 AM<BR>> > >> To: SAP Workflow Users' Group<BR>> > >> Subject: Re: Condition step not working in Workflow<BR>> > >><BR>> > >> Hi Sue,<BR>> > >> Are you using a standard return parameter or a result parameter?<BR>> > >> ("Result<BR>> > >> parameter" checkbox on your method properties).<BR>> > >> Result parameters behave differently, T/F must be defined within<BR>> the<BR>> > >> data<BR>> > >> dictionary and become separate outcomes of the method.<BR>> > >> Also, perhaps a virtual attribute might be easier if this is all<BR>> that<BR>> > >> the<BR>> > >> method does...<BR>> > >><BR>> > >> Cheers,<BR>> > >> Mike<BR>> > >><BR>> > >> On Tue, February 26, 2008 5:06 pm, Sue Doughty wrote:<BR>> > >>> We are on 4.7, ECC 6.0<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> I have a sub-workflow that executes a loop until a result flag is<BR>> > set<BR>> > >> to<BR>> > >>> T. It executes a method that reads a table with some information.<BR>> > > If<BR>> > >>> the record is found, the result is set to T, if not it is set to F<BR>> > > and<BR>> > >>> the result container is set in the method. The next step is a<BR>> > >> condition<BR>> > >>> to check the result. If T, the loop and sub-workflow are<BR>> completed,<BR>> > >> if<BR>> > >>> F, it waits and tries again after five minutes.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> My problem: If the method executes and the result is T, the<BR>> > workflow<BR>> > >>> works as designed. If the method returns a result of F, the<BR>> > workflow<BR>> > >>> stops at that step and does not move to the condition step to<BR>> check<BR>> > >> the<BR>> > >>> result.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> I can see that the method is returning the result container. If<BR>> the<BR>> > >>> Result = T, I can see that the Result container is sent back to<BR>> the<BR>> > >>> sub-workflow. When I look at the step in the log, it says that the<BR>> > >>> background item was created, started, work item processing is<BR>> > > complete<BR>> > >>> and the result processing is done with no errors.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> If the Result is F, I can see that the method is returning the<BR>> > result<BR>> > >>> container, but the workflow container does NOT get set to the<BR>> > Result.<BR>> > >>> When I look at the step in the log, it says that the background<BR>> item<BR>> > >> was<BR>> > >>> created; started and work item processing is complete with no<BR>> > errors,<BR>> > >>> BUT the Result Processing is NOT done.<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> What am I missing? Why is the Result processing being done for one<BR>> > >>> result but not the other?<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> Regards,<BR>> > >>><BR>> > >>> Sue T. Doughty<BR>> > >>><BR>> > >>> SAP Workflow Specialist<BR>> > >>><BR>> > >>> Old Dominion Freight Line, Inc.<BR>> > >>><BR>> > >>> 500 Old Dominion Way<BR>> > >>><BR>> > >>> Thomasville, NC 27360<BR>> > >>><BR>> > >>> Phone: (336) 822-5189<BR>> > >>><BR>> > >>> Toll Free (800 ) 432-6335, ext. 5189<BR>> > >>><BR>> > >>> Email: sue.doughty@odfl.com<BR>> > >>><BR>> > >>><BR>> > >>><BR>> > >>> ****************************<BR>> > >>> CONFIDENTIALITY NOTICE: The information contained in this message<BR>> > may<BR>> > >> be<BR>> > >>> confidential, privileged, proprietary, or otherwise legally exempt<BR>> > >> from<BR>> > >>> disclosure. If the reader of this message is not the intended<BR>> > >> recipient,<BR>> > >>> or an employee or agent responsible for delivering this message to<BR>> > > the<BR>> > >>> intended recipient, you are hereby notified that you are not<BR>> > >> authorized to<BR>> > >>> read, print, retain, copy or disseminate this message, any part of<BR>> > > it,<BR>> > >> or<BR>> > >>> any attachments. If you have received this message in error,<BR>> please<BR>> > >> delete<BR>> > >>> this message and any attachments from your system without reading<BR>> > the<BR>> > >>> content and notify the sender immediately of the inadvertent<BR>> > >> transmission.<BR>> > >>> Thank you for your cooperation.<BR>> > >>><BR>> > >>> _______________________________________________<BR>> > >>> SAP-WUG mailing list<BR>> > >>> SAP-WUG@mit.edu<BR>> > >>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >>><BR>> > >><BR>> > >><BR>> > >> _______________________________________________<BR>> > >> SAP-WUG mailing list<BR>> > >> SAP-WUG@mit.edu<BR>> > >> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >><BR>> > >><BR>> > >> ****************************<BR>> > >> CONFIDENTIALITY NOTICE: The information contained in this message<BR>> may<BR>> > > be<BR>> > >> confidential, privileged, proprietary, or otherwise legally exempt<BR>> > > from<BR>> > >> disclosure. If the reader of this message is not the intended<BR>> > > recipient,<BR>> > >> or an employee or agent responsible for delivering this message to<BR>> > the<BR>> > >> intended recipient, you are hereby notified that you are not<BR>> > > authorized to<BR>> > >> read, print, retain, copy or disseminate this message, any part of<BR>> > it,<BR>> > > or<BR>> > >> any attachments. If you have received this message in error, please<BR>> > > delete<BR>> > >> this message and any attachments from your system without reading<BR>> the<BR>> > >> content and notify the sender immediately of the inadvertent<BR>> > > transmission.<BR>> > >> Thank you for your cooperation.<BR>> > >><BR>> > >> _______________________________________________<BR>> > >> SAP-WUG mailing list<BR>> > >> SAP-WUG@mit.edu<BR>> > >> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > >><BR>> > ><BR>> > ><BR>> > > _______________________________________________<BR>> > > SAP-WUG mailing list<BR>> > > SAP-WUG@mit.edu<BR>> > > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > ><BR>> > ><BR>> > > ****************************<BR>> > > CONFIDENTIALITY NOTICE: The information contained in this message<BR>> may<BR>> > be<BR>> > > confidential, privileged, proprietary, or otherwise legally exempt<BR>> > from<BR>> > > disclosure. If the reader of this message is not the intended<BR>> > recipient,<BR>> > > or an employee or agent responsible for delivering this message to<BR>> the<BR>> > > intended recipient, you are hereby notified that you are not<BR>> > authorized to<BR>> > > read, print, retain, copy or disseminate this message, any part of<BR>> it,<BR>> > or<BR>> > > any attachments. If you have received this message in error, please<BR>> > delete<BR>> > > this message and any attachments from your system without reading<BR>> the<BR>> > > content and notify the sender immediately of the inadvertent<BR>> > transmission.<BR>> > > Thank you for your cooperation.<BR>> > ><BR>> > > _______________________________________________<BR>> > > SAP-WUG mailing list<BR>> > > SAP-WUG@mit.edu<BR>> > > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > ><BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > ****************************<BR>> > CONFIDENTIALITY NOTICE: The information contained in this message may<BR>> be<BR>> > confidential, privileged, proprietary, or otherwise legally exempt<BR>> from<BR>> > disclosure. If the reader of this message is not the intended<BR>> recipient,<BR>> > or an employee or agent responsible for delivering this message to the<BR>> > intended recipient, you are hereby notified that you are not<BR>> authorized<BR>> > to read, print, retain, copy or disseminate this message, any part of<BR>> > it, or any attachments. If you have received this message in error,<BR>> > please delete this message and any attachments from your system<BR>> without<BR>> > reading the content and notify the sender immediately of the<BR>> inadvertent<BR>> > transmission. Thank you for your cooperation.<BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > <BR>> > ------------------------------<BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > End of SAP-WUG Digest, Vol 39, Issue 78<BR>> > ***************************************<BR>> <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> Express yourself instantly with MSN Messenger! MSN Messenger<BR>> <http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080228/eec6fdc3/attachment.htm<BR>> <BR>> ------------------------------<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> <BR>> End of SAP-WUG Digest, Vol 39, Issue 81<BR>> ***************************************<BR><BR><br /><hr />Express yourself instantly with MSN Messenger! <a href='http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/' target='_new'>MSN Messenger</a></body>
</html>