archiving work items

8/6/2019 Archiving Work Items

1/17

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG

Archiving Work Items

Applies to:Applies to ECC 6.0

Summary

The Worldwide Workflow Survey revealed that many are not archiving work items in workflow. These tablescan build up fast quickly. This paper walks you through the steps to archive work items using SAP standardutilities.

Author: Tammy Powlas

Company: Fairfax Water

Created on: 16 August 2010

Author Bio

Tammy Powlas works for Fairfax Water, is a SAP Mentor and ASUG volunteer with the BI andBITI communities. She is SAP-certified in FI, CO, BW, SEM and ASAP.


2/17



2010 SAP AG

Table of Contents

Work Item Archiving ............................................................................................................................................ 3Background: .................................................................................................................................................... 3Prerequisite ..................................................................................................................................................... 3Transaction AOBJ ........................................................................................................................................... 4Transaction SWW_SARA Write Program .................................................................................................... 7Transaction SWW_SARA Delete Program ................................................................................................ 12

Related Content ................................................................................................................................................ 16Disclaimer and Liability Notice .......................................................................................................................... 17


3/17



2010 SAP AG

Work Item Archiving

The 2010 Workflow Survey showed that only 38% of respondents are archiving. Most performanceproblems in Business Workplace are caused by not archiving work items. Archiving work items should bepart of an overall archiving strategy of a company. Only cancelled or closed work items are eligible forarchiving.

Background:

Archiving helps you control your data growth and system performance. The overall steps are shown here:

Source: ASUG Data Archiving 101 Presentation J. Malfetti, R. Jackson

A write program is written to the archive fi le and then a delete program is run to delete the information fromthe online database.

Prerequisite

During an archiving delete run all (activated) archive information structures belonging to an archiving objectare filled automatically. See this note from theSAP Help:

Use transaction SARJ to activate archive info structure SAP_BO_2_WI_001 (Business Object Repository) or

SAP_O_2_WI_001 (Object-Oriented class structures)
http://help.sap.com/saphelp_erp60/helpdata/EN/8d/3e704c462a11d189000000e8323d3a/frameset.htmhttp://help.sap.com/saphelp_erp60/helpdata/EN/8d/3e704c462a11d189000000e8323d3a/frameset.htmhttp://help.sap.com/saphelp_erp60/helpdata/EN/8d/3e704c462a11d189000000e8323d3a/frameset.htmhttp://help.sap.com/saphelp_erp60/helpdata/EN/8d/3e704c462a11d189000000e8323d3a/frameset.htm


4/17



2010 SAP AG

Transaction AOBJ

Use this transaction to set up variants for running the archiving (write) program in test mode and productionmode.

Press ENTER to continue.

Select the POSITION button:

Enter WORKITEM

Select Customizing Settings and WORKITEM and double-click Customizing Settings.


5/17



2010 SAP AG

At this point you will set up variant names to run archiving program in test mode and production mode.

In this example, we will enter TEST as the variant name and click the Variant button.

Leave it in Test Mode and select SAVE option when exiting screen.

Enter Meaning and click SAVE button. Select BACK button.

To set up production variant, enter PROD as description and click the Variant button:


6/17



2010 SAP AG

Select Production Mode radio button and click BACK button.

Select Yes button.

Enter Meaning and click SAVE.


7/17



2010 SAP AG

Click SAVE.

Now you are reading to test the archiving workflows write program to the archive file.

Transaction SWW_SARA Write Program

The archiving program reads work items for archiving and writes them into an archive. The deletion programdeletes the work items from the database. The archiving object is WORKITEM.

Enter transaction SWW_SARA

Click Write


8/17



2010 SAP AG

We will enter the variants created under transaction AOBJ.

Enter TEST and click Maintain

Enter desired parameters and click SAVE


9/17



2010 SAP AG

Click Start Date

Follow normal background job steps

Next click Spool Params to see if you want to print the log


10/17



2010 SAP AG

Execute

SM37 to check

Here are the work items before archiving:

Test Archiving Result Log:


11/17



2010 SAP AG

Now to archive in production mode, enter your production mode variant and follow the same steps as test:

Execute

SM37 to check

The log looks the same except is shows Production mode:


12/17



2010 SAP AG

Transaction SWW_SARA Delete Program

The deletion program deletes the work items from the database. These steps walk you through the deletionprogram.

Click DELETE button.

Select Test Mode

Click Archive Selection.

Select session to delete and press ENTER.


13/17



2010 SAP AG

Click Start Date and run immediate.

Click SPOOL PARAMETERS and select appropriate spool parameters and click EXECUTE.

Message received below is:

Check through normal steps using transaction SM37

Check the test mode output:


14/17



2010 SAP AG

Now follow the same steps and click off test mode and Archive Selection button:

Follow the same steps as test mode, and then Execute after all lights are green:


15/17



2010 SAP AG

Check the production output log:

Now check to see that the workflows are now gone:


16/17



2010 SAP AG

Related Content

Workflow Survey Response to Comments

2010 Workflow Survey Responses

Recent Archiving Blog
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/20479http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/20479http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b00e1e89-bd81-2d10-4c8c-e75bd1b27e22http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b00e1e89-bd81-2d10-4c8c-e75bd1b27e22http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/19841http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/19841http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/19841http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b00e1e89-bd81-2d10-4c8c-e75bd1b27e22http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/20479


17/17


Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.

archiving work items

Documents