<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body><P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >Hi</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p ><FONT face="Times New Roman" size=3 > </FONT></o:p></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >We are using the SRM 5.0 SP8 with extended scenario, for the local <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:place >PO</st1:place> we are using the workflow WS14000145.</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >This workflow is working perfectly with the Purchase Order on WBS or Cost center, however for the purchase order on asset we do have a problem.</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >Our way of working is on cost center and WBS to determine the approval route with the first approver being on the R3 system responsible of the cost object.</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >For asset, we are determining the approval route with the first approver being the manager of the creator of the Purchase Order ( Shopping cart) </FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >While debugging the BUS2201 there is no problem the route is determined without a problem.</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >But when a Shopping Cart on asset is approved, then the status is staying in Item in transfer, the <st1:place >PO</st1:place> never being created and a short dump is being created.</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >This short dump is showing a time out during the pre-check of the workflow, while looking more thoroughly at the code within the short dump we can see that some parameter like the creator of the PO are not transmitted to our functions.</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >Have you ever met this kind of behaviour ? Is there an <st1:City ><st1:place >OSS</st1:place></st1:City> note or something to be done ?</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><o:p ><FONT face="Times New Roman" size=3 > </FONT></o:p></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT face="Times New Roman" size=3 >Thanks for your reply</FONT></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" ><FONT size=3 ><FONT face="Times New Roman" >Stephane<o:p ></o:p></FONT></FONT></P>
<BR>
<BR ><BR ><BR ><BR ><BR >
<HR id=stopSpelling>
> From: sap-wug-request@mit.edu<BR>> Subject: SAP-WUG Digest, Vol 19, Issue 32<BR>> To: sap-wug@mit.edu<BR>> Date: Tue, 13 Jun 2006 02:57:32 -0400<BR>> <BR>> Send SAP-WUG mailing list submissions to<BR>> sap-wug@mit.edu<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> or, via email, send a message with subject or body 'help' to<BR>> sap-wug-request@mit.edu<BR>> <BR>> You can reach the person managing the list at<BR>> sap-wug-owner@mit.edu<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: Task attributes not getting transported properly<BR>> (akshay.bhagwat@wipro.com)<BR>> 2. RE: Task attributes not getting transported properly<BR>> (Dart, Jocelyn)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Tue, 13 Jun 2006 11:34:23 +0530<BR>> From: <akshay.bhagwat@wipro.com><BR>> Subject: RE: Task attributes not getting transported properly<BR>> To: <sap-wug@mit.edu><BR>> Message-ID:<BR>> <0F35D2C4458E9B4A9891BE2D4E0C8390F84EDB@PNE-HJN-MBX01.wipro.com><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> <BR>> Hi Jocelyn,<BR>> <BR>> Thanks for the valuable inputs, however wanted to know is this procedure<BR>> also applicable if I want to move this data in same system , but in<BR>> different clients? e.g. from client 300 to client 400 of system TST.<BR>> <BR>> Regards,<BR>> <BR>> Akshay Bhagwat<BR>> <BR>> SAP Practice<BR>> <BR>> Wipro Technologies<BR>> <BR>> ': +91 20 2293 3700 x 3608<BR>> Fax: +91 20 2293 3756<BR>> <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of Dart, Jocelyn<BR>> Sent: Tuesday, June 13, 2006 10:13 AM<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: Task attributes not getting transported properly<BR>> <BR>> <BR>> Ok .. I really think its time this one was on the FAQ - Mike P. can you<BR>> assist?<BR>> <BR>> Task attributes are client dependent so they are not transferred by<BR>> change requests.<BR>> Task attributes are not customizing so they are not transferred by<BR>> customizing requests.<BR>> Task attributes are HR data. <BR>> To transport HR data you must use an HR transport program such as<BR>> RHMOVE30.<BR>> <BR>> Nominate your task, list of tasks, or task group.<BR>> Use evaluation path TASKHIER.<BR>> Nominate a transport request.<BR>> On the results list, select all tasks for transport and then include<BR>> them in the transport request.<BR>> <BR>> <BR>> Regards,<BR>> Jocelyn Dart<BR>> Senior Consultant<BR>> SAP Australia Pty Ltd.<BR>> Level 1/168 Walker St.<BR>> North Sydney<BR>> NSW, 2060<BR>> Australia<BR>> T +61 412 390 267<BR>> M + 61 412 390 267<BR>> E jocelyn.dart@sap.com<BR>> http://www.sap.com <http://www.sap.com/> <BR>> <BR>> The information contained in or attached to this electronic transmission<BR>> is confidential and may be legally privileged. It is intended only for<BR>> the person or entity to which it is addressed. If you are not the<BR>> intended recipient, you are hereby notified that any distribution,<BR>> copying, review, retransmission, dissemination or other use of this<BR>> electronic transmission or the information contained in it is strictly<BR>> prohibited. If you have received this electronic transmission in error,<BR>> please immediately contact the sender to arrange for the return of the<BR>> original documents.<BR>> <BR>> Electronic transmission cannot be guaranteed to be secure and<BR>> accordingly, the sender does not accept liability for any such data<BR>> corruption, interception, unauthorized amendment, viruses, delays or the<BR>> consequences thereof.<BR>> <BR>> Any views expressed in this electronic transmission are those of the<BR>> individual sender, except where the message states otherwise and the<BR>> sender is authorized to state them to be the views of SAP AG or any of<BR>> its subsidiaries. SAP AG, its subsidiaries, and their directors,<BR>> officers and employees make no representation nor accept any liability<BR>> for the accuracy or completeness of the views or information contained<BR>> herein. Please be aware that the furnishing of any pricing information/<BR>> business proposal herein is indicative only, is subject to change and<BR>> shall not be construed as an offer or as constituting a binding<BR>> agreement on the part of SAP AG or any of its subsidiaries to enter into<BR>> any relationship, unless otherwise expressly stated.<BR>> <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of akshay.bhagwat@wipro.com<BR>> Sent: Tuesday, 13 June 2006 2:27 PM<BR>> To: sap-wug@mit.edu<BR>> Subject: Task attributes not getting transported properly<BR>> <BR>> <BR>> Hello,<BR>> <BR>> Point no 1.:<BR>> For a particular scenario, I had assigned task property as general task<BR>> for one of the tasks used in workflow.<BR>> As we need to move this to testing client, using transaction SCC1, I<BR>> moved the same config to testing client.<BR>> This happened successfully and I could see task as general task in<BR>> testing client.<BR>> However, later I changed the task properties as General forwarding not<BR>> allowed, and assigned specific Positions to this task.<BR>> <BR>> Now when I am trying to move this to testing client, the changes are not<BR>> getting reflected in testing client.<BR>> Could you pls suggest, what might be the reason?<BR>> <BR>> point no.2<BR>> <BR>> Instead of assigning many positions in Org structure, I tried to assign<BR>> the Root org unit to this task, however at run time I got error in WF<BR>> saying object type A not allowed. So wanted to know that can we not<BR>> assign Root org units to tasks?<BR>> <BR>> Thanks in Advance.<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 message and any attachments<BR>> to this message are intended for the exclusive use of the addressee(s)<BR>> and may contain proprietary, confidential or privileged information. If<BR>> you are not the intended recipient, you should not disseminate,<BR>> distribute or copy this e-mail. Please notify the sender immediately and<BR>> destroy all copies of this message and any attachments.<BR>> <BR>> WARNING: Computer viruses can be transmitted via email. The recipient<BR>> should check this email and any attachments for the presence of viruses.<BR>> The company accepts no liability for any damage caused by any virus<BR>> transmitted by this email.<BR>> <BR>> www.wipro.com<BR>> <BR>> <BR>> <BR>> <BR>> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.<BR>> <BR>> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.<BR>> <BR>> www.wipro.com<BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060613/b271cd70/attachment-0001.htm<BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Tue, 13 Jun 2006 14:55:03 +0800<BR>> From: "Dart, Jocelyn" <jocelyn.dart@sap.com><BR>> Subject: RE: Task attributes not getting transported properly<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <F843AF000027394A9F3D3194109269F453BF68@sgsine11.sin.sap.corp><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> Yes. The settings are client dependent. <BR>> <BR>> <BR>> Regards, <BR>> Jocelyn Dart <BR>> Senior Consultant <BR>> SAP Australia Pty Ltd. <BR>> Level 1/168 Walker St. <BR>> North Sydney <BR>> NSW, 2060 <BR>> Australia <BR>> T +61 412 390 267 <BR>> M + 61 412 390 267 <BR>> E jocelyn.dart@sap.com <BR>> http://www.sap.com <http://www.sap.com/> <BR>> <BR>> The information contained in or attached to this electronic transmission<BR>> is confidential and may be legally privileged. It is intended only for<BR>> the person or entity to which it is addressed. If you are not the<BR>> intended recipient, you are hereby notified that any distribution,<BR>> copying, review, retransmission, dissemination or other use of this<BR>> electronic transmission or the information contained in it is strictly<BR>> prohibited. If you have received this electronic transmission in error,<BR>> please immediately contact the sender to arrange for the return of the<BR>> original documents. <BR>> <BR>> Electronic transmission cannot be guaranteed to be secure and<BR>> accordingly, the sender does not accept liability for any such data<BR>> corruption, interception, unauthorized amendment, viruses, delays or the<BR>> consequences thereof.<BR>> <BR>> Any views expressed in this electronic transmission are those of the<BR>> individual sender, except where the message states otherwise and the<BR>> sender is authorized to state them to be the views of SAP AG or any of<BR>> its subsidiaries. SAP AG, its subsidiaries, and their directors,<BR>> officers and employees make no representation nor accept any liability<BR>> for the accuracy or completeness of the views or information contained<BR>> herein. Please be aware that the furnishing of any pricing information/<BR>> business proposal herein is indicative only, is subject to change and<BR>> shall not be construed as an offer or as constituting a binding<BR>> agreement on the part of SAP AG or any of its subsidiaries to enter into<BR>> any relationship, unless otherwise expressly stated. <BR>> <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of akshay.bhagwat@wipro.com<BR>> Sent: Tuesday, 13 June 2006 4:04 PM<BR>> To: sap-wug@mit.edu<BR>> Subject: RE: Task attributes not getting transported properly<BR>> <BR>> <BR>> Hi Jocelyn,<BR>> <BR>> Thanks for the valuable inputs, however wanted to know is this procedure<BR>> also applicable if I want to move this data in same system , but in<BR>> different clients? e.g. from client 300 to client 400 of system TST.<BR>> <BR>> Regards, <BR>> <BR>> Akshay Bhagwat<BR>> <BR>> SAP Practice <BR>> <BR>> Wipro Technologies<BR>> <BR>> ': +91 20 2293 3700 x 3608 <BR>> Fax: +91 20 2293 3756<BR>> <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of Dart, Jocelyn<BR>> Sent: Tuesday, June 13, 2006 10:13 AM<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: Task attributes not getting transported properly<BR>> <BR>> <BR>> Ok .. I really think its time this one was on the FAQ - Mike P. can you<BR>> assist?<BR>> <BR>> Task attributes are client dependent so they are not transferred by<BR>> change requests. <BR>> Task attributes are not customizing so they are not transferred by<BR>> customizing requests. <BR>> Task attributes are HR data. <BR>> To transport HR data you must use an HR transport program such as<BR>> RHMOVE30. <BR>> <BR>> Nominate your task, list of tasks, or task group. <BR>> Use evaluation path TASKHIER.<BR>> Nominate a transport request.<BR>> On the results list, select all tasks for transport and then include<BR>> them in the transport request. <BR>> <BR>> <BR>> Regards, <BR>> Jocelyn Dart <BR>> Senior Consultant <BR>> SAP Australia Pty Ltd. <BR>> Level 1/168 Walker St. <BR>> North Sydney <BR>> NSW, 2060 <BR>> Australia <BR>> T +61 412 390 267 <BR>> M + 61 412 390 267 <BR>> E jocelyn.dart@sap.com <BR>> http://www.sap.com <http://www.sap.com/> <BR>> <BR>> The information contained in or attached to this electronic transmission<BR>> is confidential and may be legally privileged. It is intended only for<BR>> the person or entity to which it is addressed. If you are not the<BR>> intended recipient, you are hereby notified that any distribution,<BR>> copying, review, retransmission, dissemination or other use of this<BR>> electronic transmission or the information contained in it is strictly<BR>> prohibited. If you have received this electronic transmission in error,<BR>> please immediately contact the sender to arrange for the return of the<BR>> original documents. <BR>> <BR>> Electronic transmission cannot be guaranteed to be secure and<BR>> accordingly, the sender does not accept liability for any such data<BR>> corruption, interception, unauthorized amendment, viruses, delays or the<BR>> consequences thereof.<BR>> <BR>> Any views expressed in this electronic transmission are those of the<BR>> individual sender, except where the message states otherwise and the<BR>> sender is authorized to state them to be the views of SAP AG or any of<BR>> its subsidiaries. SAP AG, its subsidiaries, and their directors,<BR>> officers and employees make no representation nor accept any liability<BR>> for the accuracy or completeness of the views or information contained<BR>> herein. Please be aware that the furnishing of any pricing information/<BR>> business proposal herein is indicative only, is subject to change and<BR>> shall not be construed as an offer or as constituting a binding<BR>> agreement on the part of SAP AG or any of its subsidiaries to enter into<BR>> any relationship, unless otherwise expressly stated. <BR>> <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of akshay.bhagwat@wipro.com<BR>> Sent: Tuesday, 13 June 2006 2:27 PM<BR>> To: sap-wug@mit.edu<BR>> Subject: Task attributes not getting transported properly<BR>> <BR>> <BR>> Hello,<BR>> <BR>> Point no 1.:<BR>> For a particular scenario, I had assigned task property as general task<BR>> for one of the tasks used in workflow.<BR>> As we need to move this to testing client, using transaction SCC1, I<BR>> moved the same config to testing client.<BR>> This happened successfully and I could see task as general task in<BR>> testing client.<BR>> However, later I changed the task properties as General forwarding not<BR>> allowed, and assigned specific Positions to this task.<BR>> <BR>> Now when I am trying to move this to testing client, the changes are not<BR>> getting reflected in testing client.<BR>> Could you pls suggest, what might be the reason?<BR>> <BR>> point no.2 <BR>> <BR>> Instead of assigning many positions in Org structure, I tried to assign<BR>> the Root org unit to this task, however at run time I got error in WF<BR>> saying object type A not allowed. So wanted to know that can we not<BR>> assign Root org units to tasks?<BR>> <BR>> Thanks in Advance.<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 message and any attachments<BR>> to this message are intended for the exclusive use of the addressee(s)<BR>> and may contain proprietary, confidential or privileged information. If<BR>> you are not the intended recipient, you should not disseminate,<BR>> distribute or copy this e-mail. Please notify the sender immediately and<BR>> destroy all copies of this message and any attachments. <BR>> <BR>> WARNING: Computer viruses can be transmitted via email. The recipient<BR>> should check this email and any attachments for the presence of viruses.<BR>> The company accepts no liability for any damage caused by any virus<BR>> transmitted by this email.<BR>> <BR>> www.wipro.com<BR>> <BR>> <BR>> The information contained in this electronic message and any attachments<BR>> to this message are intended for the exclusive use of the addressee(s)<BR>> and may contain proprietary, confidential or privileged information. If<BR>> you are not the intended recipient, you should not disseminate,<BR>> distribute or copy this e-mail. Please notify the sender immediately and<BR>> destroy all copies of this message and any attachments. <BR>> <BR>> WARNING: Computer viruses can be transmitted via email. The recipient<BR>> should check this email and any attachments for the presence of viruses.<BR>> The company accepts no liability for any damage caused by any virus<BR>> transmitted by this email.<BR>> <BR>> www.wipro.com<BR>> <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060613/d8e0df24/attachment.htm<BR>> <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>> End of SAP-WUG Digest, Vol 19, Issue 32<BR>> ***************************************<BR><BR><br /><hr />À vous de rechercher : <a href='http://ideas.live.com/programpage.aspx?versionId=6e782662-5f2a-4161-a64a-7f63644e1f0a' target='_new'>Essayez Windows Live Search for Mobile Beta</a></body>
</html>