<div>G'day all, </div>
<div> </div>
<div>A clarification here from Phil. </div>
<div> </div>
<div>Have fun,</div>
<div>Mark<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">Soady, Phil</b> <<a href="mailto:phil.soady@sap.com">phil.soady@sap.com</a>><br>Date: Jul 22, 2006 4:09 AM
<br>Subject: FW: SAP-WUG Digest, Vol 20, Issue 54<br>To: <a href="mailto:mark.pyc@gmail.com">mark.pyc@gmail.com</a><br><br> </span></div>
<div>
<div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Hi Mark,</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Just a small qualification on your good advice regarding released and not released objects.</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">SAP agrees to advise of pending change or discontinuation of support</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">in the next release version in the case of released objects. eg see BAPI_SALESORDER*</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">So 2 releases later, ie 1 after the notification it may be rdifferent or indeed removed from support.</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">ie you get 2 release level guarantee. Current for any patches and Next for 1 upgrade.</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">The release level 2 ahead may or may not be ok.</font></span></div>
<div><span><font face="Arial" color="#0000ff" size="2"></font></span> </div>
<div><span><font face="Arial" color="#0000ff" size="2">cheers</font></span></div>
<div><span><font face="Arial" color="#0000ff" size="2">Phil.</font></span></div>
<div><span></span><font face="Arial" color="#0000ff" size="2"></font> </div>
<p><b><span lang="en-us"><font face="Arial" color="#000080" size="1">Phil Soady</font></span></b><span lang="en-us"></span> <br><span lang="en-us"><font face="Arial" color="#808080" size="1">Solution Architect</font></span>
<br><span lang="en-us"><font face="Arial" color="#808080" size="1">Netweaver Consulting</font></span> <br><span lang="en-us"><b><font face="Arial" color="#808080" size="1">SAP Australia </font></b></span><br><span lang="en-us">
<font face="Arial" color="#808080" size="1">M +61 412 213 079</font></span> <br><span lang="en-us"><font face="Arial" color="#808080" size="1">F +61 2 9957 7263 </font></span><br><span lang="en-us"><font face="Arial" color="#808080" size="1">
mailto:</font></span><a title="mailto:phil.soady@sap.com" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:phil.soady@sap.com" target="_blank"><span lang="en-us"><u><font face="Arial" color="#0000ff" size="1">
phil.soady@sap.com</font></u></span></a><span lang="en-us"></span> </p>
<div> </div><br>
<div lang="en-us" dir="ltr" align="left">
<hr>
<font face="Tahoma" size="2"><b>From:</b> <a title="mailto:sap-wug-bounces@mit.edu" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>
[mailto:<a title="mailto:sap-wug-bounces@mit.edu" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>] <b>On Behalf Of </b>Mark Pyc<br>
<b>Sent:</b> Friday, 21 July 2006 8:55 PM<br><b>To:</b> SAP Workflow Users' Group<br><b>Subject:</b> Re: SAP-WUG Digest, Vol 20, Issue 54<br></font><br> </div>
<div></div>
<div>Functions that are released for the customer are ones where SAP guarantees to keep the signature and functionality fixed in future releases and therefore you can use them safely. In the case of unreleased ones there is no such guarantee. The signature could change, the functionality could change or it could even be deleted. In any of these cases you'd have to deal with the consequences after upgrade.
</div>
<div> </div>
<div>Realistically though it's unlikely. If changes are made SAP also has to change all of their own dependant code. As such it's quite normal to make use of such functions if there is nothing else available, but there is a risk.
</div>
<div> </div>
<div>Have fun,</div>
<div>Mark<br><br> </div>
<div><span class="gmail_quote">On 7/21/06, <b class="gmail_sendername">Albina Fernando</b> <<a title="mailto:albinafernando@gmail.com" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:albinafernando@gmail.com" target="_blank">
albinafernando@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div> </div>
<div>Thanks for the update. I forgot to mention that we are ofcourse using Excluded Agents. But since the user A himself is a substitute, and he will not be able to view the approval task, Hence we are sending it to 2 managers before the deadline date.
i.e M1 and M2 and after the deadline date it still remains in M2's UWL list. Now the problem is when the deadline date is passed, the maanger M2 will see 2 instances of the same approval task. So to avoid that, we are using func. module SWW_WI_AGENTS_CHANGE, so that only one instance of the approval task remains in the UWL list of M2.
</div>
<div> </div>
<div>That'w why we had queries regarding SWW_WI_AGENTS_CHANGE. Also What does it mean when you say, "Some function modules are not released<br>for the customer".</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 7/21/06, <b class="gmail_sendername"><a title="mailto:sap-wug-request@mit.edu (mailto:sap-wug-request@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-request@mit.edu" target="_blank">
sap-wug-request@mit.edu</a></b> <<a title="mailto:sap-wug-request@mit.edu (mailto:sap-wug-request@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu
</a>> wrote: </span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Send SAP-WUG mailing list submissions to<br> <a title="mailto:sap-wug@mit.edu (mailto:sap-wug@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug@mit.edu" target="_blank">
sap-wug@mit.edu</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a title="http://mailman.mit.edu/mailman/listinfo/sap-wug (http://mailman.mit.edu/mailman/listinfo/sap-wug)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>or, via email, send a message with subject or body 'help' to <br> <a title="mailto:sap-wug-request@mit.edu (mailto:sap-wug-request@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-request@mit.edu" target="_blank">
sap-wug-request@mit.edu</a><br><br>You can reach the person managing the list at<br> <a title="mailto:sap-wug-owner@mit.edu (mailto:sap-wug-owner@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-owner@mit.edu" target="_blank">
sap-wug-owner@mit.edu</a><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. Re: Workflow using SWW_WI_AGENTS_CHANGE (Mark Pyc)
<br> 2. RE: Accept change button (Yogesh Chopra)<br> 3. RE: Accept change button (Adao-Cruz, Miguel) <br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 21 Jul 2006 08:26:14 +0100
<br>From: "Mark Pyc" <<a title="mailto:mark.pyc@gmail.com (mailto:mark.pyc@gmail.com)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:mark.pyc@gmail.com" target="_blank">mark.pyc@gmail.com
</a>><br>Subject: Re: Workflow using SWW_WI_AGENTS_CHANGE <br>To: "SAP Workflow Users' Group" <<a title="mailto:sap-wug@mit.edu (mailto:sap-wug@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug@mit.edu" target="_blank">
sap-wug@mit.edu</a>><br>Message-ID: <br> <<a title="mailto:23f0a78a0607210026t3fc058cfv3b6e0347d84fbd77@mail.gmail.com (mailto:23f0a78a0607210026t3fc058cfv3b6e0347d84fbd77@mail.gmail.com)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:23f0a78a0607210026t3fc058cfv3b6e0347d84fbd77@mail.gmail.com" target="_blank">
23f0a78a0607210026t3fc058cfv3b6e0347d84fbd77@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>G'day Albina,<br><br>That's sounds like a really complicated solution to a very standard
<br>situation!<br><br>If you're concern is about the A seeing their own approvals when operating<br>as substitute for the manager, use Excluded agents on the step. If you are<br>an excluded agent the system will never let you process the step.
<br><br>Have fun,<br>Mark<br><br><br>On 7/21/06, Albina Fernando <<a title="mailto:albinafernando@gmail.com (mailto:albinafernando@gmail.com)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:albinafernando@gmail.com" target="_blank">
albinafernando@gmail.com</a>> wrote:<br>><br>> Hi,<br>><br>> What does it mean when you say, "Some function modules are not released <br>> for the customer". In our case, we are using the function module
<br>> SWW_WI_AGENTS_CHANGE. Will it cause any problem.<br>> We have a scenario wherein, there is an employee A and 2 managers M1, & <br>> M2. The approval task goes to 2 managers. Before the deadline date, it is
<br>> with one manager i.e M1 and after the deadline date, it is with the other<br>> manager i.e M2. Whenever the 1st manager , M1 creates the user A as a <br>> substitute, then A will also be able to view the approval task. So this
<br>> should not happem. So what we are doing is, before the deadline date, we are<br>> sending it to the 1st and 2nd manager. And after the deadline date, it <br>> remains with the 2nd manager. In such a case, the 2 manager will see 2
<br>> instances of the same approval task. So to avoid that, we are using function<br>> module SWW_WI_AGENTS_CHANGE. This is used so that whenever a deadline is <br>> reached, it will call this module and remove the agent from the approval
<br>> task, which is before the deadline date. By doing this, there will be only<br>> one instance of the approval task with the 2nd manager. <br>><br>> Thanks<br>><br>><br>> _______________________________________________
<br>> SAP-WUG mailing list<br>> <a title="mailto:SAP-WUG@mit.edu (mailto:SAP-WUG@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
> <a title="http://mailman.mit.edu/mailman/listinfo/sap-wug (http://mailman.mit.edu/mailman/listinfo/sap-wug)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>><br>><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a title="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/980b517b/attachment-0001.htm (http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/980b517b/attachment-0001.htm)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/980b517b/attachment-0001.htm" target="_blank">
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/980b517b/attachment-0001.htm</a><br><br>------------------------------<br><br>Message: 2<br>Date: Fri, 21 Jul 2006 17:08:02 +0800<br>From: "Yogesh Chopra" <
<a title="mailto:Yogesh.Chopra@axonglobal.com (mailto:Yogesh.Chopra@axonglobal.com)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Yogesh.Chopra@axonglobal.com" target="_blank">Yogesh.Chopra@axonglobal.com
</a>><br>Subject: RE: Accept change button <br>To: "SAP Workflow Users' Group" <<a title="mailto:sap-wug@mit.edu (mailto:sap-wug@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug@mit.edu" target="_blank">
sap-wug@mit.edu</a> >, "SAP Workflow <br> Users' Group" <<a title="mailto:sap-wug@mit.edu (mailto:sap-wug@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug@mit.edu" target="_blank">
sap-wug@mit.edu</a>><br>Message-ID:<br> < <a title="mailto:5D9A6409FE6AB043998D62E01544EFF6130638@myisms01.axongroup.co.uk (mailto:5D9A6409FE6AB043998D62E01544EFF6130638@myisms01.axongroup.co.uk)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:5D9A6409FE6AB043998D62E01544EFF6130638@myisms01.axongroup.co.uk" target="_blank">
5D9A6409FE6AB043998D62E01544EFF6130638@myisms01.axongroup.co.uk</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Hello! Miguel<br><br>Thanks for your reply. In my SC there is no start condition because it is N-step header level SC. Approvers are all on-line approvers. I am BADI. I am selecting all approvers. Only few approvers are able to change the SC. This is controlled by security level. At present the approvers who can change the SC have LOW level security. When approver makes a change in Price or quantity or currency then e-mail is going back to requestor with a ACCEPT CHANGE button but when there is a change in any other field then e-mail is going back to requestor but without ACCEPT CHANGE button.
<br><br><br><br>My issue is :- mails should go back with accept change button in any case and when requestor accept changes then workflow should restart again.<br><br><br><br>Thanks<br>Yog<br><br>________________________________
<br><br>From: <a title="mailto:sap-wug-bounces@mit.edu (mailto:sap-wug-bounces@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu
</a> on behalf of Adao-Cruz, Miguel <br>Sent: Fri 21/07/2006 00:19<br>To: SAP Workflow Users' Group<br>Subject: RE: Accept change button<br><br><br>Hi,<br><br>For certain POs approval workflows, SRM does distinction between the type of changes done via the start conditions ( see attributes in BUS2201
PurchaseOrderEC.SimpleListOfChanges PurchaseOrderEC.TechnicalListOfChanges ) but I have never seen something like that for shopping carts.<br>You are talking about e-mails, I guess you mean the off-line approval. Did you check if online (EBP inbox) the workitems are the same?
<br>On which support pack are you? In the last SP (8-9 and 10) there are some OSS notes for off-line approval. <br>In your two cases, is it the same approver changing the shopping cart? If not, do they have the same security level in their role or SU01.
<br><br>Cheers<br><br>___________________________________________________________________________ <br>Miguel Adao-Cruz | Capgemini | London<br>Technology Services<br>SAP Application Architect<br><br>T.+44-870-238-2927 | Int.700
2927 | <a title="http://www.capgemini.com (http://www.capgemini.com/)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.capgemini.com/" target="_blank">www.capgemini.com</a> <<a title="file:///C:/Documents%20and%20Settings/madaocru/Application%20Data/Microsoft/Signatures/www.capgemini.com">
file:///C:/Documents%20and%20Settings/madaocru/Application%20Data/Microsoft/Signatures/www.capgemini.com</a>><br><br>Join the Collaborative Business Experience<br>___________________________________________________________________________
<br><br>________________________________<br><br>From: <a title="mailto:sap-wug-bounces@mit.edu (mailto:sap-wug-bounces@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">
sap-wug-bounces@mit.edu </a>on behalf of Yogesh Chopra<br>Sent: Thu 20/07/2006 16:49<br>To: SAP Workflow Users' Group; SAP Workflow Users' Group <br>Subject: RE: Accept change button<br><br><br>Thanks for the reply Mark.<br>
<br>Requestor is getting a mail but as i mentioned in my mail , Accept change button disappear in the e-mail notification when approver make changes in Item category . If approver make changes on price then that button appears.
<br><br>I don't know why it is working for some fields only.<br><br>Thanks<br>Yogesh<br><br>________________________________<br><br>From: <a title="mailto:sap-wug-bounces@mit.edu (mailto:sap-wug-bounces@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">
sap-wug-bounces@mit.edu</a> on behalf of Mark Pyc <br>Sent: Thu 20/07/2006 23:16<br>To: SAP Workflow Users' Group<br>Subject: Re: Accept change button<br><br><br>G'day Yogesh,<br><br>I don't claim to know much about SRM (hence all my questions) but are you saying the requestor is still getting a Workitem for review of changes but that the button is missing? Or is it that they don't receive the workitem at all??
<br><br>If its that they don't receive the workitem at all, then have a look at discussion over the last few days between myself and Miguel. There is a badi that may be useful to you.<br><br>Have fun,<br>Mark<br><br><br>On 7/20/06, Yogesh Chopra <
<a title="mailto:Yogesh.Chopra@axonglobal.com (mailto:Yogesh.Chopra@axonglobal.com)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Yogesh.Chopra@axonglobal.com" target="_blank">Yogesh.Chopra@axonglobal.com
</a>> wrote:<br><br><br> Hi! Workflow Experts <br><br><br><br> I am using header level N-step workflow and there is not start condition. When requestor creates a shopping cart and if approver makes a change in price field then requester receives a message to accept changes or reject changes but when approver makes a change product category then accept change button disappear. Can any one please give me clue why it is working for some fields and why not for other fields?
<br><br><br><br> Thanks<br><br> Yogesh<br><br><br><br><br><br><br><br>The content of this email is confidential and for the<br>addressee only. If you are not the addressee of this<br>email (or responsible for the delivery of this message
<br>to such person) you may not copy, forward, disclose<br>or otherwise use it or any part of it in any form<br>whatsoever. If you have received this email in error<br>please email the sender by replying to this message<br>
and delete this message thereafter.<br><br>Opinions, conclusions and other information in this<br>message that do not relate to the official business<br>of our Company shall be understood as neither<br>given nor endorsed by it.
<br><br><br><br> _______________________________________________<br> SAP-WUG mailing list<br> <a title="mailto:SAP-WUG@mit.edu (mailto:SAP-WUG@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target="_blank">
SAP-WUG@mit.edu</a><br> <a title="http://mailman.mit.edu/mailman/listinfo/sap-wug (http://mailman.mit.edu/mailman/listinfo/sap-wug)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug </a><br><br><br><br><br><br><br><br><br><br><br><br>The content of this email is confidential and for the<br>addressee only. If you are not the addressee of this<br>email (or responsible for the delivery of this message
<br>to such person) you may not copy, forward, disclose<br>or otherwise use it or any part of it in any form<br>whatsoever. If you have received this email in error<br>please email the sender by replying to this message<br>
and delete this message thereafter. <br><br>Opinions, conclusions and other information in this<br>message that do not relate to the official business<br>of our Company shall be understood as neither<br>given nor endorsed by it.
<br><br><br><br><br><br>The content of this email is confidential and for the <br>addressee only. If you are not the addressee of this<br>email (or responsible for the delivery of this message<br>to such person) you may not copy, forward, disclose
<br>or otherwise use it or any part of it in any form <br>whatsoever. If you have received this email in error<br>please email the sender by replying to this message<br>and delete this message thereafter.<br><br>Opinions, conclusions and other information in this
<br>message that do not relate to the official business <br>of our Company shall be understood as neither<br>given nor endorsed by it.<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>
URL: <a title="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/92925240/attachment-0001.htm (http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/92925240/attachment-0001.htm)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/92925240/attachment-0001.htm" target="_blank">
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/92925240/attachment-0001.htm</a><br><br>------------------------------ <br><br>Message: 3<br>Date: Fri, 21 Jul 2006 10:19:28 +0100<br>From: "Adao-Cruz, Miguel" <
<a title="mailto:miguel.adao-cruz@capgemini.com (mailto:miguel.adao-cruz@capgemini.com)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:miguel.adao-cruz@capgemini.com" target="_blank">miguel.adao-cruz@capgemini.com
</a>><br>Subject: RE: Accept change button <br>To: "SAP Workflow Users' Group" <<a title="mailto:sap-wug@mit.edu (mailto:sap-wug@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug@mit.edu" target="_blank">
sap-wug@mit.edu</a>><br>Message-ID: <br> <<a title="mailto:77898EE30049594BBC2E2AB2A9A54B2F016B83D2@MISSBHXVS01.uki.capgemini.com (mailto:77898EE30049594BBC2E2AB2A9A54B2F016B83D2@MISSBHXVS01.uki.capgemini.com)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:77898EE30049594BBC2E2AB2A9A54B2F016B83D2@MISSBHXVS01.uki.capgemini.com" target="_blank">
77898EE30049594BBC2E2AB2A9A54B2F016B83D2@MISSBHXVS01.uki.capgemini.com</a>><br><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Hi,<br><br>I understood your problem. But if you wantus to help you, you have to do a
<br>couple of checks.<br><br>"<br>You are talking about e-mails, I guess you mean the off-line approval. Did<br>you check if online (EBP inbox) the workitems are the same?<br>On which support pack are you? In the last SP (8-9 and 10) there are some
<br>OSS notes for off-line approval.<br>In your two cases, is it the same approver changing the shopping cart? If<br>not, do they have the same security level in their role or SU01.<br>"<br>When you change the price, and then when you change the category, are you
<br>doing it with the same requestor and approver.<br><br>Cheers<br><br><br><br>___________________________________________________________________________<br>Miguel Adao-Cruz | Capgemini | London<br>Technology Services<br>
SAP Application Architect<br><br>T.+44-870-238-2927 | Int.700 2927 | <a title="http://www.capgemini.com (http://www.capgemini.com/)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.capgemini.com/" target="_blank">
www.capgemini.com </a><br><<a title="file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft">file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft </a><br>\Signatures\www.capgemini.com>
<br><br>Join the Collaborative Business Experience<br>___________________________________________________________________________<br><br>________________________________<br><br>From: <a title="mailto:sap-wug-bounces@mit.edu (mailto:sap-wug-bounces@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">
sap-wug-bounces@mit.edu</a> on behalf of Yogesh Chopra<br>Sent: Fri 21/07/2006 10:08<br>To: SAP Workflow Users' Group; SAP Workflow Users' Group<br>Subject: RE: Accept change button <br><br><br>Hello! Miguel<br><br>Thanks for your reply. In my SC there is no start condition because it is
<br>N-step header level SC. Approvers are all on-line approvers. I am BADI. I am<br>selecting all approvers. Only few approvers are able to change the SC. This <br>is controlled by security level. At present the approvers who can change the
<br>SC have LOW level security. When approver makes a change in Price or<br>quantity or currency then e-mail is going back to requestor with a ACCEPT <br>CHANGE button but when there is a change in any other field then e-mail is
<br>going back to requestor but without ACCEPT CHANGE button.<br><br><br><br>My issue is :- mails should go back with accept change button in any case <br>and when requestor accept changes then workflow should restart again.
<br><br><br><br>Thanks<br>Yog<br><br>________________________________<br><br>From: <a title="mailto:sap-wug-bounces@mit.edu (mailto:sap-wug-bounces@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">
sap-wug-bounces@mit.edu</a> on behalf of Adao-Cruz, Miguel<br>Sent: Fri 21/07/2006 00:19<br>To: SAP Workflow Users' Group<br>Subject: RE: Accept change button<br><br><br>Hi,<br><br>For certain POs approval workflows, SRM does distinction between the type of
<br>changes done via the start conditions ( see attributes in BUS2201<br>PurchaseOrderEC.SimpleListOfChanges PurchaseOrderEC.TechnicalListOfChanges)<br>but I have never seen something like that for shopping carts.<br>You are talking about e-mails, I guess you mean the off-line approval. Did
<br>you check if online (EBP inbox) the workitems are the same?<br>On which support pack are you? In the last SP (8-9 and 10) there are some<br>OSS notes for off-line approval.<br>In your two cases, is it the same approver changing the shopping cart? If
<br>not, do they have the same security level in their role or SU01.<br><br>Cheers<br><br>___________________________________________________________________________<br>Miguel Adao-Cruz | Capgemini | London<br>Technology Services
<br>SAP Application Architect<br><br>T.+44-870-238-2927 | Int.700 2927 | <a title="http://www.capgemini.com (http://www.capgemini.com/)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.capgemini.com/" target="_blank">
www.capgemini.com </a><br><<a title="file:///C:/Documents%20and%20Settings/madaocru/Application%20Data/Microsoft"> file:///C:/Documents%20and%20Settings/madaocru/Application%20Data/Microsoft</a><br>/Signatures/,DanaInfo=owa+www.capgemini.com>
<br><br>Join the Collaborative Business Experience<br>___________________________________________________________________________ <br><br>________________________________<br><br>From: <a title="mailto:sap-wug-bounces@mit.edu (mailto:sap-wug-bounces@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">
sap-wug-bounces@mit.edu</a> on behalf of Yogesh Chopra<br>Sent: Thu 20/07/2006 16:49<br>To: SAP Workflow Users' Group; SAP Workflow Users' Group <br>Subject: RE: Accept change button<br><br><br>Thanks for the reply Mark.<br>
<br>Requestor is getting a mail but as i mentioned in my mail , Accept change<br>button disappear in the e-mail notification when approver make changes in <br>Item category . If approver make changes on price then that button appears.
<br><br>I don't know why it is working for some fields only.<br><br>Thanks<br>Yogesh<br><br>________________________________<br><br>From: <a title="mailto:sap-wug-bounces@mit.edu (mailto:sap-wug-bounces@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">
sap-wug-bounces@mit.edu</a> on behalf of Mark Pyc<br>Sent: Thu 20/07/2006 23:16<br>To: SAP Workflow Users' Group<br>Subject: Re: Accept change button<br><br><br>G'day Yogesh,<br><br>I don't claim to know much about SRM (hence all my questions) but are you
<br>saying the requestor is still getting a Workitem for review of changes but<br>that the button is missing? Or is it that they don't receive the workitem at<br>all??<br><br>If its that they don't receive the workitem at all, then have a look at
<br>discussion over the last few days between myself and Miguel. There is a badi<br>that may be useful to you.<br><br>Have fun,<br>Mark<br><br><br>On 7/20/06, Yogesh Chopra <<a title="mailto:Yogesh.Chopra@axonglobal.com (mailto:Yogesh.Chopra@axonglobal.com)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Yogesh.Chopra@axonglobal.com" target="_blank">
Yogesh.Chopra@axonglobal.com</a>> wrote:<br><br><br> Hi! Workflow Experts<br><br><br><br> I am using header level N-step workflow and there is not start<br>condition. When requestor creates a shopping cart and if approver makes a
<br>change in price field then requester receives a message to accept changes or<br>reject changes but when approver makes a change product category then accept<br>change button disappear. Can any one please give me clue why it is working
<br>for some fields and why not for other fields?<br><br><br><br> Thanks<br><br> Yogesh<br><br><br><br><br><br><br><br>The content of this email is confidential and for the<br>addressee only. If you are not the addressee of this
<br>email (or responsible for the delivery of this message<br>to such person) you may not copy, forward, disclose<br>or otherwise use it or any part of it in any form<br>whatsoever. If you have received this email in error
<br>please email the sender by replying to this message<br>and delete this message thereafter.<br><br>Opinions, conclusions and other information in this<br>message that do not relate to the official business<br>of our Company shall be understood as neither
<br>given nor endorsed by it.<br><br><br><br> _______________________________________________<br> SAP-WUG mailing list<br> <a title="mailto:SAP-WUG@mit.edu (mailto:SAP-WUG@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target="_blank">
SAP-WUG@mit.edu</a><br> <a title="http://mailman.mit.edu/mailman/listinfo/sap-wug (http://mailman.mit.edu/mailman/listinfo/sap-wug)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug </a><br><br><br><br><br><br><br><br><br><br><br><br>The content of this email is confidential and for the<br>addressee only. If you are not the addressee of this<br>email (or responsible for the delivery of this message
<br>to such person) you may not copy, forward, disclose<br>or otherwise use it or any part of it in any form<br>whatsoever. If you have received this email in error<br>please email the sender by replying to this message<br>
and delete this message thereafter. <br><br>Opinions, conclusions and other information in this<br>message that do not relate to the official business<br>of our Company shall be understood as neither<br>given nor endorsed by it.
<br><br><br><br><br><br><br><br><br>The content of this email is confidential and for the<br>addressee only. If you are not the addressee of this<br>email (or responsible for the delivery of this message<br>to such person) you may not copy, forward, disclose
<br>or otherwise use it or any part of it in any form<br>whatsoever. If you have received this email in error<br>please email the sender by replying to this message<br>and delete this message thereafter.<br><br>Opinions, conclusions and other information in this
<br>message that do not relate to the official business<br>of our Company shall be understood as neither<br>given nor endorsed by it.<br><br><br>-------------- next part --------------<br>A non-text attachment was scrubbed...
<br>Name: not available<br>Type: application/ms-tnef<br>Size: 16009 bytes<br>Desc: not available<br>Url : <a title="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/d27d6948/attachment.bin (http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/d27d6948/attachment.bin)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/d27d6948/attachment.bin" target="_blank">
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/d27d6948/attachment.bin </a><br>-------------- next part --------------<br>This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
<br><br>------------------------------<br><br>_______________________________________________<br>SAP-WUG mailing list<br><a title="mailto:SAP-WUG@mit.edu (mailto:SAP-WUG@mit.edu)" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target="_blank">
SAP-WUG@mit.edu</a><br><a title="http://mailman.mit.edu/mailman/listinfo/sap-wug (http://mailman.mit.edu/mailman/listinfo/sap-wug)" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug </a><br><br><br>End of SAP-WUG Digest, Vol 20, Issue 54<br>***************************************<br></blockquote></div><br> </div><br>_______________________________________________
<br>SAP-WUG mailing list<br><a title="mailto:SAP-WUG@mit.edu" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br><a title="http://mailman.mit.edu/mailman/listinfo/sap-wug" onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br><br></blockquote></div><br> </div></div>