<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<div><br></div>Hello Paul,<div><br></div><div>Why don't you cancel the existing workflow and start a new one manually in SWUE with the same key field and see if that fixes the issue?</div><div><br></div><div>I was also wondering if the language issue for the deadline job might be fixed if a new user who's logged in 'EN' and have the proper authorization run the automatic customizing in SWU3.</div><div><br></div><div>Regards,</div><div>Ali</div><div><br></div><div><br><br><div><div id="SkyDrivePlaceholder"></div>> From: sap-wug-request@mit.edu<br>> Subject: SAP-WUG Digest, Vol 86, Issue 23<br>> To: sap-wug@mit.edu<br>> Date: Mon, 23 Jan 2012 23:21:54 -0500<br>> <br>> Send SAP-WUG mailing list submissions to<br>> sap-wug@mit.edu<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>> or, via email, send a message with subject or body 'help' to<br>> sap-wug-request@mit.edu<br>> <br>> You can reach the person managing the list at<br>> sap-wug-owner@mit.edu<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of SAP-WUG digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. SWWDHEX starts a French workflow<br>> (Paul.Bakker@osr.treasury.qld.gov.au)<br>> 2. RE: SWWDHEX starts a French workflow (Dart, Jocelyn)<br>> 3. RE: SWWDHEX starts a French workflow<br>> (Paul.Bakker@osr.treasury.qld.gov.au)<br>> 4. RE: SWWDHEX starts a French workflow (Dart, Jocelyn)<br>> 5. RE: SWWDHEX starts a French workflow<br>> (Paul.Bakker@osr.treasury.qld.gov.au)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Tue, 24 Jan 2012 12:17:56 +1000<br>> From: Paul.Bakker@osr.treasury.qld.gov.au<br>> Subject: SWWDHEX starts a French workflow<br>> To: sap-wug@mit.edu<br>> Message-ID: <201201240218.q0O2I4F7008815@mailhub-dmz-3.mit.edu><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> <br>> Regular readers of the WUG group might remember my question from a few<br>> weeks ago:<br>> <br>> How is the WorkItemLanguage of a workflow set?<br>> <br>> I had an urgent problem: mining engineers in the outback were receiving<br>> workflow emails in French, and they weren't happy about it.<br>> <br>> Using advice from Florin W. I tracked down the culprit: the deadline job<br>> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in<br>> the 'step' tab).<br>> <br>> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates<br>> the current workitem. The workflow continues on and approves the<br>> procurement document (at the current release level), and this triggers a<br>> new approval workflow for the next level.<br>> <br>> This new workflow is started with the WorkItemLanguage copied from the<br>> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU at the<br>> time that the workflow is triggered.<br>> <br>> My question is now: how can I change SY-LANGU in the ABAP code, before the<br>> next workflow is triggered?<br>> <br>> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:<br>> - sy-langu = 'EN'.<br>> - 'SET LOCALE LANGUAGE 'E'.<br>> <br>> But neither have had any effect.<br>> <br>> Is there a better approach? Or is there another way to stop the evil<br>> influence of the SWWDHEX job?<br>> <br>> thanks<br>> Paul Bakker<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>> Message: 2<br>> Date: Tue, 24 Jan 2012 03:56:56 +0100<br>> From: "Dart, Jocelyn" <jocelyn.dart@sap.com><br>> Subject: RE: SWWDHEX starts a French workflow<br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Message-ID:<br>> <8C507B5E0BA5114E933C3C6E2E9729E007674CEE85@DEWDFECCR01.wdf.sap.corp><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> Hi Paul, <br>> Maybe you should just get them to set on the inbox Personal Workflow Settings to translate work items to your own language (English) temporarily?<br>> Or is the problem that French isn't giving you any text at all?<br>> <br>> You could also try just updating WI_LANG on table SWWWIHEAD which should do the same thing.<br>> Regards,<br>> Jocelyn <br>> <br>> -----Original Message-----<br>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of Paul.Bakker@osr.treasury.qld.gov.au<br>> Sent: Tuesday, 24 January 2012 1:18 PM<br>> To: sap-wug@mit.edu<br>> Subject: SWWDHEX starts a French workflow<br>> <br>> <br>> Regular readers of the WUG group might remember my question from a few<br>> weeks ago:<br>> <br>> How is the WorkItemLanguage of a workflow set?<br>> <br>> I had an urgent problem: mining engineers in the outback were receiving<br>> workflow emails in French, and they weren't happy about it.<br>> <br>> Using advice from Florin W. I tracked down the culprit: the deadline job<br>> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in<br>> the 'step' tab).<br>> <br>> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates<br>> the current workitem. The workflow continues on and approves the<br>> procurement document (at the current release level), and this triggers a<br>> new approval workflow for the next level.<br>> <br>> This new workflow is started with the WorkItemLanguage copied from the<br>> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU at the<br>> time that the workflow is triggered.<br>> <br>> My question is now: how can I change SY-LANGU in the ABAP code, before the<br>> next workflow is triggered?<br>> <br>> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:<br>> - sy-langu = 'EN'.<br>> - 'SET LOCALE LANGUAGE 'E'.<br>> <br>> But neither have had any effect.<br>> <br>> Is there a better approach? Or is there another way to stop the evil<br>> influence of the SWWDHEX job?<br>> <br>> thanks<br>> Paul Bakker<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>> SAP-WUG mailing list<br>> SAP-WUG@mit.edu<br>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Tue, 24 Jan 2012 13:17:41 +1000<br>> From: Paul.Bakker@osr.treasury.qld.gov.au<br>> Subject: RE: SWWDHEX starts a French workflow<br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Message-ID: <201201240317.q0O3GVEk013986@mailhub-dmz-3.mit.edu><br>> Content-Type: text/plain; charset=US-ASCII<br>> <br>> <br>> Thanks for that. Unfortunately, Inbox settings won't help.<br>> <br>> The problem is that the workflow is using 'SendTaskDescriptio'n to send<br>> emails containing the workitem text.<br>> Because WorkitemLanguage = 'FR', it is always choosing to send the<br>> translated French text in the email.<br>> <br>> (I know - it should have been built to use Extended Notifications<br>> instead.... I'm just the maintenance guy)<br>> <br>> Also, it's not so easy to change the WI language - once the WI Language of<br>> the toplevel workflow is set, it flows through to every subsequent<br>> workitem.<br>> <br>> +++<br>> <br>> This is a bit of a worrying 'feature' of deadlines - any new workflows<br>> kicked off by deadline handling will inherit a hardcoded language..... the<br>> logon language of the guy who happened to run SWU3 in Production!<br>> <br>> cheers<br>> Paul Bakker<br>> <br>> <br>> <br>> From: "Dart, Jocelyn" <jocelyn.dart@sap.com><br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Date: 24/01/2012 01:00 PM<br>> Subject: RE: SWWDHEX starts a French workflow<br>> Sent by: sap-wug-bounces@mit.edu<br>> <br>> <br>> <br>> Hi Paul,<br>> Maybe you should just get them to set on the inbox Personal Workflow<br>> Settings to translate work items to your own language (English)<br>> temporarily?<br>> Or is the problem that French isn't giving you any text at all?<br>> <br>> You could also try just updating WI_LANG on table SWWWIHEAD which should do<br>> the same thing.<br>> Regards,<br>> Jocelyn<br>> <br>> -----Original Message-----<br>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of<br>> Paul.Bakker@osr.treasury.qld.gov.au<br>> Sent: Tuesday, 24 January 2012 1:18 PM<br>> To: sap-wug@mit.edu<br>> Subject: SWWDHEX starts a French workflow<br>> <br>> <br>> Regular readers of the WUG group might remember my question from a few<br>> weeks ago:<br>> <br>> How is the WorkItemLanguage of a workflow set?<br>> <br>> I had an urgent problem: mining engineers in the outback were receiving<br>> workflow emails in French, and they weren't happy about it.<br>> <br>> Using advice from Florin W. I tracked down the culprit: the deadline job<br>> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in<br>> the 'step' tab).<br>> <br>> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates<br>> the current workitem. The workflow continues on and approves the<br>> procurement document (at the current release level), and this triggers a<br>> new approval workflow for the next level.<br>> <br>> This new workflow is started with the WorkItemLanguage copied from the<br>> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU at the<br>> time that the workflow is triggered.<br>> <br>> My question is now: how can I change SY-LANGU in the ABAP code, before the<br>> next workflow is triggered?<br>> <br>> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:<br>> - sy-langu = 'EN'.<br>> - 'SET LOCALE LANGUAGE 'E'.<br>> <br>> But neither have had any effect.<br>> <br>> Is there a better approach? Or is there another way to stop the evil<br>> influence of the SWWDHEX job?<br>> <br>> thanks<br>> Paul Bakker<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>> 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>> ------------------------------<br>> <br>> Message: 4<br>> Date: Tue, 24 Jan 2012 04:33:20 +0100<br>> From: "Dart, Jocelyn" <jocelyn.dart@sap.com><br>> Subject: RE: SWWDHEX starts a French workflow<br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Message-ID:<br>> <8C507B5E0BA5114E933C3C6E2E9729E007674CEE9D@DEWDFECCR01.wdf.sap.corp><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> Hi Paul, <br>> Is there some reason why you can't just fix the job in SM37 in Prod? Yes its scheduled by SWU3 but that's a matter of convenience ... the job is just a job. <br>> Cheers, <br>> Jocelyn <br>> <br>> -----Original Message-----<br>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of Paul.Bakker@osr.treasury.qld.gov.au<br>> Sent: Tuesday, 24 January 2012 2:18 PM<br>> To: SAP Workflow Users' Group<br>> Subject: RE: SWWDHEX starts a French workflow<br>> <br>> <br>> Thanks for that. Unfortunately, Inbox settings won't help.<br>> <br>> The problem is that the workflow is using 'SendTaskDescriptio'n to send<br>> emails containing the workitem text.<br>> Because WorkitemLanguage = 'FR', it is always choosing to send the<br>> translated French text in the email.<br>> <br>> (I know - it should have been built to use Extended Notifications<br>> instead.... I'm just the maintenance guy)<br>> <br>> Also, it's not so easy to change the WI language - once the WI Language of<br>> the toplevel workflow is set, it flows through to every subsequent<br>> workitem.<br>> <br>> +++<br>> <br>> This is a bit of a worrying 'feature' of deadlines - any new workflows<br>> kicked off by deadline handling will inherit a hardcoded language..... the<br>> logon language of the guy who happened to run SWU3 in Production!<br>> <br>> cheers<br>> Paul Bakker<br>> <br>> <br>> <br>> From: "Dart, Jocelyn" <jocelyn.dart@sap.com><br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Date: 24/01/2012 01:00 PM<br>> Subject: RE: SWWDHEX starts a French workflow<br>> Sent by: sap-wug-bounces@mit.edu<br>> <br>> <br>> <br>> Hi Paul,<br>> Maybe you should just get them to set on the inbox Personal Workflow<br>> Settings to translate work items to your own language (English)<br>> temporarily?<br>> Or is the problem that French isn't giving you any text at all?<br>> <br>> You could also try just updating WI_LANG on table SWWWIHEAD which should do<br>> the same thing.<br>> Regards,<br>> Jocelyn<br>> <br>> -----Original Message-----<br>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of<br>> Paul.Bakker@osr.treasury.qld.gov.au<br>> Sent: Tuesday, 24 January 2012 1:18 PM<br>> To: sap-wug@mit.edu<br>> Subject: SWWDHEX starts a French workflow<br>> <br>> <br>> Regular readers of the WUG group might remember my question from a few<br>> weeks ago:<br>> <br>> How is the WorkItemLanguage of a workflow set?<br>> <br>> I had an urgent problem: mining engineers in the outback were receiving<br>> workflow emails in French, and they weren't happy about it.<br>> <br>> Using advice from Florin W. I tracked down the culprit: the deadline job<br>> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in<br>> the 'step' tab).<br>> <br>> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates<br>> the current workitem. The workflow continues on and approves the<br>> procurement document (at the current release level), and this triggers a<br>> new approval workflow for the next level.<br>> <br>> This new workflow is started with the WorkItemLanguage copied from the<br>> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU at the<br>> time that the workflow is triggered.<br>> <br>> My question is now: how can I change SY-LANGU in the ABAP code, before the<br>> next workflow is triggered?<br>> <br>> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:<br>> - sy-langu = 'EN'.<br>> - 'SET LOCALE LANGUAGE 'E'.<br>> <br>> But neither have had any effect.<br>> <br>> Is there a better approach? Or is there another way to stop the evil<br>> influence of the SWWDHEX job?<br>> <br>> thanks<br>> Paul Bakker<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>> 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>> SAP-WUG mailing list<br>> SAP-WUG@mit.edu<br>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Tue, 24 Jan 2012 14:21:32 +1000<br>> From: Paul.Bakker@osr.treasury.qld.gov.au<br>> Subject: RE: SWWDHEX starts a French workflow<br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Message-ID: <201201240421.q0O4Lghv018437@mailhub-dmz-4.mit.edu><br>> Content-Type: text/plain; charset=US-ASCII<br>> <br>> Jocelyn,<br>> <br>> The French users might storm the Bastille if I did that! :-)<br>> <br>> I don't want any language to be hardcoded, if it controls the translation<br>> of the emails.<br>> <br>> Our idea is to have sy-langu transferred from the original<br>> (deadline-terminated) workflow to the new one.<br>> I have all the bindings in place to do that, but SY-LANGU just doesn't want<br>> to be changed..<br>> <br>> merci<br>> Paul<br>> <br>> <br>> <br>> From: "Dart, Jocelyn" <jocelyn.dart@sap.com><br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Date: 24/01/2012 01:37 PM<br>> Subject: RE: SWWDHEX starts a French workflow<br>> Sent by: sap-wug-bounces@mit.edu<br>> <br>> <br>> <br>> Hi Paul,<br>> Is there some reason why you can't just fix the job in SM37 in Prod? Yes<br>> its scheduled by SWU3 but that's a matter of convenience ... the job is<br>> just a job.<br>> Cheers,<br>> Jocelyn<br>> <br>> -----Original Message-----<br>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of<br>> Paul.Bakker@osr.treasury.qld.gov.au<br>> Sent: Tuesday, 24 January 2012 2:18 PM<br>> To: SAP Workflow Users' Group<br>> Subject: RE: SWWDHEX starts a French workflow<br>> <br>> <br>> Thanks for that. Unfortunately, Inbox settings won't help.<br>> <br>> The problem is that the workflow is using 'SendTaskDescriptio'n to send<br>> emails containing the workitem text.<br>> Because WorkitemLanguage = 'FR', it is always choosing to send the<br>> translated French text in the email.<br>> <br>> (I know - it should have been built to use Extended Notifications<br>> instead.... I'm just the maintenance guy)<br>> <br>> Also, it's not so easy to change the WI language - once the WI Language of<br>> the toplevel workflow is set, it flows through to every subsequent<br>> workitem.<br>> <br>> +++<br>> <br>> This is a bit of a worrying 'feature' of deadlines - any new workflows<br>> kicked off by deadline handling will inherit a hardcoded language..... the<br>> logon language of the guy who happened to run SWU3 in Production!<br>> <br>> cheers<br>> Paul Bakker<br>> <br>> <br>> <br>> From: "Dart, Jocelyn" <jocelyn.dart@sap.com><br>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>> Date: 24/01/2012 01:00 PM<br>> Subject: RE: SWWDHEX starts a French workflow<br>> Sent by: sap-wug-bounces@mit.edu<br>> <br>> <br>> <br>> Hi Paul,<br>> Maybe you should just get them to set on the inbox Personal Workflow<br>> Settings to translate work items to your own language (English)<br>> temporarily?<br>> Or is the problem that French isn't giving you any text at all?<br>> <br>> You could also try just updating WI_LANG on table SWWWIHEAD which should do<br>> the same thing.<br>> Regards,<br>> Jocelyn<br>> <br>> -----Original Message-----<br>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of<br>> Paul.Bakker@osr.treasury.qld.gov.au<br>> Sent: Tuesday, 24 January 2012 1:18 PM<br>> To: sap-wug@mit.edu<br>> Subject: SWWDHEX starts a French workflow<br>> <br>> <br>> Regular readers of the WUG group might remember my question from a few<br>> weeks ago:<br>> <br>> How is the WorkItemLanguage of a workflow set?<br>> <br>> I had an urgent problem: mining engineers in the outback were receiving<br>> workflow emails in French, and they weren't happy about it.<br>> <br>> Using advice from Florin W. I tracked down the culprit: the deadline job<br>> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in<br>> the 'step' tab).<br>> <br>> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates<br>> the current workitem. The workflow continues on and approves the<br>> procurement document (at the current release level), and this triggers a<br>> new approval workflow for the next level.<br>> <br>> This new workflow is started with the WorkItemLanguage copied from the<br>> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU at the<br>> time that the workflow is triggered.<br>> <br>> My question is now: how can I change SY-LANGU in the ABAP code, before the<br>> next workflow is triggered?<br>> <br>> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:<br>> - sy-langu = 'EN'.<br>> - 'SET LOCALE LANGUAGE 'E'.<br>> <br>> But neither have had any effect.<br>> <br>> Is there a better approach? Or is there another way to stop the evil<br>> influence of the SWWDHEX job?<br>> <br>> thanks<br>> Paul Bakker<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>> _______________________________________________<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>> ------------------------------<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 86, Issue 23<br>> ***************************************<br></div></div> </div></body>
</html>