sap technical data management

SAP data dictionary tables

DD02T This table contains the text description of SAP tables in the field DDTEXT. The key for this table is TABNAME for the table name. Fields DDLANGUAGE and AS4LOCAL contain the language and activation status respectively.

tables and their housekeeping

ARFCSDATA Transactional RFC. Deletion from transaction SM58 by the owner. Program RSARFCEX should be run regularly to re-attempt unexecuted ones. Program RSARFCER can reorganise deleted ones. Application logs. Program SBAL_DELETE (transaction SLG2) is used to delete logs. Note that these logs can be classified as Operational (i.e. relating to technical processes) and Functional (related to business processes). Operational logs could and should be deleted during this method. A regular scheduled background job can be set up using a standard variant that identifies the operational logs by their log type and removes anything older than needed. This would normally be something like older than 7 days. Functional application logs may need to be retained by the business for extended periods. These can be archived using standard archiving object BC_SBAL. Batch input. Program RSBDCREO. Job name SAP_REORG_BATCHINPUT. Cleans up <DIR_GLOBAL> Background jobs. Program RSBTCDEL, RSBTCDEL2. Job name SAP_REORG_JOBS. Cleans up <DIR_GLOBAL>/<client>/JOBLG Change Pointers. These can be deactivated globally from transaction BD61 or individually from BD50. This is useful to prevent unnecessary entries during data migration or load. They can be deleted with program RBDCPCLR (transaction BD22) Background job runtime statistics. Program RSBPSTDE. Job name SAP_REORG_JOBSTATISTIC. Change documents. Program RSCDOK99 and SD_CHANGEDOCUMENT_REORG can delete. Archive object CHANGEDOCU can be used. Most other archive objects also result in change documents relating to that archive object also being archived and deleted. IDOC tables. They are controlled by using archiving with object IDOC. Some elect to delete and not archive, using program RSETESTD (transaction WE11) Confirmed alerts. Program RSALERTPROC should be scheduled regularly. Program RSALERTCONS checks and deletes inconsistencies. SMTP MIME documents. Can be reorganised with programs RSBCS_REORG and RSBCS_DELETE_MIME. SAP Office documents. There are many programs which deal with different situations: RSBCS_REORG, RSSOTRCL, RSSO_DELETE_PRIVATE, RSSOEXDA, RSSODLWF, RSSOREDF, RSSORESN, RSGOSRE01 SAPscript texts. Phantom texts can be deleted with program RVTEXTE. Generally, archiving is needed to control these tables. Spool jobs. Program RSPO0041, RSPO1041. Job name SAP_REORG_SPOOL. Cleans up <DIR_INSTANCE>/data Update tables. Should not be large, but may become so after particular incidents. They are managed from transaction SM13, including deletion. Some special programs exist to reprocess and keep record of failed accounting document updates: RSM13005 and RFVBER00.

BAL*

BDC*, APQ* BTC* BTCP, BDCPS

BTCJSTAT* CDHDR, CDCLS

EDIDC, EDIDS, EDI40 SALRT SBCMCONT1 SOC3, SOFM, SOOD, SOOS, SOST, SOFFCONT1 STXH, STXL TSP*, TST* VBDATA, VBHDR, VBMOD, VBERROR

BI tables and their housekeeping

RSBERRORLOG RSDDSTATAGGRDEF BI system DTP records with failures. Programs RSB_ANALYZE_ERRORLOG and RSBM_ERRORLOG_DELETE are relevant for management. BI OLAP statistics entries that are not linked to other entries in tables RSDDSTAT*. Program RSDDK_STA_DEL_DATA can be used to delete these entries. BI process chain logs. Delete obsolete chains and logs with reports RSPC_LOG_DELETE and RSPC_INSTANCE_CLEANUP. Be aware of BI Support Pack levels, in particular need to be at levels specified in OSS note 1275318. Lower levels may result in scheduled jobs being deleted.

RSPCLOGCHAIN, RSPCPROCESSLOG

Solution manager housekeeping

DSVASRESULTSGEN Report RDSMOPREDUCEDATA is used to clean up old EWA and similar sessions which can grow quite large in size.