<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<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:0cm;
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:purple;
text-decoration:underline;}
p
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.emailstyle17
{font-family:Arial;
color:navy;}
span.EmailStyle19
{font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body bgcolor=white lang=EN-AU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Alternatively you can enhance the standard
purchase requisition release strategy with user exits.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Step 1. Build a functionality in user exit
exit_saplebnd_001 (M06B0002) to store the chosen user/position/etc in communication
structure CEBAN user field.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Step 2. Use user exit exit_saplebnf_001
(M06B0001) to determine the agent based on the communication structure. </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Kind regards,</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Anke Hofstede</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Deloitte</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 face=Tahoma><span lang=EN-US style='font-size:
10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]
<b><span style='font-weight:bold'>On Behalf Of </span></b>Chatterjee, Partha
(US - San Ramon)<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, 24 March 2005 4:40
AM<br>
<b><span style='font-weight:bold'>To:</span></b> SAP Workflow Users' Group<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: Purchase Requsition
workflow - Approver selection</span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
<div id=idOWAReplyText59393>
<div>
<p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>In order to not go to the inbox, one easy
possibility is to use a z-transaction code. The first part of the
Z-transaction is to do the call transaction to me51n. Right after that do
the function module pop-up for the approver and then use SWE_EVENT_CREATE to
trigger your workflow.</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Alternatively, have your folks create a customer field for
approver on the me51n transaction with the appropriate drop-downs.</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>With regards,</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Partha</span></font></p>
</div>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
<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>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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 on behalf of Sathish Venkatesan<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tue 3/22/2005 10:37 PM<br>
<b><span style='font-weight:bold'>To:</span></b> SAP Workflow Users' Group<br>
<b><span style='font-weight:bold'>Subject:</span></b> Purchase Requsition
workflow - Approver selection</span></font></p>
</div>
<div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Hello all,</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>We are in the process of implementing Purchase Requisition
Overall Release workflow.</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>There are 3 levels of Approval and the client wants each
level approver to select next level approver</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>till its finally released. Also approver details are
maintained in a custom table instead of org chart.</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Thinking of having a custom method after each level of
Approval\release to select the next approver.</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>But the real concern for me is the user who is creating the
purchase requisition wants to select the </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>first level approver immediately after creating purchase
requisition. Thought of having a select agent </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>activity in the first step of the workflow and assign wf
initiator to that task, but they don't want to go</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>SAP Inbox and select the agent either. </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Is there a way, so that a pop-up can be raised to
select a approver immediately after creating a purchase requisition?</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Also client does not like express workitem after purchase
requisition creation. Let me know if any user exit can be used.</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>We are in SAP 46C (Patch level 47).</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Thanks!</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Sathish Venkatesan</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
</div>
</div>
<FONT SIZE=3><BR>
<BR>
***********Confidentiality/Limited Liability Statement***************<BR>
<BR>
This message contains privileged and confidential information intended<BR>
only for the use of the addressee named above. If you are not the <BR>
intended recipient of this message, you must not disseminate, copy or <BR>
take any action in reliance on it. If you have received this message <BR>
in error, please notify Deloitte immediately. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Deloitte.<BR>
<BR>
Liability limited by the Accountants' Scheme, approved under the Professional Standards Act 1994 (NSW).<BR>
<BR>
The sender cannot guarantee that this email or any attachment to it <BR>
is free of computer viruses or other conditions which may damage or<BR>
interfere with data, hardware or software with which it might be used.<BR>
It is sent on the strict condition that the user carries out and relies<BR>
on its own procedures for ensuring that its use will not interfere with<BR>
the recipients systems and the recipient assumes all risk of use and<BR>
absolves the sender of all responsibility for any consequence of its use.<BR>
</FONT>
</body>
</html>