<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D = "DAV:" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3086" name=GENERATOR><!--[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]-->
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99
}
SPAN.EmailStyle18 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle20 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
..MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=724132213-08062007><FONT face=Arial
color=#0000ff size=2>Sriharsha,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=724132213-08062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=724132213-08062007></SPAN><SPAN
class=724132213-08062007><FONT face=Arial color=#0000ff size=2>I have the user
decision inside a loop. The loop does not complete until the invoice is
successfully posted or rejected/deleted. If the post fails the workflow
will simply loop back and sent a new workitem back to the approver. Does
this answer your question or are you looking for something
else?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=724132213-08062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=724132213-08062007><FONT face=Arial
color=#0000ff size=2>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=724132213-08062007><FONT face=Arial
color=#0000ff size=2>Seth</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>Sriharsha_Medisetty<BR><B>Sent:</B> Thursday, June 07, 2007 10:36
PM<BR><B>To:</B> SAP Workflow Users' Group<BR><B>Subject:</B> RE: Payment Block
On Vendor Invoice<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Hi
Seth,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Thanks
for your reply,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">In
my scenario, when user approves, in more technical way when user clicks on
approve button in decision task, back ground task runs and clear payment
indicator through FB02.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
would like to know, if process is incomplete or unsuccessful how to bring back
workitem into approvers inbox. Please give details
steps.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Sri
harsha.M<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>Stevens, Seth<BR><B>Sent:</B> Thursday, June 07, 2007 1:53 PM<BR><B>To:</B>
SAP Workflow Users' Group<BR><B>Subject:</B> RE: Payment Block On Vendor
Invoice<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">My
solution probably won't work in your situation. By the time the workflow
gets to this point the document should be correct and ready to post (background
step). A simulation runs, then the post happens. If the simulation
returns any other errors (besides a duplicate warning) we will use advance with
dialog and tell the user why the invoice isn't ready to post. If the
duplicate message is the ONLY error, I will use a background step to set the
payment block then try posting the invoice.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">In this
scenario we will still be setting the payment block correctly and will only lose
advance with dialog in the unusual case in which the background step fails to
add the block or the invoice fails posting due to some error that was not found
during simulation. In this case the workitem will be back in the
approver's inbox the next time they refresh.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Hope
this helps.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Thanks,</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Seth</SPAN><o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>Sriharsha_Medisetty<BR><B>Sent:</B> Tuesday, June 05, 2007 11:00
PM<BR><B>To:</B> SAP Workflow Users' Group<BR><B>Subject:</B> RE: Payment Block
On Vendor Invoice</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Hi
Seth,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
am also developing workflow for same scenario. Once user approves the invoice
workflow has to clear the blocking indicator, Even I am using call
transaction(FB02) for the same. If there is any error occurs in process just I
am capturing errors and sending mail to workflow initiator with error details.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
am not clear with synchronous and asynchronous updating. After seeing your
message I am very keen know what procedure you are following. It would be
grateful if give me information in detail.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Sri
harsha.M<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>Stevens, Seth<BR><B>Sent:</B> Tuesday, June 05, 2007 10:17 PM<BR><B>To:</B>
SAP Workflow Users' Group<BR><B>Subject:</B> RE: Payment Block On Vendor
Invoice<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Thanks
for the responses. To answer your question Mike, there is document
simulation that runs to check the invoice before posting. If there are any
errors we do not attempt to post the invoice and use advance with dialog to
immediately display the errors to the user. Setting the payment block is a
part of this simulation step and needs to happen before posting so that the user
can review.</SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">We have
developed a work around that we think will be acceptable. It will break
advance with dialog for a very small percentage of work items but we somehow got
the users to agree.</SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Thanks
for the help!!!</SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>Edward Diehl<BR><B>Sent:</B> Tuesday, June 05, 2007 12:12 PM<BR><B>To:</B>
SAP Workflow Users' Group<BR><B>Subject:</B> RE: Payment Block On Vendor
Invoice<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">You could perhaps
use a Secondary Method type AFTER, but I'm not sure that is executed by
WF-BATCH. You might check that out.<BR><BR><BR>> Date: Tue, 5 Jun 2007
17:44:33 +0100<BR>> Subject: Re: Payment Block On Vendor Invoice<BR>>
From: asap@workflowconnections.com<BR>> To: sap-wug@mit.edu<BR>> <BR>>
Hi Seth,<BR>> <BR>> Let me get this right: is the posting also done in
dialog? So if they have<BR>> auth to post then why not give auth to change?
Or else could you not do a<BR>> background step after all the advance with
dialog stuff?<BR>> <BR>> Otherwise fire an event and do a background
update asynchronously in a<BR>> separate task.<BR>> <BR>>
Cheers,<BR>> Mike<BR>> <BR>> On Tue, June 5, 2007 4:32 pm, Stevens,
Seth wrote:<BR>> > All,<BR>> ><BR>> > Does anyone have any
suggestions for the below scenario? We have a<BR>> > workflow used for
approving and posting FI vendor invoices. Before the<BR>> > workflow posts
the document we need to, possibly, set a payment block on<BR>> > the
invoice based on some business rules.<BR>> ><BR>> > We have written
a call transaction to set the block; however, in most<BR>> > cases the
user does not have edit access so the call transaction won't<BR>> > work
if running under the user's ID. We cannot set this as a background<BR>> >
task because there is a requirement to have advance with dialog. I<BR>> >
cannot find a function module to accomplish this and obviously didn't<BR>>
> want to do a direct table update.<BR>> ><BR>> > Any help or
ideas would be greatly appreciated!<BR>> ><BR>> > Thanks,<BR>>
> Seth<BR>> ><BR>> ><BR>> ><BR>> >
-----------------------------------------<BR>> > *Please note my E-Mail
Address has changed. Please update your<BR>> > contact list*<BR>>
><BR>> > Anadarko Confidentiality Notice:<BR>> > This electronic
transmission and any attached documents or other<BR>> > writings are
intended only for the person or entity to which it is<BR>> > addressed and
may contain information that is privileged,<BR>> > confidential or
otherwise protected from disclosure. If you have<BR>> > received this
communication in error, please immediately notify<BR>> > sender by return
e-mail and destroy the communication. Any<BR>> > disclosure, copying,
distribution or the taking of any action<BR>> > concerning the contents of
this communication or any attachments by<BR>> > anyone other than the
named recipient is strictly<BR>> >
prohibited._______________________________________________<BR>> > SAP-WUG
mailing list<BR>> > SAP-WUG@mit.edu<BR>> >
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> ><BR>> <BR>>
<BR>> -- <BR>> Mike Pokraka<BR>> Senior Consultant<BR>> Workflow
Connections<BR>> Mobile: +44(0)7786 910855<BR>> <BR>>
_______________________________________________<BR>> SAP-WUG mailing
list<BR>> SAP-WUG@mit.edu<BR>>
http://mailman.mit.edu/mailman/listinfo/sap-wug<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">*Please note my
E-Mail Address has changed. Please update your contact list*
<o:p></o:p></SPAN></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
<HR align=center width="100%" SIZE=1>
</SPAN></DIV>
<P><STRONG><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Anadarko
Confidentiality Notice: This electronic transmission and any attached documents
or other writings are intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. If you have received this communication in
error, please immediately notify sender by return e-mail and destroy the
communication. Any disclosure, copying, distribution or the taking of any action
concerning the contents of this communication or any attachments by anyone other
than the named recipient is strictly prohibited. </SPAN></STRONG><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"><o:p></o:p></SPAN></P>
<P>DISCLAIMER:<BR>This email (including any attachments) is intended for the
sole use of the intended recipient/s and may contain material that is
CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others
or copying or distribution or forwarding of any or all of the contents in this
message is STRICTLY PROHIBITED. If you are not the intended recipient, please
contact the sender by email and delete all copies; your cooperation in this
regard is appreciated.. <o:p></o:p></P></DIV>
<P></P>
<P>DISCLAIMER:<BR>This email (including any attachments) is intended for the
sole use of the intended recipient/s and may contain material that is
CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others
or copying or distribution or forwarding of any or all of the contents in this
message is STRICTLY PROHIBITED. If you are not the intended recipient, please
contact the sender by email and delete all copies; your cooperation in this
regard is appreciated.. </P></BODY></HTML>