Hi Priyank<br><br>Your queries have been quite endless really and I really appreciate Jocelyn for all the patience she has shown and replied, quite promptly, to all your queries so far. And what Mike says, does make a lot of sense, as you may have issues with your workflows in production that need fixing ASAP by someone with good knowledge in this area. From what we could see, you indeed lack this knowledge, which was already pointed out to you in one of your earlier threads by me.<br>
When experts like Mike are making some suggestions, you need to give them the respect they deserve and not misunderstand.<br>Finally, let me remind you that no one is compelled to answer your questions and any such basic level questions may remain unanswered thus delaying a fix in your productive environment.<br>
<br>Ravi<br>P.S.: I hope you see this mail in a positive light.... :)<br><br><div class="gmail_quote">On Sat, Jul 3, 2010 at 2:04 AM, <span dir="ltr"><<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Send SAP-WUG mailing list submissions to<br>
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a><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: Activating workflow without using SWDD tcode (Patil, Priyank)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 2 Jul 2010 16:42:35 +0530<br>
From: "Patil, Priyank" <<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a>><br>
Subject: RE: Activating workflow without using SWDD tcode<br>
To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
Message-ID:<br>
<<a href="mailto:79908A2D8E564E40BF42221D2EC963777DC98DAE10@MAIL801.KDS.KEANE.COM">79908A2D8E564E40BF42221D2EC963777DC98DAE10@MAIL801.KDS.KEANE.COM</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hey mikey cool..you could have told me the difference between the client dependent/independent transport request in WF rite:(..Thanks for your concern I really appreciate your gesture. This blog is awesome believe me.<br>
<br>
Thanks<br>
PD<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf Of Mike Pokraka<br>
Sent: Friday, July 02, 2010 4:33 PM<br>
To: SAP Workflow Users' Group<br>
Subject: RE: Activating workflow without using SWDD tcode<br>
<br>
Not sure if you misunderstood, I was genuinely trying to be helpful -<br>
that's the reason I gave you a justification as to why it would save your<br>
company a lot of money to send you on training.<br>
<br>
Learning is all good and well (and I've learnt a lot from this list<br>
myself), but production failures are not the best environment for this,<br>
and certainly not the cheapest for your company. You may get by figuring<br>
out WHAT is broken and how to fix it, but a course will do a much better<br>
job of teaching you WHY it's broken.<br>
<br>
Otherwise try and get them to buy you a copy of the WF book. Proceeds go<br>
to charity, so it will be a good deed as well!<br>
<br>
<br>
On Fri, July 2, 2010 11:12 am, Patil, Priyank wrote:<br>
> I was just wondering to know the difference between client<br>
> dependent/independent change request in workflow. Its all about learning a<br>
> new things.<br>
><br>
><br>
> Thanks<br>
> PD<br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
> Of Mike Pokraka<br>
> Sent: Friday, July 02, 2010 3:29 PM<br>
> To: SAP Workflow Users' Group<br>
> Subject: RE: Activating workflow without using SWDD tcode<br>
><br>
> A workflow course could be considered a behaviour-changing conversation.<br>
> If you really don't have any workflow skilled people then I would highly<br>
> recommend some training.<br>
> It will save your company good money in the long run - you have already<br>
> spend over two days on a problem that should take an hour at most to<br>
> resolve.<br>
><br>
><br>
><br>
> On Fri, July 2, 2010 8:09 am, Patil, Priyank wrote:<br>
>> Joce,<br>
>> Here we don't have any WF developers. We need to take care of<br>
>> everything. Could you tell me some details on behavior-changing<br>
>> conversation. Actually what is it and how it works?<br>
>><br>
>> Thanks<br>
>> PD<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
>> Of Dart, Jocelyn<br>
>> Sent: Friday, July 02, 2010 12:11 PM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: RE: Activating workflow without using SWDD tcode<br>
>><br>
>> No difference at all - event activation is event activation no matter<br>
>> where you do it.<br>
>> But that's why you want to watch the Linkages in Errors tab regularly -<br>
>> because if it's getting deactivated due to an error that's where it will<br>
>> appear.<br>
>> Of course if it's new transports deactivating it then you want to go and<br>
>> have a behaviour-changing conversation with your workflow developers.<br>
>> Regards<br>
>> Jocelyn<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
>> Of Patil, Priyank<br>
>> Sent: Friday, 2 July 2010 4:07 PM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: RE: Activating workflow without using SWDD tcode<br>
>><br>
>> Thanks Jocelyn its quite informative...But this is only to activate the<br>
>> event(swu0) attached to the WF I guess. But once iam done with it ,<br>
>> don't<br>
>> you think it will get deactivate again??.Because I feel its same like<br>
>> getting into SWDD and activate the event.I don't find any difference in<br>
>> SWU0 and getting into SWDD to reactivate the event . What is the<br>
>> difference in SWU0 and getting into SWDD(reactivate the event).<br>
>><br>
>> Thanks<br>
>> PD<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
>> Of Dart, Jocelyn<br>
>> Sent: Friday, July 02, 2010 11:19 AM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: RE: Activating workflow without using SWDD tcode<br>
>><br>
>> Ok - If neither of them are the event you are looking for then another<br>
>> way<br>
>> to fix event activation issues is through transaction SWU0 - simulate<br>
>> event.<br>
>><br>
>> Run the simulation on the event in question and it will show if there is<br>
>> any problem with the activation - e.g. if the workflow itself is not<br>
>> activated. If everything this is fine but it's just the event that is<br>
>> deactivated you can double click on the event activation line and you'll<br>
>> get a pop-up where you can change the event activation flag and save it.<br>
>><br>
>> When you've done that run SWU0 again to check everything is ok.<br>
>> Regard,s<br>
>> Jocelyn<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
>> Of Patil, Priyank<br>
>> Sent: Friday, 2 July 2010 3:38 PM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: RE: Activating workflow without using SWDD tcode<br>
>><br>
>> In that tab, we have 2 objects and associated events assigned to them.<br>
>> And<br>
>> linkage status/activation are marked I green color.<br>
>><br>
>> Thanks,<br>
>> PD<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
>> Of Dart, Jocelyn<br>
>> Sent: Friday, July 02, 2010 11:00 AM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: RE: Activating workflow without using SWDD tcode<br>
>><br>
>> Yes Patil that's fine... but transaction SWEQADM has 5 different tabs<br>
>> and<br>
>> you are describing the settings on the Basic Data tab.<br>
>> The settings you are using are correct and mean that you should then see<br>
>> any failed events in the Linkages with Errors tab..<br>
>><br>
>> So what Paul and I are asking is what are you seeing in the Linkages<br>
>> with<br>
>> Errors tab. So just try moving over to that Tab and see if the<br>
>> offending<br>
>> event is listed.<br>
>><br>
>><br>
>> Regards,<br>
>> Jocelyn<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
>> Of Patil, Priyank<br>
>> Sent: Friday, 2 July 2010 3:19 PM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: RE: Activating workflow without using SWDD tcode<br>
>><br>
>> How long!!..Its hard to find out but I guess, we merged 2 servers to one<br>
>> single instance. So on that time it may caused this issue.Anyways I<br>
>> changed in the basic event tab as 'Linkages with errors'. Under this<br>
>> the<br>
>> entries are -<br>
>> 1)Event linkages with errors must be set manually to "No errors"<br>
>> 2)Events can be redelivered to the receiver after errors<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
>> Of Rick Bakker<br>
>> Sent: Friday, July 02, 2010 10:41 AM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: Re: Activating workflow without using SWDD tcode<br>
>><br>
>> Hello,<br>
>><br>
>> How long has SWEQADM been set to that value, do you know?<br>
>> Any entries under the "Linkages with errors" tab?<br>
>><br>
>> regards<br>
>> Rick Bakker<br>
>> Hanabi Technology<br>
>><br>
>><br>
>><br>
>> On Fri, Jul 2, 2010 at 12:57 PM, Patil, Priyank<br>
>> <<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a><mailto:<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a>>> wrote:<br>
>> In SWEQADM its 'MARK LINKAGE AS HAVING ERRORS'.<br>
>><br>
>> Thanks<br>
>> PD<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>><br>
>> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>>] On<br>
>> Behalf<br>
>> Of Rick Bakker<br>
>> Sent: Thursday, July 01, 2010 6:07 PM<br>
>><br>
>> To: SAP Workflow Users' Group<br>
>> Subject: Re: Activating workflow without using SWDD tcode<br>
>><br>
>> Depends what the System Default is. What's the setting in SWEQADM?<br>
>> On Thu, Jul 1, 2010 at 8:21 PM, Patil, Priyank<br>
>> <<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a><mailto:<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a>>> wrote:<br>
>><br>
>> Some workflows its 'MARK LINKAGE AS HAVING ERRORS' and for some others<br>
>> its<br>
>> SYSTEM DEFAULTS.I guess this should not be a problem.<br>
>><br>
>><br>
>><br>
>> Thanks<br>
>><br>
>> PD<br>
>><br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>><br>
>> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>>] On<br>
>> Behalf<br>
>> Of Rick Bakker<br>
>> Sent: Thursday, July 01, 2010 5:46 PM<br>
>><br>
>> To: SAP Workflow Users' Group<br>
>> Subject: Re: Activating workflow without using SWDD tcode<br>
>><br>
>> What's the setting in SWEQADM?<br>
>> On Thu, Jul 1, 2010 at 8:08 PM, Patil, Priyank<br>
>> <<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a><mailto:<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a>>> wrote:<br>
>> No, it was set to 'Mark linkage as having errors'.<br>
>><br>
>> Thanks,<br>
>> PD<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>><br>
>> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>>] On<br>
>> Behalf<br>
>> Of Neumann, Marcia<br>
>> Sent: Thursday, July 01, 2010 5:33 PM<br>
>><br>
>> To: SAP Workflow Users' Group<br>
>> Subject: RE: Activating workflow without using SWDD tcode<br>
>><br>
>> We have 'Behavior Upon Error Feedback' set to 'Do not change linkage' in<br>
>> event linkage SWETYPV for all our workflows. Is your set to<br>
>> 'Deactivation<br>
>> on linkage'?<br>
>> [cid:image001.jpg@01CB19E3.9424C760]<br>
>><br>
>><br>
>> Marcia Neumann<br>
>> IT Claims/CSU Development & Support<br>
>> Ext 4461<br>
>><br>
>> Confidentiality notice: The information included in this e-mail,<br>
>> including<br>
>> any attachments, is for the sole use of the intended recipient and may<br>
>> contain information that is confidential and protected. Any unauthorized<br>
>> review, use, disclosure, distribution or similar action is prohibited.<br>
>> If<br>
>> you are not the intended recipient, please contact the sender and delete<br>
>> all copies of the original message immediately.<br>
>><br>
>> ________________________________<br>
>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>><br>
>> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>>] On<br>
>> Behalf<br>
>> Of Patil, Priyank<br>
>> Sent: Thursday, July 01, 2010 7:57 AM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: RE: Activating workflow without using SWDD tcode<br>
>><br>
>> The triggering event attached to WF is getting deactivated all the time.<br>
>> Its creating a huge problem to us. And it's a customized workflow not a<br>
>> standard one.<br>
>><br>
>> Thanks<br>
>> Priyank<br>
>><br>
>> From: <a href="mailto:sap-wug-bounces@MIT.EDU">sap-wug-bounces@MIT.EDU</a><mailto:<a href="mailto:sap-wug-bounces@MIT.EDU">sap-wug-bounces@MIT.EDU</a>><br>
>> [mailto:<a href="mailto:sap-wug-bounces@MIT.EDU">sap-wug-bounces@MIT.EDU</a><mailto:<a href="mailto:sap-wug-bounces@MIT.EDU">sap-wug-bounces@MIT.EDU</a>>] On<br>
>> Behalf<br>
>> Of Bhupinder<br>
>> Sent: Thursday, July 01, 2010 5:18 PM<br>
>> To: SAP Workflow Users' Group<br>
>> Subject: Re: Activating workflow without using SWDD tcode<br>
>><br>
>> Hi Priyank,<br>
>><br>
>> Normally at production system, we are simply activating the triggering<br>
>> event attached to WF which sometimes deactivated.<br>
>><br>
>> Is this the case in your scenario or WF definition itself gets<br>
>> deactivated?<br>
>><br>
>> To activate the event, you can either use OOCU tcode or using PFTC.<br>
>><br>
>> Best Regards,<br>
>> Bhupinder<br>
>> On Thu, Jul 1, 2010 at 5:03 PM, Patil, Priyank<br>
>> <<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a><mailto:<a href="mailto:Priyank.Patil@keane.com">Priyank.Patil@keane.com</a>>> wrote:<br>
>> Wuggers,<br>
>> Can we activate our workflow without going into<br>
>> SWDD.Suppose I have created one workflow for PO<br>
>> approval.Actuallly we don't have access to SWDD tcode<br>
>> in production and often the WF is getting inactive<br>
>> once its activated. Now is there any way to activate<br>
>> workflow using any tcodes or standard program.<br>
>><br>
>> ______________________<br>
>> Thanks and Regards,<br>
>> Priyank Dev Patil<br>
>><br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of<br>
>> the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or subsidiaries.<br>
>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><mailto:<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
>><br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of<br>
>> the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or subsidiaries.<br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of<br>
>> the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or subsidiaries.<br>
>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><mailto:<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
>><br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of<br>
>> the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or subsidiaries.<br>
>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><mailto:<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
>><br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of<br>
>> the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or subsidiaries.<br>
>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><mailto:<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
>><br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of<br>
>> the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or subsidiaries.<br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of<br>
>> the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or subsidiaries.<br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of<br>
>> the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or subsidiaries.<br>
>><br>
>> ______________________________________________________________________<br>
>> Disclaimer: This email message and any attachments are for the sole use<br>
>> of the intended recipient(s) and may contain information that is<br>
>> confidential, legally privileged or otherwise exempt from disclosure<br>
>> under<br>
>> applicable law. If you are not the intended recipient(s) or have<br>
>> received<br>
>> this message in error, you are instructed to immediately notify the<br>
>> sender<br>
>> by return email and required to delete this message from your computer<br>
>> system. This communication does not form any contractual obligation on<br>
>> behalf of the sender, the sender's employer or such employer's parent<br>
>> company, affiliates or<br>
>> subsidiaries._______________________________________________<br>
>> SAP-WUG mailing list<br>
>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>
> ______________________________________________________________________<br>
> Disclaimer: This email message and any attachments are for the sole use<br>
> of the intended recipient(s) and may contain information that is<br>
> confidential, legally privileged or otherwise exempt from disclosure under<br>
> applicable law. If you are not the intended recipient(s) or have received<br>
> this message in error, you are instructed to immediately notify the sender<br>
> by return email and required to delete this message from your computer<br>
> system. This communication does not form any contractual obligation on<br>
> behalf of the sender, the sender's employer or such employer's parent<br>
> company, affiliates or subsidiaries.<br>
><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>
<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
______________________________________________________________________<br>
Disclaimer: This email message and any attachments are for the sole use of the intended recipient(s) and may contain information that is confidential, legally privileged or otherwise exempt from disclosure under applicable law. If you are not the intended recipient(s) or have received this message in error, you are instructed to immediately notify the sender by return email and required to delete this message from your computer system. This communication does not form any contractual obligation on behalf of the sender, the sender's employer or such employer's parent company, affiliates or subsidiaries.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
<br>
End of SAP-WUG Digest, Vol 68, Issue 27<br>
***************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Best Regards<br>Ravi Dixit<br>