Best-Practice Document Data Management Guide

(1)

SAP Business Suite

Version 6.7

Dietmar-Hopp-Allee 16 D-69190 Walldorf DATE July 2014 SAP PRODUCT(S) Generic PRODUCT VERSION(S) Independent OPERATING SYSTEM(S) All DATABASE(S) All ALM PHASE(S) Run SAP SOLUTION MANAGER 7.1 SP Generic

SAP SOLUTION MANAGER W ORK CENTER(S) Data Volume Management

(2)

1 Management Summary/Introduction

1.1 Motivation

An efficient data management strategy is an important part of trying to maintain good system performance and keep the total cost of your system in check. This is particularly relevant for applications that generate large amounts of data, such as the two environments we describe in our examples: retail and consumer products. However the information and recommendations in this guide are not limited to these two areas. The guide covers the entire component spectrum of SAP Business Suite and SAP NetWeaver.

1.2 Contact SAP

Nevertheless, due to the large number of components and application scenarios of SAP Business Suite, it is impossible to cover all tables in detail. We make every effort to continuously upgrade and expand this guide to include other critical tables from different components. Your feedback is a very important part of this process.

If you notice that a table is missing from our list or that the information for a certain table can be improved, feel free to contact us [email protected] or [email protected].

1.3 SAP Data Volume Management (DVM)

SAP Data Volume Management (DVM) is a framework that helps the solution operations team of an SAP-centric solution to balance the need of business’ access to a wealth of data and IT efforts to maintain storage, databases, and applications.

The methodology provided in this framework consists of best practices, tools, and SAP services along all stages of the DVM life cycle, from initial identification of the challenges all the way through to continuous improvement. It also supports the deployment and operation of a DVM strategy.

It covers concepts for control center for data discovery (alerting, monitoring) and data profiling (analyzing), data management and data archiving for reduction of data volume size and growth (managing the Information Lifecycle), and efficient data storage utilization (database management, data aging) in accordance with legal requirements and corporate policies.

SAP DVM is an essential part of the SAP Active Global Support (AGS) engineering services.

For important information relating to SAP Data Volume Management, see the following quick link in SAP Service Marketplace:

http://service.sap.com/dvm

How does DVM support you?

SAP supports your implementation of a data management and data archiving strategy with a Guided Self-Service for Data Volume Management (DVM), which is an SAP tool-based approach powered by SAP Solution Manager 7.0 and 7.1.

The self-service generates a best-practice document that describes how to handle your largest data objects using the methodologies of data avoidance, summarization, archiving, and deletion, and combines this guidance with a detailed analysis of the data on your system.

The Data Volume Management work center in SAP Solution Manager 7.1 offers capabilities to gain insights into the source of data volume movements in single landscape environments and especially in multisystem landscape environments. The solution is based on SAP Business Warehouse (SAP BW) and provides a holistic landscape overview of your data. This analytical and reporting infrastructure from SAP provides you with a rich array of functions and features that allow you to:

(7)

Get transparency of system landscape data consumption at different levels. Reveal potential for creating/optimizing a data volume management strategy. Leverage best-practice documents to drive your data volume management strategy.

Simulate different data volume scenarios (for example, moderate versus aggressive archiving). Provide monitoring and reporting capabilities for technical KPIs across a system landscape. Provide a compliance check of a corporate data volume management strategy.

SAP offers an expert-guided session on usage of the DVM self-service and setting up the Data Volume Management work center.

For a detailed schedule and registration, see the Expert Guided Implementation Calendar : (https://service.sap.com/Expert-Guided-Implementation)

1.4 Data Volume Management Guide for SAP Banking Services 6.0

You can find more information about data volume management especially for SAP Banking Services 6.0 within the following document, available in Enterprise Support Academy as a best-practice document:

https://service.sap.com/sap/bc/bsp/spn/esa_redirect/index.htm?gotocourse=X&courseid=70193436 Document name: Data Volume Management: Guide SAP Banking Services 6.0

The document helps you in the following topics:

Know archiving and deletion processes in a Banking Services 6.0 system that is used for account management.

Understand dependencies between the different objects and the commonly used residence times for the objects.

Learn how analyze the system and the biggest gowing objects.

1.5 SAP Information Lifecycle Management (SAP ILM)

Information has a life cycle. It is created, it lives within databases and systems, it changes, and it is archived and eventually deleted. With SAP Information Lifecycle Management (SAP ILM) companies can meet their data retention, data destruction, and system decommissioning requirements and obtain compliance with legal and regulatory mandates. As a result, SAP Information Lifecycle Management (SAP ILM) helps companies streamline their technical infrastructure, reduce IT costs, and improve IT risk and compliance management.

SAP Information Lifecycle Management (SAP ILM) is based on the following pillars: Data archiving (active data and system):

o Analyze data volumes.

o Securely move data from database to archive. o Access archived data conveniently.

Retention management (end-of-life data):

o Define and manage all retention policies across the enterprise. o Manage destruction of data responsibly based on policies. o Enforce retention policies.

o Use secure information lifecycle management– aware storage (partner offerings). o Perform e-discovery and set legal holds.

(8)

o Decommission SAP and non-SAP legacy systems to a central retention warehouse. o Enforce retention policies on data from shut-down system.

o Run reporting on data from shut-down system (SAP Business Warehouse (SAP BW) and local reporting).

o Use predefined business warehouse queries for reporting.

o Interpret and understand data in archives without help of original system.

To learn more about SAP Information Lifecycle Management (SAP ILM), please contact your SAP representative, write to us [email protected], or visit us on the Web at

http://scn.sap.com/community/information-lifecycle-management.

1.6 Examples of Data Growth in SAP Systems

1.6.1 Retail

In the retail environment, data growth is strongly affected by such factors as the number of articles or stores of a company, which can reach the following orders of magnitude:

Number of articles = 105 Number of stores = 103

Because much of the data is processed and updated on article or store level, this order of magnitude can reach 108. An update of a given product can affect several different areas:

Article data at store level (such as stock or valuation data) Listing conditions

Processing of sales data from stores using POS inbound (which can result in inventory corrections and revenue postings)

Depending on the master data, Customizing settings, and business processes, data growth in this type of environment can reach several gigabytes a day.

(9)

Database Growth

0

100

200

300

400

500

J a n F e b M a r A p r M a y J u n J u l A u g S e p

Month

[G

B

]

Month Size (in GB) Monthly Growth (in GB)

January 33.17

The statistics in this example reflect the following:

In January and February, the project was still being implemented.

In March, a noticeable increase in data volume was recorded. This could be due to the following: o The customer started live operations in certain stores.

o Legacy data was copied from previous systems.

The data volume increased dramatically during subsequent months for the following reasons: o Live operations are running normally.

o Additional stores have gone live.

The monthly data growth has stabilized at a normal level.

In October, the data growth dropped off considerably. It increased slightly in November, but not at the same aggressive rate as in previous months. Assuming that business continued under normal conditions, the notable decline in data growth can be attributed to the following factors:

o The updating of data not important from a business point of view, was reduced. o Data from completed business processes was archived.

o Data that was no longer needed was deleted from the database.

Based on the behavior of the data in this example, we can draw the following conclusions:

In some installations, data growth can begin to increase sharply only a short time after the system has gone live, and the appropriate measures have to be taken to reduce this growth. Thus, how long a system has been productive is not always the best point of reference for deciding whether or not to begin to archive or prevent data. The only reliable indicators for making this decision are the actual amount of data in your system and the growth rate of this data.

(10)

To make sure that your data volumes do not grow too large, too quickly, you must implement data management measures, such as data archiving and data avoidance, as soon as possible after go-live

1.6.2 Consumer Products

The following table shows the largest database tables used by a consumer products (CP) installation:

Nam e Size

(in GB )

Mon thl y grow th (in G B)

Description

FILC A 83.97 7.18 Line items for cons olidation GLP C A 78.41 5.81 Ac tu al line item s in Profit

C enter Accounting

ACC TIT 63.99 5.23 Interme diate da ta from Materia l M anagem ent fo r subseq uent p ostin gs to FI.

CO EP 53.76 4.32 C O object: Line item s GL FUN CA 42.47 3.37 Ac tu al line item s fo r F I BSIS 22.73 1.84 O pen lin e item s for G/L

acc ounts 344.33 27.75

Size (in GB) M onthly grow th (in GB)

Total of d ata base tables inc ludin g indexes

626.00 50.55

The data contained in the table was gathered on a key date.

The monthly growth figure is an average calculated over several months.

As the data presented here relates to a CP installation, the sequence of tables differs somewhat from the sequence of tables used by a typical retailer. This is particularly true, for example, of the tables for FI consolidation and the special ledger.

The monthly increase in data in the FI tables represents a large proportion of the total volume on the database, thus making performance-related measures unavoidable if the increase of data on the database is to be reduced.

Based on the data in this scenario, we can draw the following conclusions:

Data archiving can be most effective in reducing data volumes if it targets specific critical tables with the help of the relevant archiving objects. Therefore, it is important that you implement the archiving objects that affect the most critical tables first.

Which tables are the most critical depends largely on the installation of each individual customer. Therefore, it is impossible to say which archiving objects would be best to use and when to use them.

(11)

2 Goal of Using this Best-Practice Document

This document provides SAP customers and consultants with information about tables that may show a strong growth in data volume. Additional table information is also provided, for example, about how to deactivate updating, whether you can summarize (aggregate) data, and how data can be removed from the tables. Furthermore, we provide hints and recommendations on performance-critical processes and how they can be improved by decreasing data volumes.

For important information relating to performance issues, see the following quick link in SAP Service Marketplace:

http://service.sap.com/performance-scalability

You can find the Data Management Guide document via the following link:

http://service.sap.com/ilm Data Archiving Media Library Literature & Brochures.

We recommend you set the following priorities: 1. Data prevention/data avoidance

Technically, it is possible to deactivate updating for certain types of data. If, from a business point of view, you do not require this data, you should deactivate updating.

Example: Switch off updating for table ACCT* 2. Data aggregation/data summarization

In some cases, data can be aggregated/summarized at a higher level, for example, by generating totals. You should use aggregated/summarized data if it provides you with the sufficient level of information that you require for your business processes.

Example: Aggregate profit center accounting data (table GLPCA). For retail customers, line items are usually not necessary because their data volumes are too high for reporting.

3. Deletion

You can delete a lot of data that you do not want to archive soon after it has been created in your system.

Example: Spool data (for more information, seeHousekeeping).

Before you delete data records from the system, make sure that they are no longer referenced to any other data that requires that these records remain in the system. If so, do not delete the data records.

4. Archiving

Data archiving handles data that cannot be prevented or easily deleted. You should examine archiving possibilities as early as possible in the implementation process (blueprint project preparation), and long before you go live.

Check how long you want to retain your data in your system. You should only archive data that you no longer require for live operations. Archiving can only, therefore, be used in a limited context when reducing the amount of data in your system.

Example: Archiving of accounting documents using archiving object FI_DOCUMNT. This archives header data (table BKPF) and items data (cluster RFBLG).

(12)

Note:

The measures in the aforementioned examples were applied in actual projects (for details, see the section for each table). Before you adopt any of these measures, make sure that it can be applied to your business context.

Check SAP Notes regularly to find out about any new data archiving developments. You can use the terms Archiving, ADK, or the name of the relevant archiving object when searching for any new developments in SAP Notes.

If you are new to data archiving and want to familiarize yourself with this topic, you can read the document "Introduction to SAP Data Archiving” in the SAP Service Marketplace. This document provides an excellent overview of the technology behind data archiving and discusses the relevant processes and settings.

You can find this document at http://service.sap.com/ilm Data Archiving Media Library Literature & Brochures.

For a comprehensive description of individual archiving objects, see the SAP Library under: o SAP R/3: Cross-Application Components Archiving Application Data (CA-ARC) o SAP R/3 Enterprise: Scenarios in Applications Data Archiving

o SAP ERP: SAP ERP Central Component Scenarios in Applications Data Archiving (Address:http://help.sap.com)

(13)

3 Which Tables Are Examined?

The following tables are commonly associated with high data growth in customer production systems. The table below shows if it is possible to avoid, aggregate (summarize), delete, or archive data in each of the listed tables. For more information, see the detailed description of the table in question or the relevant SAP Notes.

This guide does not include all tables for which an archiving solution exists. Rather, it deals with those tables for which data growth may be a problem.

The tables are listed in alphabetical order. If more than one table belongs to a table family, then the sort order is based on the main table (if known).

Much of the information is release-specific and cannot be applied to all releases. Deletion is marked as not being possible if this is done only in the context of archiving.

Legend:

= possible = not possible

BW = SAP Business Warehouse (SAP BW) BKM = SAP for Banking

CRM = SAP Customer Relationship Management (SAP CRM) ERP = mySAP ERP/SAP R/3 Enterprise/SAP R/3

EWM = SAP Extended Warehouse Management (SAP EWM) HK = Housekeeping measures (seechapter ‘Housekeeping’) ISU = SAP for Utilities

NW = SAP NetWeaver/SAP Basis ST = SAP Solution Manager tool

SRM = SAP Supplier Relationship Management (SAP SRM)

Table Description C o m p o n e n t A v o id a n c e S u m m a ri z a ti o n D e le ti o n A rc h iv in g L a s t C h a n g e d in V e rs io n

1. _{/BA1_R4_REC_BP} _{Result record header table} balance processor

BKM 5.9

2. _{/VIRSA/ZFFTNSLOG,} /VIRSA/ZFFCDHDR, /VIRSA/ZVIRFFLOG

Firefighter Logs for governance, risk and compliance

NW 6.3

3. /SCWM/DOOR_SRACT, /SCWM/TDOOR

Door activities within SAP EWM

EWM 6.6

4. _{/SCWM/TU_SR_ACT,} /SCWM/TU_STATUS

Transportation units within SAP EWM

EWM 6.6

5. _{/SCWM/WAVEITM,} /SCWM/WAVEHDR

Wave management within SAP EWM

(14)

6. _/SCWM/WHO _{Warehouse order processing} within SAP EWM

EWM 6.6

7. _AABLG _{Cluster table for CO}

settlement documents (tables AUAA, AUAB, AUAO, AUAS, AUAT, AUAV, AUAW, AUAY)

ERP 5.4

8. _{ACCTHD, ACCTCR,} ACCTIT

Follow-up posting data from MM

ERP 6.1

9. _ADQUINDX _{Business addresses INDX} _NW _6.7

10. _{APQD, APQI, APQL} _{Batch input directory} _NW _6.1

11. _ARFCSDATA _{Outgoing RFCs} _NW _5.4

12. _{BALHDR*, BALDAT,} BALC, BAL_INDX, BALM*

Application log: Log messages

NW 6.7

13. _{BBP_TRANSXSTRING} _{Temporary working storage} for attachments

SRM 6.4

14. _BBPCONT _{SAP SRM attachments} _SRM _6.4

15. _{BBPD_PD_INDEX_I,} BBPD_PD_INDEX_H

SAP SRM index tables SRM 6.4

16. _{BDCP, BDCPS} _{Change pointers} _NW _4.6

17. _{BKPF, RFBLG (esp.} BSEG, BSEC, BSED, BSET), and BSIS, BSAS, BSIM

RFBLG = Cluster for FI documents (BSEG = FI document items, BSEC = CPD data, BSED = bill of exchange fields, BSET = tax data), secondary indexes (BSIS = G/L accounts – open items, BSAS = G/L accounts – cleared items, BSIM = article documents in retail)

ERP 6.1

18. _BTC* _{Tables for background}

processing

(15)

Table Description C o m p o n e n t A v o id a n c e S u m m a ri z a ti o n D e le ti o n A rc h iv in g L a s t C h a n g e d in V e rs io n 19. _CE(1-4)xxxx (xxxx = operating concern)

Results tables and profitability analysis

(for example, CE1xxxx line items)

ERP 5.7

20. _{CDHDR, CDCLS} _{Cluster structure for change} documents

NW 6.1

21. _CKIS Items unit costing/itemization

product costing ERP 4.5

22. _CKMI1 Index for accounting

documents for material/article ERP 5.3

23. _COEJ _{Plan line items in cost}

accounting

ERP 5.1

24. _COEP _{CO object: Line items (by}

period)

ERP 4.5

25. _COSB _{Total variances/results}

analyses for CO Object

ERP 5.0

26. _{COSS, COSP} _{Cost totals in cost accounting} _ERP _4.5

27. _{CRMD_MKTTG_TG_*} _{SAP CRM marketing target} groups

CRM 6.7

28. _{CRMD_ORDER_INDEX} _{Index for SAP CRM business} transaction

CRM 5.2

29. _{CRMD_ORDERADM_*} _{SAP CRM documents} _CRM _6.7

30. _{CRMD_PARTNER,} BBP_PDIGP

SAP SRM business documents

SRM 6.4

31. _{CRMD_SCHEDLIN} _{Schedule lines for items of a} SAP CRM business

transaction

CRM 5.2

32. _{CRM_JEST} _{Status information for SAP} CRM business object

CRM 5.2

33. _{D010* ((D010L,} D010TAB, D010S, D010Q, D010INCA)

(16)

Table Description C o m p o n e n t A v o id a n c e S u m m a ri z a ti o n D e le ti o n A rc h iv in g L a s t C h a n g e d in V e rs io n 34. _{DBERDL, DBERDLB,} DBERDZ and ERDK, ERDB, ERDO, DBERDR, DBERDU

Print document line items and headers

ISU 5.5

35. _DBTABLOG _{Table change logs} _NW _6.6

36. _DBERCHZ1-8,

DBERCHZ, and ERCHC (also ERCHO, ERCHP, DBERCHU)

Billing document line items and headers

IS-U 5.5

37. _DDLOG _{Buffer synchronization data} _NW _4.8

38. _{DFKKOP, DFKKOPK,} DFKKKO

Contract accounting documents

ERP 5.5

39. _DFKKRDI _{Revenue distribution FI-CA} _ERP _6.7

40. _{DPAYH, DPAYP} _{Payment program FI-CA} _ERP _6.0

41. _{DSVASRESULTS*} _{Service sessions in SAP} Solution Manager

ST 6.5

42. _DYNPLOAD, DYNPSOURCE

Screen loads, screen source information

NW 6.7

43. _{E070, E071, E071K} _{Change and Transport} System

NW 6.2

44. _{EABL, EABLG} _{MR documents} _ISU _5.5

45. _{EDI40, EDIDS} _{IDoc data and status records} _NW _5.3

46. _{EIPO, EIKP} _{Import/export data in foreign} trade

ERP 5.6

47. _{EKKO, EKPO, EKBE,} EKKN

Purchasing tables ERP 5.8

48. _ERCH _{Billing document headers} _ISU _6.6

49. _ERDK _{Print document headers} _ISU _6.6

50. _FAGLFLEXA _{FI General Ledger Accounting} (new): Actual line items

(17)

Table Description C o m p o n e n t A v o id a n c e S u m m a ri z a ti o n D e le ti o n A rc h iv in g L a s t C h a n g e d in V e rs io n 51. _{FAGL_SPLINFO,} FAGL_SPLINFO_VAL

FI General Ledger Accounting (new): Splitting information

ERP 6.2

52. _FILCA _{Actual line items in}

consolidation

ERP 4.5

53. _FMIFIIT _{FI line items in funds} management

ERP 6.5

54. _GLPCA _{Profit center line items} _ERP _4.6

55. _GREP File of stored reports for

Report Writer ERP 6.0

56. _IDOCREL, SRRELROLES

Object link data _NW _6.3

57. _INDX System table INDX _NW _6.7

58. _JEST Status control data _ERP _6.0

59. _LIPS Delivery items _ERP _4.5

60. _LTAP _{Transport order item} _ERP _4.7

61. _{MAPR, PROP, WFCS_} WRFT

Sales forecast ERP 4.9

62. _{MARC, MARD, MBEW} _{Material master data at plant} level (plant, storage location, valuation)

ERP 4.7

63. _MBEWH _{Material valuation – history} _ERP _4.7

64. _MSEG _{Article document items} _ERP _6.1

65. _{NAST, CMFP, CMFK} _{Message and error} management tables

ERP 5.4

66. _PCL2 _{RP Cluster 2: Different HR}

data (mainly payroll and time evaluation data)

ERP 4.5

67. _PCL4 _{RP Cluster 4: Different HCM}

data (including remuneration statement, short and long-term documents for infotype changes)

(18)

Table Description C o m p o n e n t A v o id a n c e S u m m a ri z a ti o n D e le ti o n A rc h iv in g L a s t C h a n g e d in V e rs io n 68. _PPFTTRIGG, PPFTMETHRU

Post Processing Framework CRM 6.3

69. _{PPOIX, PPOPX} _{Posting index of payroll} results

ERP 5.8

70. _{PRCD_COND} _{Conditions for SAP CRM} business transaction )

CRM 5.2

71. _{PROF, PROH, PRON ,} PROP, PROW

Forecast ERP 5.0

72. _{REGUH, REGUC} _{Tables for payment data} _ERP _5.1

73. _{REPOLOAD, REPOSRC,} REPOTEXT

Report objects NW 6.7

74. _{RESB, RKPF} _{Reservations and dependent} requirements

ERP 5.6

75. _RSBERRORLOG _{Log entries for erroneous DTP} data records

BW 5.8

76. _{RSDDSTATAGGRDEF} _{Statistics data OLAP:} Navigation step/aggregate definition

BW 6.3

77. _{RSMON* and RS*DONE} _{Request administration data} _BW _4.8

78. _{RSPCLOGCHAIN und} RSPCPROCESSLOG

BW process chain _BW 5.7

79. _RSRWBSTORE _{Objects in binary format} _BW _4.8

80. _SACONT01, SASACONT1

Document management in SAP Solution Manager

ST 6.5

81. _SADLSTRECB _{Dynamic part of an address} _ERP _5.0

82. _SALRT* _{Alert management data} _NW _6.3

83. _SBCMCONT1 _{Table for document contents} (import/export)

NW 6.4

84. _{SE16N_CD_DATA,} SE16N_CD_KEY

Table display – Change documents

(19)

85. _SGOSHIST _{generic object services:} object history data

NW 6.7

86. _{SMO*, CDB*} _{SAP CRM mobile application} data

CRM 6.7

87. _SMOKONV _{Conditions for SAP CRM}

business transaction (CRM Middleware)

CRM 5.2

88. _{SOC3 (SOFD, SOFM,} SOOD, SOFFCONT1, SOOS, SOST) Business Workplace/ SAPoffice objects NW 5.3 89. _{SM* (SMMAIN,} SMPARAM, SMSELKRIT)

Schedule Manager tables ERP 5.6

90. _SMO8 _{CRM Middleware tables} _HK _6.7

91. _{SMW3_*} _{CRM Middleware tables} _HK _6.7

92. _{SMW3_BDOC*} _{CRM Middleware/BDocs} _CRM _6.7

93. _{SMWT_TRC} _{CRM Middleware tables} _HK,

CRM

6.7

94. _SNAP _{ABAP/4 snapshot for runtime}

errors

HK 6.7

95. _Snnn _{RIS – Information structures} _ERP _4.9

96. _SO33 _{Logistics Information System}

(LIS) information structure S033

ERP 5.4

97. _{STERM_*} _{SAP terminology} _NW _6.7

98. _{STXH, STXL} _{SAPscript texts} _NW _5.8 99. _{SWW_*, SWWWIHEAD,} SWWLOGHIST, SWPNODELOG, SWPSTEPLOG Work items NW 6.4 100. SWFRXIHDR, SWFRXICNT, SWFRXIPRC XI adapter NW 6.6

(20)

101. SXMSCLUR, SXMSCLUP XML message of the Integration Engine

NW 6.4

102. SXMSPFRAWH PI SXMS performance data NW 6.6

103. SXMSPHIST, SXMSPHIST2

Historical XML messages NW 6.4

104. TBTC* Background jobs tables HK 6.7

105. TPRI_PAR ABAP print parameter storage HK 6.7

106. TSP* Spool tables HK 6.7

107. TST01 TemSe: List of objects and parts

HK 6.7

108. TST03 Spool data from the print and output controller

NW 6.7

109. TXMILOGRAW External job scheduling tools logs

HK 5.6

110. VARI ABAP/4: Variant storage HK 6.7

111. VBDATA Update request data NW 5.4

112. VBFA Sales document flow ERP 5.0

113. VBFS Collective processing logs ERP 5.0

114. VBRP Billing items ERP 4.7

115. VBOX Rebate processing ERP 6.3

116. VEKP Header table for handling

units

ERP 5.6

117. WLK1 Listing conditions ERP 4.9

Some of the above-mentioned tables can be archived using several different archiving objects. Archiving and deleting data that was created during different time periods can lead to a fragmentation of the database tables. The affected data blocks can only be used for new data if you perform a reorganization.

Using the table analysis tool (transaction TAANA), you can analyze the distribution of table entries based on specific fields (for example, organizational unit, time periods).

(21)

This helps you decide which archiving objects to use to achieve the greatest benefit through data archiving. The fields for carrying out a table analysis are determined via an analysis variant. If part of the standard, these variants are listed in the documentation for the corresponding table under the data archiving section.

For more information on table analyses, see the documentation in the SAP Library for SAP NetWeaver 7.0 (2004s) under SAP NetWeaver by Key Capabilities Solution Life Cycle Management by Key Capabilities Data Archiving Introduction to Data Archiving Table Analysis.

(22)

4 Best-Practice Document: Housekeeping

You can delete some types of data from your system very soon after it has been created. You should carry out deletion at regular intervals for the data discussed in this section. See SAP Note 16083 (release-independent). When performing our recommendations, use the recommended job names within the single chapters, as they can be used to check if the jobs have already been active in your system.

Where applicable, we have included a section on the deletion of data under the table-specific sections of this document.

See also SAP Notes:

16083 (release-independent): Standard Jobs, Reorg Jobs

48400 (SAP_BASIS 46B – 710): Reorganization of TemSe and Spool 706478 (release-independent): Preventing strong growth of basis tables

800927 (SAP_APO 30A – 310, SCM 400 – 700): Standard jobs in the SCM/APO area 1034532 (SAP_BASIS 640 – 720): Changes for standard jobs

1411877 (SAP_BASIS 46C – 730): New standard jobs 1829728 (SAP_BW 700 – 740): BW Housekeeping Task List

4.1 Housekeeping for Background Jobs

4.1.1 Administration Data for Background Jobs

Program: RSBTCDEL2

Reorganized tables: BTC*

Job scheduling: Daily (with variants)

Recommended job name: SAP_REORG_JOBS This report deletes old background jobs.

784969 (SAP_BASIS 46C - 640): Program RSBTCDEL2

852351 (SAP_BASIS 46C – 711): Program RSBTCDEL2: Enhancement (2) 1893670 (SAP_BASIS 700 – 740): Problems with RSBTCCNS (SM65)

Important recommendation: Please ensure that report RSBTCDEL2 is replacing the former report RSBTCDEL. Please make sure that you reschedule your jobs with the new report name.

4.1.2 Print Parameters for Background Jobs

Program: RSBTCPRIDEL

Reorganized tables: TPRI_PAR Job scheduling: monthly (with variants)

Recommended job name: SAP_REORG_PRIPARAMS See also SAP Notes:

759682 (SAP_BASIS 620 - 640): Performance problems when scheduling batch jobs 1407635 (SAP_BASIS 700 – 720): Unnecessary database accesses in RSBTCPRIDEL

4.1.3 Runtime Statistics for Background Jobs

(23)

Reorganized tables: BTCJSTAT* Job scheduling: monthly (with variants)

Recommended job name: SAP_REORG_JOBSTATISTIC This report deletes old data from the job runtime statistics.

4.1.4 Consistency Check for Administration Tables of Background Jobs

Program: RSBTCCNS

Reorganized tables: TBTC*

Job scheduling: daily (with variants)

Recommended job name: SAP_BTC_TABLE_CONSISTENCY_CHECK This report checks the consistency of job definitions and repairs erroneous entries. See also SAP Notes:

1549293 (SAP_BASIS 700 - 740): SM65: Improvements in consistency check 1893670 (SAP_BASIS 700 – 740): Problems with RSBTCCNS (SM65)

4.1.5 Orphaned Temporary Variants in Table VARI

Program: BTC_DELETE_ORPHANED_IVARIS

Reorganized tables: VARI

Job scheduling: weekly (with variants)

Recommended job name: SAP_DELETE_ORPHANED_IVARIS

If you schedule a report as a background job, the system generates a variant called &0000000000xxx for the report. However, if an error occurs during scheduling, the generated variant is not deleted.

1021775 (SAP_BASIS 46C – 711): Orphaned temporary variants in the table VARI

4.2 Housekeeping for Spool Data

4.2.1 Spool Data and Administration Data for Spool Jobs

Program: RSPO1041

Reorganized tables: TSP*

Recommended job name: SAP_REORG_SPOOL This report deletes old spool data.

130978 (SAP_BASIS 46A - 710): RSPO1041 - Replacement for RSPO0041

Important recommendation: Please ensure that report RSPO1041 is replacing the former report RSPO0041. Please make sure that you reschedule your jobs with the new report name.

4.2.2 Spool Data Consistency Check

Program: RSPO1043

Reorganized tables: TSP*, TST01, TST03 Job scheduling: Daily (with variants)

(24)

Report RSPO1043 enables continuous monitoring of inconsistent spool objects (example: no entries in TST01 but entries in TST03 for a selected spool are available). Just as in RSPO0043, the write locks are analyzed and, if necessary, deleted. In contrast to report RSPO0043, report RSPO1043 can run parallel to the other activities in the background. To do this, the report must run daily.

98065 (SAP_APPL 40A - 604): Spool consistency check with RSPO1043 as of 4.0A 1748033 (SAP_BASIS 46C – 740): RSPO1043 does not delete all inconsistencies

Important recommendation: Please ensure that report RSPO1043 is replacing the former report RSPO0043. Please makes sure that you reschedule your jobs with the new report name.

4.2.3 Orphaned ADS Spool Files

Program: RSPO1042

Recommended job name: SAP_ADS_SPOOL_CONSISTENCY_CHECK

The DIR_GLOBAL directory or in the client-specific ADSP subdirectories contain files starting with SPOOL. Some of them may be very old. Usually, these files are removed by deleting the relevant spool request. However, under certain circumstances, these files may remain in the system as "orphaned" files. To reorganize these files, you can use report RSPO1042.

1440439 (SAP_BASIS 700 – 740): New Standard Jobs (2) 1493058 (SAP_BASIS 700 – 740): Orphaned ADS files

4.3 Orphaned Job Logs

Program: RSTS0024

Reorganized tables: TST01

Job scheduling: Weekly (with variants)

Recommended job name: SAP_REORG_ORPHANED_JOBLOGS

The TST01 table can contain job log headers or files that are older than the jobs in the TBTCO table. To delete such “orphaned” job logs, you can use report RSTS0024.

666290 (SAP_BASIS 46B – 710): Deleting “orphaned” job logs

1293277 (SAP_BASIS 46C – 720): Report RSTS0024 runs for a very long time 1436325 (SAP_BASIS 46C – 720): TemSe objects JOBLGX_ZOMBIE

1605708 (SAP_BASIS 46C – 802): RSTS0024 terminates with COMPUTE_INT_TIMES_OVERFLOW

4.4 TemSe: File System Against TST01

Program: RSTS0043

Job scheduling: Weekly (with variants)

Recommended job name: SAP_REORG_ORPHANED_TEMSE_FILES

Files (for example, spool requests, job logs, batch input logs) are stored on the file system but the relevant entries are missing in table TST01.

(25)

936049 (SAP_BASIS 46C - 711): TemSe: Consistency check, file system against TST01 1246731 (SAP_BASIS 640 – 731): RSTS0043: Some of the job logs are not recognized 1272528 (SAP_BASIS 46C – 711): RSTS0043: All orphaned logs are not deleted 1676870 (SAP_BASIS 46C – 731): RSTS0043 incorrectly deletes files

4.5 Administration Data for Batch Input

Program: RSBDCREO or

RSBDC_REORG from release 4.6D onwards (different selection screen) Reorganized tables: BDC* and APQ*

Recommended job name: SAP_REORG_BATCHINPUT This report deletes old batch input sessions.

147354 (release-independent): Batch input: Reorg. and delete sessions and logs

4.6 ABAP Short Dumps

Program: RSSNAPDL

RSNAPJOB (program to schedule report RSSNAPDL as a job) Reorganized tables: SNAP

Recommended job name: SAP_REORG_ABAPDUMPS This report deletes old ABAP short dumps.

11838 (release-independent): Deleting short dumps from the SNAP table 1091769 (SAP_BASIS 700 – 710): RSSNAPDL deletes too many short dumps

4.7 External Job Scheduling Tools

Program: RSXMILOGREORG

Reorganized tables: TXMILOGRAW

Job scheduling: weekly (recommended) Recommended job name: SAP_REORG_XMILOG

If you use external job scheduling programs, XMI log entries are written to table TXMILOGRAW. As a result, this table can grow quite large and should be reorganized periodically.

As of SAP R/3 4.6C, program RSXMILOGREORG is available as part of the standard. For earlier releases, see SAP Note 182963 (SAP R/3 3.1I – SAP NetWeaver AS 6.40). This report deletes XMI logs.

A weekly reorganization of your tables should delete any entries that are older than seven days. If the table is already large, we recommend that you use the reorganization method TRUNCATE at database level. This can be done without any negative consequences because the table does not have any dependencies to other tables. For more information, see SAP Note 182963.

SAP Note 852933 (SAP NetWeaver AS 6.40 – 7.00) provides information about how to speed up the deletion process when you are using reorganization program RSXMILOGREORG.

(26)

182963 (SAP_APPL 31G – 46B): Huge increase in Table TXMILOGRAW 852933 (SAP_BASIS 620 – 700): XMILOG-Reorg: Performance optimization

1715863 (SAP_BASIS 46C – 731): Entries too frequent in XMI log

4.8 Checking Database Indexes

If your system has very slow response times, check whether your database indexes are fragmented in any way. If your system is showing signs of fragmentation, regenerate your indexes or defragment them. If changes are made to tables on a regular basis, we recommend that you regenerate your indexes or defragment them on a regular basis, such as once a week.

Important recommendation: Indexes should be regenerated regularly in retail if your database does not do so automatically (for example, Oracle databases cannot perform this function).

4.9 Housekeeping for SAP CRM

4.9.1 SAP CRM Inactive Products

Program: COM_PRODUCT_DELETE_INACTIV

Recommended job name: SAP_REORG_CRM_PRODUCTS_INACTIV

You can use report COM_PRODUCT_DELETE_INACTIV to delete the inactive products indicated for deletion in SAP CRM.

432875 (BBPCRM 20C - 300): Deleted inactive product cannot be created again

4.9.2 CRM Middleware Tables

Program: SMO6_REORG

SMO6_REORG2 (as of SAP CRM 4.0 support package 6) Reorganized tables: SMO8* (SAP CRM 2.0B and 2.0C)

SMW3_* and SMWT_TRC (both as of SAP CRM 3.0) Job scheduling: daily (with variant SAP&_MW_REORG)

Recommended job name: MW_REORG

In Customer Relationship Management (SAP CRM) and Supplier Relationship Management (SAP SRM), it is common to see strong growth of BDoc and trace tables in CRM Middleware. This could have a negative impact on performance during the processing of BDocs.

You can delete processed BDocs using transaction SMO8REORG. As a general rule, you should schedule report SMO6_REORG as a background job and run it on a daily basis to reorganize your trace data and processed BDocs regularly.

See SAP Note:

206439 (BBPCRM 2.0 – 4.0): Reorganization of tables in CRM Middleware

675725 (BBPCRM 3.1 – 4.0): Unnecessary BDocs in SAP SRM (EBP) from CSA_MASS_BUPA Queue

713173 (BBPCRM 4.0 – 5.0): Update of the CRM Middleware reorganization 1876287 (BBPCRM 5.0 – 7.13): Performance Optimization Of SMO6_REORG

Important recommendation: As of SAP CRM 4.0 Support Package 6, there is a new report available: SMO6_REORG2 (please see also SAP Note 713173, BBPCRM 4.0 – 5.0). This report

(27)

can be scheduled on a daily basis like report SMO6_REORG, but please take care that only one report is executed.

4.10 Housekeeping for SAP Solution Manager (BW Housekeeping for Diagnostics)

Program: E2E_HK_CONTROLLER

Job scheduling: daily

Recommended job name: E2E BI HOUSEKEEPING

A central housekeeping process (report E2E_HK_CONTROLLER) runs on a daily basis on SAP Solution Manager ABAP. Please make sure that the following SAP Notes are implemented in your system: See SAP Note:

1480588 (Solution Manager ST 400 – 710): ST: E2E Diagnostics - BI Housekeeping - Information 1266915 (SAP BI_CONT 703 – 705): ST: Housekeeping of BI Hashtables

1254977 (SAP BI_CONT 703 – 704): ST: Memory Problem for E2E Housekeeping job

1510178 (SAP BI_CONT 704, Solution Manager ST 400): InfoCubes remain in loading mode after Housekeeping

1510411 (SAP BI_CONT 704, Supportpackage 09): Corrections for E2E BI Housekeeping 1794478 (ST 710): Monitoring and Reporting: High Redo log volumes

By default, E2E BI Housekeeping includes the following tasks:

Aggregation of data, that is, data is transferred from InfoCubes with hourly resolution to those with only daily resolution (with ST400, aggregation of data to an hourly resolution is only supported for 0SMD_* InfoCubes).

Deletion of data, that is, data from the higher volume cubes is deleted if it is older than a specified period of days (default is 91 days).

Update statistics (available with ST-BCO 7.10 [ST710]). Compress InfoCube (available with ST-BCO 7.10 [ST710]). Delete requests (Available with ST-BCO 7.10 [ST710]).

Logs of E2E BI Housekeeping can be found in the spool log of report E2E_HK_CONTROLLER as well as in the application log (TA SLG1) in the BW client (Available with ST400 SP24, Object/Subobject is

BW_PROCESS/REPORT [ext. number E2E_HK_CONTROLLER]).

4.11 Housekeeping for SAP BW Systems

For performing a regular housekeeping on your SAP BW system, please take care of SAP Note 1829728, which provides detailed information about regular tasks and tools.

See SAP Note:

1829728 (SAP_BW 700 - 740): BW Housekeeping Task List

4.12 Housekeeping for SAP EWM Systems

In addition to the above-mentioned standard jobs, you must schedule SAP EWM-specific jobs in your SAP system. To keep the SAP EWM application running smoothly, please ensure that the housekeeping tasks are scheduled regularly.

For details see the “Application Operations Guide, SAP™ Extended Warehouse Management Operations Guide” for SAP EWM in the SAP Service Marketplace:

(28)

1100035870000015092&_HIER_KEY=601100035870000179414&_HIER_KEY=601100035870000179427& _HIER_KEY=601100035870000214478&_HIER_KEY=701100035871000566961&

(29)

5 Best-Practice Document: Detailed Table-Specific Information

5.1 SAP NetWeaver

5.1.1 ADQUINDX: Business Addresses INDX

Table ADQUINDX is used as INDX-type table for quarterly adjustment addresses. Quarterly adjustment is carried out if postal address validation using reference data is active.

Postal addresses can be validated using the standard SAP regional structure (city file) or via third-party providers.

When the quarterly adjustment is executed, the addresses of business partners in the SAP R/3 system are replicated in the SAP CRM system. When the quarterly adjustment is used and running, address changes are saved outside the usual object maintenance of the applications.

5.1.1.1 Avoidance Cannot be used

5.1.1.2 Summarization Cannot be used

5.1.1.3 Deletion

Table ADQUINDX is populated by both RSADRQU1 and RSADRQU2 reports. If there is a large number of addresses in ADRC to be processed, the size of ADQUINDX will increase because RSADRQU1 will first write the indexed entries, then RSADRQU2 will write the modified data into this table. Finally, RSADRQU3 picks up data from ADQUINDX and writes into database (ADRC). Then it deletes all the entries from ADQUINDX. So RSADRQU3 has to run for the entry in table ADQUINDX to be deleted.

5.1.1.4 Archiving Cannot be used

5.1.2 APQD, APQI, APQL: Batch Input Folders

Batch input folders are stored in tables APQD (batch input object data), APQI (contents of queues), and APQL (links between the folders and the logs; the logs themselves are stored in the TemSe files; see also SAP Note 175596, SAP_BASIS 46A - 700). Batch input folders are created in the background when data is transferred to an SAP system (for example, during a legacy data transfer). In the following cases, these folders remain in the tables:

If they were not processed If they are corrupt

If they were created with the KEEP indicator activated. 5.1.2.1 Avoidance

You can keep these tables from growing unnecessarily large by deactivating the KEEP indicator when

making the settings for the folder. If this indicator is deactivated, the folder will be automatically deleted after it has been processed. However, you will not be able to display this folder later, and would not be able to trace any activities that were executed in the past, for example. Nevertheless, this is rarely necessary; instead, you can view the batch input logs that are not automatically deleted.

(30)

36781 (release-independent): Explains how you can reduce the size or curtail the growth of table APQD

24438 (release-independent): Contains tips for how to handle batch input folders and explains under which conditions these folders can be deleted

You can delete processed folders and their logs by client, using program RSBDCREO (see SAP Notes 16083 and 25219). From SAP Basis 4.6D on, you can also use deletion report RSBDC_REORG (see SAP Note 147354). You can choose whether the folders, the logs, or both should be deleted. When folders are deleted, data records are deleted from tables APQI and APQD. When logs are deleted, data records are deleted from table APQL. If you want to delete folders without logs (no APQI entry) data records will be deleted in APQL and in the TemSe entry.

It is also possible to delete logs that no longer have a folder with this program. You can delete corrupted folders via transaction SM35.

See the following SAP Notes:

16083 (release-independent): Standard jobs, reorganization jobs 25219 (release-independent): RSBDCREO and parametrization

147354 (release-independent): Batch input: Reorg. and delete sessions and logs 5.1.2.4 Archiving

Batch input folders cannot be archived. However, you can archive the logs of processed folders (status “processed”) with archiving object BDCLOGPROD, even if their folders have already been deleted. You can use transaction SARA to access the log archiving functions, or transaction SM35P using Goto Archive…. Overview of scenarios:

The following scenarios exist for deleting and archiving folders and their logs:

A folder can be deleted regardless of whether the log has been archived or not. A log can be deleted when its folder has already been deleted.

A log can be archived regardless of whether the folder has been deleted or not. Table analysis

If you want to run a table analysis (transaction TAANA) before data archiving (seechapter 'Goal of Using this Best-Practice Document'), the following analysis variant is offered for the corresponding tables:

Table Analysis Variant

APQI STANDARD

APQL STANDARD

Also see SAP Notes:

147354 (release-independent): additional information for the reorganization of folders and logs, and tips for RSBDC_REORG.

175596 (SAP BASIS 46A - 700): improving runtime when large folders are processed or many folders are processed in parallel.

(31)

5.1.3 ARFCSDATA: Outgoing RFCs

Transactional RFCs (tRFCs) and queued RFCs (qRFCs) called in the sending system are stored in tables ARFCSDATA (data of the sent RFCs) and ARFCSSSTATE (status of the sent RFCs). After the RFC has been executed in the target system, the corresponding table entries are deleted. However, if an error or an exception occurs during the call, the system resets all database operations that were started by the previous call and writes a corresponding error message into the ARFCSSTATE file.

5.1.3.1 Avoidance

In an SAP ERP-CRM scenario, it may occur that the OPEN FI Event 00501015 is run through in the ERP system, even if delivery-related SAP CRM billing is not used. This generates unnecessary entries in table ARFCRDATA in the SAP CRM system (data of the received RFCs). To prevent this data from being created, you can deactivate the event in the ERP system. For more information, see SAP Note 441352 (release-independent).

In a normal work environment, this table should not get too large because the data is usually automatically deleted after the RFCs have been executed successfully. Entries are not deleted only during asynchronous processing, for example, when SAP CRM Mobile Sales is used, or when the RFC calls could not be processed due to an error. These tables can also grow quite large in development or test systems in which tRFC or qRFC errors are not corrected.

Asynchronous processing

Queues with the status NOSEND in the qRFC monitor of the outgoing queue (transaction SMQ1) contain logical units of work (LUWs) that are not sent, but are retrieved by the receiving applications. These queues are only used internally at SAP (by SAP NetWeaver BW or SAP CRM in the communication with SAP CRM Mobile Clients). Even when an LUW was read by an application, this status does not change. Only when this application confirms the retrieval is the LUW deleted from the queue (group confirmation possible). Under no circumstances should this status be changed and the queue be activated using SMQ1! See SAP Note 378903 (release-independent).

Errors by RFC processing

Unsuccessful tRFC calls can be analyzed, processed, and, if necessary, deleted using transaction SM58; unsuccessful qRFC calls can be handled using transaction SMQ1. Before you delete these entries, it is highly recommended that you notify users and system administrators (for example, workflow administration). Also, you should examine the reason for the error and try to eliminate or switch off the error to avoid a resumed growth of the table. A good source of information for this is SAP Note 337592. It describes common causes of errors for different SAP releases and scenarios (for example, when SAP Advanced Planning and

Optimization [SAP APO] and SAP CRM Mobile Client are used). The note also provides possible solutions to these errors. These are listed separately according to outgoing and incoming tRFCs and qRFCs.

In SM58, you can delete the entries either individually (Edit Delete Entry) or as a group (Log File

Reorganize). During this deletion, and also during the deletion of the log file (Log File Delete), only tRFC entries are deleted.

After RFC requests have been deleted, you should perform a reorganization of the corresponding database tables to free up space.

(32)

5.1.3.4 Archiving Cannot be used See also SAP Notes:

371068 (release-independent): tRFC/qRFC: Measures for better performance 81814 (release-independent): tRFC: Executed LUWs are not deleted

378903 (release-independent): Queue status in SMQ1, SMQ2 and table ARFCRSTATE 706478 (release-independent): Preventing strong growth of basis tables

375566 (release-independent): Large number of entries in the tRFC and qRFC tables

5.1.4 sBALHDR*, BALDAT, BALC, BAL_INDX, BALM*: Application Log (Log Messages)

Events can be logged centrally within applications in the log for the application in question. Object logs consist of the following:

Log header with a unique log number (information that clearly indicates who triggered which event with what program or transaction):

o Prior to SAP R/3 4.6C: in tables BALHDR and BALHDRP o As of SAP R/3 4.6C: in table BALHDR

As many log messages as you require, with their relevant status:

o Prior to SAP R/3 4.6C: in tables BALM; BALMP, BALC and BAL_INDX o As of SAP R/3 4.6C: in table BALDAT and BAL_INDX

Logs are given expiry dates. The logs must remain on the database until these dates expire. After the expiry date has passed, the data is deleted from the database. There are often a large number of application logs in the database because no expiry dates are assigned to the logs. If no specific expiry date has been assigned to an application log, the system assigns a very late expiry date.

5.1.4.1 Performance-Critical Processes

Use the following message types to distribute or transfer material/article master data: MATMAS (IDoc type MATMASxx for material master data)

ARTMAS (IDoc type ARTMASxx for article master data)

The application log is used to collect and save messages that are recorded when IDocs are edited. Both IDoc types use the same application log object (MATU) that was created solely for messages relating to material/article master data.

5.1.4.2 Avoidance

See the following SAP Notes:

451706 (SAP R/3 Release 4.6B – 4.6C, SAP BASIS 46D) for reducing the number of process messages and the deletion of process messages (component PP).

183960 (SAP R/3 Release 4.0A - 4.6C) for deactivating the application log for using ALE to edit material master data in the standard system.

460310 (SAP R/3 Release 4.6B – 4.6C) for deactivating the application log for using ALE to edit article master data in SAP Retail. The processing logs can be deactivated after successful test runs – particularly for the initial data transfer.

373688 (SAP R/3 Release 4.0B – 4.6C) on the reduction of logged messages when transferring/distributing material master data.

376555 (SAP R/3 Release 4.0B – 4.6C) on the reduction of logged messages when transferring/distributing article master data.

(33)

When the event manager is used (part of SAP SCM) with links to other SAP applications within SAP Business Suite, such as SAP ERP, SAP CRM, and SAP NetWeaver BW), an entry is generated in the application log for each item under every document type that appears in the event manager. Examples of these entries are goods movements and inbound and outbound deliveries. These kinds of entries are numerous and can cause the log tables BALHADR and BALDAT to grow very large. However, in general the log entries are not needed.

In SAP R/3 Enterprise, you can switch off the updating of these logs in Customizing for all objects (see SAP Note 815682, PI_BASIS 2003_1_620 – 2004_1_640). However, keep in mind that this may stop the updating of some entries that could be necessary. Use the following path in the SAP Reference IMG (transaction SPRO):

Integration with Other SAP Components Event Management Interface Define Application Interface Define Used Bus. Proc. Types, Appl. Obj. Types and Evt Types

In Customizing, select the desired Business Process Type and, in the dialog structure, double-click Define Application Object Types. Then double-click the desired Application Object Type and set the ApplLogDeactivation indicator.

As of SAP ERP 6.0, you can switch off the updating of the application log in Customizing per application object type and/or event type. The path in Customizing is identical to the path named above. Then go through the following procedure to switch off log updating:

Select the desired Business Process Type, double-click Define Event Types and then double-click the desired assignment between Business Processes and Event Type. Then set the

ApplLogDeactivation indicator.

Recommendation: At the beginning, switch on the log update to determine for which objects you need to have the log entries. Then delete the application log (transaction SLG2), for example, after a maximum of five days. If the production system is running smoothly after the initial phase, you may be able deactivate the application log update completely.

5.1.4.3 Summarization

A different database interface is used for application logs as of SAP R/3 4.6C. Shortened logs are stored in table BALDAT, thus reducing the volume of data by factor of 5 to 10. Even if logs are stored in compressed form, this table can, over time, become large. It is therefore advisable to delete logs periodically from the table. You can do this in transaction SLG2. See also SAP Note 195157 (SAP R/3 3.0F – 4.5B, SAP_BASIS 46A - 640).

5.1.4.4 Deletion As of SAP R/3 4.6A:

SLG2 is the main transaction for deleting logs (report SBAL_DELETE, available as of SAP R/3 4.6A). For information on using transaction SLG2, refer to menu path help application help.

See SAP Note 211940 (SAP R/3 Release 4.6A – 4.6C): This supplies a correction for performance improvement when deleting logs.

Before SAP R/3 4.6A:

For releases prior to 4.6A, the following generic programs can be used to delete logs (these reports are also compatible as of SAP R/3 4.6A):

Best-Practice Document Data Management Guide

SAP Business Suite

Version 6.7

Table of Contents

1

Management Summary/Introduction

Database Growth

0

100

200

300

400

500

Month

[G

B

]

2

Goal of Using this Best-Practice Document

3

Which Tables Are Examined?

4

Best-Practice Document: Housekeeping

5

Best-Practice Document: Detailed Table-Specific Information