Deletion of old workflow log items

[Andy Curtis]

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.

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).

Andy





On Mon, Mar 24, 2014 at 3:39 PM, <sap-wug-request at mit.edu> wrote:

> Send SAP-WUG mailing list submissions to
>         sap-wug at mit.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mailman.mit.edu/mailman/listinfo/sap-wug
> or, via email, send a message with subject or body 'help' to
>         sap-wug-request at mit.edu
>
> You can reach the person managing the list at
>         sap-wug-owner at mit.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SAP-WUG digest..."
>
> Today's Topics:
>
>    1. Deletion of old workflow log items  (Magalhaes, Marcia)
>    2. Re: Register incoming MM/FI invoices in workflow as a step
>       (Robert van den Berg)
>    3. RE: Deletion of old workflow log items
>       (Keohan, Susan - 1140 - MITLL)
>
>
> ---------- Forwarded message ----------
> From: "Magalhaes, Marcia" <marcia.magalhaes at ocps.net>
> To: "'sap-wug at mit.edu'" <sap-wug at mit.edu>
> Cc:
> Date: Mon, 24 Mar 2014 10:37:10 -0400
> Subject: Deletion of old workflow log items
>
> Hi all,
>
> 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.
>
>
>
> Thanks so much for your expertise and time,
>
> *Marcia Magalhaes*
>
> *Senior SAP Developer*
>
> *Orange County Public Schools*
>
> *Orlando, FL*
>
> ------------------------------
> The information contained in this e-mail message is intended solely for
> the recipient(s) and may contain privileged information. Tampering with
> or altering the contents of this message is prohibited. This information
> is the same as any written document and may be subject to all rules
> governing public information according to Florida Statutes. Any message
> that falls under Chapter 119 shall not be altered in a manner that
> misrepresents the activities of Orange County Public Schools.
>
> [References: Florida State Constitution I.24, Florida State Statutes
> Chapter 119, and OCPS Management Directive A-9.] If you have received
> this message in error, or are not the named recipient notify the sender
> and delete this message from your computer.
>
>
>
> ---------- Forwarded message ----------
> From: "Robert van den Berg" <wug at bergtop-ict.nl>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Cc:
> Date: Mon, 24 Mar 2014 15:18:20 GMT
> Subject: Re: Register incoming MM/FI invoices in workflow as a step
> Anyone have any ideas about how to call FV60 in a synchronous method which
> returns the BELNR?
>
> Regards,
> Robert
>
> Op 19 maart 2014, schreef Dart, Jocelyn <jocelyn.dart at sap.com>:
>
>  Hi Robert
> 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
> Rgds
> Jocelyn
>
> Sent from my iPhone with many apologies for the spelling, grammar and any
> other deficiencies
>
> On 19 Mar 2014, at 7:39 pm, "Robert van den Berg" <wug at bergtop-ict.nl>
> wrote:
>
>  Actually, it is not to approve, but to change the document.
> First person registers the document and fill's in the header. (FV60 / MIRO)
> Then it is send to a second person who complements the data. (FV60 / MIR4)
> Then it is send to a third person who approves the invoice. (FV60 / MIR4)
> When it is approved, the invoice is booked.
>
>  For both FI and MM invoices.....
>
> Idea now is to create a subtype of the BOR objects and just call MIRO and
> FV60 in a sync method.
> Anyone knows why the methods are async?
>
> Regards,
> Robert
>
> Op 18 maart 2014, schreef Andy Curtis <abcurtis at gmail.com>:
>
>    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.
>
>  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.
>
>  QQ, wouldn't you have already approved the PO and GRN/SES? So a 3 way
> match could be posted?
>
>  Andy
>
>
>
> ---------- Forwarded message ----------
> From: "Robert van den Berg" <wug at bergtop-ict.nl>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Cc:
> Date: Tue, 18 Mar 2014 14:46:57 GMT
> Subject: Register incoming MM/FI invoices in workflow as a step
> All,
>
>  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.
>
>  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..
> But to be able to call MIRO or FV60, I can only use async methods.
>
>  BUS2081-CREATE I can use, because this triggers the event
> BUS2081-CREATED. So MIRO seems to be checked.
> 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...
>
>  Does anyone have any experience with the registration of incoming
> invoices (MM/FI) from a workflow?
>
>  Kind regards,
> Robert
>
>
>     _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>   _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>  _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> ---------- Forwarded message ----------
> From: "Keohan, Susan - 1140 - MITLL" <keohan at ll.mit.edu>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Cc:
> Date: Mon, 24 Mar 2014 15:39:54 +0000
> Subject: RE: Deletion of old workflow log items
>
> Hi Marcia,
>
>
>
> 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.
>
>
>
> Regards,
> Sue
>
>
>
>
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Magalhaes, Marcia
> *Sent:* Monday, March 24, 2014 10:37 AM
> *To:* 'sap-wug at mit.edu'
> *Subject:* Deletion of old workflow log items
>
>
>
> Hi all,
>
> 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.
>
>
>
> Thanks so much for your expertise and time,
>
> *Marcia Magalhaes*
>
> *Senior SAP Developer*
>
> *Orange County Public Schools*
>
> *Orlando, FL*
>
>
> ------------------------------
>
> The information contained in this e-mail message is intended solely for
> the recipient(s) and may contain privileged information. Tampering with
> or altering the contents of this message is prohibited. This information
> is the same as any written document and may be subject to all rules
> governing public information according to Florida Statutes. Any message
> that falls under Chapter 119 shall not be altered in a manner that
> misrepresents the activities of Orange County Public Schools.
>
> [References: Florida State Constitution I.24, Florida State Statutes
> Chapter 119, and OCPS Management Directive A-9.] If you have received
> this message in error, or are not the named recipient notify the sender
> and delete this message from your computer.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140324/9f8b376e/attachment-0001.htm