<DIV>Hi Klaus,</DIV> <DIV> </DIV> <DIV>Please check the transaction SM58 for batch user WF-BATCH if it is a background task.</DIV> <DIV> </DIV> <DIV>It will show you the relevant message.</DIV> <DIV> </DIV> <DIV>Cheers,</DIV> <DIV>Gaurav<BR><BR><B><I>sap-wug-request@mit.edu</I></B> wrote:</DIV> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">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: Raising a QMSM event with change doc MELDUNG - possible?<BR>(Mic!
hael
Pokraka)<BR>2. RE: Workflow status 'Ready' but does not move on<BR>(Baunach, Natasha R)<BR>3. RE: Workflow status 'Ready' but does not move on<BR>(Klaus-Dieter Spatz)<BR>4. RE: Raising a QMSM event with change doc MELDUNG - possible?<BR>(Kisloff, Philip B)<BR>5. Can't single step through RH_ORG_INFO_AND_TASKS (Rick Sample)<BR>6. RE: Workflow status 'Ready' but does not move on<BR>(Baunach, Natasha R)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Date: Tue, 29 Nov 2005 08:22:37 -0800 (PST)<BR>From: Michael Pokraka <WUG.REPLIES@WORKFLOWCONNECTIONS.COM><BR>To: "SAP Workflow Users' Group" <SAP-WUG@MIT.EDU><BR>Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?<BR>Message-ID: <20051129162237.30961.qmail@web30202.mail.mud.yahoo.com><BR>In-Reply-To: <87548400CF397141B3EA2B66CC2F7B9E124D6706@CORPMAIL1.corp.dayzim.com><BR>Content-Type: text/plain; charset=iso-8859-1<BR>MIME-Version: 1.0<BR>Content-Transfer-Enco!
ding:
8bit<BR>Precedence: list<BR>Reply-To: SAP Workflow Users' Group <SAP-WUG@MIT.EDU><BR>Message: 1<BR><BR>Hi Margaret, <BR>Always happy to help someone who has clearly spent some time and effort to try<BR>and figure it out: <BR><BR>Hit F1 on the fields in SWEC and it gives you template FM's to copy to your own<BR>:-)<BR><BR>I'm not sure how to do multiples of the same events without messing about with<BR>it myself, so I'll stick to raising one event with a multiline container<BR>element of your own type contianing the change(s) - key, old and new. So add a<BR>custom FM to populate container and inside your copy of<BR>SWE_CD_TEMPLATE_CONTAINER_FB_2, you'd do something like: <BR><BR>Data: l_cdpos like cdpos,<BR>l_changes type zQmsmParnrChgs " Your custom struct<BR>t_changes type standard table of zQmsmParnrChgs.<BR><BR>* Add all changes to table<BR>loop at changedocument_position into l_cdpos<BR>where tabname = 'QMSM'<BR>and fname = 'PARNR'.<BR>...assign l_cdpos-key/old/new to
l_changes-parnr/old/new<BR>...and append to t_changes<BR>endloop.<BR><BR>if sy-subrc = 0.<BR>* Add table to event container<BR>call method event_container->set<BR>exporting<BR>name = 'ChangeList' " Your event parameter name<BR>value = t_changes.<BR>endif.<BR><BR>Should work... unchecked, untested, standard disclaimers apply. <BR>Cheers<BR>Mike<BR><BR><BR><BR>--- "Hilsbos, Margaret A" <MARGARET.HILSBOS@DAYZIM.COM>wrote:<BR><BR>> Mike,<BR>> <BR>> Thanks...I'll give this a try.<BR>> <BR>> I'm pretty weak at ABAP so if there is an example of what this might look<BR>> like... :-) <BR>> (You could save me some time; I'll struggle through it though if need be)<BR>> <BR>> It seems like the best approach if I can't fill the event container using the<BR>> program-raised event as Anna suggested.<BR>> <BR>> Margaret<BR>> <BR>> -----Original Message-----<BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]On Behalf<BR>> O!
f Michael
Pokraka<BR>> Sent: Monday, November 28, 2005 5:09 PM<BR>> To: SAP Workflow Users' Group<BR>> Subject: Re: Raising a QMSM event with change doc MELDUNG - possible?<BR>> <BR>> <BR>> Hi Margaret, <BR>> OK you laid down the challenge, so here goes: <BR>> <BR>> You're mostly on the right track, but keep the event at the same level as<BR>> your<BR>> change doc, i.e. stick to the notification. Create an event<BR>> ZRESPONSIBLEPERSONCHANGED with event parameter(s). <BR>> <BR>> In SWEC, specify your event using a FM - the changedocs are provided as<BR>> parameters for your entertainment. <BR>> The other FM in there is one for populating the event container, which is<BR>> where<BR>> you can put the Task number and old/new values.<BR>> <BR>> A design choice that depends on your intended usage is whether to have<BR>> multiple<BR>> events with one per task, or one event with all changed tasks as a multiline<BR>> parame!
ter.
<BR>> <BR>> Cheers<BR>> Mike<BR>> <BR>> --- "Hilsbos, Margaret A" <MARGARET.HILSBOS@DAYZIM.COM>wrote:<BR>> <BR>> > Hello WUGers,<BR>> > <BR>> > I have a perplexing little problem that I'm betting someone here knows just<BR>> > the answer to.<BR>> > <BR>> > I want to trigger a WF based on a change in the field QMSM-PARNR, which<BR>> means<BR>> > a change to the "person responsible" for a task on a service notification<BR>> (or<BR>> > q-note, etc). But the only change document I found is MELDUNG, which is<BR>> based<BR>> > on the key for the notification, not the task. Since there can be many<BR>> tasks<BR>> > on a notification, it is possible that more than one task will have this<BR>> > field changed in a single transaction. We need to trigger a workflow for<BR>> each<BR>> > task that is changed, or at least loop through a set of work items for each<BR>> > task tha!
t was
changed. We also need to be able to identify the old and new<BR>> > values in QMSM-PARNR.<BR>> > <BR>> > QMSM-PARNR old and new values are written to CDPOS but I am unclear how to<BR>> > handle the event trigger. SWEC wants an object like BUS2080 and CDHDR only<BR>> > has the notification number as the key. I was wondering if I could use a<BR>> > function module in SWED to translate the object key, using CDPOS -TABKEY <BR>> to<BR>> > get the key for QMSM....but I'm guessing I can't trigger separate events<BR>> for<BR>> > each TABKEY value on a single change document.<BR>> > <BR>> > Alternatively I think I could trigger the event based on BUS2080 and loop<BR>> > through values in the workflow, using a multiline container element...but<BR>> in<BR>> > that case do the old and new values alternate in the container element? It<BR>> > seems like it will be a pain to sort them out to the task nu!
mbers in
the<BR>> > loop. <BR>> > <BR>> > If I sound lost then I probably am... anyone want to help me out of the<BR>> > wilderness? Can you give me a suggestion as to the best way to handle this<BR>> > situation? <BR>> > <BR>> > Thanks!<BR>> > <BR>> > Margaret Hilsbos<BR>> > Day & Zimmermann<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>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<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>Date: Tue,!
29 Nov
2005 08:23:31 -0800<BR>From: "Baunach, Natasha R" <NATASHA.R.BAUNACH@INTEL.COM><BR>To: "SAP Workflow Users' Group" <SAP-WUG@MIT.EDU><BR>Subject: RE: Workflow status 'Ready' but does not move on<BR>Message-ID: <31F5998A44B92447BD334F8FBBA0B01F0AABF0BF@orsmsx401.amr.corp.intel.com><BR>Content-Type: text/plain;<BR>charset="us-ascii"<BR>MIME-Version: 1.0<BR>Content-Transfer-Encoding: 8bit<BR>Precedence: list<BR>Reply-To: SAP Workflow Users' Group <SAP-WUG@MIT.EDU><BR>Message: 2<BR><BR>Klaus,<BR><BR>If it is a dialog step, did you remember to set it as General task or<BR>assign specific agents as allowed agents for the task?<BR><BR>Natasha<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Klaus-Dieter Spatz<BR>Sent: Tuesday, November 29, 2005 8:13 AM<BR>To: 'SAP Workflow Users' Group'<BR>Subject: Workflow status 'Ready' but does not move on<BR><BR>Hi All,<BR><BR>I do have a workflow method, which sits in the!
log with
the status<BR>'Ready'<BR>but does not move on to the next step. <BR><BR>Please see the attachment, perhaps someone has seen this before. <BR><BR>Thanks Klaus<BR><BR>------------------------------<BR><BR>Date: Tue, 29 Nov 2005 08:34:11 -0800<BR>From: "Klaus-Dieter Spatz" <KLAUS@KDSSC.COM><BR>To: "'SAP Workflow Users' Group'" <SAP-WUG@MIT.EDU><BR>Subject: RE: Workflow status 'Ready' but does not move on<BR>Message-ID: <016c01c5f502$bb3a7f80$283d1eac@DELLKDSSC><BR>In-Reply-To: <31F5998A44B92447BD334F8FBBA0B01F0AABF0BF@orsmsx401.amr.corp.intel.com><BR>Content-Type: text/plain;<BR>charset="us-ascii"<BR>MIME-Version: 1.0<BR>Content-Transfer-Encoding: 7bit<BR>Precedence: list<BR>Reply-To: SAP Workflow Users' Group <SAP-WUG@MIT.EDU><BR>Message: 3<BR><BR>Natasha,<BR><BR>It is not a dialog step. It is supposed to process an update and just go to<BR>the next step. <BR><BR>Klaus<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.e!
du] On
Behalf Of<BR>Baunach, Natasha R<BR>Sent: Tuesday, November 29, 2005 8:24 AM<BR>To: SAP Workflow Users' Group<BR>Subject: RE: Workflow status 'Ready' but does not move on<BR><BR>Klaus,<BR><BR>If it is a dialog step, did you remember to set it as General task or<BR>assign specific agents as allowed agents for the task?<BR><BR>Natasha<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Klaus-Dieter Spatz<BR>Sent: Tuesday, November 29, 2005 8:13 AM<BR>To: 'SAP Workflow Users' Group'<BR>Subject: Workflow status 'Ready' but does not move on<BR><BR>Hi All,<BR><BR>I do have a workflow method, which sits in the log with the status<BR>'Ready'<BR>but does not move on to the next step. <BR><BR>Please see the attachment, perhaps someone has seen this before. <BR><BR>Thanks Klaus<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>Date: Tue, 29 Nov 2005 16:41:45 -0000<BR>From: "Kisloff, Philip B" <PHILIP.KISLOFF@ASTRAZENECA.COM><BR>To: "'SAP Workflow Users' Group'" <SAP-WUG@MIT.EDU><BR>Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?<BR>Message-ID: <77B8D39FB855D511B6FE0002A55C0CE6051412FD@ukcfphmsx01.ukcf.astrazeneca.net><BR>Content-Type: text/plain;<BR>charset="iso-8859-1"<BR>MIME-Version: 1.0<BR>Precedence: list<BR>Reply-To: SAP Workflow Users' Group <SAP-WUG@MIT.EDU><BR>Message: 4<BR><BR>Hi Margaret,<BR><BR>Sorry, IHPA does record the partners for the task level. That was the point.<BR>I don't see a need to create any additional events or ABAP code, but perhaps<BR>I don't understand.<BR><BR>Regards<BR><BR>Phil<BR><BR><BR>OBJECTCLAS MELDUNG <BR>OBJECTID 000600003730 <BR>CHANGENR 718676 <BR>TABNAME QMSM <BR>TABKEY 2000006000037300001 <BR>FNAME PA!
RNR
<BR>CHNGIND U <BR><BR>TEXT CASE 1 <BR>UNIT OLD <BR>UNIT NEW <BR>CUKY OLD <BR>CUKY NEW <BR>VALUE NEW 50001984 <BR>VALUE OLD 50001988 <BR><BR>-----Original Message-----<BR>From: Hilsbos, Margaret A [mailto:Margaret.Hilsbos@dayzim.com]<BR>Sent: 29 November 2005 15:22<BR>To: SAP Workflow Users' Group<BR>Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?<BR><BR><BR>Phil,<BR><BR>Thanks for your suggestion. However I've found that the change doc only<BR>records QMSM-PARNR when I change the responsible on the task. I believe IHPA<BR>only records the partners for the notification header level.<BR><BR>I was able to set the restriction in SWEC on QMSM-PARNR and raised my custom<BR>event ZBUS2080.responsibleIsChanged2.<BR><BR>The issue at this point is handling the old and new PARNR values and<BR>handling multiple changes per transaction. Mike P made a suggestion about<BR>that, which I'll try as soon as I figure out how to code
it.<BR><BR>Thanks,<BR><BR>Margaret<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]On Behalf<BR>Of Kisloff, Philip B<BR>Sent: Tuesday, November 29, 2005 8:27 AM<BR>To: 'SAP Workflow Users' Group'<BR>Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?<BR><BR><BR>Hi Margaret,<BR><BR>I have only raised a responsible is changed with Meldung for notifications,<BR>and you are right, there is a problem with setting an event with QMSM in<BR>SWEC(warning W8-706).<BR><BR>But this is not really a problem, because I still use MELDUNG and business<BR>object BUS7051, as the changes to "partners" such as responsible person are<BR>recorded in table IHPA, and it is IHPA-PARNR that you can set a field<BR>restriction to in SWEC, not QMSM-PARNR. If you then go to the condition<BR>editor you will then see IHPA_PARNR_OLD <> IHPA_PARNR_NEW. These IHPA<BR>restrictions work for both notifications and tasks. <BR><BR>After cha!
nging the
task processor, I'm currently looking at an event log<BR>entry with QMSM as the object type, but SWEC only has MELDUNG and BUS7051. I<BR>imagine should also work for BUS2080.<BR><BR>Let me how you get on,<BR><BR>Best regards<BR><BR>Phil<BR><BR><BR><BR>-----Original Message-----<BR>From: Hill, Anna [mailto:anna.hill@sap.com]<BR>Sent: 29 November 2005 10:22<BR>To: SAP Workflow Users' Group<BR>Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?<BR><BR><BR>Margaret - I managed to check; the event is definitely raised as<BR>standard on the system I'm currently on so it should also be for you.<BR><BR>Good luck!<BR>Cheers<BR>Anna<BR>SAP UK<BR><BR>-----Original Message-----<BR>From: Hill, Anna <BR>Sent: Tuesday, November 29, 2005 10:16 AM<BR>To: 'SAP Workflow Users' Group'<BR>Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?<BR>Hi Margaret<BR><BR>There is actually an event on the QMSM business object called<BR>responsibleIsChanged so I expect t!
here must
be a way of raising this, if<BR>it's not raised automatically by the application. I know that the<BR>equivalent on BUS2080 is raised automatically but I can't test it for<BR>QMSM as the system I'm on doesn't have th option available to enter<BR>responsible users at task level. <BR><BR>Try switching on the event trace (SWELS) for your user ID and change the<BR>responsible field on a task to see if the event is raised as a first<BR>option, if you haven't already done this. If this doesn't work then let<BR>me know and we can have a re-think.<BR><BR>Cheers<BR>Anna<BR>SAP UK <BR><BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Dart, Jocelyn<BR>Sent: Tuesday, November 29, 2005 12:12 AM<BR>To: SAP Workflow Users' Group<BR>Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?<BR><BR>Have you checked out the option of using status management to notify the<BR>workflow that person responsible has been !
changed?
You would probably<BR>need a user-defined status but both notifications and tasks are<BR>transactions not master data and do a lot with status management so you<BR>may have more luck there. <BR><BR><BR>Regards,<BR>Jocelyn Dart<BR>Senior Consultant<BR>SAP Australia Pty Ltd.<BR>Level 1/168 Walker St.<BR>North Sydney <BR>NSW, 2060<BR>Australia<BR>T +61 412 390 267<BR>M + 61 412 390 267<BR>E jocelyn.dart@sap.com<BR>http://www.sap.com<BR><BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Hilsbos, Margaret A<BR>Sent: Tuesday, 29 November 2005 7:20 AM<BR>To: SAP-WUG (E-mail)<BR>Subject: Raising a QMSM event with change doc MELDUNG - possible?<BR><BR>Hello WUGers,<BR><BR>I have a perplexing little problem that I'm betting someone here knows<BR>just the answer to.<BR><BR>I want to trigger a WF based on a change in the field QMSM-PARNR, which<BR>means a change to the "person responsible" for a task on a service<BR>noti!
fication
(or q-note, etc). But the only change document I found is<BR>MELDUNG, which is based on the key for the notification, not the task.<BR>Since there can be many tasks on a notification, it is possible that<BR>more than one task will have this field changed in a single transaction.<BR>We need to trigger a workflow for each task that is changed, or at least<BR>loop through a set of work items for each task that was changed. We also<BR>need to be able to identify the old and new values in QMSM-PARNR.<BR><BR>QMSM-PARNR old and new values are written to CDPOS but I am unclear how<BR>to handle the event trigger. SWEC wants an object like BUS2080 and<BR>CDHDR only has the notification number as the key. I was wondering if I<BR>could use a function module in SWED to translate the object key, using<BR>CDPOS -TABKEY to get the key for QMSM....but I'm guessing I can't<BR>trigger separate events for each TABKEY value on a single change<BR>document.<BR><BR>Alternatively I think I could tr!
igger the
event based on BUS2080 and<BR>loop through values in the workflow, using a multiline container<BR>element...but in that case do the old and new values alternate in the<BR>container element? It seems like it will be a pain to sort them out to<BR>the task numbers in the loop. <BR><BR>If I sound lost then I probably am... anyone want to help me out of the<BR>wilderness? Can you give me a suggestion as to the best way to handle<BR>this situation? <BR><BR>Thanks!<BR><BR>Margaret Hilsbos<BR>Day & Zimmermann<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>Date: Tue, 29 Nov 2005 10:50:04 -0600<BR>From: "Rick Sample" <RICK.SAMPLE@GBE.COM><BR>To: sap-wug@mit.edu<BR>Subject: Can't single step through RH_ORG_INFO_AND_TASKS<BR>Message-ID: <200511291650.jATGo78j004160@ns3.graybar.com><BR>Content-Type:
text/plain;<BR>charset=us-ascii<BR>MIME-Version: 1.0<BR>Content-Transfer-Encoding: 7bit<BR>Precedence: list<BR>Reply-To: SAP Workflow Users' Group <SAP-WUG@MIT.EDU><BR>Message: 5<BR><BR>I set my break points at the first executable statement in this FM. <BR>It never steps inside this FM. Never had this issue before. <BR>Anyone have a clues why?<BR><BR>In 4.6c srv pack 50<BR><BR>Thanks<BR>Rick<BR><BR>------------------------------<BR><BR>Date: Tue, 29 Nov 2005 08:52:42 -0800<BR>From: "Baunach, Natasha R" <NATASHA.R.BAUNACH@INTEL.COM><BR>To: "SAP Workflow Users' Group" <SAP-WUG@MIT.EDU><BR>Subject: RE: Workflow status 'Ready' but does not move on<BR>Message-ID: <31F5998A44B92447BD334F8FBBA0B01F0AABF152@orsmsx401.amr.corp.intel.com><BR>Content-Type: text/plain;<BR>charset="us-ascii"<BR>MIME-Version: 1.0<BR>Content-Transfer-Encoding: 8bit<BR>Precedence: list<BR>Reply-To: SAP Workflow Users' Group <SAP-WUG@MIT.EDU><BR>Message: 6<BR><BR>In your attachment, the step that is !
stuck in
status Ready has icon for<BR>agents. Background steps don't have that icon. Check on your task<BR>definition to make sure that background checkbox is checked in the lower<BR>left corner.<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Klaus-Dieter Spatz<BR>Sent: Tuesday, November 29, 2005 8:34 AM<BR>To: 'SAP Workflow Users' Group'<BR>Subject: RE: Workflow status 'Ready' but does not move on<BR><BR>Natasha,<BR><BR>It is not a dialog step. It is supposed to process an update and just go<BR>to<BR>the next step. <BR><BR>Klaus<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of<BR>Baunach, Natasha R<BR>Sent: Tuesday, November 29, 2005 8:24 AM<BR>To: SAP Workflow Users' Group<BR>Subject: RE: Workflow status 'Ready' but does not move on<BR><BR>Klaus,<BR><BR>If it is a dialog step, did you remember to set it as General task or<BR>assign specific agents!
as
allowed agents for the task?<BR><BR>Natasha<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Klaus-Dieter Spatz<BR>Sent: Tuesday, November 29, 2005 8:13 AM<BR>To: 'SAP Workflow Users' Group'<BR>Subject: Workflow status 'Ready' but does not move on<BR><BR>Hi All,<BR><BR>I do have a workflow method, which sits in the log with the status<BR>'Ready'<BR>but does not move on to the next step. <BR><BR>Please see the attachment, perhaps someone has seen this before. <BR><BR>Thanks Klaus<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>_______________________________________________<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 12, Issue 143<BR>****************************************<BR></BLOCKQUOTE> <DIV><BR></DIV><p>
<hr size=1> <a href="http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=36035/*http://music.yahoo.com/unlimited/">Yahoo! Music Unlimited - Access over 1 million songs. Try it free.</a>