<div dir="ltr"><div class="gmail_extra">Same topic came up here with similar volumes. Basic decided it was not business data and they had authority to delete it and scheduled a couple of jobs to run RSWWWIDE & RSWWHIDE in production, until I highlighted that SAP say 'don't run these programs in production'. I am now looking at Wf Archiving and have done it in Development quite easily. Looking to move it through to Prod when we can all agree on filesystems/naming conventions.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">So in short, Archive don't run RSWWWIDE & RSWWHIDE (got an idea SWPR runs these programs, but at least theres rigour about what it's deleting).</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Andy</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Mar 24, 2014 at 3:39 PM, <span dir="ltr"><<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
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" 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 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>Today's Topics:<br>
<br>
1. Deletion of old workflow log items (Magalhaes, Marcia)<br>
2. Re: Register incoming MM/FI invoices in workflow as a step<br>
(Robert van den Berg)<br>
3. RE: Deletion of old workflow log items<br>
(Keohan, Susan - 1140 - MITLL)<br>
<br><br>---------- Forwarded message ----------<br>From: "Magalhaes, Marcia" <<a href="mailto:marcia.magalhaes@ocps.net">marcia.magalhaes@ocps.net</a>><br>To: "'<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>'" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
Cc: <br>Date: Mon, 24 Mar 2014 10:37:10 -0400<br>Subject: Deletion of old workflow log items<br>
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Hi all,<u></u><u></u></p>
<p class="MsoNormal">I have a general question about deletion of old Completed workflow log items (logs older than 7 years for example). Is there a standard SAP job that I can schedule to routinely delete these old logs? Also, is there a policy that I should
follow or precautions to be aware of? BTW, our log table SWWLOGHIST has over 80 million records. We are in SAP ECC 6.0.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks so much for your expertise and time,<u></u><u></u></p>
<p class="MsoNormal"><i><span style="font-size:12pt;font-family:'Arial Narrow',sans-serif;color:rgb(29,27,17)">Marcia Magalhaes<u></u><u></u></span></i></p>
<p class="MsoNormal"><i><span style="font-size:12pt;font-family:'Arial Narrow',sans-serif;color:rgb(29,27,17)">Senior SAP Developer</span></i><span style="font-size:12pt;font-family:'Times New Roman',serif;color:rgb(29,27,17)"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:12pt;font-family:'Arial Narrow',sans-serif;color:rgb(29,27,17)">Orange County Public Schools</span></i><span style="font-size:12pt;font-family:'Times New Roman',serif;color:rgb(29,27,17)"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:12pt;font-family:'Arial Narrow',sans-serif;color:rgb(29,27,17)">Orlando, FL</span></i><span style="font-family:Arial,sans-serif;color:rgb(29,27,17)"><u></u><u></u></span></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1">The information contained in this e-mail message is intended solely for<br>
the recipient(s) and may contain privileged information. Tampering with<br>
or altering the contents of this message is prohibited. This information<br>
is the same as any written document and may be subject to all rules<br>
governing public information according to Florida Statutes. Any message<br>
that falls under Chapter 119 shall not be altered in a manner that<br>
misrepresents the activities of Orange County Public Schools.<br>
<br>
[References: Florida State Constitution I.24, Florida State Statutes<br>
Chapter 119, and OCPS Management Directive A-9.] If you have received<br>
this message in error, or are not the named recipient notify the sender<br>
and delete this message from your computer.<br>
<br>
</font>
</div>
<br><br>---------- Forwarded message ----------<br>From: "Robert van den Berg" <<a href="mailto:wug@bergtop-ict.nl">wug@bergtop-ict.nl</a>><br>To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
Cc: <br>Date: Mon, 24 Mar 2014 15:18:20 GMT<br>Subject: Re: Register incoming MM/FI invoices in workflow as a step<br>Anyone have any ideas about how to call FV60 in a synchronous method which returns the BELNR?<div><br></div>
<div>Regards,</div><div>Robert<br><br><p>Op 19 maart 2014, schreef Dart, Jocelyn <<a href="mailto:jocelyn.dart@sap.com" target="_blank">jocelyn.dart@sap.com</a>>:</p><blockquote type="cite"><div>
<div>
<div>Hi Robert </div>
<div>The vast majority of database updates from such transactions occurs in the LUW triggered from but separate to the transaction itself. Which means if you use synch methods you risk the database updates being incomplete or failing at the time the workflow
moves onto the next step. Typically adding any user activity into the same method will add sufficient delay to avoid problems other than actual failure. However suggest you think around a couple of worst case scenarios in your design</div>
<div>Rgds</div>
<div>Jocelyn</div>
<div><br>
Sent from my iPhone with many apologies for the spelling, grammar and any other deficiencies </div>
<div><br>
On 19 Mar 2014, at 7:39 pm, "Robert van den Berg" <<a href="mailto:wug@bergtop-ict.nl" target="_blank">wug@bergtop-ict.nl</a>> wrote:<br>
<br>
</div>
<blockquote>
<div>Actually, it is not to approve, but to change the document.
<div>First person registers the document and fill's in the header. (FV60 / MIRO)</div>
<div>Then it is send to a second person who complements the data. (FV60 / MIR4)</div>
<div>Then it is send to a third person who approves the invoice. (FV60 / MIR4)</div>
<div>When it is approved, the invoice is booked.</div>
<div><br>
</div>
<div>For both FI and MM invoices.....<br>
<br>
Idea now is to create a subtype of the BOR objects and just call MIRO and FV60 in a sync method.</div>
<div>Anyone knows why the methods are async?</div>
<div><br>
Regards,</div>
<div>Robert<br>
<p>Op 18 maart 2014, schreef Andy Curtis <<a href="mailto:abcurtis@gmail.com" target="_blank">abcurtis@gmail.com</a>>:</p>
<blockquote>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>At risk of repeating Mike here, we use a solution for this built by OpenText (VIM Vendor Invoice Management) it is very good actually. They basically have code in teh LIV Invoice SAVE BADI, and probably the equivalent in FI Invoices, I don't do much with
them so now too sure.</div>
<div><br>
</div>
<div>OpenTexts Save Badi basically popups up a screen to allow a 'Parking Reason' to be chosen (ohh this is on Parking an Invoice, it will get Posted when it's ready later in the Resolution process). The Parking Reason is the basis for the next step in the
the life of the Invoice and is used along with other Agent determination config to send the invoice to the person (approver) that needs it.</div>
<div><br>
</div>
<div>QQ, wouldn't you have already approved the PO and GRN/SES? So a 3 way match could be posted? </div>
<div><br>
</div>
<div>Andy</div>
<div><br>
</div>
<div> </div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
---------- Forwarded message ----------<br>
From: "Robert van den Berg" <<a href="mailto:wug@bergtop-ict.nl" target="_blank">wug@bergtop-ict.nl</a>><br>
To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>><br>
Cc: <br>
Date: Tue, 18 Mar 2014 14:46:57 GMT<br>
Subject: Register incoming MM/FI invoices in workflow as a step<br>
All,
<div><br>
</div>
<div>I have a requirement where we want to register an incoming invoice in a workflow step, then choose the approvers and send the invoice to the approver.</div>
<div><br>
</div>
<div>Normally (as I read from SAP documentation), a user goes to transaction MIRO of FV60, enters data and when they save, then the workflow starts. But then, the user can't choose the approvers. So I need the workflow to have the registration included..</div>
<div>But to be able to call MIRO or FV60, I can only use async methods.</div>
<div><br>
</div>
<div>BUS2081-CREATE I can use, because this triggers the event BUS2081-CREATED. So MIRO seems to be checked.</div>
<div>But for FV60, I need to use BKPF-CREATE but this triggers event CREATED from object FIPP. So I can't use this as a ending event...</div>
<div><br>
</div>
<div>Does anyone have any experience with the registration of incoming invoices (MM/FI) from a workflow?</div>
<div><br>
</div>
<div>Kind regards,</div>
<div>Robert</div>
<br>
<br>
</blockquote>
</div>
</div>
</div>
</div>
</div>
<div>
<div>_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote>
<div><span>_______________________________________________</span><br>
<span>SAP-WUG mailing list</span><br>
<span><a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a></span><br>
<span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></span><br>
</div>
</blockquote>
</div>
</div><div><div>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</div></div></blockquote></div>
<br><br>---------- Forwarded message ----------<br>From: "Keohan, Susan - 1140 - MITLL" <<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a>><br>To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
Cc: <br>Date: Mon, 24 Mar 2014 15:39:54 +0000<br>Subject: RE: Deletion of old workflow log items<br><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif">Hi Marcia,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif">You would want to investigate archiving and this is probably its’ own project – there are plenty of rules and regulations about what has to be kept, and then your business people may have additional reasons for keeping things around.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif">Regards,<br>
Sue<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u> <u></u></span></p>
<div><div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in"><p class="MsoNormal"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"> <a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>] <b>On Behalf Of </b>Magalhaes, Marcia<br>
<b>Sent:</b> Monday, March 24, 2014 10:37 AM<br><b>To:</b> '<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>'<br><b>Subject:</b> Deletion of old workflow log items <u></u><u></u></span></p></div>
</div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Hi all,<u></u><u></u></p><p class="MsoNormal">I have a general question about deletion of old Completed workflow log items (logs older than 7 years for example). Is there a standard SAP job that I can schedule to routinely delete these old logs? Also, is there a policy that I should follow or precautions to be aware of? BTW, our log table SWWLOGHIST has over 80 million records. We are in SAP ECC 6.0.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Thanks so much for your expertise and time,<u></u><u></u></p><p class="MsoNormal"><i><span style="font-size:12pt;font-family:'Arial Narrow',sans-serif;color:rgb(29,27,17)">Marcia Magalhaes<u></u><u></u></span></i></p>
<p class="MsoNormal"><i><span style="font-size:12pt;font-family:'Arial Narrow',sans-serif;color:rgb(29,27,17)">Senior SAP Developer</span></i><span style="font-size:12pt;font-family:'Times New Roman',serif;color:rgb(29,27,17)"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:12pt;font-family:'Arial Narrow',sans-serif;color:rgb(29,27,17)">Orange County Public Schools</span></i><span style="font-size:12pt;font-family:'Times New Roman',serif;color:rgb(29,27,17)"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:12pt;font-family:'Arial Narrow',sans-serif;color:rgb(29,27,17)">Orlando, FL</span></i><span style="font-family:Arial,sans-serif;color:rgb(29,27,17)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u> <u></u></span></p><div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12pt;font-family:'Times New Roman',serif"><hr size="2" width="100%" align="center">
</span></div><p class="MsoNormal" style="margin-bottom:12pt"><span style="font-size:7.5pt;font-family:Arial,sans-serif;color:gray">The information contained in this e-mail message is intended solely for<br>the recipient(s) and may contain privileged information. Tampering with<br>
or altering the contents of this message is prohibited. This information<br>is the same as any written document and may be subject to all rules<br>governing public information according to Florida Statutes. Any message<br>
that falls under Chapter 119 shall not be altered in a manner that<br>misrepresents the activities of Orange County Public Schools.<br><br>[References: Florida State Constitution I.24, Florida State Statutes<br>Chapter 119, and OCPS Management Directive A-9.] If you have received<br>
this message in error, or are not the named recipient notify the sender<br>and delete this message from your computer.</span><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u><u></u></span></p>
</div></div><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" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br></div></div>