PDF Data Volume Management - Best Practice 5000000006277

Service Report
Data Volume Management

Best Practice Session
Confidential
SAP System ID EP1

Product version EHP8 FOR SAP ERP
Release 6.0
DB System DB2 for Linux, UNIX and Windows 11.05.0600

Customer
Processed on SAP Solution Manager SPA Service Center

Release SAP SOLUTION MANAGER 7.2 Telephone
Service Tool 720 SP22 Email
Date of Service 07.03.2022 Session No. 5000000006277

Date of Report 11.04.2022 Installation No. 0020486164
Author CCOETZER Customer No.
Authorized for SAP employees delivering SAP Services and Support, authorized partners, and customer employees. Please
forward to authorized recipients only.
Data Volume Management - 07.03.2022
Contents
-
1 Contents..............................................................................................................................................................................2
2 Service Summary................................................................................................................................................................3
2.1 Summary.................................................................................................................................................... .......................4
3 General Information about SAP Data Volume Management (DVM)...............................................................................5
4 Database Resources.................................................................................................................................................. ........7
5 Expected Sizes of Objects and Tables..............................................................................................................................8
6 Tables in Scope...................................................................................................................................................... ............9
7 Analyzed Objects..............................................................................................................................................................10
7.1 Table Change Protocols..................................................................................................................................................11
7.1.1 Table Change Protocols: Deletion.................................................................................................................................11
7.1.2 Table Change Protocols: Archiving...............................................................................................................................12
7.2 Intermediate Documents..................................................................................................................................................13
7.2.1 Intermediate Documents: Deletion................................................................................................................................14
7.2.2 Intermediate Documents: Archiving...............................................................................................................................14
7.3 Change Documents.........................................................................................................................................................22
7.3.1 Change Documents: Avoidance...................................................................................................................................23
7.3.2 Change Documents: Deletion.......................................................................................................................................23
7.3.3 Change Documents: Archiving.....................................................................................................................................24
7.4 Application Logs........................................................................................................................ ......................................25
7.4.1 Application Logs: Avoidance.........................................................................................................................................26
7.4.2 Application Logs: Deletion............................................................................................................................................26
7.4.3 Application Logs: Archiving...........................................................................................................................................27
Confidential Contents 2/29

2 Service Summary
-
Within the scope of the SAP Data Volume Management service, we
detected issues that may affect your business operation and
determined that improvements can be made in your system.
Note: The recommendations provided in this report are based on general experience only. You should test these
recommendations before implementing them in your production system.
-
2.1 Summary
-
Service Information:
The data used for the analysis was collected in system EP1 on 07.03.2022. This data is stored in the SAP Solution
Manager with GUID 0LD1C61P5VEMQ0AZDUFHXTIPL.
The tables analyzed within this report were selected based on the scope you defined within the related GSS Data Volume
Management Questionnaire session by choosing one of the available "input options", for example, "SAP proposed Objects"
or "Manually specify Objects".
The "Expected Sizes of Objects and Tables" section includes an overview containing an estimation of the expected sizes
once all recommendations in this report have been implemented. It summarizes the effects of the recommendations for
each object and table analyzed.
Note:
If you are facing a situation where the size of the analyzed objects is very small in comparison to the overall database size,
we recommend changing the focus of the self-service session.
This is possible after resetting the actual session or creating a new self-service session.
Then, use either "Top relevant Tables" or "SAP Proposed Objects" in preparation step "Select Processing Mode" (if
available). Alternatively, specify your objects to be analyzed manually or select "Top 30 Objects" (if available) within the
expert mode of preparation step "Select Input Options".
Note [relevant for HANA-based systems ONLY]:
The figures for the SAP HANA memory allocation shown in transaction ST04/DB02 differ from the SAP HANA database
size in the DVM service report. The reason is that the 'memory used' shown in ST04 is a combination of the memory used
to store data (column store, row store) and the memory used for processing queries, sorting, and temporary computations.
In contrast, in ST14 (which is used to collect data for this report), we "only" collect the estimated_maximum_memory_size
of all tables defined in the ABAP DDIC and calculate the total. This number is usually significantly smaller (50% smaller, for
example) compared to the number shown in ST04.
For more details, please see 2601931 - DVM Service Session, how to interpret table size for system on HANA database .
Note:
- The reduction potential is calculated from a technical point of view based on best practice residence times.
- Contact your database administrator to find out whether tables need to be reorganized at database level to physically
reduce the table sizes after deleting and archiving data.
- The current monthly growth rate (reduction of future database size) can be reduced by avoiding and summarizing data.
Database growth can also be reduced by regularly deleting and archiving data.
For more information , see the SAP DVM wiki https://wiki.scn.sap.com/wiki/display/TechOps/Data+Volume+Management
From there, navigate to the "SAP Support" section and expand the "Tools" section. Open the link entitled "Appendix to
Service Report".
Please join the SAP Enterprise Support Value Map for Data Volume Management as outlined in SAP KBA 2243625 -
Data Volume Management Value Map - SAP Enterprise Support .
SAP Enterprise Support Value Maps – an empowerment and support program, which provides direct access to SAP
Confidential Service Summary 3/29

experts, interactive social collaboration forums, acceleration of learning, and prescriptive guidance, designed to help you in
adopting intelligent technologies, managing hybrid landscapes, and becoming more agile to focus your resources on
innovation. Value maps guide you through the knowledge, skills, and services needed to address your business
challenges, enabling your company to lead in the experience economy.
Confidential Service Summary 4/29

3 General Information about SAP Data Volume

Management (DVM)
-
The Data Volume Management (DVM) portfolio helps you to set up a data volume management strategy that defines how
to manage and reduce future data growth and the existing database size by following a holistic approach that considers
and integrates the following options: data avoidance, data summarization, data deletion, and data archiving.
While implementing data avoidance and summarization is a one-off activity affecting future data growth, data deletion and
data archiving are recurring operations aimed at reducing the existing data volume.
SAP's service and support portfolio for Data Volume Management (DVM) consists of:
- DVM app as part of the SAP ONE Support Launchpad
- DVM Guided Self-Service
- DVM Continuous Quality Check (CQC)
- DVM Enterprise Support Value Map
- DVM Launchpad in SAP Solution Manager
- DVM Engineering Service (ESRV)
Here are some details for each of these building blocks:
DVM Data Reduction Potential: The Data Reduction Potential application is a cloud-based application that allows you to
monitor your SAP HANA-based system to get insights into the DVM topic, such as:
• An evaluation of the reduction potential for memory and disk.
• Applicable reduction measures with a reduction potential based on SAP's recommended residence times.
• Simulation tool to see the impact of setting your own residence times.
• Time-based and accurate reduction potential calculations for archiving, aging, or both.
"Accurate" reflects the results after the business checks imposed by archiving or aging programs have been applied.
• HANA Memory Usage
• HANA Disk Usage
• Saving Potential on Disk
• Saving Potential in Memory
• Time-based data distribution overview for all analyzed tables
• A suite of SAP-HANA-specific analyses including:
·Tables with more than 1 billion records
·Top growing tables
·Top shrinking tables
·Largest tables
·LoB overview
·Saving potential using inverted hash keys for indexing
The DVM app is available through the SAP One Support Launchpad at the following address:
https://launchpad.support.sap.com/#/dataoverview
DVM Guided Self-Service: SAP supports your implementation of a data management and data archiving strategy with a
Self-Service for Data Volume Management (DVM), which is an SAP tool-based approach powered by SAP Solution
Manager.
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.
The best practice document shows the type and amount of data that can be archived or deleted as well as the
corresponding archiving objects or deletion reports. SAP's recommended residence times are used to calculate possible
savings.
To assist you in using the self-service and to reduce the learning curve, SAP offers an 'Expert Guided Session' in the form
of remote training.
For a detailed schedule and registration, see the 'Expert Guided Implementation Calendar'.
https://service.sap.com/Expert-Guided-Implementation
DVM Continuous Quality Check (CQC):
This service uses a similar technical infrastructure as the Guided Self-Service (see above) to generate a service report but
offers more flexibility as it is performed by an SAP service consultant together with you.
For more information, see:
https://support.sap.com/content/dam/support/en_us/library/ssp/offerings-and-programs/sap-enterprise-support/enterprise-s
upport-academy/continuous-quality-check-improvement-services/cqcdvm.pdf
For S/4HANA systems, new CQC services have been developed. Please see the following links for more details:
SAP CQC DVM Potential – Evaluation:
Confidential General Information about SAP 5/29
Data Volume Management (DVM)
upport-academy/continuous-quality-check-improvement-services/cqcdvm_pe.pdf
SAP CQC DVM Expert Analyses:

upport-academy/continuous-quality-check-improvement-services/cqcdvm_ea.pdf
DVM Enterprise Support Value Map: The SAP Enterprise Support Value Map for Data Volume Management is a social
collaboration platform offered by SAP Enterprise Support. The value map provides information on each step involved in
SAP Data Volume Management from initial assessment, through implementation, to improvement. It provides details of the
Enterprise Support services that can assist you and also a forum where you can ask questions and create discussions.
SAP Focus Advisors who have experience with DVM are available to assist you with your queries.
Other customers also participate in the value map, so they may be in a position to share their experiences and areas of
shared interest with you.
If you are interested in joining the SAP Enterprise Support value map, either register at https://support.sap.com/valuemaps
or contact your local SAP Enterprise Support Advisory Center.
DVM Launchpad (formerly known as Workcenter): The Data Volume Management Work Center in SAP Solution
Manager 7.2 offers capabilities to gain insights into the source of data volume movements in single and especially in
multisystem landscape environments. The solution is based on SAP NetWeaver 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:
- Get transparency of system landscape data consumption at different levels
- Reveal potential for creating/optimizing a data volume management strategy
- Leverage SAP Best Practices 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 'e-learning' for setting up the Data Volume Management Launchpad. The DVM e-learning can be accessed
via the following link (you need to have SAP Learning Hub access): link .
To get access to the SAP Learning Hub, please use the following link and click on 'sign up':
https://support.sap.com/en/offerings-programs/enterprise-support/enterprise-support-academy/learn.html
DVM Engineering Service (ESRV):
This engineering service is intended to help you through the whole process of the project to implement data volume
management. The idea is that all phases of the DVM lifecycle, from planning to implementation to review, can be supported
by a service consultant working together with you. A DVM Engineering Service can include any of the following activities:
- Scoping: This is usually the starting point of data volume management. A detailed look at the system identifies the major
pain points and provides an overview of the most beneficial measures (for example, deletion or data archiving) when
implementing a data volume management strategy.
- Planning: During this workshop, the results of data volume scoping are presented as a basis for defining a roadmap for
implementing data volume management. The questions of infrastructure and continued operation are also discussed.
- Implementation (Data Archiving, Deletion): This service provides all the information required to implement data
avoidance and summarization, including detailed information for scheduling deletion and archiving activities. For example,
it reveals connections between tables and archiving objects and provides information on which archiving objects should be
used and in which order. It provides recommendations on residence times for archiving objects based on SAP Best
Practices.
Workshops are conducted between the SAP service team and the customer to discuss the findings and define subsequent
steps.
- Setup of the DVM Launchpad (formerly known as Workcenter): This step includes guiding you through the setup,
troubleshooting issues that occur, and discussing how the use of this tool can best support your requirements. A setup of
detailed analysis jobs is included.
- Improvement: Supports the implementation of a DVM strategy by reviews, empowering and providing expertise on
demand.
The central location for information about SAP Data Volume Management is wiki.scn.sap.com/TechOps/DVM .
Valuable information about archiving projects can be found in the "Archiving Your SAP Data" book.
https://www.sap-press.com/archiving-your-sap-data_1375/
Confidential General Information about SAP 6/29

Data Volume Management (DVM)
4 Database Resources
-
The graph below shows the database size history for recent months. This provides a predictive indication of how existing
growth patterns will develop in future. For very large databases, this can also lead to an increase in the runtime of core
transactions and processes, backup and recovery operations, and conversion processes. Based on these predictions, you
can take countermeasures to maintain a more robust solution to meet your business requirements.
The table below shows the current size and growth rate of your DB. These figures are also used to produce the previous
graphic.
Date Total Database Size [GB] Freespace Size [GB] Used Database Size [GB]
01.12.2021 3.185 30 3.155
01.01.2022 3.235 28 3.207
01.02.2022 3.279 27 3.252
01.03.2022 3.295 26 3.269
Confidential Database Resources 7/29

5 Expected Sizes of Objects and Tables

-
The following tables contain an estimation of the sizes anticipated once the recommendations in the related document type
section in this report have been implemented. Since these objects and tables contain estimations based on current table
sizes and information provided to SAP on the date of the service delivery, they are to be used as guidelines only.
The following table shows the estimated saving potential of data archiving and deletion. The table includes only those
document types for which a saving potential calculation was possible.
If the document types listed vary from those selected in the "Tables in Scope" section, no saving potential calculation was
possible for some entries.
Archiving / Deletion
-
Document Type Current Size [GB] Reduction Potential [%] Reduction Potential Remaining Size [GB]
[GB]
Intermediate Documents 106,50 91 96,95 9,55
Application Logs 34,39 68 23,23 11,16
Table Change Protocols 11,54 38 4,37 7,17
Total 152,43 82 124,55 -
Total DB-Size 3.295,34 4 124,55 3.170,79
Note: The saving potential is estimated from a technical perspective only, it does not consider business-related aspects.
The savings calculation is based on conservative assumptions (moderate residence time).
You can reduce the existing database size by archiving and deleting data.
Reorganize table and index at database level to physically reduce the size of the tables after the first clean-up.
You can reduce the current monthly growth rate and future database size by avoiding and summarizing data or redesigning
business processes.
The database growth will also be reduced by regular data archiving and deletion.
Confidential Expected Sizes of Objects and 8/29

Tables
6 Tables in Scope
-
The following table can list the top-sized tables in your system identified by our analysis tools or, if you decided to start the
analysis for specific tables, the tables you selected to analyze are listed here.
Tables marked in the "Analyzed" column are addressed in detail in subsequent sections.
The "Document Type" of a table determines whether these detailed sections are generated in the session. This means that
you may see more than one table marked as analyzed but only one "Document Type" related section appears if those
tables belong to the same "Document Type".
In the detailed analysis sections of a "Document Type", you may find additional smaller tables in addition to the
aforementioned top tables. This allows a better calculation of the saving potential and provides a comprehensive overview
of the set of tables influenced by the different methods discussed in the specific section.
The "Size" column indicates the table total and its associated indexes.
The corresponding application area is also shown. You can use this information to determine the application areas
responsible for the space consumption in your system.
Note: The table description is also collected by our tools (that is, transaction ST14) depending on the logon language
(default is English). 'N/A' could indicate that the description is not available in the relevant language.
Analyzed Table Name Size [GB] Description Application Area Document Type
EDI40 83,30 IDoc data records for 4.0 BC Intermediate
Documents
CDCLS 34,95 Cluster structure for change BC Change
documents Documents
BALDAT 32,67 Application Log: Log data BC Application Logs
- SRRELROLES 11,76 Object Relationship Service: BC IDOC Object

Roles Linkages
DBTABLOG 11,54 Log Records of Table BC Table Change
Changes Protocols
- Total of listed Tables [GB]: 174,22 - - -
- Total DB Size [GB]: 3.295,34 - - -
Confidential Tables in Scope 9/29

7 Analyzed Objects
-
7.1 Table Change Protocols
-
SAP Application: BC-ABA (ABAP Runtime Environment) Business Content Changes to control and Customizing
tables, for example, can be logged (see SAP Note 1916). The logs are stored in table DBTABLOG.
"Before images" (before the change) are always recorded, which means a complete set of entries is available.
Changes to master data and transactional documents, however, are stored in the corresponding business areas using
change documents (tables CDHDR and CDCLS). An overview of FI and MM tables that are subject to logging is provided
in the audit guides for R/3 FI and R/3 MM (SAP Note 112388 "Tables are subject to logging").
Current Situation
-
Table Size (GB) Description
DBTABLOG 11,54 Log Records of Table Changes
Total Size 11,54 -
% of DB Size 0,35 -
-
7.1.1 Table Change Protocols: Deletion
-
General Information Data in table DBTABLOG can be deleted using deletion report RSTBPDEL according to period (end
date) and table. If the end date is selected, all change documents with the same end date or earlier are deleted from table
DBTABLOG.
This report implements the "Delete Documents" administration function within the table analysis function (transaction
SCU3) and can also be used separately.
-
7.1.1.1 General table change protocols
-
Data Content Analysis The table below shows the top 10 entries for the relevant tables. If you detect table KONP under
the top entries, see SAP Note 672503. In this case, table logging is activated for database table KONP even though it is a
master data table rather than a Customizing table.
The analysis was performed with transaction TAANA, variant AD-HOC.
Table Name (TABNAME) No. of Entries In % of Total
/VIRSA/ZFFCDHDR 955.439 2,0
AQLTS 3.153.502 6,7
KONP 27.306.635 57,9
RFCATTRIB 960.758 2,0
RFCDES 961.007 2,0
RFCDOC 951.104 2,0
TCURR 835.973 1,8
TFRM 2.207.305 4,7
USRM2 701.026 1,5
YVINVOICESUMMARY 3.956.909 8,4
Other Entries 5.212.790 11,0
Total 47.202.448 100,0
Recommendation Check whether you can delete the entries (using report RSTBPDEL) for your business or whether they
should be archived. For entries that can be deleted, deactivate logging in SE11 to avoid future logging.
The following table shows the top 5 tables with the corresponding transaction codes:
Table Name (TABNAME) Transaction Code (TCODE) No. of Entries In % of Total
AQLTS SE38 167 0,0
AQLTS SQ00 66 0,0
AQLTS SQ01 10.011 0,0
AQLTS SQ02 1.808 0,0
Confidential Analyzed Objects 10/29

Table Name (TABNAME) Transaction Code (TCODE) No. of Entries In % of Total
AQLTS SQVI 3.141.427 6,7
AQLTS (Total) - 3.153.479 6,7
KONP - 21.570.091 45,7
KONP VK11 1.682.263 3,6
KONP VK32 1.751.305 3,7
KONP YM_PIRUP 522.622 1,1
KONP YV_PUPD 610.951 1,3
KONP (Total) - 26.137.232 55,4
RFCDES - 948.496 2,0
RFCDES /VIRSA/VFAT 9.824 0,0
RFCDES SM59 2.103 0,0
RFCDES SPAM 69 0,0
RFCDES STMS 352 0,0
RFCDES (Total) - 960.844 2,0
TFRM - 540.565 1,1
TFRM SA38 208.634 0,4
TFRM SE38 1.458.106 3,1
TFRM (Total) - 2.207.305 4,7
YVINVOICESUMMARY - 3.912.972 8,3
YVINVOICESUMMARY VF01 14.973 0,0
YVINVOICESUMMARY (Total) - 3.951.920 8,4
Other Entries - 10.791.668 22,9
Total - 47.202.448 100,0
Deletion Object
-
Deletion Object Object Description
RSTBPDEL Table Log Database Management: Delete Logs
Deletion Runs If deletion jobs were scheduled recently for this document type, the following table shows some details. If
no deletion jobs were detected, nothing is displayed.
Since the history of scheduled jobs is deleted regularly (for example, after 2 weeks), this analysis cannot include details of
past periods.
-
7.1.2 Table Change Protocols: Archiving
-
General Archiving Information Data in table DBTABLOG is usually archived with archiving object BC_DBLOGS . As of
SAP NetWeaver 7.0 enhancement package 2, a new audit trail function allows audit trail data from table DBTABLOG to be
archived with archiving object S_AUT_LTXT . Audit trail records are posted for changes to tables STXH and STXL.
-
7.1.2.1 Table Change Protocols: Archiving Object BC_DBLOGS
-
Archiving object BC_DBLOGS is a cross-client object, which means that all log records are archived independently of the
client in which the change log in table DBTABLOG was created.
Since the archiving object is cross-client, you only have to schedule an archiving run in one client and not in every client in
which you have configured the Customizing settings.
Business-Process-Related Information The technical settings of a table in the data dictionary contain a logging indicator
that defines whether changes to the data records of a table are logged. If logging is activated, every change (with UPDATE,
DELETE) to an existing data record made by a user or an application program is recorded in log table DBTABLOG in the
database.
The logging indicator is set for Customizing tables in particular. The logs are used to document changes to the system and
can be relevant for external audits. Especially in industries with strict internal process audits (such as GMP in the
pharmaceutical industry), these change logs must be kept on a long-term basis.
Archived change logs can be reloaded to the database or accessed directly using transaction SCU3.
Recommendation Archive the change logs on a regular basis. Decide whether it is sufficient to archive the change logs in
the production system or in the development system. In the production system, only the software transport ID is
documented. In the development system, the name of the developer responsible for the change is documented in the
change log. In some cases, the change logs from the production system might not be sufficient for external auditors. If the
change logs are required for audit purposes, consider archiving them in the development system.
Customizing Settings: Application-Specific Customizing There are no specific Customizing settings for archiving object
BC_DBLOGS.
Archiving Object-Specific Customizing (Technical Settings) You can set parameters that apply to a specific archiving object
only.
Prerequisites for Archiving There are no application-specific prerequisites.
Maintaining the Variant: Selection fields for the write program of archiving object BC_DBLOGS:
The following selection criteria can be used:
Beginning of Archiving Period (write program RSLDARCH01)
- Date
- Time
End of Archiving Period
- Date
- Time
There is also an alternative write program available (BC_DBLOGS_WRI) (see SAP Note 1589591), which allows selection
by table name.
Display Functionalities: You can use the following functions to access archived data:
- Transaction: SCU3 (RSVTPROT)
- Read program: RSLDARCH03
- SAP Archive Information System
Dependencies on Other Objects: There are no dependencies on other archiving objects.
Data Content Analysis The following table shows the annual distribution in table DBTABLOG. The analysis was
performed with transaction TAANA, variant AD-HOC.
Archiving Object Year (LOGDATE) No. of Entries In % Total
BC_DBLOGS 2013 2.007.717 10,1
BC_DBLOGS 2014 1.775.384 8,9
BC_DBLOGS 2015 1.260.769 6,3
BC_DBLOGS 2016 2.324.502 11,7
BC_DBLOGS 2017 1.832.857 9,2
BC_DBLOGS 2018 2.547.803 12,8
BC_DBLOGS 2019 2.938.098 14,8
BC_DBLOGS 2020 2.841.360 14,3
BC_DBLOGS 2021 1.972.922 9,9
BC_DBLOGS 2022 394.401 2,0
Total - 19.895.813 100,0
Archiving Runs If there were archiving activities for this document type, the following table shows some details. If no
archiving runs were detected, nothing is displayed.
Evaluation SAP Best Practices recommend that you archive Table Change Protocols entries after 12 months, since they
probably no longer need to be accessed frequently after this period of time.
17.885.194 entries, or 38% of the entries, are older than 12 months. Archiving these entries would produce a
saving of approximately 4,37 GB.
-
7.2 Intermediate Documents
-
SAP Application: BC-SRV-EDI (IDoc Interface) Business Content All applications that exchange data electronically,
internally, or across the company, write intermediate documents (IDoc) to tables EDIDC, EDIDS, and EDI40. In some
cases, table EDI30C (table cluster for records as of Release 3.0C) contains data from previous releases.
Object link data (IDoc - IDoc or IDoc - business object) are written in tables IDOCREL and SRRELROLES.
Current Situation
-
EDI40 83,30 IDoc data records for 4.0
EDIDS 20,12 Status Record (IDoc)
EDIDC 3,07 Control record (IDoc)
TEDS2 0,00 Short description of IDoc status values
STACUST 0,00 Customizing for IDoc status (status groups, archive, procg)
EDI30C 0,00 IDoc cluster (data records) from 3.0C onwards
EDID4 0,00 IDoc Data Records from 4.0 onwards
Total Size 106,50 -
% of DB Size 3,23 -
-
7.2.1 Intermediate Documents: Deletion
-
Transaction WE11 can be used in test systems to delete obsolete Intermediate Documents (IDocs) and IDocs that are no
longer used. As an alternative to using transaction WE11, report RSETESTD can be started directly.
Important: The deletion function is not intended to be used in productive systems as Intermediate Documents are
considered to be of possible legal relevance.
-
7.2.2 Intermediate Documents: Archiving
-
General Archiving Information Data from intermediate documents (IDoc) can normally be archived using archiving object
"IDOC" (depending on the status).
- In transaction WE47, status values are defined that are required by an IDoc (sent or received) so that it can be considered
for archiving.
- IDocs can be reloaded.
- Some SAP Industry Solutions (IS) use specific archiving objects (for example, SAP-DIMP: VHURL_TR).
- With Basis Release 620, object linkages are always archived but are not deleted with the corresponding IDocs. This
means that report RSRLDREL is still required to delete the object linkages.
Recommendation In general, it is sufficient to archive IDoc data by selecting the creation date, current status, and/or
logical message (message type).
Customizing Settings Application-Specific Customizing There are no application-specific Customizing settings for the
IDoc archiving object. Use the selection criteria when selecting IDocs to be archived and check whether the status can be
archived (transaction WE47). An indirect residence time is available by restricting the date/time in the selection variant
(creation date/date of the last change).
Archiving Object-Specific Customizing (Technical Settings) For more information, see the "Standard Operation Technical
Customizing Settings" section.
Prerequisites for Archiving IDoc data can be archived with archiving object IDOC, depending on its status. Transaction
WE47 defines the status of an IDoc (received or sent) that can be archived.
Maintaining the Variant The following selection criteria are available:
- Created at (time)
- Created on (date)
- Last changed at
- Last changed on
- Direction (1=outbound, 2=inbound)
- IDoc number
- Current status
- Basic type
- Enhancement
- Logical message
- Port of sender
- Partner type of sender
- Partner number of sender
- Port of receiver
- Partner type of receiver
- Partner number of receiver
Display Functionalities You can use the following functions to access archived data:
- Transaction WE10
- Read program: RSEXARCR
- SAP Archive Information System
Dependencies The IDOC archiving object does not have any direct dependencies to other archiving objects. There is no
reference check to application documents generated from IDocs.
However, indirect dependencies exist to the deletion reports for ALE change pointers (tables BDCP and BDCPS) and
object linkages (tables IDOCREL and SRRELROLES). ALE change pointers (report RBDCPCLR) and object linkages

(report RSRLDREL) must be deleted after the IDocs have been archived. For releases later than Basis Release 620, object
linkages are always archived but still not deleted together with the corresponding IDocs. This means that report
RSRLDREL is still required to delete the object linkages.
IDocs can be archived depending on their Customizing status (transaction WE47). The Customizing settings for the IDoc
status were analyzed with table STACUST in terms of the ARCHFL field. The table below shows which IDocs are enabled
for archiving in your system. The analysis was performed with transaction TAANA, variant AD-HOC.
Status (STATUS) Description Archiving possible (ARCHFL = X)
03 Data passed to port OK X
04 Error within control information of EDI subsystem X
05 Error During Translation X
06 Translation OK X
07 Error during syntax check X
08 Syntax check OK X
09 Error during interchange handling X
10 Interchange handling OK X
11 Error during dispatch X
12 Dispatch OK X
13 Retransmission OK X
14 Interchange acknowledgment positive X
15 Interchange acknowledgment negative X
16 Functional acknowledgment positive X
17 Functional acknowledgment negative X
18 Triggering EDI subsystem OK X
19 Data passed to port for test X
21 Error passing data for test X
23 Error during retransmission X
24 Control information of EDI subsystem OK X
28 IDoc sent to ALE distribution unit retroactively X
31 Error - no further processing X
33 Original of an IDoc which was edited X
35 IDoc reloaded from archive X
38 IDoc archived X
40 Application document not created in target system X
41 Application document created in target system X
53 Application document posted X
57 Test IDoc: Error during application check X
58 IDoc copy from R/2 connection X
68 Error - no further processing X
70 Original of an IDoc which was edited X
71 IDoc reloaded from archive X
73 IDoc archived X
Data Content Analysis A distinction is made between outbound IDocs (EDIDC-DIRECT = 1) and inbound IDocs
(EDIDC-DIRECT = 2). Table EDIDC was therefore analyzed in terms of the DIRECT field. The analysis was performed with
transaction TAANA and variant AD-HOC.
Direction for IDoc transmission (EDIDC-DIRECT) Description No. of Entries In % of total
1 Outbound 7.081.113 13,9
2 Inbound 43.867.986 86,1
Total - 50.949.099 100,0
Data Content Analysis for Outbound IDocs The following table shows the annual distribution of outbound IDocs
(EDIDC-DIRECT = 1) in table EDIDC. The analysis was performed with transaction TAANA and variant AD-HOC.
Year (CREDAT) No. of Entries In % of Total
older than 2019 3.585.173 50,6
2019 999.173 14,1
2020 1.065.039 15,0
2021 1.187.040 16,8
2022 244.688 3,5
Total 7.081.113 100,0
The following table shows the different status values used in your system. It also shows the number of entries for each
status in table EDIDC. The analysis was performed with transaction TAANA and variant AD-HOC.
Status (STATUS) Description No. of Entries In % of Total
02 Error passing data to port 881 0,0
03 Data passed to port OK 7.064.469 99,8
12 Dispatch OK 7.267 0,1
20 Error triggering EDI subsystem 4.104 0,1
26 Error during syntax check of IDoc (outbound) 1.451 0,0
29 Error in ALE service 50 0,0
30 IDoc ready for dispatch (ALE service) 70 0,0
31 Error - no further processing 11 0,0
32 IDoc was edited 3 0,0
33 Original of an IDoc which was edited 100 0,0
37 Error when adding IDoc 3 0,0
51 Application document not posted 2 0,0
68 Error - no further processing 2.702 0,0
Total - 7.081.113 100,0
The following table shows the top message types (maximum 20) used in your system. It also shows the number of entries
for each message type in table EDIDC. The analysis was performed with transaction TAANA, variant AD-HOC.
Message Type (EDIDC-MESTYP) No. of Entries In % of Total
/IRM/AGRREQS 74.663 0,1
DESADV 5.035.015 9,9
FIN_DCFL_TV 1 0,0
INVOIC 1.320.256 2,6
MBGMCR 19.811 0,0
ODTF_CCTR 841 0,0
ORDCHG 12.861 0,0
ORDERS 171.298 0,3
ORDRSP 143.700 0,3
RSINFO 300.241 0,6
RSSEND 2.425 0,0
WMINVE 1 0,0
Total 50.949.099 100,0
The following table shows the top five message types for outbound IDocs by status and annual distribution (only the
message types that caused the highest number of entries). Table EDIDC was analyzed using transaction TAANA and
variant AD-HOC.
Message Type (EDIDC-MESTYP) Status (EDIDC-STATUS) Year (CREDAT) No. of Entries In % of Total
DESADV 02 older than 2019 42 0,0
DESADV 02 2020 1 0,0
DESADV 03 older than 2019 2.800.240 5,5
DESADV 03 2019 686.626 1,3
DESADV 03 2020 676.420 1,3
DESADV 03 2021 717.258 1,4
DESADV 03 2022 149.969 0,3
DESADV 12 older than 2019 3.550 0,0
DESADV 30 2021 1 0,0
DESADV 30 2022 9 0,0
DESADV 33 2019 27 0,0

DESADV 33 2020 4 0,0
DESADV 68 2019 1 0,0
DESADV (Total) - - 5.035.015 9,9
INVOIC 02 older than 2019 3 0,0
INVOIC 02 2019 13 0,0
INVOIC 02 2020 10 0,0
INVOIC 02 2021 2 0,0
INVOIC 03 older than 2019 484.027 1,0
INVOIC 03 2019 252.326 0,5
INVOIC 03 2020 264.706 0,5
INVOIC 03 2021 261.209 0,5
INVOIC 03 2022 53.564 0,1
INVOIC 20 2019 645 0,0
INVOIC 20 2020 1.390 0,0
INVOIC 20 2021 1.137 0,0
INVOIC 20 2022 170 0,0
INVOIC 26 2019 22 0,0
INVOIC 26 2020 2 0,0
INVOIC 26 2021 17 0,0
INVOIC 30 2022 1 0,0
INVOIC 32 2020 1 0,0
INVOIC 33 2019 5 0,0
INVOIC 33 2020 4 0,0
INVOIC 33 2021 2 0,0
INVOIC (Total) - - 1.320.256 2,6
ORDERS 02 older than 2019 4 0,0
ORDERS 03 older than 2019 111.641 0,2
ORDERS 03 2019 15.301 0,0
ORDERS 03 2020 15.576 0,0
ORDERS 03 2021 23.668 0,0
ORDERS 03 2022 5.049 0,0
ORDERS 32 2020 1 0,0
ORDERS 33 2020 1 0,0
ORDERS (Total) - - 171.298 0,3
ORDRSP 02 2021 298 0,0
ORDRSP 03 older than 2019 24.707 0,0
ORDRSP 03 2019 36.151 0,1
ORDRSP 03 2020 35.791 0,1
ORDRSP 03 2021 36.535 0,1
ORDRSP 03 2022 6.842 0,0
ORDRSP 26 older than 2019 71 0,0
ORDRSP 26 2019 387 0,0
ORDRSP 26 2020 473 0,0

ORDRSP 26 2021 366 0,0
ORDRSP 26 2022 107 0,0
ORDRSP 30 2021 32 0,0
ORDRSP 30 2022 27 0,0
ORDRSP 68 older than 2019 1.913 0,0
ORDRSP (Total) - - 143.700 0,3
RSINFO 03 older than 2019 139.280 0,3
RSINFO 03 2020 46.344 0,1
RSINFO 03 2021 94.163 0,2
RSINFO 03 2022 17.052 0,0
RSINFO 12 older than 2019 2.230 0,0
RSINFO 12 2020 598 0,0
RSINFO 12 2021 574 0,0
RSINFO (Total) - - 300.241 0,6
Other Entries - - 43.978.589 86,3
Total - - 50.949.099 100,0
Recommendation If you want to remove obsolete IDocs from the database, for example, because an obsolete billing
document is not to be sent to a customer again, you can select the archiving indicator temporarily, for example, for a
particular status (transaction WE47), restrict the date selection for the IDoc, archive it, and remove the archiving indicator
again after the archiving run.
General Comment If you use outbound IDocs, you can define IDoc processing in two ways: You can specify that the
receiver system sends a status message for the IDoc, or you can specify that the receiver system does NOT send a status
message. In both cases, the IDoc passes through status "03". If the receiver system sends a message, the IDoc ends in a
different status (normally status "12" if it was processed successfully). In this case, the IDoc should only be archived with
status "12". We recommend that you archive such IDocs by message type. If the receiver system does not send a
message back, the IDoc remains in status "03" permanently. These IDocs also have to be archived.
Report RBDMOIND sets IDocs with current status 03 ("Passed to port OK") to status 12 ("Dispatch OK") if no entry can be
found for these IDocs in the queue of the transactional remote function call.
This function is available for IDocs sent using a TRFC port or an R/2 port.
Evaluation of Outbound IDocs Outbound IDocs with a standard archive status (for example, status "12" = Dispatch OK
and "38" = IDoc archived) that are older than 6 months can be archived.
These correspond to 6.453.995 entries or 13 % of all entries in table EDIDC.
For status values other than "12" and "38" that allow archiving, see Customizing in transaction WE47.
Data Content Analysis for Inbound IDocs The following table shows the annual distribution in the EDIDC table for the
inbound IDocs (EDIDC-DIRECT = 2). The analysis was carried out with transaction TAANA and variant AD-HOC.
older than 2019 28.176.875 64,2
2019 5.447.601 12,4
2020 5.747.258 13,1
2021 3.760.063 8,6
2022 736.189 1,7
Total 43.867.986 100,0
The following table shows the different status values used in your system. It also shows the number of entries per status in
table EDIDC. The analysis was performed with transaction TAANA, variant AD-HOC.
38 IDoc archived 3 0,0
51 Application document not posted 1.652.811 3,8
52 Application document not fully posted 2.096 0,0
53 Application document posted 41.457.111 94,5
56 IDoc with errors added 1.701 0,0
60 Error during syntax check of IDoc (inbound) 84 0,0
62 IDoc passed to application 3 0,0
64 IDoc ready to be passed to application 277.578 0,6
65 Error in ALE service 81.534 0,2
68 Error - no further processing 265.135 0,6

69 IDoc was edited 1.984 0,0
70 Original of an IDoc which was edited 127.944 0,3
73 IDoc archived 2 0,0
Total - 43.867.986 100,0
The following table shows the top 30 message types used in your system. It also shows the number of entries for each
message type in table EDIDC. The analysis was performed with transaction TAANA and variant AD-HOC.
Message Type (EDIDC-MESTYP) No. of Entries In % of Total
/IRM/CLMRQSTS 74.667 0,2
/KJEPS/ORDERS 191.966 0,4
ACC_DOCUMENT 4.314.172 9,8
ADRMAS 44.328 0,1
BATMAS 172.361 0,4
COND_A 17.714.393 40,4
DEBMAS 3.348 0,0
FIDCC1 272.148 0,6
FIDCC2 278.234 0,6
FIN_DCFL_TV 21.807 0,1
FIXEDASSET_CREATEINCLVALUES 15.365 0,0
IBAN_SAVEREPLICA 1.955 0,0
INFREC 457.095 1,0
INVOIC 3.390.462 7,7
MATERIALBOM_CREATEBOMGROUP 9.179 0,0
MATMAS_BAPI 251.275 0,6
MATQM 90.956 0,2
MBGMCR 7.377.268 16,8
ORDERS 884.002 2,0
PORDCH 194.245 0,4
PORDCR 29.975 0,1
PORDCR1 7.573 0,0
REMADV 515.895 1,2
ROUTING_CREATE 8.697 0,0
RSRQST 65.827 0,2
SHPCON 7.375.584 16,8
SRCLST 13.542 0,0
YFFIDCC2 13.152 0,0
YF_FACTORY 70.562 0,2
ZBAPICUSTOMERHEIRARCHY 2.915 0,0
Total 43.862.948 100,0
The following table shows the top five message types for inbound IDocs by status and annual distribution (only the
message types that caused the highest number of entries). Table EDIDC was analyzed using transaction TAANA and
variant AD-HOC.
ACC_DOCUMENT 51 older than 2019 3.311 0,0
ACC_DOCUMENT 51 2019 1.391 0,0
ACC_DOCUMENT 51 2020 1.274 0,0
ACC_DOCUMENT 51 2021 10.392 0,0
ACC_DOCUMENT 51 2022 2.033 0,0
ACC_DOCUMENT 53 older than 2019 2.185.929 4,3
ACC_DOCUMENT 53 2019 694.826 1,4
ACC_DOCUMENT 53 2020 705.898 1,4
ACC_DOCUMENT 53 2021 597.456 1,2
ACC_DOCUMENT 53 2022 101.584 0,2
ACC_DOCUMENT 56 older than 2019 10 0,0
ACC_DOCUMENT 56 2019 1 0,0
ACC_DOCUMENT 70 older than 2019 5.630 0,0
ACC_DOCUMENT 70 2019 1.074 0,0
ACC_DOCUMENT 70 2020 923 0,0
ACC_DOCUMENT 70 2021 1.770 0,0
ACC_DOCUMENT 70 2022 601 0,0
ACC_DOCUMENT (Total) - - 4.314.172 8,5
COND_A 51 older than 2019 829.480 1,6
COND_A 51 2019 91.981 0,2
COND_A 51 2020 67.411 0,1
COND_A 51 2021 82.262 0,2
COND_A 51 2022 37.574 0,1
COND_A 53 older than 2019 10.712.660 21,0
COND_A 53 2019 2.470.717 4,8
COND_A 53 2020 2.498.142 4,9
COND_A 53 2021 534.063 1,0
COND_A 53 2022 98.625 0,2
COND_A 64 2019 56.038 0,1
COND_A 64 2020 220.407 0,4
COND_A 68 older than 2019 15.023 0,0
COND_A 70 older than 2019 10 0,0
COND_A (Total) - - 17.714.393 34,8
INVOIC 51 2019 2.504 0,0
INVOIC 51 2020 6.681 0,0
INVOIC 51 2021 7.855 0,0
INVOIC 51 2022 1.068 0,0
INVOIC 53 older than 2019 1.987.812 3,9
INVOIC 53 2019 419.303 0,8
INVOIC 53 2020 418.596 0,8
INVOIC 53 2021 427.354 0,8
INVOIC 53 2022 80.670 0,2
INVOIC 64 2019 20 0,0
INVOIC 64 2020 25 0,0
INVOIC 64 2021 34 0,0
INVOIC 64 2022 13 0,0
INVOIC 68 2020 2 0,0
INVOIC 69 2019 76 0,0
INVOIC 69 2020 127 0,0
INVOIC 69 2021 1 0,0

INVOIC 70 2019 334 0,0
INVOIC 70 2020 168 0,0
INVOIC 70 2021 3 0,0
INVOIC (Total) - - 3.390.462 6,7
MBGMCR 51 older than 2019 192.931 0,4
MBGMCR 51 2019 9.250 0,0
MBGMCR 51 2020 11.394 0,0
MBGMCR 51 2021 16.112 0,0
MBGMCR 51 2022 4.789 0,0
MBGMCR 53 older than 2019 6.305.482 12,4
MBGMCR 53 2019 189.415 0,4
MBGMCR 53 2020 198.665 0,4
MBGMCR 53 2021 231.869 0,5
MBGMCR 53 2022 45.327 0,1
MBGMCR 60 older than 2019 2 0,0
MBGMCR 64 2020 2 0,0
MBGMCR 64 2021 10 0,0
MBGMCR 68 2019 18.565 0,0
MBGMCR 68 2020 15.189 0,0
MBGMCR 68 2021 25.775 0,1
MBGMCR 68 2022 3.349 0,0
MBGMCR 69 2019 83 0,0
MBGMCR 69 2020 21 0,0
MBGMCR 69 2021 24 0,0
MBGMCR 69 2022 4 0,0
MBGMCR 70 2019 5.370 0,0
MBGMCR 70 2020 1.969 0,0
MBGMCR 70 2021 2.989 0,0
MBGMCR 70 2022 437 0,0
MBGMCR (Total) - - 7.377.268 14,5
SHPCON 51 older than 2019 37.540 0,1
SHPCON 51 2019 16.353 0,0
SHPCON 51 2020 25.192 0,0
SHPCON 51 2021 39.725 0,1
SHPCON 51 2022 7.819 0,0
SHPCON 52 2021 1 0,0
SHPCON 53 older than 2019 3.448.760 6,8
SHPCON 53 2019 1.137.803 2,2
SHPCON 53 2020 1.115.401 2,2
SHPCON 53 2021 1.181.057 2,3
SHPCON 53 2022 249.920 0,5
SHPCON 64 older than 2019 121 0,0
SHPCON 64 2019 48 0,0
SHPCON 64 2020 8 0,0
SHPCON 64 2021 20 0,0
SHPCON 64 2022 14 0,0
SHPCON 68 2019 10.556 0,0
SHPCON 68 2020 17.258 0,0
SHPCON 68 2021 17.878 0,0

SHPCON 68 2022 967 0,0
SHPCON 69 older than 2019 26 0,0
SHPCON 69 2019 13 0,0
SHPCON 69 2020 10 0,0
SHPCON 69 2021 3 0,0
SHPCON 69 2022 4 0,0
SHPCON 70 2019 54 0,0
SHPCON 70 2020 53 0,0
SHPCON 70 2021 57 0,0
SHPCON 70 2022 6 0,0
SHPCON (Total) - - 7.375.584 14,5
Other Entries - - 10.777.220 21,2
Total - - 50.949.099 100,0
Recommendation IDocs with an error status can only be archived after error handling or once you have checked whether
the IDoc is still required. In other words, they either have to be migrated to an archive status (postprocessing) or managed
as obsolete IDocs (see below).
If you want to remove obsolete IDocs from the database, for example, because an obsolete billing document is not to be
sent to a customer again, you can select the archiving indicator temporarily, for example, for a particular status (transaction
WE47), restrict the date selection for the IDoc, archive it, and remove the archiving indicator again after the archiving run.
Evaluation of Inbound IDocs Inbound IDocs with a standard archive status (for example, status "53" = application
document posted or "68" = completed) and that are older than 6 months can be archived.
These correspond to 39.925.445 entries or 78 % of all entries in table EDIDC.
For status values other than "53" or "68" that allow archiving, see Customizing in transaction WE47.
Archiving Objects
-
Archiving Object Object Description
IDOC IDoc - Intermediate Document
VHURL_TR Packaging Material Logistics: Transmissions
Evaluation SAP best practices recommend that you archive Intermediate Documents after 6 months, since they probably
no longer need to be accessed frequently after this period of time.
46.379.440 entries, or 91% of the entries, are older than 6 months, and have status values "03", "12", "38", "53",
and "68". These can be archived with object IDOC. Total potential reduction for IDocs (outbound and inbound): 91
%. Archiving these entries would produce a saving of approximately 96,95 GB.
-
7.3 Change Documents
-
SAP Application: BC-SRV-ASF (Technology Service Functions) Business Content Change documents are used to
log changes to master records, tables, and documents. All changes made to material master data, for example, are
automatically updated in change documents. Changes that are carried out in one step are saved in one change document.
Changes that are made sequentially, but at different points in time, are stored in different change documents.
Change documents are stored in tables CDHDR (header data) and CDPOS (item data). Table CDPOS is part of the
CDCLS cluster table. Table CDPOS_UID is also available as of Release 4.7, and table CDPOS_STR as of Release
ECC5.0.
Current Situation
-
CDCLS 34,95 Cluster structure for change documents
CDHDR 13,39 Change document header
CDPOS_UID 0,00 Additional Table for Inclusion of TABKEY>70 Characters
CDPOS_STR 0,00 Additional Change Document - Table for STRINGs
CDPOS 0,00 Change document items
Total Size 48,35 -
% of DB Size 1,47 -
-
7.3.1 Change Documents: Avoidance
-
General Information For networks and plant maintenance orders, you can prevent change documents from being written
by configuring certain Customizing settings. You can deactivate the creation of change documents or apply the settings to
specific status changes on the network/order (changes at header level, operations, materials, or production/resource tools).
Use the following menu path in the IMG for networks:
Project System -> Structures -> Operative Structures -> Network -> Settings for Networks -> Specify Parameters for
Network Type
Use the following menu path in the IMG for plant maintenance orders:
Plant Maintenance and Customer Service -> Maintenance and Service Processing -> Functions and Settings for Order
Types -> Define Change Docs, Collective Purc. Req. Indicator, MRP-Relevance
For more information, see SAP Note 390635.
You can deactivate the change documents for CO groups (change document object SETS) in Customizing: IMG ->
Controlling -> General Controlling -> Production Start-Up Preparation -> Activate Change Documents for Groups. (For
more information, see SAP Note 367073.)
The table below shows the CO groups for which change documents are written.
Table SETCLS_CD was analyzed with transaction TAANA, variant AD-HOC (filter SETWRITECD = X). Table SETCL
contains the descriptions of the CO groups identified.
Set Class Description
0000 Sets
0101 Cost Center Groups
0102 Cost Element Groups
0104 Statistical Key Figure Groups
0105 Activity Type Groups
0106 Profit Center Groups
0107 Transaction Groups
0108 Cost Object Groups
0109 Account Groups
0111 Fund Groups
0112 Functional Area Groups
0113 Grant Groups
0301 EC-CS Cons. Unit Sets
0302 EC-CS FS Item Sets
0303 EC-CS FS Subitem Sets
0311 Commitment Item Groups
0312 Funds Center Groups
For initial listing (Retail), you can use transaction WSM8 (Reorganize Listing Conditions by Material Group) to deactivate
the creation of change documents for tables WLK1 and MARC by setting the "Deactivate Change Documents" indicator.
You should do this for performance reasons since change documents are generally not required for initial listing.
-
7.3.2 Change Documents: Deletion
-
General Information You can use report RSCDOK99 to delete change documents.
You can use report RWSORT54 to delete change documents for object classes WLK1, ASMODULE, WBASISWG, and
LAYMOND depending on date selection.
Recommendation These deletion reports should be used in exceptional cases only and are the sole responsibility of the
customer.
It is better to archive change documents using the relevant application archiving objects or generic archiving object
CHANGEDOCU.
Deletion Objects The following table shows the deletion objects relevant for the document type.
Deletion Object
-
RSCDOK99 Delete Change Documents
RWSORT54 Delete Out-of-Date Change Documents for WLK1 and ASMODULE
past periods.
-
7.3.3 Change Documents: Archiving
-
General Archiving Information Change documents can be archived in the following way:
a) In context with the corresponding application archiving object:
For example, change documents for sales documents are archived together with the sales documents (archiving object
SD_VBAK in ERP systems or archiving object CRM_SALDOC in CRM systems). Change documents for business partner
master data are archived together with archiving object CA_BUPA.
b) You can archive change documents separately from their related business object with archiving object CHANGEDOCU.
This is a common approach for change documents for master data.
Recommendation We recommend archiving change documents for application data together with the corresponding
archiving object. Change documents for master data can be archived separately with archiving object CHANGEDOCU in
advance (for example, after a retention period of one year) since this master data is generally stored for a long-term period
or never archived or deleted.
Archiving Object CHANGEDOCU The characteristics of archiving object CHANGEDOCU are described below.
Customizing Settings Application-Specific Customizing There are no specific Customizing settings for archiving object
CHANGEDOCU.
Prerequisites for Archiving There are no application-specific prerequisites.
Maintaining the Variant Selection fields of the write program for archiving object CHANGEDOCU:
The following selection criteria are possible:
- Change Doc Object
- Change Document Object Value
- From Date
- To Date
- From Time
- To Time
- Transaction Code
- Changed by (user name)
Display Functionality You can use the following functions to access archived data:
- SAP Archive Information System (for more information, see SAP Note 192976). SAP Note 183774 describes how you can
activate a business view that displays the long texts or change documents with formatting.
- Read program: CHANGEDOCU_READ (sequential read of selected archive files)
Dependencies There are no dependencies on other archiving objects.
Data Content Analysis The following table shows the 15 object classes that cause the most entries sorted in alphabetical
order. Table CDHDR was analyzed using transaction TAANA, variant AD-HOC.
OBJECTCLAS No. of Entries In % of Total
/IRM/GCOND_A 6.599.906 5,0
/IRM/GCR 3.948.168 3,0
ADRESSE 6.111.042 4,7
BANF 1.672.396 1,3
BELEG 4.328.901 3,3
BELEGR 3.522.976 2,7
CHARGE 6.762.111 5,1
CLASSIFY 2.896.499 2,2
COND_A 42.795.302 32,6
COND_B 3.717.820 2,8
DEBI 1.686.385 1,3
EINKBELEG 2.644.814 2,0
LIEFERUNG 14.207.583 10,8
MATERIAL 5.967.648 4,5
VERKBELEG 12.307.899 9,4

OBJECTCLAS No. of Entries In % of Total
Total 131.395.943 100,0
Note You can use transaction SCDO to find out which tables are involved in the object class. Call transaction SCDO ->
Select an object such as HANDL_UNIT -> Change doc.object -> Display. Tables HUSSTAT, HUSTOBJ, VEKP, and VEPO
are then displayed. This enables you to determine whether the changes are related to master data (which indicates the use
of archiving object CHANGEDOCU) or related to transactional data.
Archiving Objects The following table shows the most relevant archiving objects related to the top object classes. The
'No. of Entries' column shows the number of records for which the recommended residence time has already been
exceeded. These are considered as good candidates for archiving. As a result, the following table lists the potential savings
and does not list the overall total number of records that are assigned to the archiving object.
Archiving Object Description TAANA Table No. of Entries older than the In % of Total
residence time
SD_COND Pricing condition records CDHDR 25.810.252 19,6
CHANGEDOCU Change Documents CDHDR 13.169.962 10,0
RV_LIKP Deliveries CDHDR 11.373.718 8,7
SD_VBAK Sales Documents CDHDR 9.411.863 7,2
MM_SPSTOCK LO: Batches and Special Stock CDHDR 5.541.148 4,2
FI_DOCUMNT Financial Accounting Documents CDHDR 4.379.822 3,3
MM_EKKO Purchasing Documents CDHDR 2.100.098 1,6
MM_EBAN Purchase Requisitions CDHDR 1.344.736 1,0
MM_REBEL Materials Management: Invoice CDHDR 838.677 0,6
Documents
SD_AGREEM Agreements and conditions CDHDR 791.070 0,6
Evaluation SAP best practices recommend that you archive Change Documents entries.
The possible savings on Change Documents depend on the archiving potential of the most relevant related archiving
objects.
-
7.4 Application Logs
-
SAP Application: BC-SRV-BAL (Basis Application Log) Business Content The application log is a tool to collect, save,
and display logs. Logs from different applications are written to the database and contain information or messages for the
end user. However, logs are not automatically deleted. The central transaction for analyzing application logs is SLG1.
Several different logs (for various objects) can be written at the same time by an application.
The application log is, in principal, similar to the system log. Whereas system event information is logged in the system log,
relevant application events should be written to the application log.
The application log can also be used as a message collector.
Application events can be logged centrally in the application log. The log for an object comprises:
- The log header (table BALHDR) with a unique log number:
This provides information about who triggered a particular event, using which program or transaction.
- Multiple numbers of log messages and their urgency status (tables BALDAT).
Expiration Date of Application Logs
The logs are usually assigned an expiration date, which is the date to which they must be retained in the database. This
date is normally set by the application, which calls the "Application Log" tool. They can be removed from the database after
this date.
The end user cannot set the expiration date. The expiration date does not mean that logs that have reached this date will
automatically be deleted. The DEL_BEFORE indicator in the BALHDR table determines whether the log can be deleted
before the expiration date is reached.
Current Situation
-
BALDAT 32,67 Application Log: Log data
BALHDR 1,72 Application log: log header
BAL_INDX 0,00 Application Log: INDX tables
BALM 0,00 Application log: log message
BALC 0,00 Application Log: Log or message context

BALHDRP 0,00 Application log: log parameter
BALMP 0,00 Application log: message parameter
Total Size 34,39 -
% of DB Size 1,04 -
-
7.4.1 Application Logs: Avoidance
-
General Information There is no general procedure for activating or deactivating the application log. Some applications
provide this option or let you reduce the number of entries created.
Material / Article Master Data Distribution (ALE) The writing of message logs for changes to material / article master
documents can be deactivated or at least reduced to a minimum. This is essential if the master documents are frequently
changed. For more information, see SAP Note 183960.
As of Release 4.7, application logs can be created in the receiving system via Customizing (transaction OMT0).
With the 'Control Application Log' indicator, you can deactivate the application log or reduce the data volume.
Indicator value 1: Create application log
Indicator value 2: Reduce the data volume by updating the application log only for error messages (probclass = 1)
Indicator value 3: Deactivate the application log
For Releases < 4.7, the following SAP Notes should be implemented: 183960, 373688, 393667, 376555, and 460310. Also
refer to these SAP Notes for more detailed information.
Process Messages (PP-PI) When messages are sent to process message destination PI01, a copy of the process
message is created in the process message record for additional evaluation and for archiving in the process data
documentation or in the batch record. Thus, the fewer messages sent to PI01, the fewer messages written to the
application logs. Therefore, investigate which of the process messages listed in the 'Usage of Destination PI01' table are
not required for business purposes.
Also refer to SAP Note 451706.
Content Server During the automatic monitoring of a Content Server, several entries of the object class SCMS may
accumulate in client 000. If this is the case, refer to SAP Note 392242.
Data Content Analysis Use the analysis result from the 'Archiving' chapter.
-
7.4.2 Application Logs: Deletion
-
General Information As of R/3 Release 4.6A You can use transaction SLG2 to delete records according to the selection
criteria specified. This transaction allows you to calculate the number of entries that meet the selection criteria, generate
the list of selected records, and/or delete them immediately.
The relevant report - SBAL_DELETE - can be scheduled as a background job at regular intervals.
Business-Process-Related Information When you delete process messages in the message monitor or using deletion
program RCOCB009 (transaction CO62), the message logs are not deleted if the message was sent to destination PI01
"Process message record".
For more information and deletion recommendations, see SAP Note 451706.
The following information applies to the SBAL_DELETE deletion report (transaction SLG2).
Prerequisites for Deletion Application log entries can be deleted after they have reached their expiry date. However, if the
DEL_BEFORE indicator in the BALHDR table is set to "blank" (not "X"), the logs can be deleted even before the expiry
date is reached. For more information, see SAP Note 195157.
You can use transaction SLG2 to delete the records according to specified selection criteria (you can restrict the selection
using the following fields: Object, Subobject, ProbClass, Transaction, Date Range, and so on). This transaction allows you
to calculate the number of entries that meet the selection criteria, generate the list of selected records, and/or delete them
immediately.
SLG2 is a report transaction. The corresponding report - SBAL_DELETE - can be scheduled as a background job at
regular intervals.
Only Important for CRM Systems: In CRM systems , application logs with subobject type "SINGLE" must not be deleted
with deletion report SBAL_DELETE (see SAP Note 595856). Table entries with subtype "SINGLE" are deleted while
archiving CRM documents with the related archiving objects. For more information, see the "Archiving" section.
Maintaining the Variant Selection fields for the SBAL_DELETE delete program (transaction SLG2):
- Object
- Subobject
- External ID
- Transaction Code
- User
- Log Number
- Problem Class
- From Date (BALHDR-ALDATE) - To Date (BALHDR-ALDATE)
- Transaction Code
Expiry Date
You can delete logs that have reached their expiry date or you can delete logs before the expiry date.
Options
- Only calculate the amount => this is a simulation
- Generate list => The report identifies the logs that can be deleted and displays a list from which you have to select the
logs to delete.
- Delete immediately => The report identifies the logs that can be deleted and deletes them without any input from the user.
Data Content Analysis Use the analysis result from the "Archiving" section.
Deletion Objects The following deletion object applies to tables BAL*.
SBAL_DELETE Application Log: Delete Expired Logs
past periods.
-
7.4.3 Application Logs: Archiving
-
General Archiving Information Log data can usually be archived with archiving object BC_SBAL as well. Consider this if
the application log contains information that is relevant for your business. It allows you to retain log data that could be
relevant for auditing or error evaluation.
You cannot reload archived application logs to the database.
Important for CRM Systems Log data relating to CRM documents (BALHDR-SUBOBJECT = 'SINGLE') is deleted as
soon as the CRM documents are archived (during the deletion phase).
Business-Process-Related Information Application log entries of the IHC payment order data (BALHDR-OBJECT = IHC)
are archived with the related business data by archiving object IHC_ARC.
In Enhanced Message Management (EMMA) for clarification cases in the FI contract accounting area, application log
entries are also created. These entries (BALHDR-OBJECT = EMMA) are archived with the related business data by
archiving object EMMA_CASE.
Recommendation In some cases, it may be useful to archive the log data of problem class 1 or 2 instead of deleting it.
Check whether this is relevant for you. If not, you can also delete the logs of problem class 1.
Check the business requirements to determine whether log data can be deleted, since object types may be relevant for
auditing or error evaluation.
Archive on a regular basis (for example, monthly). Select only those object classes for archiving that refer to data that must
be retained on a long-term basis.
Analyze the content of the application log tables in advance to be sure of the object classes that exist (check the OBJECT
field of table BALHDR) and decide whether the related logs can be deleted or need to be archived for each object class
identified.
The following information applies to archiving object BC_SBAL.
Customizing Settings Application-Specific Customizing There are no application-specific Customizing settings for archiving
object BC_SBAL.
A residence time is not available.
Prerequisites for Archiving A log can be archived only if it has expired (expiration date has been reached or has passed),
or it can be deleted before the expiration date.
Maintaining the Variant Selection fields of the write program for archiving object BC_SBAL:
- Object
- Subobject
- External ID
- Log Number
- Problem Class
- From Date (BALHDR-ALDATE)
- To Date (BALHDR-ALDATE)
- User
- Transaction Code
- Program
Note
The program selects entries within the time range specified in field BALHDR-ALDATE if the expiry date
(BALHDR-ALDATE_DEL) is before the current system date or equal to "00000000", or field BALHDR-DEL_BEFORE
(Application Log: Keep log until expiry) is blank.
Display Functionalities - Archived data can be accessed from the standard transaction SLG1 (as of Release 4.6C).
- SAP Archive Information System; a standard field catalog and info structure are available for the technical view of
archived log data.
Dependencies on Other Objects There are no dependencies on other archiving objects.
Data Content Analysis The following table contains the results of the analysis for the BALHDR table regarding the top ten
application log objects/application codes, and the relevant subobjects. You can see which log objects should be kept until
the expiry date has been reached and log objects which can be archived earlier.
The analysis was carried out with transaction TAANA, variant AD-HOC.
Object Name Subobject Keep Log until expiry No. of Entries In % of Total
/IRM/GCR CHANGE - 634.228 6,1
/IRM/GCR CREATE - 178.255 1,7
/IRM/GCR DELETE - 1.395 0,0
/IRM/GCR POST - 633.862 6,0
/IRM/GCR STAT_LOAD - 1 0,0
/IRM/GCR (Total) - - 1.447.741 13,8
/IRM/IPBB ACCRUE - 5.727 0,1
/IRM/IPBB CREATE - 93.149 0,9
/IRM/IPBB DELETE - 534 0,0
/IRM/IPBB RECREATE - 4.661 0,0
/IRM/IPBB REV_SETTLE - 8 0,0
/IRM/IPBB SETTLE - 2.393 0,0
/IRM/IPBB (Total) - - 106.472 1,0
/SDF/E2E /SDF/E2E - 1.770.079 16,9
/SDF/E2E /SOMO/BPMON - 6.596 0,1
/SDF/E2E /SSF/LOG - 8 0,0
/SDF/E2E (Total) - - 1.776.683 16,9
BCSWNC INSTANCE - 125.082 1,2
BCSWNC TOTAL - 43.520 0,4
BCSWNC (Total) - - 168.602 1,6
EHDI IMP_BOMBOS - 230.894 2,2
FIBL FEB_BS - 1.593.753 15,2
MATU - - 3.221.962 30,7
PPORDER HEADER - 332.780 3,2
QALS AUTO_UD - 643.804 6,1
QALS RECUR_INSP - 15.939 0,2
QALS (Total) - - 659.743 6,3
WF SWU_OBUF - 24 0,0
WF WIDELETE - 3.088 0,0
WF WIERRE - 571.236 5,4
WF (Total) - - 574.348 5,5
Total - - 10.112.978 96,5
The following table contains the results of the analysis for the BALHDR table regarding the top five application log
objects/application codes, their problem classes, and yearly distribution. The analysis was carried out with transaction
TAANA, variant AD-HOC.
Object Name (OBJECT) Log Problem Class (PROBCLASS) Year (ALDATE) No. of Entries In % of Total
/IRM/GCR 4 2020 370.265 4,3
/IRM/GCR 4 2021 952.144 10,9
/IRM/GCR 4 2022 125.332 1,4
/IRM/GCR (Total) - - 1.447.741 16,6
/SDF/E2E 4 2019 768 0,0
/SDF/E2E 4 2020 5.750 0,1
/SDF/E2E 4 2021 1.714.555 19,7
/SDF/E2E 4 2022 55.610 0,6

Object Name (OBJECT) Log Problem Class (PROBCLASS) Year (ALDATE) No. of Entries In % of Total
/SDF/E2E (Total) - - 1.776.683 20,4
FIBL 1 2019 176.178 2,0
FIBL 1 2020 241.030 2,8
FIBL 1 2021 364.860 4,2
FIBL 1 2022 76.582 0,9
FIBL 2 2019 1.241 0,0
FIBL 2 2020 795 0,0
FIBL 2 2021 1.507 0,0
FIBL 2 2022 264 0,0
FIBL 3 2019 175.564 2,0
FIBL 3 2020 142.372 1,6
FIBL 3 2021 133.564 1,5
FIBL 3 2022 25.555 0,3
FIBL 4 2019 111.843 1,3
FIBL 4 2020 76.764 0,9
FIBL 4 2021 51.586 0,6
FIBL 4 2022 14.048 0,2
FIBL (Total) - - 1.593.753 18,3
MATU 1 older than 2019 54.484 0,6
MATU 1 2019 2.782 0,0
MATU 1 2020 18.190 0,2
MATU 1 2021 2.633 0,0
MATU 1 2022 141 0,0
MATU 2 older than 2019 5.743 0,1
MATU 2 2019 163 0,0
MATU 2 2020 1.795 0,0
MATU 2 2021 1.252 0,0
MATU 2 2022 3 0,0
MATU 4 older than 2019 2.148.818 24,7
MATU 4 2019 184.371 2,1
MATU 4 2020 489.320 5,6
MATU 4 2021 277.276 3,2
MATU 4 2022 34.991 0,4
MATU (Total) - - 3.221.962 37,0
QALS 1 older than 2019 221 0,0
QALS 1 2019 37 0,0
QALS 1 2020 23 0,0
QALS 2 older than 2019 46.923 0,5
QALS 2 2019 687 0,0
QALS 2 2020 17.453 0,2
QALS 2 2021 17.559 0,2
QALS 2 2022 3.139 0,0
QALS 4 older than 2019 375.240 4,3
QALS 4 2019 73.628 0,8
QALS 4 2020 57.102 0,7
QALS 4 2021 57.448 0,7
QALS 4 2022 10.283 0,1
QALS (Total) - - 659.743 7,6
Total - - 8.699.882 100,0
Archiving Objects The following table shows the archiving objects relevant for document type Application Logs.
Archiving Objects
-
/AIF/PERSX Archiving object for the AIF XML persistency

BC_SBAL Archiving Object for Application Log
EMMA_CASE Clarification Case
IHC_ARC IHC Archiving Object for Payment Order Data
QM_CERT Archiving Object for Quality Certificate
Evaluation SAP Best Practices recommend that you archive Application Logs entries after 6 months, since they probably
no longer need to be accessed frequently after this period of time.
8.872.649 entries, or 68% of the entries, are older than 6 months. Archiving these entries would produce a saving
of approximately 23,23 GB.

PDF Data Volume Management - Best Practice 5000000006277

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDF Data Volume Management - Best Practice 5000000006277

Uploaded by

Copyright:

Available Formats

Service Report

Data Volume Management

SAP System ID EP1

DB System DB2 for Linux, UNIX and Windows 11.05.0600

Processed on SAP Solution Manager SPA Service Center

Service Tool 720 SP22 Email

Date of Service 07.03.2022 Session No. 5000000006277

Author CCOETZER Customer No.

Confidential Contents 2/29

Confidential Service Summary 3/29

Confidential Service Summary 4/29

3 General Information about SAP Data Volume

SAP CQC DVM Expert Analyses:

Confidential General Information about SAP 6/29

Confidential Database Resources 7/29

5 Expected Sizes of Objects and Tables

Confidential Expected Sizes of Objects and 8/29

- SRRELROLES 11,76 Object Relationship Service: BC IDOC Object

Confidential Tables in Scope 9/29

Confidential Analyzed Objects 10/29

Confidential Analyzed Objects 13/29

Confidential Analyzed Objects 15/29

Confidential Analyzed Objects 16/29

Confidential Analyzed Objects 17/29

Confidential Analyzed Objects 19/29

Confidential Analyzed Objects 20/29

Confidential Analyzed Objects 23/29

Confidential Analyzed Objects 24/29

Confidential Analyzed Objects 27/29

Confidential Analyzed Objects 28/29

Confidential Analyzed Objects 29/29

You might also like