<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Tahoma;
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;color:blue'>Stephane,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;color:blue'>I believe think link displays default
method of the business object. In previous releases, you could have a business
object without default method. Here, I was unable to get rid of it. I think
method Display is default method for BUS2121. What you can do, is create a
subtype, use delegation and redefine Display method to actually show something.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;color:blue'>Natasha<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;color:blue'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Stéphane Bailleul<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, June 15, 2006 1:27
AM<br>
<b><span style='font-weight:bold'>To:</span></b> sap-wug@mit.edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> UWL and SRM workflow</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>Hi All, <br>
<br>
I hope you are fine</span></font><font face=Arial><span style='font-family:
Arial'><br>
We are using the SRM 5.0 extended scenario with badi workflow, the task shown
in the UWL are displaying a link that is <br>
the business object therefore if we click on the attachment there is nothing
shown and the screen displays a blank screen <br>
This is causing confusion with our users.<br>
The task we are using in the back end are standard from standard workflow<br>
TS10008126 for shopping Cart workflow from WS14000134<br>
TS14007970 for Local Purchase order workflow from WS14000146<br>
<br>
Of course we can still process the tasks by clicking directly on the title of
the mail or on the Launch SAP task button<br>
But apparently the users are really confused ...<br>
<br>
Does anybody have a solution for this ?<br>
<br>
Cheers<br>
Stephane<br>
</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'><br>
<br>
<br>
<br>
<br>
<o:p></o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
<hr size=2 width="100%" align=center id=stopSpelling>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'><br>
> From: <st1:PersonName w:st="on">sap-wug-request@mit.edu</st1:PersonName><br>
> Subject: SAP-WUG Digest, Vol 19, Issue 37<br>
> To: sap-wug@mit.edu<br>
> Date: Thu, 15 Jun 2006 04:10:42 -0400<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>
> <st1:PersonName w:st="on">sap-wug-request@mit.edu</st1:PersonName><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. instantiate an object and attach it to a workflow? - FICA<br>
> (Paul.Bakker@osr.treasury.qld.gov.au)<br>
>
2. Re: instantiate an object and attach it to a workflow? - FICA<br>
> (Mark Pyc)<br>
>
3. Re: instantiate an object and attach it to a workflow? - FICA<br>
> (Paul.Bakker@osr.treasury.qld.gov.au)<br>
>
4. Re: instantiate an object and attach it to a workflow? - FICA<br>
> (Mark Pyc)<br>
> <br>
> <br>
> ----------------------------------------------------------------------<br>
> <br>
> Message: 1<br>
> Date: Thu, 15 Jun 2006 15:00:08 +1000<br>
> From: Paul.Bakker@osr.treasury.qld.gov.au<br>
>
Subject: instantiate an object and attach it to a workflow? - FICA<br>
> To: sap-wug@mit.edu<br>
> Message-ID:<br>
>
<OF9706AED0.433198D8-ON4A25718E.001B1EBA-4A25718E.001B73F6@treasury.qld.gov.au><br>
> <br>
> Content-Type: text/plain; charset="us-ascii"<br>
> <br>
> Workflow Gurus,<br>
> <br>
>
I have a custom workflow which, after seeking agent approval, creates an<br>
> object (a document of type CA_DOC).<br>
> <br>
>
I would like to attach an instance of the created object to the workflow,<br>
>
so that 'object services' can be used later.<br>
> <br>
>
To do this, I added a custom step which calls the method<br>
> SYSTEM.GENERICINSTANTIATE. Apparently if you pass the object key (and<br>
>
object type) to this method, it instantiates the object. This is then<br>
> passed back to the workflow container.<br>
> <br>
>
At least, that's what I hoped it would do! In practice the workflow goes<br>
> into error with message OL808: "Object with runtime number '0' not defined"<br>
> <br>
>
When I try to view the new CA_DOC object (via FPE3), it does not exist. I<br>
>
suspect this is because the workflow went into error... it didn't get a<br>
> chance to save the document.<br>
> <br>
> And yet, if I run the workflow without the extra GENERECINSTANTIATE step,<br>
> it works fine.<br>
> <br>
>
Does anyone have any idea what the problem is? Could it be that a 'COMMIT<br>
>
WORK' needs to be done before trying to instantiate the new object? Is<br>
> there a workflow step for doing that?<br>
> <br>
>
Or am I just being stupid. Is there a much easier way to attach an object<br>
> to a workflow via a background step?<br>
> <br>
> merci<br>
> Paul Bakker<br>
> <st1:City w:st="on"><st1:place w:st="on">Brisbane</st1:place></st1:City><br>
> <br>
> <br>
>
******************************************************************************************************************************************************<br>
> <br>
>
Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments. Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.<br>
> <br>
>
The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright. If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments. Queensland Treasury uses virus scanning software. However, it is not liable for viruses present in this e-mail or in any attachment. <br>
> <br>
> ******************************************************************************************************************************************************<br>
> <br>
> <br>
> <br>
> ------------------------------<br>
> <br>
> Message: 2<br>
> Date: Thu, 15 Jun 2006 08:42:04 +0100<br>
> From: "Mark Pyc" <mark.pyc@gmail.com><br>
>
Subject: Re: instantiate an object and attach it to a workflow? - FICA<br>
>
To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> Message-ID:<br>
> <23f0a78a0606150042t35c63f9di9999d3204f6b36ec@mail.gmail.com><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
> <br>
> G'day Paul,<br>
> <br>
>
You're on the right path. I don't seem to have an object type of CA_DOC in<br>
>
my ECC system so I can't comment on specifics.<br>
> <br>
>
Have you tried just testing the SYSTEM method from SWO1?? If you've got the<br>
>
key right you should be get an object link back that you can double click<br>
> into to confirm that it's worked happily.<br>
> <br>
> Good luck,<br>
> Mark<br>
> <br>
> <br>
> On 6/15/06, Paul.Bakker@osr.treasury.qld.gov.au <<br>
> Paul.Bakker@osr.treasury.qld.gov.au> wrote:<br>
> ><br>
> > Workflow Gurus,<br>
> ><br>
>
> I have a custom workflow which, after seeking agent approval, creates an<br>
> > object (a document of type CA_DOC).<br>
> ><br>
>
> I would like to attach an instance of the created object to the workflow,<br>
> > so that 'object services' can be used later.<br>
> ><br>
>
> To do this, I added a custom step which calls the method<br>
>
> SYSTEM.GENERICINSTANTIATE. Apparently if you pass the object key (and<br>
>
> object type) to this method, it instantiates the object. This is then<br>
> > passed back to the workflow container.<br>
> ><br>
>
> At least, that's what I hoped it would do! In practice the workflow goes<br>
>
> into error with message OL808: "Object with runtime number '0' not<br>
> > defined"<br>
> ><br>
>
> When I try to view the new CA_DOC object (via FPE3), it does not exist. I<br>
>
> suspect this is because the workflow went into error... it didn't get a<br>
> > chance to save the document.<br>
> ><br>
>
> And yet, if I run the workflow without the extra GENERECINSTANTIATE step,<br>
> > it works fine.<br>
> ><br>
>
> Does anyone have any idea what the problem is? Could it be that a 'COMMIT<br>
>
> WORK' needs to be done before trying to instantiate the new object? Is<br>
>
> there a workflow step for doing that?<br>
> ><br>
>
> Or am I just being stupid. Is there a much easier way to attach an object<br>
> > to a workflow via a background step?<br>
> ><br>
> > merci<br>
> > Paul Bakker<br>
> > <st1:City w:st="on"><st1:place w:st="on">Brisbane</st1:place></st1:City><br>
> ><br>
> ><br>
> ><br>
>
> ******************************************************************************************************************************************************<br>
> ><br>
> > Only an individual or entity who is intended to be a recipient of this<br>
>
> e-mail may access or use the information contained in this e-mail or any of<br>
>
> its attachments. Opinions contained in this e-mail or any of its<br>
>
> attachments do not necessarily reflect the opinions of Queensland Treasury.<br>
> ><br>
>
> The contents of this e-mail and any attachments are confidential and may<br>
>
> be legally privileged and the subject of copyright. If you have received<br>
>
> this e-mail in error, please notify Queensland Treasury immediately and<br>
>
> erase all copies of the e-mail and the attachments. <st1:State
w:st="on"><st1:place w:st="on">Queensland</st1:place></st1:State> Treasury<br>
>
> uses virus scanning software. However, it is not liable for viruses present<br>
>
> in this e-mail or in any attachment.<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>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
>
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060615/55c699f8/attachment-0001.htm<br>
> <br>
> ------------------------------<br>
> <br>
> Message: 3<br>
> Date: Thu, 15 Jun 2006 17:54:20 +1000<br>
> From: Paul.Bakker@osr.treasury.qld.gov.au<br>
>
Subject: Re: instantiate an object and attach it to a workflow? - FICA<br>
>
To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> Message-ID:<br>
> <OF986B5F4A.AC0486EB-ON4A25718E.002B2D30-4A25718E.002B66B3@treasury.qld.gov.au><br>
> <br>
> Content-Type: text/plain; charset=US-ASCII<br>
> <br>
> Mark,<br>
> <br>
>
Thanks for that. I've solved the problem now, but in a fairly ugly way.. I<br>
>
put a 'Requested Start' of "+1 minute" on the workitem that does the<br>
> instantiation. By the time ithe workitem executes, the CA_DOC has been<br>
> created and the instantation works.<br>
> <br>
>
FYI: the object CA_DOC is specific to Contract Accounting (or PSCD)<br>
> <br>
> cheers - and thanks,<br>
> Paul B<br>
> <br>
> <br>
> <br>
> |---------+----------------------------><br>
>
| | "Mark Pyc" |<br>
>
| | <mark.pyc@gmail.c|<br>
>
| | om> |<br>
>
| | Sent by: |<br>
>
| | sap-wug-bounces@m|<br>
>
| | it.edu |<br>
>
| | |<br>
>
| | |<br>
>
| | 15/06/2006 17:42 |<br>
>
| | Please respond to|<br>
>
| | "SAP Workflow |<br>
>
| | Users' Group" |<br>
>
| | |<br>
> |---------+----------------------------><br>
>
>------------------------------------------------------------------------------------------------------------------------------|<br>
>
| |<br>
>
| To: "SAP Workflow Users' Group" <sap-wug@mit.edu> |<br>
> | cc: |<br>
>
| Subject: Re: instantiate an object and attach it to a workflow? - FICA |<br>
> >------------------------------------------------------------------------------------------------------------------------------|<br>
> <br>
> <br>
> <br>
> <br>
> G'day Paul,<br>
> <br>
>
You're on the right path. I don't seem to have an object type of CA_DOC in<br>
> my ECC system so I can't comment on specifics.<br>
> <br>
>
Have you tried just testing the SYSTEM method from SWO1?? If you've got the<br>
>
key right you should be get an object link back that you can double click<br>
> into to confirm that it's worked happily.<br>
> <br>
> Good luck,<br>
> Mark<br>
> <br>
> <br>
> On 6/15/06, Paul.Bakker@osr.treasury.qld.gov.au <<br>
> Paul.Bakker@osr.treasury.qld.gov.au> wrote:<br>
> Workflow Gurus,<br>
> <br>
>
I have a custom workflow which, after seeking agent approval, creates an<br>
> object (a document of type CA_DOC).<br>
> <br>
> I would like to attach an instance of the created object to the workflow,<br>
>
so that 'object services' can be used later.<br>
> <br>
>
To do this, I added a custom step which calls the method<br>
>
SYSTEM.GENERICINSTANTIATE . Apparently if you pass the object key (and<br>
> object type) to this method, it instantiates the object. This is then<br>
> passed back to the workflow container.<br>
> <br>
>
At least, that's what I hoped it would do! In practice the workflow goes<br>
>
into error with message OL808: "Object with runtime number '0' not defined"<br>
> <br>
> When I try to view the new CA_DOC object (via FPE3), it does not exist. I<br>
>
suspect this is because the workflow went into error... it didn't get a<br>
> chance to save the document.<br>
> <br>
>
And yet, if I run the workflow without the extra GENERECINSTANTIATE step,<br>
> it works fine.<br>
> <br>
>
Does anyone have any idea what the problem is? Could it be that a 'COMMIT<br>
>
WORK' needs to be done before trying to instantiate the new object? Is<br>
> there a workflow step for doing that?<br>
> <br>
>
Or am I just being stupid. Is there a much easier way to attach an object<br>
> to a workflow via a background step?<br>
> <br>
> merci<br>
> Paul Bakker<br>
> <st1:City w:st="on"><st1:place w:st="on">Brisbane</st1:place></st1:City><br>
> <br>
> <br>
>
******************************************************************************************************************************************************<br>
> <br>
> <br>
>
Only an individual or entity who is intended to be a recipient of this<br>
>
e-mail may access or use the information contained in this e-mail or any of<br>
>
its attachments. Opinions contained in this e-mail or any of its<br>
> attachments do not necessarily reflect the opinions of Queensland Treasury.<br>
> <br>
>
The contents of this e-mail and any attachments are confidential and may be<br>
>
legally privileged and the subject of copyright. If you have received this<br>
> e-mail in error, please notify Queensland Treasury immediately and erase<br>
>
all copies of the e-mail and the attachments. Queensland Treasury uses<br>
>
virus scanning software. However, it is not liable for viruses present in<br>
> this e-mail or in any attachment.<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>
> 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>
> <br>
> Message: 4<br>
> Date: Thu, 15 Jun 2006 09:10:44 +0100<br>
> From: "Mark Pyc" <mark.pyc@gmail.com><br>
>
Subject: Re: instantiate an object and attach it to a workflow? - FICA<br>
>
To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> Message-ID:<br>
> <23f0a78a0606150110i2eb2d1aaj3f27c3d2f5c9f47b@mail.gmail.com><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
> <br>
>
There is always a sinking sense of failure when having to resort to good ol'<br>
> 1 minute delay. Unavoidable sometimes though...<br>
> <br>
> On 6/15/06, Paul.Bakker@osr.treasury.qld.gov.au <<br>
> Paul.Bakker@osr.treasury.qld.gov.au> wrote:<br>
> ><br>
> > Mark,<br>
> ><br>
>
> Thanks for that. I've solved the problem now, but in a fairly ugly way.. I<br>
>
> put a 'Requested Start' of "+1 minute" on the workitem that does the<br>
>
> instantiation. By the time ithe workitem executes, the CA_DOC has been<br>
> > created and the instantation works.<br>
> ><br>
>
> FYI: the object CA_DOC is specific to Contract Accounting (or PSCD)<br>
> ><br>
> > cheers - and thanks,<br>
> > Paul B<br>
> ><br>
> ><br>
> ><br>
> > |---------+----------------------------><br>
>
> | | "Mark Pyc" |<br>
>
> | | <mark.pyc@gmail.c|<br>
>
> | | om> |<br>
>
> | | Sent by: |<br>
>
> | | sap-wug-bounces@m|<br>
>
> | | it.edu |<br>
>
> | | |<br>
>
> | | |<br>
>
> | | 15/06/2006 17:42 |<br>
>
> | | Please respond to|<br>
>
> | | "SAP Workflow |<br>
>
> | | Users' Group" |<br>
> > | | |<br>
> > |---------+----------------------------><br>
> ><br>
>
> >------------------------------------------------------------------------------------------------------------------------------|<br>
> ><br>
>
> | |<br>
>
> | To: "SAP Workflow Users' Group" <sap-wug@mit.edu<br>
>
> > |<br>
> > |<br>
> > cc: |<br>
>
> | Subject: Re: instantiate an object and attach it to a workflow? -<br>
>
> FICA |<br>
> ><br>
> > >------------------------------------------------------------------------------------------------------------------------------|<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > G'day Paul,<br>
> ><br>
>
> You're on the right path. I don't seem to have an object type of CA_DOC in<br>
> > my ECC system so I can't comment on specifics.<br>
> ><br>
>
> Have you tried just testing the SYSTEM method from SWO1?? If you've got<br>
> > the<br>
>
> key right you should be get an object link back that you can double click<br>
>
> into to confirm that it's worked happily.<br>
> ><br>
> > Good luck,<br>
> > Mark<br>
> ><br>
> ><br>
>
> On 6/15/06, Paul.Bakker@osr.treasury.qld.gov.au <<br>
> > Paul.Bakker@osr.treasury.qld.gov.au> wrote:<br>
> > Workflow Gurus,<br>
> ><br>
>
> I have a custom workflow which, after seeking agent approval, creates an<br>
> > object (a document of type CA_DOC).<br>
> ><br>
>
> I would like to attach an instance of the created object to the workflow,<br>
>
> so that 'object services' can be used later.<br>
> ><br>
>
> To do this, I added a custom step which calls the method<br>
> > SYSTEM.GENERICINSTANTIATE . Apparently if you pass the object key (and<br>
>
> object type) to this method, it instantiates the object. This is then<br>
> > passed back to the workflow container.<br>
> ><br>
>
> At least, that's what I hoped it would do! In practice the workflow goes<br>
> > into error with message OL808: "Object with runtime number '0' not<br>
> > defined"<br>
> ><br>
>
> When I try to view the new CA_DOC object (via FPE3), it does not exist. I<br>
>
> suspect this is because the workflow went into error... it didn't get a<br>
> > chance to save the document.<br>
> ><br>
>
> And yet, if I run the workflow without the extra GENERECINSTANTIATE step,<br>
> > it works fine.<br>
> ><br>
>
> Does anyone have any idea what the problem is? Could it be that a 'COMMIT<br>
>
> WORK' needs to be done before trying to instantiate the new object? Is<br>
> > there a workflow step for doing that?<br>
> ><br>
>
> Or am I just being stupid. Is there a much easier way to attach an object<br>
>
> to a workflow via a background step?<br>
> ><br>
> > merci<br>
> > Paul Bakker<br>
> > <st1:City w:st="on"><st1:place w:st="on">Brisbane</st1:place></st1:City><br>
> ><br>
> ><br>
> ><br>
> > ******************************************************************************************************************************************************<br>
> ><br>
> ><br>
>
> Only an individual or entity who is intended to be a recipient of this<br>
>
> e-mail may access or use the information contained in this e-mail or any<br>
> > of<br>
>
> its attachments. Opinions contained in this e-mail or any of its<br>
>
> attachments do not necessarily reflect the opinions of <st1:State
w:st="on"><st1:place w:st="on">Queensland</st1:place></st1:State><br>
> > Treasury.<br>
> ><br>
>
> The contents of this e-mail and any attachments are confidential and may<br>
> > be<br>
>
> legally privileged and the subject of copyright. If you have received<br>
> > this<br>
>
> e-mail in error, please notify Queensland Treasury immediately and erase<br>
>
> all copies of the e-mail and the attachments. Queensland Treasury uses<br>
> > virus scanning software. However, it is not liable for viruses present in<br>
> > this e-mail or in any attachment.<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>
> > 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>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
>
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060615/b225ca39/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 19, Issue 37<br>
> ***************************************<br>
<br>
<o:p></o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>À vous de rechercher : <a
href="http://ideas.live.com/programpage.aspx?versionId=6e782662-5f2a-4161-a64a-7f63644e1f0a"
target="_new">Essayez Windows Live Search for Mobile Beta</a><o:p></o:p></span></font></p>
</div>
</body>
</html>