<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>Hi, <BR >In workflow WS1400046 the loop never stops. The condition for ending the loop are the standard one CurrentAgents NX AND Approval status = 0 OR Approval status <> 0 .<BR >When there is a rejection this is working fine the workflow stops<BR >After the final approver of the workflow has approved , in the step called Determine next approver, the actualAgents table is not updated and the <FONT class=""><FONT class=""><FONT class="">No_further_<FONT class="">approval</FONT></FONT>_needed</FONT></FONT> is not updated either.<BR >Behind this step is task TS14007989, BUS4101 with method NEXTDYNAMICAPPROVERGET. All the binding seems correct.<BR >When testing the Method directly the result is the same as within the workflow ( ActualAgent is not correct and <FONT class="">No_further_<FONT class="">approval</FONT></FONT> is not set)<BR >It seems to be coming from Function <FONT class="">BBP_WFL_DIN_APPR_CONTAINER_<FONT class="">GET</FONT></FONT> where the approvallist-state = 2 for the last approver.<BR >(Code: * get the list of dynamic approvers from wi-container<BR >swf_<FONT class="">get_element</FONT> ev_wi_container_handle c_wf_appr_list <FONT class="">lt_cont_<FONT class="">approver</FONT></FONT>.)<BR >While testing the BADI function directly the <FONT class="">no_further_<FONT class="">approval</FONT></FONT> flag is present<BR > <BR >Can someone help me to determine why this method is not returning the right value or why the approval state of my last approver is set at 2 ?<BR > <BR >Our version is SRM 4.0 with support package applied is SAPKIBKS08<BR >Thanks for your help <BR >Stephane Bailleul<BR ><BR ><BR ><BR ><BR ><BR >
<HR id=stopSpelling>
> From: sap-wug-request@mit.edu<BR>> Subject: SAP-WUG Digest, Vol 18, Issue 79<BR>> To: sap-wug@mit.edu<BR>> Date: Thu, 18 May 2006 15:36:20 -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: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile<BR>> (Rickayzen, Alan)<BR>> 2. RE: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile<BR>> (Rickayzen, Alan)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Thu, 18 May 2006 21:34:51 +0200<BR>> From: "Rickayzen, Alan" <alan.rickayzen@sap.com><BR>> Subject: RE: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <056B06CE86417342AAF8AB7CDD3CA3C901EE6011@dewdfe14.wdf.sap.corp><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> Hi Jocelyn,<BR>> <BR>> So how come no-one has built a SOx compliant CPU yet, that logs the instructions and the users on who's behalf the instruction is being executed?<BR>> <BR>> Alan <BR>> <BR>> <BR>> _____ <BR>> <BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of Dart, Jocelyn<BR>> Sent: Dienstag, 16. Mai 2006 06:55<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile<BR>> <BR>> <BR>> <BR>> 1. Explain logically and sensibly why this is so. <BR>> 2. Compare WF-BATCH with other system users such as background users for running jobs, DDIC, SAP*, et al.<BR>> 3. Explain logically and sensibly *** with quiet but firm emphasis *** why this is so. <BR>> 4. Paint a picture of the sort of problems they are likely to cause the company by doing this - use lots of black and red. <BR>> 5. Explain logically and sensibly *** with VOLUME and manic punctuation marks!!! *** why this is so. <BR>> 6. Illustrate the workload/pain likely to fall upon them with monster dump trucks and lots of lead bullets. <BR>> 7. Explain logically and sensibly *** using baseball bat to beat the sense into them *** why this is so. <BR>> 8. Write washing-my-hands-on-your-own-heads-be-it-I-told-you-so document and get the guilty parties to sign. <BR>> 9. Leave company citing nervous strain. <BR>> <BR>> ;-)<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 is confidential and may be legally privileged. It is intended only for the person or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, review, retransmission, dissemination or other use of this electronic transmission or the information contained in it is strictly prohibited. If you have received this electronic transmission in error, please immediately contact the sender to arrange for the return of the original documents. <BR>> <BR>> Electronic transmission cannot be guaranteed to be secure and accordingly, the sender does not accept liability for any such data corruption, interception, unauthorized amendment, viruses, delays or the consequences thereof.<BR>> <BR>> Any views expressed in this electronic transmission are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of SAP AG or any of its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and employees make no representation nor accept any liability for the accuracy or completeness of the views or information contained herein. Please be aware that the furnishing of any pricing information/ business proposal herein is indicative only, is subject to change and shall not be construed as an offer or as constituting a binding agreement on the part of SAP AG or any of its subsidiaries to enter into 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 Of Kjetil Kilhavn<BR>> Sent: Saturday, 13 May 2006 12:54 AM<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile<BR>> <BR>> <BR>> Since I have been ordered to not badmouth my company in public I can't tell you my opinion on how it was handled here. I tried the same argument, it is a non-dialog user with a password that no-one knows. It felt a bit like discussing with the Monolith (http://www.traveladventures.org/continents/europe/vigeland09.shtml)<BR>> <BR>> WF-BATCH has a copy of SAP_ALL and SAP_NEW. At least it creates employment opportunities...<BR>> -- <BR>> Kjetil Kilhavn, Statoil ?FT KTJ BAS DEV SAP<BR>> <BR>> <BR>> <BR>> <BR>> _____ <BR>> <BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of Shahram Shadmani<BR>> Sent: 12. mai 2006 16:21<BR>> To: sap-wug@mit.edu<BR>> Subject: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile<BR>> <BR>> <BR>> Hi there,<BR>> <BR>> Our SAP security team is attending to remove the SAP_ALL and SAP_NEW profile from WF-Batch user due to SOX requirements.<BR>> We (SAP Workflow Team) know that this will cause lot of problems and are pointing to the type of this user which is "system" and not a dialog user. However, I was wondering if other people / companies have or had the same problem and how they resolved it.<BR>> <BR>> Thanks a lot for your response in advance,<BR>> <BR>> Shahram Shadmani<BR>> <BR>> <BR>> <BR>> <BR>> -------------------------------------------------------------------<BR>> The information contained in this message may be CONFIDENTIAL and is<BR>> intended for the addressee only. Any unauthorised use, dissemination of the<BR>> information or copying of this message is prohibited. If you are not the<BR>> addressee, please notify the sender immediately by return e-mail and delete<BR>> this message.<BR>> Thank you. <BR>> <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060518/cc8c5b1b/attachment-0001.htm<BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Thu, 18 May 2006 21:33:16 +0200<BR>> From: "Rickayzen, Alan" <alan.rickayzen@sap.com><BR>> Subject: RE: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <056B06CE86417342AAF8AB7CDD3CA3C901EE6010@dewdfe14.wdf.sap.corp><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> A non-text attachment was scrubbed...<BR>> Name: not available<BR>> Type: application/x-pkcs7-mime<BR>> Size: 19568 bytes<BR>> Desc: not available<BR>> Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20060518/439d804a/attachment.bin<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 18, Issue 79<BR>> ***************************************<BR><br /><hr />Votre nouvelle utilisation de la messagerie : <a href='http://ideas.live.com/programpage.aspx?versionId=0eccd94b-eb48-497c-8e60-c6313f7ebb73' target='_new'>Windows Live Messenger Beta</a></body>
</html>