<div>Hello Mark,</div>
<div> </div>
<div> Thanks once again for the quick reply. Is there any way to find out which function module, etc is released for the customer. Any option as such..</div>
<div> </div>
<div>Thanks</div>
<div>Albina</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 7/21/06, <b class="gmail_sendername"><a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a></b> <<a href="mailto:sap-wug-request@mit.edu">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 href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
<br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>or, via email, send a message with subject or body 'help' to
<br> <a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br><br>You can reach the person managing the list at<br> <a href="mailto:sap-wug-owner@mit.edu">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: Re : Material Master Workflow (Kisloff, Philip B)<br> 2. Re: SAP-WUG Digest, Vol 20, Issue 54 (Mark Pyc)<br><br><br>----------------------------------------------------------------------
<br><br>Message: 1<br>Date: Fri, 21 Jul 2006 11:44:25 +0100<br>From: "Kisloff, Philip B" <<a href="mailto:Philip.Kisloff@astrazeneca.com">Philip.Kisloff@astrazeneca.com</a>><br>Subject: RE: Re : Material Master Workflow
<br>To: "'SAP Workflow Users' Group'" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID:<br> <<a href="mailto:77B8D39FB855D511B6FE0002A55C0CE6051415F5@ukcfphmsx01.ukcf.astrazeneca.net">
77B8D39FB855D511B6FE0002A55C0CE6051415F5@ukcfphmsx01.ukcf.astrazeneca.net</a>><br><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Hi Vijay,<br><br>The problem with creation of one material master view completing all other
<br>parallel workitems view can be solved by creating a "view-specific" check<br>function to the terminating event binding. Hope the example code helps (its<br>from four years ago, so I'm a bit rusty on the details)
<br><br>Phil<br><br>FUNCTION z_multi_view_maintenance.<br>*"----------------------------------------------------------------------<br>*"*"Local interface:<br>*" IMPORTING<br>*" VALUE(EVENT) LIKE SWETYPECOU-EVENT
<br>*" VALUE(RECTYPE) LIKE SWETYPECOU-RECTYPE<br>*" VALUE(OBJTYPE) LIKE SWETYPECOU-OBJTYPE<br>*" VALUE(OBJKEY) LIKE SWEINSTCOU-OBJKEY<br>*" VALUE(EXCEPTIONS_ALLOWED) LIKE SWEFLAGS-EXC_OK DEFAULT 'X'
<br>*" EXPORTING<br>*" VALUE(REC_ID) LIKE SWELOG-RECID<br>*" TABLES<br>*" EVENT_CONTAINER STRUCTURE SWCONT<br>*" EXCEPTIONS<br>*" INVALID_MATCH<br>*"----------------------------------------------------------------------
<br>INCLUDE <cntain>.<br>DATA: old_wi_id LIKE swwwihead-wi_id.<br>DATA: local_wi_header LIKE swwwihead.<br><br>* search work item from receiver<br>swc_get_element event_container evt_receiver_id old_wi_id.<br>local_wi_header-wi_id = old_wi_id.
<br><br>* read workitem container<br>CLEAR wi_container. REFRESH wi_container.<br>CALL FUNCTION 'SWW_WI_CONTAINER_READ'<br> EXPORTING<br> wi_id = local_wi_header-wi_id<br> TABLES<br>
wi_container = wi_container<br> EXCEPTIONS<br> container_does_not_exist = 01.<br><br>READ TABLE wi_container WITH KEY element = 'VIEW'.<br><br>CASE wi_container-value.<br> WHEN 'V'. " Sales
<br> READ TABLE wi_container WITH KEY element = 'PLANT'.<br> READ TABLE event_container WITH KEY element = 'PLANT'.<br> IF wi_container-value(4) <> event_container-value(4).<br> RAISE invalid_match.
<br> ENDIF.<br> when 'L'.<br> READ TABLE wi_container WITH KEY element = 'STORAGELOCATION'.<br> READ TABLE event_container WITH KEY element = 'STORAGELOCATION'.<br>************************<br> tables indx.
<br> export wi_container-value event_container-value<br> to database indx(wf) id 'test1'.<br>************************<br> IF wi_container-value+5(4) <> event_container-value(4).<br> RAISE invalid_match.
<br> ENDIF.<br> READ TABLE event_container WITH KEY element = 'PLANT'.<br> IF wi_container-value+1(4) <> event_container-value(4).<br> RAISE invalid_match.<br> ENDIF.<br> WHEN 'S'. " Warehouse
<br> READ TABLE wi_container WITH KEY element = 'WAREHOUSE'.<br> READ TABLE event_container WITH KEY element = 'WHSENUMBER'.<br> IF wi_container-value+9(3) <> event_container-value(3).<br> RAISE invalid_match.
<br> ENDIF.<br> WHEN 'D'. " MRP<br> READ TABLE wi_container WITH KEY element = 'PLANT'.<br> READ TABLE event_container WITH KEY element = 'PLANT'.<br> IF wi_container-value(4) <> event_container-value(4).
<br> RAISE invalid_match.<br> ENDIF.<br> WHEN 'E'. " Purchasing<br> READ TABLE wi_container WITH KEY element = 'PLANT'.<br> READ TABLE event_container WITH KEY element = 'PLANT'.<br> IF wi_container-value(4) <> event_container-value(4).
<br> RAISE invalid_match.<br> ENDIF.<br> WHEN 'B'. " Accounting<br> READ TABLE wi_container WITH KEY element = 'PLANT'.<br> READ TABLE event_container WITH KEY element = 'VALUATIONAREA'.<br>************************
<br> export wi_container-value event_container-value<br> to database indx(wf) id 'test3'.<br>************************<br> IF wi_container-value(4) <> event_container-value(4).<br> RAISE invalid_match.<br>
ENDIF.<br> WHEN OTHERS.<br>ENDCASE.<br><br>ENDFUNCTION.<br><br>-----Original Message-----<br>From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">
sap-wug-bounces@mit.edu</a>]On Behalf Of K<br>Vijayasekar<br>Sent: 21 July 2006 05:04<br>To: SAP WF User group<br>Subject: Re : Material Master Workflow<br><br><br>Hi Friends ,<br> Presently i'm given a task of creating workflow for
<br>material master creation. Following is the scenario...<br><br>1. One user ( Initiator ) will create a basic data 1 & 2 and the workflow<br>should be triggered .<br><br>2. Other views like Sales , MRP , Scheduling will be created by different
<br>people , hence each user should receive a workitem in their sap inbox for<br>creating the required view.<br><br>I have identified business object BUS1001006 for this workflow and i'm<br>planning to use the following methods and events.
<br><br>Events :<br> Created --> to trigger the workflow<br> ViewCreated --> terminating event for the Workitem ( for view<br>creation )<br><br>Methods :<br><br> GetMissedViews --> to get all the required views to be created for this
<br>material.<br> CreateView --> to create required for the material.<br><br><br>I'm facing two problems......<br><br>1. Using "GetMissedViews" i'm getting all the missing view details in a<br>multiline container element . I have created parallel task ( by putting
<br>multiline container element in the "Others" tab . Terminating event for this<br>task is "ViewCreated".<br>Depending on the no. of views in the multiline item , that many workitem<br>gets created.<br>
The issue is if once view gets created all the other workitems are removed<br>from my inbox ( status completed ).<br><br>2. At the time of creation of basic data1 & 2 , the org. elements are not<br>required . I want to determine the agent for rest of the views by the
<br>org.elements . How can we acheive it ???<br><br>Help me to reslove above 2 issues ......If any done workflow material master<br>please do share you technical expetise...<br><br>Regards,<br>Vijay<br><br><br><br><br><br>
<br><br><br><br><br><br><br>_____<br><br>Yahoo! Messenger with Voice. Make<br><<a href="http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/ev">http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/ev
</a><br>t=39663/*<a href="http://voice.yahoo.com">http://voice.yahoo.com</a>> PC-to-Phone Calls to the US (and 30+<br>countries) for 2?/min or less.<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...
<br>URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/18133ff1/attachment-0001.htm">http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/18133ff1/attachment-0001.htm</a><br><br>------------------------------
<br><br>Message: 2<br>Date: Fri, 21 Jul 2006 11:55:12 +0100<br>From: "Mark Pyc" <<a href="mailto:mark.pyc@gmail.com">mark.pyc@gmail.com</a>><br>Subject: Re: SAP-WUG Digest, Vol 20, Issue 54<br>To: "SAP Workflow Users' Group" <
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Message-ID:<br> <<a href="mailto:23f0a78a0607210355w277681f4jdd06890950cf0aa4@mail.gmail.com">23f0a78a0607210355w277681f4jdd06890950cf0aa4@mail.gmail.com
</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Functions that are released for the customer are ones where SAP guarantees<br>to keep the signature and functionality fixed in future releases and
<br>therefore you can use them safely. In the case of unreleased ones there is<br>no such guarantee. The signature could change, the functionality could<br>change or it could even be deleted. In any of these cases you'd have to deal
<br>with the consequences after upgrade.<br><br>Realistically though it's unlikely. If changes are made SAP also has to<br>change all of their own dependant code. As such it's quite normal to make<br>use of such functions if there is nothing else available, but there is a
<br>risk.<br><br>Have fun,<br>Mark<br><br><br>On 7/21/06, Albina Fernando <<a href="mailto:albinafernando@gmail.com">albinafernando@gmail.com</a>> wrote:<br>><br>><br>> Thanks for the update. I forgot to mention that we are ofcourse using
<br>> Excluded Agents. But since the user A himself is a substitute, and he will<br>> not be able to view the approval task, Hence we are sending it to 2 managers<br>> before the deadline date. i.e M1 and M2 and after the deadline date it
<br>> still remains in M2's UWL list. Now the problem is when the deadline date is<br>> passed, the maanger M2 will see 2 instances of the same approval task. So to<br>> avoid that, we are using func. module SWW_WI_AGENTS_CHANGE, so that only one
<br>> instance of the approval task remains in the UWL list of M2.<br>><br>> That'w why we had queries regarding SWW_WI_AGENTS_CHANGE. Also What does<br>> it mean when you say, "Some function modules are not released
<br>> for the customer".<br>><br>><br>><br>> On 7/21/06, <a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a> <<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>> wrote:
<br>> ><br>> > Send SAP-WUG mailing list submissions to<br>> > <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>> ><br>> > To subscribe or unsubscribe via the World Wide Web, visit
<br>> > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>> > or, via email, send a message with subject or body 'help' to<br>> >
<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>> ><br>> > You can reach the person managing the list at<br>> > <a href="mailto:sap-wug-owner@mit.edu">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 href="mailto:mark.pyc@gmail.com">
mark.pyc@gmail.com</a> ><br>> > Subject: Re: Workflow using SWW_WI_AGENTS_CHANGE<br>> > To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>> > Message-ID:
<br>> > < <a href="mailto:23f0a78a0607210026t3fc058cfv3b6e0347d84fbd77@mail.gmail.com">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
<br>> > operating<br>> > as substitute for the manager, use Excluded agents on the step. If you<br>> > 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 href="mailto:albinafernando@gmail.com">albinafernando@gmail.com</a>> wrote:<br>> > ><br>> > > Hi,<br>> > >
<br>> > > What does it mean when you say, "Some function modules are not<br>> > 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<br>> > M1, &<br>> > > M2. The approval task goes to 2 managers. Before the deadline date, it<br>> > is<br>> > > with one manager
i.e M1 and after the deadline date, it is with the<br>> > 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
<br>> > this<br>> > > should not happem. So what we are doing is, before the deadline date,<br>> > we are<br>> > > sending it to the 1st and 2nd manager. And after the deadline date, it<br>> >
<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<br>> > function<br>> > > module SWW_WI_AGENTS_CHANGE. This is used so that whenever a deadline
<br>> > is<br>> > > reached, it will call this module and remove the agent from the<br>> > approval<br>> > > task, which is before the deadline date. By doing this, there will be<br>> > 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 href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> > > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug
</a><br>> > ><br>> > ><br>> > ><br>> > -------------- next part --------------<br>> > An HTML attachment was scrubbed...<br>> > URL:<br>> > <a href="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</a><br>> ><br>> > ------------------------------<br>> ><br>> > Message: 2<br>> > Date: Fri, 21 Jul 2006 17:08:02 +0800
<br>> > From: "Yogesh Chopra" < <a href="mailto:Yogesh.Chopra@axonglobal.com">Yogesh.Chopra@axonglobal.com</a>><br>> > Subject: RE: Accept change button<br>> > To: "SAP Workflow Users' Group" <
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a> >, "SAP Workflow<br>> > Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>> > Message-ID:<br>> > <
<a href="mailto:5D9A6409FE6AB043998D62E01544EFF6130638@myisms01.axongroup.co.uk">5D9A6409FE6AB043998D62E01544EFF6130638@myisms01.axongroup.co.uk</a><br>> > ><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<br>> > is N-step header level SC. Approvers are all on-line approvers. I am BADI. I
<br>> > am selecting all approvers. Only few approvers are able to change the SC.<br>> > This is controlled by security level. At present the approvers who can<br>> > change the SC have LOW level security. When approver makes a change in Price
<br>> > or 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<br>> > case and when requestor accept changes then workflow should restart again.<br>> >
<br>> ><br>> ><br>> > Thanks<br>> > Yog<br>> ><br>> > ________________________________<br>> ><br>> > From: <a href="mailto:sap-wug-bounces@mit.edu">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<br>> > type of changes done via the start conditions ( see attributes in BUS2201<br>> > PurchaseOrderEC.SimpleListOfChanges<br>> >
PurchaseOrderEC.TechnicalListOfChanges ) but I have never seen something<br>> > like that for shopping carts.<br>> > You are talking about e-mails, I guess you mean the off-line approval.<br>> > 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<br>> > some OSS notes for off-line approval.<br>> > In your two cases, is it the same approver changing the shopping cart?<br>
> > If not, do they have the same security level in their role or SU01.<br>> ><br>> > Cheers<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 href="http://www.capgemini.com">
www.capgemini.com</a> <<a href="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>> ><br>> > Join the Collaborative Business Experience<br>> > ___________________________________________________________________________<br>> ><br>> ><br>> > ________________________________
<br>> ><br>> > From: <a href="mailto:sap-wug-bounces@mit.edu">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<br>> > change button disappear in the e-mail notification when approver make
<br>> > changes in Item category . If approver make changes on price then that<br>> > 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 href="mailto:sap-wug-bounces@mit.edu">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
<br>> > you saying the requestor is still getting a Workitem for review of changes<br>> > but that the button is missing? Or is it that they don't receive the<br>> > workitem at 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 href="mailto:Yogesh.Chopra@axonglobal.com">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 href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">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:<br>> > <a href="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
</a><br>> ><br>> > ------------------------------<br>> ><br>> > Message: 3<br>> > Date: Fri, 21 Jul 2006 10:19:28 +0100<br>> > From: "Adao-Cruz, Miguel" <<a href="mailto:miguel.adao-cruz@capgemini.com">
miguel.adao-cruz@capgemini.com</a>><br>> > Subject: RE: Accept change button<br>> > To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>> > Message-ID:
<br>> > <<a href="mailto:77898EE30049594BBC2E2AB2A9A54B2F016B83D2@MISSBHXVS01.uki.capgemini.com">77898EE30049594BBC2E2AB2A9A54B2F016B83D2@MISSBHXVS01.uki.capgemini.com</a><br>> > ><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<br>> > a<br>> > couple of checks.
<br>> ><br>> > "<br>> > You are talking about e-mails, I guess you mean the off-line approval.<br>> > 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
<br>> > some<br>> > OSS notes for off-line approval.<br>> > In your two cases, is it the same approver changing the shopping cart?<br>> > 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<br>> > you<br>> > doing it with the same requestor and approver.<br>> ><br>> > Cheers<br>> >
<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 href="http://www.capgemini.com">www.capgemini.com</a><br>> > <<a href="file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft">
file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft</a><br>> ><br>> > \Signatures\www.capgemini.com><br>> ><br>> > Join the Collaborative Business Experience<br>> >
<br>> > ___________________________________________________________________________<br>> ><br>> > ________________________________<br>> ><br>> > From: <a href="mailto:sap-wug-bounces@mit.edu">
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<br>> > is<br>> > N-step header level SC. Approvers are all on-line approvers. I am BADI.
<br>> > I am<br>> > selecting all approvers. Only few approvers are able to change the SC.<br>> > This<br>> > is controlled by security level. At present the approvers who can change<br>> > 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<br>> > ACCEPT<br>> > CHANGE button but when there is a change in any other field then e-mail
<br>> > 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<br>> > 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 href="mailto:sap-wug-bounces@mit.edu">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<br>> > type of<br>> > changes done via the start conditions ( see attributes in BUS2201
<br>> > PurchaseOrderEC.SimpleListOfChanges<br>> > 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.
<br>> > 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<br>> > some<br>> > OSS notes for off-line approval.
<br>> > In your two cases, is it the same approver changing the shopping cart?<br>> > If<br>> > not, do they have the same security level in their role or SU01.<br>> ><br>> > Cheers<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 href="http://www.capgemini.com">www.capgemini.com</a><br>> > <<a href="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>> ><br>> > From: <a href="mailto:sap-wug-bounces@mit.edu">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
<br>> > change<br>> > button disappear in the e-mail notification when approver make changes<br>> > in<br>> > Item category . If approver make changes on price then that button<br>> > 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 href="mailto:sap-wug-bounces@mit.edu">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<br>> > you<br>> > saying the requestor is still getting a Workitem for review of changes
<br>> > but<br>> > that the button is missing? Or is it that they don't receive the<br>> > 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<br>> > badi<br>> > that may be useful to you.<br>> ><br>> > Have fun,<br>> > Mark<br>> ><br>> >
<br>> > On 7/20/06, Yogesh Chopra < <a href="mailto:Yogesh.Chopra@axonglobal.com">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<br>> > a<br>> > change in price field then requester receives a message to accept
<br>> > changes or<br>> > reject changes but when approver makes a change product category then<br>> > accept<br>> > change button disappear. Can any one please give me clue why it is<br>> > 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 href="mailto:SAP-WUG@mit.edu">
SAP-WUG@mit.edu</a><br>> > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">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 href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/d27d6948/attachment.bin">
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/d27d6948/attachment.bin</a><br>> ><br>> > -------------- next part --------------<br>> > This message contains information that may be privileged or confidential
<br>> > and is the property of the Capgemini Group. It is intended only for the<br>> > person to whom it is addressed. If you are not the intended recipient, you<br>> > are not authorized to read, print, retain, copy, disseminate, distribute,
<br>> > or use this message or any part thereof. If you receive this message in<br>> > error, please notify the sender immediately and delete all copies of this<br>> > message.<br>> ><br>> > ------------------------------
<br>> ><br>> > _______________________________________________<br>> > SAP-WUG mailing list<br>> > <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>> ><br>> ><br>> > End of SAP-WUG Digest, Vol 20, Issue 54<br>> > ***************************************<br>> ><br>><br>><br>><br>
> _______________________________________________<br>> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug
</a><br>><br>><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/922d4904/attachment.htm">http://mailman.mit.edu/pipermail/sap-wug/attachments/20060721/922d4904/attachment.htm
</a><br><br>------------------------------<br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br><br>End of SAP-WUG Digest, Vol 20, Issue 56<br>***************************************<br></blockquote></div><br>