<div>Thank you Rick,</div>
<div>We do not have that specific user exit available but it send me in the right direction... .</div>
<div>We have a user exit CBIH_LB14_IAL_UPD_CRE_CHECK that I think I will be able to use.</div>
<div>Regards</div>
<div>Gerda<br><br></div>
<div class="gmail_quote">On Tue, May 4, 2010 at 3:00 PM, <span dir="ltr"><<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">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: Triggering EHS Workflow for Incident/Accident log.<br> (Rick Bakker)<br> 2. Benefit Enrollment Workflow (Nash John)<br>
3. Re: Benefit Enrollment Workflow (Rick Bakker)<br> 4. RE: workflow maintenance and enhancements (Dart, Jocelyn)<br> 5. RE: workflow maintenance and enhancements (Nat 4 Govender)<br><br><br>----------------------------------------------------------------------<br>
<br>Message: 1<br>Date: Mon, 3 May 2010 11:16:03 -0600<br>From: Rick Bakker <<a href="mailto:rbakker@gmail.com">rbakker@gmail.com</a>><br>Subject: Re: Triggering EHS Workflow for Incident/Accident log.<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:k2r7a3a922f1005031016rd27030fcw3aab21369511c834@mail.gmail.com">k2r7a3a922f1005031016rd27030fcw3aab21369511c834@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br>
<br>Hello,<br><br>You could try the user exit in fm CBIH_IA30_IAL_UPDATE (default<br>CBIH_IA30_UE_IAL_MAIN_CHECK)<br>so that it creates an event when the status changes to In Process.<br><br>regards<br>Rick Bakker<br>Hanabi Technology<br>
<br>On Mon, May 3, 2010 at 8:03 AM, Gerda Wright <<a href="mailto:gerdawright@gmail.com">gerdawright@gmail.com</a>> wrote:<br>> Good day everyone,<br>><br>> I have a problem triggering a workflow on the change of the status of the<br>
> incident/accident- transaction CBIH82.<br>> I have created a custom object to use in the workflow but see that status is<br>> not part of the change document and I need to trigger a workflow when the<br>> status change to "in Process".<br>
> Do you know how I can achieve this.<br>> Regards<br>> Gerda<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>------------------------------<br><br>Message: 2<br>Date: Mon, 3 May 2010 16:41:11 -0400<br>From: Nash John <<a href="mailto:emailtonash@gmail.com">emailtonash@gmail.com</a>><br>Subject: Benefit Enrollment Workflow<br>
To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>,<br> <a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>Message-ID:<br> <<a href="mailto:q2r7169de101005031341g4f8c0c99p4033fc09e1642ba0@mail.gmail.com">q2r7169de101005031341g4f8c0c99p4033fc09e1642ba0@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="windows-1252"<br><br>Hi Friends,<br><br><br>I am working on open enrollment benefits workflow scenario. Basically when<br>even a health plan is enter through ESS for an employee, I have to send an<br>
email to set of people. I have done following workflow steps but getting an<br>error : RFC_ERROR_SYSTEM_FAILURE , GETWA_NOT_ASSIGNED<br><br> Step 1: BUS302901 extended to ZBUS302901 to include Custom event CREATED.<br>Delegated.<br>
<br> Step 2 : SWEHR1. ? Made following entry in.<br><br> type : P , Info type : 0167 , Object Type : BUS302901<br><br> Step 3: SWEHR3<br><br> Object type : P , Infotype : 0167 , Update op : INS , Event<br>
object type : BUS302901 and event : CREATED.<br><br> Step 4: Create a custom workflow and Liked event CREATED to it.<br><br>It would really appreciate if you could help me out<br><br><br><br>Thanks<br><br><br><br>Nash<br>
-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20100503/6e390e22/attachment-0001.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20100503/6e390e22/attachment-0001.htm</a><br>
<br>------------------------------<br><br>Message: 3<br>Date: Mon, 3 May 2010 14:50:18 -0600<br>From: Rick Bakker <<a href="mailto:rbakker@gmail.com">rbakker@gmail.com</a>><br>Subject: Re: Benefit Enrollment Workflow<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:y2w7a3a922f1005031350pb98a78d2z5e7eb3642db8b384@mail.gmail.com">y2w7a3a922f1005031350pb98a78d2z5e7eb3642db8b384@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=windows-1252<br><br>Hello,<br><br>Have you checked OSS? I seem to remember there being a number of notes<br>about that (GETWA_NOT_ASSIGNED).<br><br>regards<br>Rick Bakker<br>Hanabi Technology<br>
<br><br>On Mon, May 3, 2010 at 2:41 PM, Nash John <<a href="mailto:emailtonash@gmail.com">emailtonash@gmail.com</a>> wrote:<br>> Hi Friends,<br>><br>><br>><br>> I am working on open enrollment benefits workflow scenario. Basically when<br>
> even a health plan is enter through ESS for an employee, I have to send an<br>> email to set of people. I have done following workflow steps but getting an<br>> error : RFC_ERROR_SYSTEM_FAILURE , ?GETWA_NOT_ASSIGNED<br>
><br>> ?Step 1: BUS302901 extended to ZBUS302901 to include Custom event CREATED.<br>> Delegated.<br>><br>> ?Step 2 : ?SWEHR1. ? Made following entry in.<br>><br>> ?????????? type : P , ?Info type : 0167 , ?Object Type : BUS302901<br>
><br>> ?Step 3:? SWEHR3<br>><br>> ?????????? Object type : P , Infotype : 0167 , ?Update op : INS , ?Event<br>> object type : BUS302901 and event : CREATED.<br>><br>> ?Step 4:? Create a custom workflow and Liked event CREATED to it.<br>
><br>> It would really appreciate if you could help me out<br>><br>><br>><br>> Thanks<br>><br>><br>><br>> Nash<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><br><br><br>------------------------------<br><br>Message: 4<br>Date: Tue, 4 May 2010 01:30:46 +0200<br>From: "Dart, Jocelyn" <<a href="mailto:jocelyn.dart@sap.com">jocelyn.dart@sap.com</a>><br>
Subject: RE: workflow maintenance and enhancements<br>To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID:<br> <8C507B5E0BA5114E933C3C6E2E9729E0065E2B5A10@DEWDFECCR01.wdf.sap.corp><br>
Content-Type: text/plain; charset="Windows-1252"<br><br>Hi Sue,<br>For something like this we would usually use parallel environments and use the CHARM transport process to sort it out.<br>Essentially to control/automate the synchronization process as much as possible.<br>
This is one of those... "go talk to the basis guys" answers - sorry.<br>Regards,<br>Jocelyn<br><br>________________________________<br>From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf Of Keohan, Susan - 1140 - MITLL [<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a>]<br>
Sent: Saturday, 1 May 2010 12:56 AM<br>To: SAP Workflow Users' Group<br>Subject: RE: workflow maintenance and enhancements<br><br>Hi Sue, Gayathri,<br><br>I do understand this dilemma ? we go thru it every time we upgrade or apply major support packs. We get a ?prime? Dev environment in which we do production support, and then we get the upgrade environment in which we do enhancements. It?s a beast.<br>
<br>I was not taking that ? the ?upgrade factor? ? into consideration. Call it selective amnesia.<br><br>As far as I know copying the WFs and trying to keep both versions in sync is the only way to do this. Of course, in my own perfect little world (imaginary) we would not have to do this kind of thing :)<br>
<br>Thanks for bringing me back to reality on a Friday,<br>Sue<br><br>----<br>Susan R. Keohan<br>SAP Workflow Specialist<br>Enterprise Applications<br>Information Services Department<br>MIT Lincoln Laboratory<br>244 Wood Street, LI-200<br>
Lexington, MA. 02420<br>781-981-3561<br><a href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a><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 Of Sue Doughty<br>
Sent: Friday, April 30, 2010 10:47 AM<br>To: 'SAP Workflow Users' Group'<br>Subject: RE: workflow maintenance and enhancements<br><br>Hi Sue,<br><br>I can understand Gayathri?s issue.<br><br>I?m currently working on a six month project that involves changes to the system done by another group, plus workflow changes to an existing workflow. While this six month project is going on we need to have a path to production to be able to send fixes (if they occur) for the existing workflow while we are in development on the project.<br>
<br>The only way I knew to do that was to make a copy of the existing workflow in which I am making the project changes. If any fixes need to be done before the project goes to PRD, I?ll have to make changes in both workflows to keep everything in sync. It is challenging.<br>
<br>There is no other way to do that, is there?<br><br>Regards,<br>Sue<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>] On Behalf Of Keohan, Susan - 1140 - MITLL<br>
Sent: Friday, April 30, 2010 10:18 AM<br>To: SAP Workflow Users' Group<br>Subject: RE: workflow maintenance and enhancements<br><br>Hi Gayathri,<br>I would not try to simultaneously fix productive workflows and also do enhancements ? unless you are planning on all of these corrections/enhancements going to the same place at the same time. Personally, I would fix the issue with production, transport up, and then generate a new version of the workflow in your Dev environment and begin the enhancements.<br>
<br>Having said that, you could, of course, copy the productive workflow to another workflow template, allowing you to do the fixes in the original template, and the enhancements in the copied template. I would hate to have to coordinate that development effort though.<br>
<br>Just my 2p,<br>Sue<br><br>----<br>Susan R. Keohan<br>SAP Workflow Specialist<br>Enterprise Applications<br>Information Services Department<br>MIT Lincoln Laboratory<br>244 Wood Street, LI-200<br>Lexington, MA. 02420<br>
781-981-3561<br><a href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a><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 Of Gayathri Shivakumar<br>
Sent: Friday, April 30, 2010 8:25 AM<br>To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>Subject: workflow maintenance and enhancements<br><br>HI experts,<br><br>What is the best way to handle simultaneously fixes to a production workflow and also work on enhancements to the same workflow ?<br>
<br>Regards,<br>Gayathri<br><br>Yazaki North America, Inc. - Confidentiality & Security Notice<br><br>________________________________<br>This email is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, distribution, reliance on, or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this message in error, please immediately notify the sender and delete it and all copies of it from your system.<br>
<br>Visitors are prohibited from taking pictures or video at anytime in YNA or its affiliated company facilities unless prior authorization is obtained from facilities management.<br><br>Thank you.<br><br><br><br>------------------------------<br>
<br>Message: 5<br>Date: Tue, 4 May 2010 15:00:30 +0200<br>From: Nat 4 Govender <<a href="mailto:ngovender4@toyota.co.za">ngovender4@toyota.co.za</a>><br>Subject: RE: workflow maintenance and enhancements<br>To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
Cc: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>,<br> <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><br>Message-ID:<br> <<a href="mailto:OFD3B4E5A4.ECFAE0DC-ON42257719.00476525-42257719.00477DE9@toyota.co.za">OFD3B4E5A4.ECFAE0DC-ON42257719.00476525-42257719.00477DE9@toyota.co.za</a>><br>
<br>Content-Type: text/plain; charset="utf-8"<br><br>Hi Jocelyn,<br><br>Sorry to ask a silly question but what is the "CHARM transport process" ?<br><br>Regards<br>Nat Govender<br>Toyota South Africa<br>
IT - SAP Workflow Specialist<br>Internal Ext. : 32645<br>Direct Line : +27 031 910 2645<br>Fax : 086 607 0414<br>E-mail : <a href="mailto:ngovender4@toyota.co.za">ngovender4@toyota.co.za</a><br>
<br>If you tell the truth, you don't have to remember anything.<br><br><br><br> "Dart, Jocelyn"<br> <jocelyn.dart@sap<br> .com> To<br>
Sent by: "SAP Workflow Users' Group"<br> sap-wug-bounces@m <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br> <a href="http://it.edu/" target="_blank">it.edu</a> cc<br>
<br> Subject<br> 2010/05/04 01:38 RE: workflow maintenance and<br> AM enhancements<br><br><br> Please respond to<br>
"SAP Workflow<br> Users' Group"<br> <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br><br><br><br><br><br><br>Hi Sue,<br>For something like this we would usually use parallel environments and use<br>
the CHARM transport process to sort it out.<br>Essentially to control/automate the synchronization process as much as<br>possible.<br>This is one of those... "go talk to the basis guys" answers - sorry.<br>Regards,<br>
Jocelyn<br><br>________________________________<br>From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf Of<br>Keohan, Susan - 1140 - MITLL [<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a>]<br>
Sent: Saturday, 1 May 2010 12:56 AM<br>To: SAP Workflow Users' Group<br>Subject: RE: workflow maintenance and enhancements<br><br>Hi Sue, Gayathri,<br><br>I do understand this dilemma ? we go thru it every time we upgrade or apply<br>
major support packs. We get a ?prime? Dev environment in which we do<br>production support, and then we get the upgrade environment in which we do<br>enhancements. It?s a beast.<br><br>I was not taking that ? the ?upgrade factor? ? into consideration. Call it<br>
selective amnesia.<br><br>As far as I know copying the WFs and trying to keep both versions in sync<br>is the only way to do this. Of course, in my own perfect little world<br>(imaginary) we would not have to do this kind of thing :)<br>
<br>Thanks for bringing me back to reality on a Friday,<br>Sue<br><br>----<br>Susan R. Keohan<br>SAP Workflow Specialist<br>Enterprise Applications<br>Information Services Department<br>MIT Lincoln Laboratory<br>244 Wood Street, LI-200<br>
Lexington, MA. 02420<br>781-981-3561<br><a href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a><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 Of<br>
Sue Doughty<br>Sent: Friday, April 30, 2010 10:47 AM<br>To: 'SAP Workflow Users' Group'<br>Subject: RE: workflow maintenance and enhancements<br><br>Hi Sue,<br><br>I can understand Gayathri?s issue.<br><br>I?m currently working on a six month project that involves changes to the<br>
system done by another group, plus workflow changes to an existing<br>workflow. While this six month project is going on we need to have a path<br>to production to be able to send fixes (if they occur) for the existing<br>
workflow while we are in development on the project.<br><br>The only way I knew to do that was to make a copy of the existing workflow<br>in which I am making the project changes. If any fixes need to be done<br>before the project goes to PRD, I?ll have to make changes in both workflows<br>
to keep everything in sync. It is challenging.<br><br>There is no other way to do that, is there?<br><br>Regards,<br>Sue<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>] On Behalf Of<br>
Keohan, Susan - 1140 - MITLL<br>Sent: Friday, April 30, 2010 10:18 AM<br>To: SAP Workflow Users' Group<br>Subject: RE: workflow maintenance and enhancements<br><br>Hi Gayathri,<br>I would not try to simultaneously fix productive workflows and also do<br>
enhancements ? unless you are planning on all of these<br>corrections/enhancements going to the same place at the same time.<br>Personally, I would fix the issue with production, transport up, and then<br>generate a new version of the workflow in your Dev environment and begin<br>
the enhancements.<br><br>Having said that, you could, of course, copy the productive workflow to<br>another workflow template, allowing you to do the fixes in the original<br>template, and the enhancements in the copied template. I would hate to<br>
have to coordinate that development effort though.<br><br>Just my 2p,<br>Sue<br><br>----<br>Susan R. Keohan<br>SAP Workflow Specialist<br>Enterprise Applications<br>Information Services Department<br>MIT Lincoln Laboratory<br>
244 Wood Street, LI-200<br>Lexington, MA. 02420<br>781-981-3561<br><a href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a><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 Of<br>
Gayathri Shivakumar<br>Sent: Friday, April 30, 2010 8:25 AM<br>To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>Subject: workflow maintenance and enhancements<br><br>HI experts,<br><br>What is the best way to handle simultaneously fixes to a production<br>
workflow and also work on enhancements to the same workflow ?<br><br>Regards,<br>Gayathri<br><br>Yazaki North America, Inc. - Confidentiality & Security Notice<br><br>________________________________<br>This email is intended only for the person or entity to which it is<br>
addressed and may contain confidential, proprietary and/or privileged<br>material. Any review, distribution, reliance on, or other use of this<br>information by persons or entities other than the intended recipient is<br>
prohibited. If you receive this message in error, please immediately notify<br>the sender and delete it and all copies of it from your system.<br><br>Visitors are prohibited from taking pictures or video at anytime in YNA or<br>
its affiliated company facilities unless prior authorization is obtained<br>from facilities management.<br><br>Thank you.<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>This e-mail is a privileged and private communication and may be<br>
read, copied and used only by the intended recipient(s). If you are<br>not an intended recipient, please inform the sender by return<br>e-mail with the subject heading "Received in error". Please then<br>delete the e-mail; destroy any copies of it and do not disclose its<br>
contents to any person or entity. If you are not the intended<br>recipient, note that any disclosure, copying, distribution or any<br>action taken or omitted to be taken in reliance on it, is strictly<br>prohibited and may be unlawful. Neither the sender nor Toyota South<br>
Africa Motors (Pty) Ltd accepts any liability whatsoever as a<br>result of the further dissemination of this e-mail.<br><br>Toyota South Africa Motors (Pty) Ltd does not guarantee that e-mail<br>communications are secure or error-free, as information could be<br>
intercepted, corrupted, amended, lost, destroyed, arrive late or<br>incomplete, or contain viruses.<br><br>******************************************************************<br>-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/attachment.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/attachment.htm</a><br>-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>Name: graycol.gif<br>Type: image/gif<br>Size: 105 bytes<br>Desc: not available<br>Url : <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/graycol.gif" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/graycol.gif</a><br>
-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: pic09758.gif<br>Type: image/gif<br>Size: 1255 bytes<br>Desc: not available<br>Url : <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/pic09758.gif" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/pic09758.gif</a><br>
-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: ecblank.gif<br>Type: image/gif<br>Size: 45 bytes<br>Desc: not available<br>Url : <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/ecblank.gif" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/ecblank.gif</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>End of SAP-WUG Digest, Vol 66, Issue 2<br>**************************************<br></blockquote></div><br>