<br><font size=2 face="sans-serif">Kavitha,</font>
<br>
<br><font size=2 face="sans-serif">Glad to hear you found the problem!</font>
<br>
<br><font size=2 face="sans-serif">Ineke</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>kavitha mahishi <kavitha.sap@gmail.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">08-09-2005 12:02</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"</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">"SAP Workflow Users'
Group" <sap-wug@mit.edu></font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: Workitem reaching a wrong
agent for release of PO</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Hi Ineke,<br>
<br>
You were absolutely right, the problem was because the select<br>
statement was not checked for Sy-Subrc and also data is not refreshed.<br>
This is happening in the standard function module -<br>
ME_REL_GET_RESPONSIBLE for table t16fc.<br>
<br>
Hence the data from the previous work item executed by the same
user<br>
(our case a gap of a minute) is going into the current user exit.<br>
Wrong Release code values is going in. Hence was the wrong agent<br>
determination.<br>
<br>
Thanks,<br>
Kavitha<br>
<br>
<br>
<br>
On 9/5/05, Ineke Hopman <ineke.hopman@nl.ibm.com> wrote:<br>
> Hello,<br>
> <br>
> It looks like a table isn't refreshed at the correct time. May be
you can <br>
> check the code in the user exit and check if the internal table with
the <br>
> release codes (or purchase groups) is refreshed correctly. If not
it can <br>
> use the release strategy from the preceding time. This explains why
<br>
> sometimes the wrong agent is determined (preceding release strategy
was <br>
> different) and sometimes the correct agent is determined (if the preceding
<br>
> release strategy was the same).<br>
> <br>
> Hope this helps...a bit finding the error.<br>
> <br>
> Kind regards,<br>
> Ineke Hopman<br>
> <br>
> <br>
> <br>
> <br>
> kavitha mahishi <kavitha.sap@gmail.com> <br>
> Sent by: sap-wug-bounces@mit.edu<br>
> 05-09-2005 08:21<br>
> Please respond to<br>
> "SAP Workflow Users' Group"<br>
> <br>
> <br>
> To<br>
> sap-wug@mit.edu<br>
> cc<br>
> <br>
> Subject<br>
> Workitem reaching a wrong agent for release of PO<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Hi,<br>
> <br>
> A workflow is implemented for release of Purchase Order(BUS2012).<br>
> For some PO's, due to some strange reason...PO meant for the
role B1<br>
> are going to A1. The agents(userid's) for sending emails of B1,A1,C1,etc
<br>
> are<br>
> mentioned in a custom table. Also the release strategy's are mapped
in<br>
> the OMGS transaction.<br>
> I tried debugging the method, but could not reach any
solution.<br>
> <br>
> The recipients are established by accessing a custom table<br>
> ZMM_PO_AUTH. Standard Role(MM_po_rel) with function module<br>
> ('ME_REL_GET_RESPONSIBLE') is used. User exit 'EXIT_SAPLEBNF_001'
is<br>
> implemented to read the agents (userid's) from this table.<br>
> These agents are determined by the purchasing groups of the Purchase<br>
> Order and Release code. The different Release codes are A1, B1,<br>
> C1,D1,E1. Further the Release codes are determined by the Release<br>
> strategy while creating the PO. Different Release strategy's are
A1,<br>
> B1, C1, D1(which have nothing to do with the Release Codes A1,<br>
> B1,...). These Release strategy's are picked up by the system based
on<br>
> the Po amount which is all mentioned in the transaction OMGS.<br>
> <br>
> Also another important observation is that is is not happening always<br>
> but only sometimes when the release strategy on the PO is changed.<br>
> Also it does not happen everytime a release strategy is changed, which<br>
> is making it impossible to replicate the case.<br>
> <br>
> Please help me resolve this.<br>
> <br>
> Thanks,<br>
> kavitha<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>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</tt></font>
<br>