<br><font size=2 face="sans-serif">Hello </font><font size=2><tt>Akshay</tt></font><font size=2 face="sans-serif">,</font>
<br>
<br><font size=2 face="sans-serif">In case you are displaying your material
via an asynchronous call (such as in a workflow secondary method), maybe
OSS note 316812 will solve your problem.</font>
<br>
<br><font size=2 face="sans-serif">We have scheduled the report recommended
in this note as a batch job, in order to clean up former calls regularly
to avoid that the wrong business object (material number, financial document
number etc) is displayed when a user is executing several work items
after each other from the SBWP workflow inbox.</font>
<br>
<br><font size=2 face="sans-serif">Note 316812 applies to all releases
from rel 4.6* and higher.</font>
<br>
<br><font size=2 face="sans-serif">Kind regards</font>
<br><font size=2 face="sans-serif">Viveka</font>
<br>
<table width=100%>
<tr>
<td width=100%></table>
<br>
<br><font size=2 face="sans-serif"> <br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b><kaukabr@yahoo.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">2006-05-19 16:31</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: Work item Inconsistence in Inbox</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Hello:<br>
I too came across with this kind of issue before, I<br>
have to set a background job of buffering once or<br>
twice a day RHWFINDEXRESET (Synchronize Runtime<br>
Buffer) or Tx SWU_OBUF. Set this in backgroud job I<br>
hope this will work for you too.<br>
Regards,<br>
Cheers,<br>
Qhurram. <br>
<br>
--- vijay srikanth <vijay_d15@hotmail.com> wrote:<br>
<br>
> Happened a lot of times with me. I think there<br>
> should be a note for this.<br>
> This might have probably happened because the user<br>
> had executed XYZ just <br>
> before ABC execution.<br>
> It happens so that the workflow takes the person to<br>
> the work item of the <br>
> previous object that was executed, and not the<br>
> current one. I'm not sure how <br>
> to tackle this problem though.<br>
> <br>
> Regards,<br>
> Vijay<br>
> <br>
> <br>
> >From: <akshay.bhagwat@wipro.com><br>
> >Reply-To: "SAP Workflow Users' Group"<br>
> <sap-wug@mit.edu><br>
> >To: <sap-wug@mit.edu><br>
> >Subject: Work item Inconsistence in Inbox<br>
> >Date: Fri, 19 May 2006 12:22:54 +0530<br>
> ><br>
> ><br>
> >Hi all,<br>
> ><br>
> >In one of our material master workflow scenario,<br>
> there was a problem due<br>
> >to changed password of WF-batch. Hence workflow has<br>
> come to a halt.<br>
> >After the new password was known, we used<br>
> synchronize password option<br>
> >and the workflow started working.<br>
> ><br>
> ><br>
> >We have come across a scenario where user receives<br>
> a work item<br>
> >notification to SAP Inbox in which material<br>
> mentioned is say "ABC" ,<br>
> >however when he executes work item, a different<br>
> material say "XYZ" is<br>
> >shown.<br>
> >I have checked the container thro' workflow log and<br>
> in log it shows a<br>
> >material "XYZ" instead of "ABC".<br>
> >I am not able to guess how this material "XYZ" is<br>
> there in workflow when<br>
> >it was started with material "ABC"<br>
> ><br>
> >(Note: Workflow was started before WF batch<br>
> password was changed. Then<br>
> >due to password problem workflow was not in working<br>
> condition, and<br>
> >afterwards, WF =batch password corrected and<br>
> workflow functioning was<br>
> >resumed.)<br>
> ><br>
> ><br>
> >Regards,<br>
> ><br>
> >Akshay Bhagwat<br>
> ><br>
> >SAP Practice<br>
> ><br>
> >Wipro Technologies<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> >The information contained in this electronic<br>
> message and any attachments to <br>
> >this message are intended for the exclusive use of<br>
> the addressee(s) and may <br>
> >contain proprietary, confidential or privileged<br>
> information. If you are not <br>
> >the intended recipient, you should not disseminate,<br>
> distribute or copy this <br>
> >e-mail. Please notify the sender immediately and<br>
> destroy all copies of this <br>
> >message and any attachments.<br>
> ><br>
> >WARNING: Computer viruses can be transmitted via<br>
> email. The recipient <br>
> >should check this email and any attachments for the<br>
> presence of viruses. <br>
> >The company accepts no liability for any damage<br>
> caused by any virus <br>
> >transmitted by this email.<br>
> ><br>
> >www.wipro.com<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>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</tt></font>
<br>