Unit 7 - Overview Diagramm: Preface

0
Unit 7 - Overview Diagramm

Preface
Introduction to End-To-End
Solution Support
Business Process Performance

Optimization
Introduction to E2E Business

Process Integration and
Automation Management
Data Consistency
Management
Job Scheduling Management
Data Volume Management
Business Process and Interface

Monitoring
Recap Customer Case
SAP AG 2006
SAP AG
E2E300
7-1
0.2
Business Process
Performance Optimization
DVM might serve as one
measure for performance

improvement
Job Scheduling
Management
Data Volume
Management
Archiving
Backup
Transports
MRP Run 1000

MRP Run 2000
Billing Run
Reorganization
MRP Run 3000
Archiving & deletion jobs often have
long runtimes
Processed data volume can have
DVM might improve
the runtime of
consistency checks
Data consistency
should be ensured
before archiving
activities
direct impact on job runtimes
DVM might improve performance & hence
might solve alert situations
Business Process &

Interface Monitoring
Data Consistency
Management
SAP AG 2007, Data Volume Management / 1
Archiving and reorganization jobs have often long runtimes so that they need some special
consideration in the scheduling. On the other hand the job runtime might be significantly improved
by reducing the data volume to be processed. Hence DVM influences JSM and also works a means
for BPPO.
As DVM activities might reduce the data to be processed and hence improve the performance of
background jobs and transactions this might also result in less monitoring alerts
By reducing the amount of application data via DVM, this might improve the runtime of data
consistency jobs which read from the very same application tables
SAP AG
E2E300
7-2
0.3
Contents:
Data Volume Scoping
Data Volume Strategy
Data Volume Reporting
The presentation covers at first an overview of DVM and then of the components of DVM
Scoping
Strategy
Reporting
SAP AG
E2E300
7-3
0.4
Data Volume Management: Unit Objectives
After completing this unit, you will be able to:
Understand the elements of Data Volume Management
Have a decision basis on whether Data Volume

Management is currently of relevance for your company
Develop a Data Volume Management roadmap for your

company
SAP AG
E2E300
7-4
0.5
Data Volume Management: Overview
Lesson 1: Data Volume Management
Lesson 2: Data Volume Scoping
Lesson 3: Data Volume Strategy
Lesson 4: Data Volume Reporting
SAP AG
E2E300
7-5
0.6
Need for Data Volume Management
When to consider Data Volume Management?
Managing data volume and data growth for
SAP Systems and/or
SAP Solution Landscapes with
database sizes > 500 GB* or
monthly data growth > 20 GB*
* Depending on System Component
DVM should be used for managing the volume (size) and the growth of a database by reducing of
unnecessary or outdated data
DVM will be used for stand alone SAP systems or landscape solutions.
On average DVM should be considered by a database size > 500 GB or a monthly data growth > 20
GB or both.
But these threshold values are dependent on the type of system (ERP, BI, CRM, SRM, ) or
solution
SAP AG
E2E300
7-6
0.7
Sample Business Scenario
CRM - C00
SAP ECC - TT5
SAP ENTERPRISE
PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Current database size of

CRM system:
110 GB
Check Availability
Current database
size of Portal
system: 150 GB
Run MRP
Procurement
Process
Manufacturing
Process
Create Outbound
Delivery
Current database size of SAP

ERP system:
890 GB
Create Billing
Document
Post Goods Issue
Warehouse - TT5
Create Outbound
Delivery
Create Picking
Transfer Order
Post Goods Issue
Confirm Picking
Transfer Order
Current database
size of Warehouse
system:
280 GB
Noticed effects in the last weeks:

Offline Database Backup for ERP systems no longer possible within given time window
MRP runtime continually increases
general dialog performance of most transactions increases
SAP AG
E2E300
7-7
0.8
Benefits 1/2
Value Generation
through Data Volume Management
System Availability
Faster and easier upgrade to
higher software releases.
Shorter runtime for backup
and recovery.
Better Performance
Shorter response times in
dialog mode for all
employees.
Use of Resources
Reduced hardware costs for
Disk, CPU, Memory as well
as administration costs.
Legal Compliance
Meeting data retention
requirements.
Data Reduction supported by DVM have benefits regarding
1: System Availability
A reduced data volume/data growth has a positive impact regarding a faster & easier upgrade to
higher software release. By an software upgrade, tables which have changes in their data
structure must be converted during the upgrade (upgrade relevant tables) and in this time the
system could not be used -> System Downtime! The main focus is the minimization of the
system downtime e.g. in an upgrade project and this could be reached by minimizing the volume
of upgrade relevant tables.
Reducing the data volume has also an impact for shorter Run Time of backup and recovery and
so you can use the system in a better time with a better performance for the other usage.
2: Use of resources
Reducing the data volume and data growth the costs for hardware could be reduced or stable for
a longer time if an upgrade to a powerful CPU or a higher memory upgrading could be delayed;
Also the cost for disk could be reduced if the same disk space will be reusable used by other
business data
Additional by a delayed hardware upgrade and a manageable hardware environment the
administration costs could also be reduced
SAP AG
E2E300
7-8
0.9
Benefits 2/2
Value Generation
through Data Volume Management
System Availability
Faster and easier upgrade to
higher software releases.
Shorter runtime for backup
and recovery.
Better Performance
Shorter response times in
dialog mode for all
employees.
Use of Resources
Reduced hardware costs for
Disk, CPU, Memory as well
as administration costs.
Legal Compliance
Meeting data retention
requirements.
3: Performance
The Elimination of unnecessary or outdated data has also a positive impact for a shorter response
time in the dialog mode for all employees
4: Legal Compliance
Reducing data with a legal or tax relevant references requires specific actions and processes
regarding their safe-keeping and availability for auditors; this must be considered by the concept
for data archiving and data deletion
Different retention periods for safe-keeping dependent of the business document type and
country (e.g. accounting documents must be kept in Germany for 7 years) must be considered
Some business documents (e.g. billing documents) must be saved as images at their creation
time!
In total it has an impact to a better TCO (Total cost of ownership) by reducing the operation and
investment costs.
SAP AG
E2E300
7-9
0.10
System Availability Downtime Costs Per Hour
Downtime Losses by Application

Financial/Trading
Typical Loss Per Hour of

Unplanned Downtime (US$)
$2,400,000
Supply Chain
$600,000
ERP
$600,000
CRM
$480,000
E-Commerce
$480,000
E-Business
$480,000
Business Application
$300,000
Database
$300,000
Messaging
$60,000
Infrastructure
$42,000
Source: Storage Magazine
System Availability:
This tables gives you an overview about costs per hour caused by system downtime
This shows that the downtime has a lower impact regarding the costs on technical levels and
increase dramatically dependent on the application area
SAP AG
E2E300
7-10
0.11
Use of Resources Storage Savings
Archiving
Data Records
10 GB
Mirrors
20 GB
System Copies
80 GB
Compression
to 20 %
2 GB
2 GB
Backup to Tape
Total savings in this scenario are not only 10 GB, but due to
system copies and mirroring: 96 GB
Use of Resources:
Explained for Storage savings
Online data are multiple available in a system
First online in the database
Then for reasons of safety on mirror disks
And once again as system copies.
In this example you have 10 GB available on the database, additional 10 GB on the mirror disks
and at last on 4 system copies
In total you need 100 GB for storage resources
If the 10 GB are reduced by data archiving you need for the archived data only 2 GB. Data
archiving compress the archived data with a factor 2-5.
In this example the data are compressed to 20%
In total you need only 4 GB for the archived data, if the archived data are backed up on tape
Comparing the storage resources of online data with the resources for archived data you have in
this scenario a total saving of 96 GB
SAP AG
E2E300
7-11
0.12
Use of Resources Distribution of Storage Costs
Hard disk costs represent less than a quarter of storage costs.
(Giga Information Group)
Various
(Training, other costs)
10%
Hard disk
Personnel
23%
45%
Environment
(Electricity, physical space)
3%
Storage Mgmt
(Soft- & Hardware)
19%
Administration costs for 1 Terabyte storage are five to seven

times higher than the storage costs
(Dataquest/Gartner)
If we argument that the storage costs could be decreased by data reduction, often we hear the counter
argument that the costs of storage is lower than the data reduction costs (project-costs, software costs
and so on)
But this statement is wrong if mostly only the disk costs are considered and not the total costs.
So the storage costs imply not only the costs for hard disks but also the costs for storage
management, environment, personal, training and so on
In the slide you see that the hard disk costs are less than a quarter of storage costs
In the end the total costs for storage must be considered
Mostly also the effort for administration of very large storage environments are underestimated; in
the slide you see that the administration costs for 1 Terabyte storage are five to seven times higher
than the storage costs.
The conclusion is that the overall cost must be regarded instead of the cost of a single disk
SAP AG
E2E300
7-12
0.13
Better Performance Areas of Improvement
Reduce display of outdated data
Faster DB access
Faster access to single documents
2500
MB / msec
2000
MSEG MB
MB51 msec
1500
1000
500
0
Month 1
Month 2
Month 3
Month 4
Reducing expired business data has an influence on the performance regarding the response time in
the dialog mode.
This slide shows an example regarding material documents and their correlated line item tables
MSEG.
MB51 transaction: Material Document List
With the crowing of the table MSEG also the response time of MB51 growth
Notes on MSEG:
creating indexes is not a Cure All, if indexes data must also be updated and need system resources
Even so MSEG is still small (1.5GB), the response time got worse
If greater than 10% of table will be retrieved a full table scan would actually be preferred
Full table scan does multi block I/O Better performance per block I/O
Full table scan does not overwrite DB cache but only its own blocks
Differentiate between data viewed by user and data touched in the DB to answer the query
Bottom line: Data archiving is the only way to improve performance in this case
SAP AG
E2E300
7-13
0.14
Future impact
Media &
Entertainment
Telecommunications
Oil & Gas
Surveillance
data
Homeland
security
Utilities
Health
records
Health care
DoD
Audio &
video
content
E-mail
attachments
Life sciences
Financial
services
worldwide storage of
compliant records will
increase from 376
petabytes in 2003 to more
than 1,600 petabytes in
2006
Other
government
agencies
Energy
Present impact
Vertical Markets and Industries
Legal Compliance Predictions or Reality?
E-Mail
Trade confirmations
Compliance Pipeline, March 2004
Voice
recordings
Accounting
records
Web sites
Insurance
claim forms
Instant messaging
The worldwide capacity of

compliant records stored
on disk-based solutions
will increase at a
compound annual growth
rate of 172%
ESG Compliance Report, June 2003
Faxes
Present impact
Future impact
Compliant Records Subject to Regulation
Source: Enterprise Storage Group, May 2003
Legal compliance increase the data growth if more and more data and documents (as images) must
be kept for a long term
This slides gives you an impact of the ripple effect regarding the compliance of regulations and the
corresponding documents types. Is shows which kinds of documents must be kept today and in
future.
So the reducing of tax or legal relevant data must in compliance with the country specific regulations
and these must be considered by the implementation of a reduction strategy:
Considering specific safe-keeping retention periods
Considering the kind of safe-keeping (as images or as print-lists or as database data)
considering the kind of documents for safe-keeping
SAP AG
E2E300
7-14
0.15
Components of Data Volume Management

Data Volume Scoping

Operation
Implementation /
Optimization
Data Volume Strategy deals with

The implementation of a new data volume strategy,
The optimization of an existing data volume strategy and
The operation of an implemented data volume strategy.
The implementation supports the step by step procedure

Identifying and using of the necessary reduction possibilities,
The set up and go live of a strategy regarding the customer business and corresponding legal, tax
requirements.
The optimization is usually triggered by changes of the business environment what cause an increase
of the data volume and data growing by e.g.
add of new organizational business units,
Increasing of the business activities,
Additional legal requirements and so on.
The necessity of an optimization will be detected by a regular monitoring / reporting of the data
volume strategy activities by e.g. the data volume reporting.
The operation deals with the set up, the scheduling and the handling of the data management
activities like automated job scheduling, troubleshooting of the jobs with the key success factor
Maximum possible throughput with maximum negative effects on standard operation!
SAP AG
E2E300
7-15
0.16
Data Volume Management Process
Data Volume
Scoping
Identify the focus for reducing database size and growth
Decision on Optimization Strategy (Data Volume Strategy vs.

Business Process Analysis )
Detailed analysis regarding the feasibility of implementing

reduction options
Data Volume
Strategy
Avoidance, Summarization
Deletion, Archiving
Considering business process requirements (workshops with

business experts), technical constraints
Focus on reporting of
Current database size and growth
Current data archiving activities
Reduction potential by data deletion and data archiving
Data Volume
Reporting
Identification of
Additional data reduction potential
Optimization potential for data archiving
Basis for
Management Reporting
Decision-Making of follow-up actions
SAP AG
E2E300
7-16
0.17
Data Volume Scoping Decision KPIs
Monitoring Data Growth:
Identify the database size and their monthly growth

Evaluate against the Data Volume Management KPIs
Recommend as follow up activity
Data Volume Scoping or
Continued monitoring of the database size and data growth
Data Volume Management KPIs

System
Component
Database Size (GB)

recommended
mandatory
Monthly growth
(GB)
ERP
500
800
20
BI
500
800
20
CRM
200
500
15
SRM
200
500
15
DVM Scoping: Monitoring Data Growth
Using the Database Monitor the size of the database and their monthly growth should be monitored
regular and identified.
Dependent on the system component (ERP or BI or CRM or SRM and so on) the identified database
data are checked again the DVM KPIs (Key Performance Indicators)
For the database size we have 2 KPIs:

A recommended size: this means that for a system with a size greater the recommended KPI the
implementation of a DVM strategy is recommended
A mandatory size: this means that in this case the DVM strategy MUST be implemented.
If one or both DVM KPIs (database size, monthly growth) are fulfilled, as follow-up activity Data
Volume Scoping is recommended for evaluating if the database could be reduced by DVM
methodologies
If not, then the database size and growth should be monitored regularly in the future.
SAP AG
E2E300
7-17
0.18
Data Volume Scoping 1/2
Data Volume Scoping:

Recommendations:
Implementation of a Data Volume Strategy or
Performing of a Business Process Analysis (not part of DVM)
Decision-Making
Business Process Analysis
Significant Potential for DVM Reduction

Methodologies detected, based on average residence
time and regarding performed data archiving
activities
DVM Reduction Methodologies not available for some
application areas
DVM Reduction Methodologies not usable regarding
data deletion or data archiving (residence time not
expired, data not older than 12 or 15 month) or
avoidance of data creation
In this step the system will be evaluated identifying the focus for reducing the database
Reduction possible using the DVM Methodologies
Data Avoidance
Data Summarization
Data Deletion
Data Archiving
Reduction only possible by performing a business process analysis (not part of DVM;
involvement of Business consultants)
DVM strategy is recommended if

Tables of business objects (top tables) are identified for which one or more of the DVM
Methodologies are available and regarding data deletion and data archiving a reduction potential
is identified
For data avoidance and data summarization the distribution over the years are not relevant
Reduction potential:
for a top table the distribution of the data over the years are identified;
using an average residence time you can check how many data are outside this residence time
Residence time = period (in days or months or years) how long the data should be kept online
SAP AG
E2E300
7-18
Example: you have identified that the data are distributed over the years 1999 until 2007 and you
assume a residence time of 15 months, so you can say that all data older than 2006 are candidates
for reduction
SAP AG
E2E300
7-19
0.19
Data Volume Scoping 2/2

Recommendations:
Implementation of a Data Volume Strategy or
Performing of a Business Process Analysis (not part of DVM)
Decision-Making
Significant Potential for DVM Reduction

Methodologies detected, based on average residence
time and regarding performed data archiving
activities
DVM Reduction Methodologies not available for some
application areas
DVM Reduction Methodologies not usable regarding
data deletion or data archiving (residence time not
expired, data not older than 12 or 15 month) or
avoidance of data creation
Business Process Analysis is recommended if

Tables of business objects (top tables) are identified for which no DVM Methodologies exist or
Tables of business objects (top tables) are identified for which DVM Methodologies (data
deletion, data archiving) exist, but the data distribution of the years shows that the data are not
older than the residence time and the could not be reduced by this methodologies
This means that we have a strong data growth within the residence time archiving or deletion could
not be used
SAP AG
E2E300
7-20
0.20
Data Volume Strategy: Definition and Content
A Data Volume Strategy consists of the elements:
Reduction of Database growth
Data Avoidance,
Data Summarization of business non relevant data
Reduction of Database size and growth
As one-time activity by
As recurrent activity by
Data Deletion of Temporary data
Data Archiving of Business, tax and / or legal relevant data (safekeeping)
Data Volume Strategy helps to reduce
The database growth

As one-time activity by
Data Avoidance (avoid the creation of unnecessary data)
Data Summarization (collecting data records to one record by avoiding unnecessary data in the
record)
Of business non relevant data (data which are not relevant for auditors or product liability or are
technical data without references to business data)
DVM is using for avoidance and summarization only standard features with setting by
customizing; it doesnt mean modifications!
The database size and growth

As recurrent activity by
Data Deletion of Temporary data
Data Archiving of Business, tax and / or legal relevant data (safekeeping)
SAP AG
E2E300
7-21
0.21
Data Volume Strategy: Methodology
Data Avoidance
Data Summarization
Data Deletion
Data Archiving
Reduction of
DB-growth
Reduction of
DB-size +
DB-growth
Overview of Standard Methodologies of DVM Strategy
SAP AG
E2E300
7-22
0.22
Data Volume Strategy: Guiding Principle
Please consider:
Data Volume Strategy is living strategy
It should be reviewed
after Implementation and

regularly (e.g. yearly) in the operation phase.
If a DVM strategy is implemented, note that this strategy must be adapted to business changes
It is a living strategy and must be monitored and reviewed regularly in the operation phase
If not, the database grows -> please see the slides with the benefits
SAP AG
E2E300
7-23
0.23
Data Volume Reporting: Definition
Identification of
Basis for
DVM Reporting has the

Identification of
Basis for
SAP AG
E2E300
7-24
0.24
Data Volume Management Roadmap
Project
Preparation
Data
Analysis
Business
Blueprint
Product.
ImplemenPrepatation
ration
Go Live
Maintenance
Support
End-ofLife
DVM Components:
DVM
Scoping
DVM Strategy
Data Consistency Check
DVM Reporting
DVM Optimization
DVM Empowering
DVM Roadmap:
DVM Scoping is used as an initial assessment for preparation of the DVM-Strategy Implementation
Project.
DVM Strategy Implementation covers the phases

Data analysis
Business blueprint (identifying the customer business requirements regarding the reduction of
data in relation with legal compliance and defining a concept considering the business
requirements)
Implementation of the concept
Preparation of the productive usage ( e.g. implementation of notes, customizing settings,
functional tests and so on)
Go Live (e.g. mass tests, performance issues and so on)
Data Consistency Check is recommended before the DVM strategy will go live. If you identify data
inconsistency after data archiving you will have a additional high effort for solving the inconsistency.
Data reduction doesnt check data consistencies!
DVM Reporting evaluates the efficiencies of the implemented DVM Strategy and reports the results
which could be used for management reporting or decision-making of a follow-up activity for DVM
Optimization
SAP AG
E2E300
7-25
DVM Optimization is used optimizing an existing strategy or adopting this strategy on new business
requirements
DVM Empowering is a set of workshops regarding different themes of data reduction, legal aspects,
performance, release information and so on. SAP Empowering is used as knowledge transfer for all
DVM phases.
SAP AG
E2E300
7-26
0.25
Data Volume Management Process View
Business Department
Business Process Champion
Define Business
Requirements
Business
Process Analysis
No
Monitor
Data Growth
No
DVM Methods
applicable?
DVM
Strategy
Implementation
Yes
DVM
Strategy
Operation
DVM KPIs
reached?
Confirm
DVM Strategy
DVM
Strategy
Optimization
Yes
DVM
Reporting
DVM
Scoping
No
Additional
Potential?
Business Process Operation Team
Yes
IT Support Organization
The first starting point to detect the need for the implementation of a DVM strategy is a defined
monitoring of data growth.
As soon as the threshold is reached a DVM scoping is initiated to determine if the data growth and
volume can best be handled by the implementation of a DVM strategy or if (in addition) a review of
the business process is the more promising approach to limit the future creation of data.
As soon as the scoping determined that DVM means (e.g. deletion of data, avoidance or dataarchiving) should be applied an implementation phase starts in which the business process and legal
requirements on data are checked against the technical need for data reduction.
After the means are implemented and the DVM strategy is in the operating phase and the archiving
and delete jobs are scheduled regularly the success of the implementation has to be monitored
continuously by DVM Reporting to detect new or additional potential for improvement that may be
caused by changed business processes.
Only when considering both all aspects of Data Volume Management (Implementation, Operation
and Reporting) it will be possible to run a system that is as large as necessary and as small as
possible on the long term.
DVM standard requires a high degree of cooperation between business process champions and IT
departments. From the business department the business process champions and from the IT
department persons of the business process operation must be involved.
SAP AG
E2E300
7-27
0.26
Data Volume Scoping
SAP AG
E2E300
7-28
0.27
Components of SAP Data Volume Management
SAP Data Volume Management

Data Volume Scoping

Operation
Implementation /
Optimization
DVM Scoping evaluates the system or system landscape regarding the anticipating data reduction
possibilities.
SAP AG
E2E300
7-29
0.28
Business Department
No
Monitor
Data Growth
No
DVM Methods
applicable?
Confirm
DVM Strategy
Define Business
Requirements
Business
Process Analysis
DVM
Strategy
Implementation
Yes
DVM
Strategy
Operation
DVM KPIs
reached?
DVM
Strategy
Optimization
Yes
DVM
Reporting
DVM
Scoping
No
Additional
Potential?
Yes
If the process Monitoring Data Growth considers the implementation of a Data Volume
Management strategy, the process DVM Scoping evaluates the system or system landscape regarding
the anticipating data reduction possibilities.
DVM Volume Scoping examines for which business areas and business objects
the data volume and the data growth can be reduced by the DVM standard reduction
methodologies data avoidance, data summarization, data deletion and data archiving,
the reduction possibilities of the data growth must be evaluated by a Business Process Analysis,
if the DVM standard reduction methodologies could not be used. This will be the case if for a
business object DVM reduction possibilities are not available or the data of this business object
are not in the scope of data deletion or data archiving regarding their residence time.
The Business Process Analysis is not in the scope of DVM.
Process Flow
The Focus of DVM Scoping is identifying and recommending the best strategy for reducing the
data volume size or the data growth or both. Based on the result of the investigation regarding
system data, top tables, data volume growth, performed archiving activities and distribution of
the data over the years
SAP AG
E2E300
7-30
0.29
Data Volume Scoping: Content
Data Volume Scoping
Analyze the top 20 tables of your database

on a very rough level
Identify the areas with potential for avoidance,

summarization, deletion and archiving
Analyze the performed archiving activities
Evaluate the most suitable strategy for reducing

your database size and growth:
Data Volume Strategy or

DVM Scoping identify and analyze the top 20 tables of the database
Identify the application areas and business objects with potential for
avoidance, summarization, deletion and archiving
Analyze the performed archiving activities
Evaluate the most suitable strategy for reducing

your database size and growth:
Data Volume Strategy or
Demo 1
SAP AG
E2E300
7-31
0.30
Demo 1: Determine data growth (1/3)
Check total size of DB and total monthly growth in transaction DB02
On TT5 system the database in fact shrank than grew but this is an exception. This should be
explained to the participants. The DB space history per month can be chosen by one of the buttons.
SAP AG
E2E300
7-32
0.31
After having checked the overall DB size and growth you can check the details on growth on table
level.
SAP AG
E2E300
7-33
0.32
Check top growing against top largest tables
The largest tables are not necessarily identical with the top growing tables. In customers system
some tables may be very large but no longer growing, e.g. because archiving or deletion is already
implemented but the DB size is still big (e.g. because of a missing DB-table reorganization to regain
disk space).
Tables BALDAT and GLFUNCA are used on the next slide as examples for how to determine an
archiving object
SAP AG
E2E300
7-34
0.33
Sample Business Scenario
CRM - C00
SAP ECC - TT5
SAP ENTERPRISE
PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement
Process
Manufacturing
Process
Create Outbound
Delivery
Current database size of

SAP ERP system: 890 GB
Create Billing
Document
Post Goods Issue
Warehouse - TT5
Create Outbound
Delivery
Create Picking
Transfer Order
Post Goods Issue
Confirm Picking
Transfer Order
In our sample scenario we focus on Data Volume Management for the SAP ERP
system.
SAP AG
E2E300
7-35
0.34
Sample Business Scenario: Database Size - History
Database Size - History
Database Size
in GB
1,000
866
900
765
800
677
700
600
613
633
702
804
890
843
737
651
565
500
400
300
200
100
0
Monthly growth of database size for ERP system in sample business scenario
SAP AG
E2E300
7-36
0.35
Sample Business Scenario: Situation at Customer
SAP ERP System - Database Resources:
Total DB size/Allocated space:
Average monthly Growth:
890 GB
30 GB
Analyzed Database Size:
Number of analyzed Tables:
Analyzed DB size:
20
405 GB (= 46% of Total DB size)
This situation is in line with SAPs recommendation for the definition

and implementation of a Data Volume Strategy
database sizes > 500 GB, and/or
a monthly data growth > 20 GB.
Sample : Situation at Customer
The database size and monthly growth fulfill the DVM KPIs and is in line with our recommendation
for DVM strategy
SAP AG
E2E300
7-37
0.36
Sample Business Scenario:

Distribution of the Top 20 Tables across Document Types
Analyzed DB-Size of 405 GB
CO-Documents
MSEG
17 GB; 4%
RESB
24 GB; 6%
AFRU
10 GB; 2%
EC-PCA-Documents
FI-SL-Documents
COEP, COEPL, COSP,
COSS
159 GB; 39%
JEST
12 GB; 3%
BALDAT
11 GB; 3%
Idocs
BKPF, BSIS
22 GB; 6%
Application Logs
ACCTIT, ACCTCR
28 GB; 7%
Object Status
MLIT, MLCR,
CKMLPREKEPH
33 GB; 8%
CKIS
17 GB; 4%
ML-Data
Compressed Data from
FI/CO Documents
FI-Documents
EDIDS
29 GB; 7%
Cost Estimates
GLPCA
31 GB; 8%
GLFUNCA
13 GB; 3%
Reservation/dependent
requirements
Material Documents
Order completion
confirmations
Shows the distribution of the top 20 tables across the document types
SAP AG
E2E300
7-38
0.37

Reduction Possibilities for the Top 20 Tables
Table Name
Data Avoidance
Data Summarization
Data Deletion
Data Archiving
Financials
BKPF
BSIS
ACCTIT
ACCTCR
GLFUNCA
COEP
COEPL
COSP
COSS
CKIS
MLCR
MLIT
CKMLPRKEPH
GLPCA
Logistics
MSEG
RESB
AFRU
Cross Application / Basis

BALDAT
EDIDS
JEST
This shows the reduction possibilities of the top 20 tables from the technical point of view
By the implementation of a DVM strategy it must be checked if these possibilities could be used
from the business point of view
SAP AG
E2E300
7-39
0.38

Archiving History of SAP ERP System
Number of
Archiving
Runs
Last Run
Archived
Objects)
Number of
Archiving
Files
Size of
Archive
Files (KB)
First Run
CO
20.10.1999
22.11.1999
612
46.256
CO_ML_BEL
CO-PC
CO_ML_DAT
CO-PC
12
03.05.2004
22.07.2004
5.099.460
178
3.682.918
CO_ML_IDX
CO-PC
11
05.05.2004
22.07.2004
5.953.137
205
1.600.362
CO_ML_SPL
CO-PC
07.05.2004
29.07.2004
5.260.731
181
1.637.004
07.05.2004
22.07.2004
2.049.756
75
553.004
CO_ORDER
CO
02.11.1999
19.02.2003
21.320
89.082
FI_DOCUMNT
FI
31.07.1999
26.11.1999
590.589
26
561.345
IDOC
CA
83
21.05.2004
23.05.2004
5.160.607
120
4.284.231
MM_EBAN
MM
25.10.1999
25.10.1999
35.543
29.493
MM_EKKO
MM
26.10.1999
30.11.1999
3.015
6.785
MM_MATBEL
MM
19.10.1999
19.10.1999
78.665
32.274
MM_SPSTOCK
MM
90
01.12.2002
20.12.2002
269
88
5.974
...
24.257.568
946
12.542.779
Archiving
Object
CO_COSTCTR
Area
Total
277
It shows the performed archiving activities on the system
Regarding the last run you can see if archiving is used currently and also how often and how
efficient
Only complete arching runs (archiving write and deletion completed) are listed
SAP AG
E2E300
7-40
0.39

Result of Data Volume Scoping
Summary and Conclusion:
As data archiving is not executed on a regular basis and in a

sufficient volume, your database is growing on a quite high
rate.
Furthermore, it should be investigated, which preventive
actions in terms of data avoidance and data summarization
could be made in your system in order to reduce your data
growth in future.
An assessment of your existing data volume should be

performed.
Summary and Conclusion:

As data archiving is not executed on a regular basis and in a sufficient volume, your database is
growing on a quite high rate.
Furthermore, it should be investigated, which preventive actions in terms of data avoidance and
data summarization could be made in your system in order to reduce your data growth in future.
An assessment of your existing data volume should be performed.
SAP AG
E2E300
7-41
0.40
SAP AG
E2E300
7-42
0.41

Data Volume Scoping

Operation
Implementation /
Optimization
Data Volume Strategy deals with

The implementation of a new data volume strategy,
The optimization of an existing data volume strategy and
The operation of an implemented data volume strategy.
The implementation supports the step by step procedure

Identifying and using of the necessary reduction possibilities,
The set up and go live of a strategy regarding the customer business and corresponding legal, tax
requirements.
The optimization is usually triggered by changes of the business environment what cause an increase
of the data volume and data growing by e.g.
add of new organizational business units,
Increasing of the business activities,
Additional legal requirements and so on.
The necessity of an optimization will be detected by a regular monitoring / reporting of the data
volume strategy activities by e.g. the data volume reporting.
The operation deals with the set up, the scheduling and the handling of the data management
activities like automated job scheduling, troubleshooting of the jobs with the key success factor
Maximum possible throughput with maximum negative effects on standard operation!
SAP AG
E2E300
7-43
0.42
Business Department
No
Monitor
Data Growth
No
DVM Methods
applicable?
Confirm
DVM Strategy
Define Business
Requirements
Business
Process Analysis
DVM
Strategy
Implementation
Yes
DVM
Strategy
Operation
DVM KPIs
reached?
DVM
Strategy
Optimization
Yes
DVM
Reporting
DVM
Scoping
No
Additional
Potential?
Yes
Three main tasks regarding a DVM strategy from the previous slide
Implementation
Operation
Optimization are here displayed in a process view and by responsible team
The implementation is driven by the Application Management team as this step requires a profound
understanding of the business processes and a strong integration of the business process owners or
champions. As soon as the strategy is defined (e.g. customizing of residence times, archiving objects
to be used, ) the business operation team takes over.
The operation of the DVM strategy (i.e. scheduling and monitoring of archive and delete jobs) is
performed by the Business Operation Team, that is also responsible for general job scheduling and
monitoring tasks.
The business operation team is also responsible for monitoring the effect of the DVM strategy and
may detect gaps or additional potential for optimization to stop the data growth even better. The
adjustment or enhancement of the existing DVM strategy is then again performed by the application
management team in conjunction with the business process champion. The adjusted definition of
jobs or archiving objects is then handed back to the business operation team.
An adjustment is usually necessary in case of:
Very strong growth of transaction data (e.g. because of the roll-out of business processes to
additional countries) that may require to shorten the already defined residence times
New implemented business processes that require new archiving objects to handle the data
volume.
SAP AG
E2E300
7-44
0.43

Data Volume Scoping

Operation
Implementation /
Optimization
In the first part the focus is on Implementation and Optimization
SAP AG
E2E300
7-45
0.44
Data Volume Strategy - Implementation
Analyze your database for potential growth

and size reductions
Decide on a strategy regarding
Avoidance,
Summarization and
Deletion
Archiving
is mostly applicable in the areas of

Financials and Basis/Cross Application
for business non-relevant data
for business, tax and / or legal relevant

data
Data Volume Management may(!) be focused on data-archiving, but besides this, there are other
means that should be seriously considered:
Avoidance
Summarization
Deletion
The details on each of the options are explained on the following slides.
SAP AG
E2E300
7-46
0.45
Data Volume Strategy: Four-Step Analysis
Is the data really needed?
No
Data
Avoidance
Yes
Can the data be summarized?
Yes
Data
Summarization
Yes
Data
Deletion
Yes
Data
Archiving
No
Can the data be deleted?
No
Can the data be archived?
Legend:
Impact on data volume
in future
Impact on current
data volume
No
Data remains
in the database
DVM Strategy Standard Methodology

DVM Strategy is using the standard methodology as a Four-Step Analysis
Step 1: it will be checked if the data growth could be reduced by avoiding of the data creation;
then it will be checked if these data are really needed for the business process and legal
compliance
Step 2: if the data are needed, it will be checked if the data growth could be reduced by
summarizing of specific data (Is summarization possible from the technical point of view); if it
is possible you must check if it is possible from the business point of view.
Step 3: if the data could be deleted , if they must not be kept regarding legal requirements
Step 4: the data will be archived considering legal aspects, residence times, overall status values
and so on
Data avoidance and summarization have an impact on the data volume in future; data created in
the past must be eliminated by deletion or archiving
Data deletion and archiving have an impact on the current data volume
SAP AG
E2E300
7-47
0.46
Data Avoidance
Data Avoidance
Unnecessary data is identified.
The functions responsible for collecting this unnecessary data
are identified and switched off.
The data is not written any more in future.
Examples for Avoidance:
Switch off the writing of Line Items (EC-PCA, FI-SL)
Switch off the line item display for G/L-accounts (FI)
Switch off unnecessary logs
The idea is to switch off the creation o data that is not needed but is nevertheless posted, e.g. because
of SAP default customizing or a wrong decision on customizing during the implementation phase.
The options of data avoidance are very application specific. Data avoidance cannot be applied in
general for all tables.
Attention: Data Avoidance will only have an effect on future(!) data. There is nothing like
retrospective avoidance.
In case a customer has decided for avoidance, the already existing data has to be deleted in a separate
step.
SAP AG
E2E300
7-48
0.47
Data Summarization
Data Summarization
Redundant/too detailed data is identified.
The functions available for aggregating this data
are identified and activated.
Data is written in reduced form in future.
Usually most applicable with accounting and controlling data.
Examples for Summarization:
Summarization in CO, CO-PA, EC-PCA, FI, FI-SL

(via customizing settings)
Summarization is mainly used in the Finance applications.
It allows to hide details of the corresponding logistics data (e.g. billing documents, material
documents) in the corresponding finance application (e.g. in accounting documents or controlling)
by combining several line items of a logistics document to one line item in the financial document.
The big benefit besides data reduction is that the finance postings are easier to read and provide a
better overview.
In case the logistics documents (e.g. material document) contain more than 999 line items
summarization MUST be used as the number of line items in an accounting document must not
exceed 999.
If summarization is acceptable from a business perspective strongly depends on the reporting

requirements (e.g. it should be kept in mind if the data is required in all details for a BW upload)
Summarization usually cannot be applied for ERP logistics data or CRM, SRM data.
SAP AG
E2E300
7-49
0.48
Summarization - Example
Billing Document
Accounting Document
Table VBRP
Tables RFBLG, BSEG

Without summarization
Pos
Pos
Account
Materialnumber
1000
S1
20
1001
S2
30
10
1000
S3
10
H1
20
1001
H1
20
H2
15
1001
H2
15
Materialnumber
Unit
Price
S1
20
S2
30
S3
4
5
Unit
Price
With summarization
Pos
Account
Materialnumber
Unit
Price
1000
15
1001
43
In SAP standard an accounting document shows exactly the same number of line items as the
corresponding logistics document (i.e. Billing Document). (see example on top right-hand side).
In case the customer does not need details of the billing document (e.g. material number or unit) in
the accounting document all line items, that differ only in the value for those characteristic fields are
summarized. The price is added up to a total price e.g. by Account
Example:
Account 1000: 6 + 9 = 15
Account 1001: 8 + 20 + 15 = 43
SAP AG
E2E300
7-50
0.49
Data Deletion
Data Deletion
Outdated data is identified.
The functions available for deleting this data
are identified and executed.
Outdated data is removed from the system.
Usually most applicable for non-business relevant data
for which data archiving is not necessary /
for which there is no corresponding archiving object.
Examples for Deletion:
Deletion of spool-requests
Deletion of payment run protocols
Deletion can only be applied for data that is not required for any business or audit purposes.
This is usually true for log or protocol data but usually cannot be applied for transactional business
data.
Still there are many basis tables that will be kept clean with so called Housekeeping jobs. (e.g. Jobs
are deleted from the job overview in TA: SM37)
SAP AG
E2E300
7-51
0.50
Data Archiving
Data Archiving
Identification of data which could be archived
under consideration of
age, business content and/or status of the data
legal compliance
retrieval requirements
interfaces to other systems
Specification of the related archiving objects

Customizing Settings for the residence times
Maintenance of archiving selection variants
Dependencies to other archiving objects
Different to the first three options data archiving deals with data that people (customers business
departments, external auditors) may have a strong interest in and want to preserve the option to
access and display it. Therefore the implementation of data-archiving requires a strong cooperation
with the business process experts and may be also the customers audit department to determine
which archiving approach and setup is feasible.
SAP AG
E2E300
7-52
0.51
Data Archiving: Guiding Principles
Please consider:
Archiving objects are not available for all tables.

Therefore archiving is not always possible!
Before archiving, dependencies related to other tables or

to the business-process have to be checked!
The definition of an archiving strategy is a

complex and time-consuming project!
But normally, this effort has to be done only once!
Business Unit (Business process champion), IT-department

(Application management team) and internal auditing department
have to work together!
Country-specific legal requirements of the tax authorities have to

be taken into account!
Data Archiving means a lot of effort for the customer!
Sometimes it is really difficult to archive data as some functions required in the business process are
not possible after the data has been archived.
Examples:
Table VBOX (Billing Document Rebate Index): after archiving, no reprint of billingdocuments is possible any
more
Table DBERCHZ* (IS-U Billing line items): after archiving, no mass reversal is possible
any more.
Demo 2, 3
SAP AG
E2E300
7-53
0.52
Demo 2: Determine archiving object (1/2)
Determine archiving object or deletion report for growing or
large table (Example: BALDAT, GLFUNCA): TA: SARA
Button Database Tables
In transaction DB15 (that can be accessed by transaction SARA -> Database Tables) the archiving
objects that include records of a given table are listed.
In case of BALDAT this is a more complex example as there are 3 possible archiving objects. Which
archiving object is really the most applicable has to be determined by a more detailed analysis in the
DVM implementation phase.
SAP AG
E2E300
7-54
0.53
Demo 2: Determine archiving object (2/2)
Example for Sales Orders from Business Process Picture:
This is example is the same as before. But this time not based on the largest / growing tables from
DB02 but based on the example sales business process.
Transaction DB15 not only allows to list the archiving objects related a specific table (first option in
screen)
In addition DB15 lists all tables that are included in one archiving object. This gives a good
impression on how complex archiving objects can be, as they cover all data of a business object
which may be spread across many different tables.
SAP AG
E2E300
7-55
0.54
Demo 3: Determine archiving / deletion potential (1/4)
Use transaction TAANA (Table Analysis) for detailed analysis:
This demo can be used to explain one part of the scoping process, i.e. to find out if the data is at all
old enough to be considered to be handled by data archiving or deletion.
Besides this TAANA analysis can also be used for the more detailed analysis that are carried out
during the implementation phase and that analyze the data not only be time, but also by other criteria,
e.g. processing status, dependencies to other business objects, distribution on organizational units,
In this demo we use table VBAK (Sales Order Header Table) to determine the age of sales orders.
Doing: Call TA: TAANA -> Menu: Table Analysis -> Perform Check.
In Popup enter VBAK and press on the highlighted yellow arrow.
SAP AG
E2E300
7-56
0.55
Use transaction TAANA (Table Analysis) for detailed analysis:
Define and ad-hoc variant that includes the fields you are interested in.
NEVER use selective fields as document number, rather USE characteristic fields e.g. plant,
document type.
In this example we use the year of creation. This field is in fact a virtual field that has been defined
before.
As nearly all logistics tables do not contain a separate YEAR field, but usually contain a full date
field (including day, year, month) the analysis by the date field will be hard to use.
Therefore we use a Virtual Field that just uses the Year-part of the full date field for the analysis.
Virtual fields are defined in transaction TAANA_VF or transaction TAANA -> Menu:
Environment -> Virtual fields
SAP AG
E2E300
7-57
0.56
Start analysis and check result:
The analysis is started as background job and the result is displayed on the right-hand side after a
double-click on the menu-tree on the left-hand side.
SAP AG
E2E300
7-58
0.57
Define a virtual field to perform an analysis by year, e.g.
based on creation date
An virtual field as a sub-field of a date field, e.g. month, year can be defined very easily.
Attention: This is regarded as customizing and requires a transport request in customers systems.
SAP AG
E2E300
7-59
0.58
Implementation phases of a Data Volume Strategy
Build
project team
Project leader
IT area
User area (audit)
Application
representative
External
Analysis:
Data and
Requirements
Assignment of
tables to
archiving object
Dependencies
and business
requirements for
archived data:
displaying
business
context
legal
Design:
Archiving
Process
Archiving
concept
Business
Technical
Implementation
plan
Activities
Schedule
Long-term
archiving
schedule
Management
of archive
files
Implementation:
Customizing
and Test
SAP Notes
Maintain
program
Variants
Customizing
Storage system
Functional tests
on
Archiving
Accessing
archived
data
Go-Live
Test phase
evaluation
Preparations
Execution of
archiving
Follow-up
Project
Deliverables:
Project team
formed
Data Content
Analysis
Archiving
business
process analysis
Sign-off
Conceptual
Design
Configured
System
Tested System
Train-the-Trainer
Performance
Analysis
Hand-over
Follow-up
SAP AG
E2E300
7-60
0.59
Customer Example
Starting point
Approx. 290GB DB size and approx. 15GB DB growth per month
Goal
Reduction of DB growth rate to:
Reduce hardware costs
Maintain stable system performance
Response times and system administration
Faster implementation of support packages and upgrade projects
Local currency conversion
Archiving
7 archiving objects from FI, CO, MM and SD
Result (after 15 months)

> 200GB archived
The following slides show some key figures of a real customer example. In fact it is a very small
system but still the DVM implementation proved to have a benefit.
SAP AG
E2E300
7-61
0.60
Customer Example of DB growth
700.00
Expected size
without archiving
600.00
Allocated DB size
500.00
400.00
Allocated DB content
300.00
'Without'
Archiving
200.00
100.00
Initial
Archiving
With regular archiving
DB growth: Reduction:
~15GB/month
~60GB
DB growth: ~7GB/month
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Feb
Mar
0.00
This graphic shows the decreased monthly data growth after the data volume management
implementation. (see blue line).
As every database contains free-space the allocated db size (see yellow blue) differs from the
allocated DB content (see blue line).
SAP AG
E2E300
7-62
0.61
Customer Example of
Dependency Chart for Archiving Objects / Reorg Reports
FI_DOCUMNT
F110
EC_PCA_ITM
EC_PCA_SUM
CO_ITEM (REO)
CO_ITEM (CTR)
CO_TOTAL
CKR1
CO_COPC
CO_COSTCTR
CO_ML_IDX
COPA1_XXXX (C)
COPA1_XXXX (F)
COPA1_XXXX (B)
QM_QMEL
PP_PLAN
Indep.
Requirements
Note
447899
PP_ORDER
QM_CONTROL
COPA1_XXXX (Totals)
QM_PLAN
CS_BOM
PM_ORDER
MM_EKKO
MM_EBAN
SD_VTTK
MM_ACCTIT
RV_LIKP
MM_MATBEL
SD_VBRK
MC_S033
SD_VBAK
SD_VBKA
LE_HU
RVVBSKDL
RL_TA
CHANGEDOCU
BC_SBAL
CATPROARCH
BC_DBLOGS
WORKITEM
SAP Office
IDOC
Object Links
ALE Change Pointer
This graphic is taken from a customer project and gives and overview of the dependencies and
scheduling sequences between archiving objects.
It also contains deletion reports (see down part, right hand side, italic letters: Deletion reports for
Object Links and ALE Change Pointer).
The straight lines between archiving objects show hard dependencies, i.e. one archiving object
must be scheduled before the other.
The dotted lines show recommended sequences
SAP AG
E2E300
7-63
0.62
Sample Business Scenario Archiving Objects
CRM - C00
SAP ECC - TT5
SAP ENTERPRISE
PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Archiving object
CRM_SASALDOC
(3) Archiving
object SD_VBAK
Run MRP
Procurement
Process
(1) Archiving
object RV_LIKP
(2) Archiving
object SD_VBRK
Manufacturing
Process
Create Outbound
Delivery
Create Billing
Document
Post Goods Issue
Archiving object
MM_MATBEL
Warehouse - TT5
Create Outbound
Delivery
Create Picking
Transfer Order
Post Goods Issue
Confirm Picking
Transfer Order
Archiving object
RL_TA
CRM_SALDOC - CRM Sales Documents
SD_VBAK Sales Documents
RV_LIKP Deliveries
SD_VBRK Billing Documents
RL_TA - MM-WM: Warehouse management: Transfer orders
MM_MATBEL - Materials management: Material documents
Observe the suggested order of some of the archiving runs.
SAP AG
E2E300
7-64
0.63
Data Volume Strategy - Optimization
DVM Optimization
How to determine the need for optimization?
DVM Reporting is a tool showing the effect of DVM and shows potential for
improvement
If DVM Reporting is not used it is recommended to check at least on a

yearly basis if new tables show up among the top growing tables
In which cases an optimization is required?
Usually in cases of changed business environment
New business objects have to be included in the DVM strategy

Increasing business volume requires the implementation of more
aggressive residence times
New organizational units (e.g. plants, company codes, ) have been
added and the DVM strategy has to be adjusted
A DVM strategy is set up once but may not fit optimal until the end-of-lifetime of system.
There are various reasons that cause a need for the adjustment of the DVM strategy.
A reporting of the success of the DVM strategy and the latest top growing tables should be
performed at least once a year.
SAP AG
E2E300
7-65
0.64

Data Volume Scoping

Operation
Implementation /
Optimization
The operation part considers the regular job scheduling and monitoring of archiving and deletion
jobs, that have been defined in the DVM strategy.
SAP AG
E2E300
7-66
0.65
Data Volume Strategy - Operation
Key success factor Operation:
Maximum possible throughput with minimum negative effect on standard

operation:
Limit the data volume processed by one job
so that the job fits into the given time window
by using the selection criteria accordingly
Automate job scheduling
Use dynamic variant definition for archive write jobs or delete jobs
Limit the number of archive delete jobs running in parallel by using

scheduler report RSARCHD
Integrate jobs in standard job monitoring tools
Training of operations team on troubleshooting in case of cancelled jobs
Some customers struggle with regular scheduling of archive jobs. Common problems are:
Jobs running in parallel to the productive operation of the system may run slower than on the test
system and may have a negative impact on the overall performance. Therefore the jobs should be
scheduled in smaller chunks to allow to better control them.
As the jobs are often not automated and integrated in the standard job scheduling they have to be
scheduled manually and are assigned to a certain person. In case this person leaves the company or
department the jobs are often stopped without being noticed.
In case of central job scheduling in the SAP basis team this team cannot estimate the impact of a
cancelled job and therefore needs either a contact person in the application management department
to contact in case of any errors or a detailed troubleshooting guideline.
SAP AG
E2E300
7-67
0.66
SAP AG
E2E300
7-68
0.67

Data Volume Scoping

Operation
Implementation /
Optimization
SAP AG
E2E300
7-69
0.68
Business Department
Define Business
Requirements
Business
Process Analysis
No
Monitor
Data Growth
No
DVM Methods
applicable?
DVM
Strategy
Implementation
Yes
DVM
Strategy
Operation
DVM KPIs
reached?
Confirm
DVM Strategy
DVM
Strategy
Optimization
Yes
DVM
Reporting
DVM
Scoping
No
Additional
Potential?
Yes
If a data volume strategy is performed (DVM Strategy Operation), DVR should be scheduled on
regular basis for monitoring the activities and estimating the efficiency.
If additional potential for data reduction is identified the follow up activity will be the optimization
of the DVM Strategy.
SAP AG
E2E300
7-70
0.69
reports on size and growth of your database
reports on top tables of your database
reports on performed archiving activities
reports on the potential for additional reduction
The collected information of the points listed in the slide are used to decide if the implemented
strategy must be reviewed.
It will be identified if for the top tables the corresponding reduction possibilities (e.g. data archiving)
are used or not.
Identifying the top tables and the related archiving objects
Identifying the performed archiving objects and their efficiency (no additional archiving
potential)
Compare both, this means if the performed archiving objects refer to the top tables
This is the indicator for starting an optimization process
The result will also be used for reporting to the management and as basis for decision-making of
optimization follow up activities.
SAP AG
E2E300
7-71
0.70
Two Views in DVM Reporting
SAP System
Archived Data
Archive Files
Online DB
Based on DB tables:
Target state of archiving:
Based on archive files:

Actual state of archiving:
Which are the top tables and their

corresponding archiving objects?
Is archiving already performed on these
tables?
What is the (remaining) archiving
potential for these tables?
Which archiving objects are in use?

How much data has been archived
already?
Is there remaining archiving potential,
i.e. could archiving be done more
aggressively?
SAP AG
E2E300
7-72
0.71
Example: Actual State of Data Archiving
Appl. Area
Arch. Object
Most relevant
Table among
Top Tables?
Size Arch.
File [MB]
No. Archived
and Deleted
Objects
No. of
Archiving
Runs
BC
IDOC
CO
Archiving
Potential
[MB]
EDIDS
4.085,8
5.160.607
80
15.777
CO_ML_BEL
MLIT
3.264,5
5.013.599
10
8.629
CO
CO_ML_IDX
No
1.561,2
5.260.731
CO
CO_ML_DAT
No
1.526,2
5.953.137
11
FI
FI_DOCUMNT
BKPF
535,3
590.589
17.009
CO
CO_ML_SPL
CKMLPRKEPH
527,4
2.049.756
3.472
CO
CO_ORDER
No
85
21.320
CO
CO_COSTCTR
No
44,1
612
MM
MM_MATBEL
MSEG
30,8
78.665
MM
MM_EBAN
No
28,1
35.543
12.509
Evaluation of the actual state of Data Archiving:

Using the function Statistics of the Archive Administration (TA: SARA), the used archiving
objects (current and past) are identified.
For the identified archiving objects the corresponding tables are identified and checked if one of
these tables are part of the identified Top Tables.
As top used archiving object IDOC (archiving of intermediate documents) is identified and also
that the IDOC table EDIDS is one of the top tables
So we see that the reduction of the top table EDIDS and their related tables (EDIDC, EDI40 and
so on) is started and performed. This is derived from the information No. of Archiving Runs
and consider completed archiving runs (write and deletion job is performed successful).
Additionally, the existing archiving potential is listed. This is an indicator for the review of the
settings for the Archiving Object IDOC
Not all IDOC status values are included in the archiving process
The IDOC archiving must be scheduled on occasion
The residence time must be shorten
The Size of Archive. Files and the No. of archived and deleted Data Objects will be used for
determining the archiving efficiency (a low number is an indicator for insufficient archiving)
The number of archiving runs shows how often this archiving is used.
SAP AG
E2E300
7-73
If for an archiving job no most relevant table is listed, you have the information, that this archiving
object is used, but no related table of this archiving object is a top table. This means that this
archiving object is used unrelated to the data growing and data volume.
Demo 4
SAP AG
E2E300
7-74
0.72
Demo 4: Check archiving activities (1/2)
Archiving statistics in TA: SARA offer a good overview
Statistics keep track of the volume of archived data and of the runtime of the archive write and the
archive delete jobs.
The feature of Archiving statistics was implemented with SAP basis 6.10. Archiving runs scheduled
in prior releases are listed without any statistics data. This explains why in the screenshot the first
archive runs for archiving object APPREQUEST show Disk Space of 0,000.
Without selecting an archiving object the statistics for all archiving objects are displayed.
SAP AG
E2E300
7-75
0.73
Demo 4: Check archiving activities (2/2)
Display details for a single archiving session
When selecting an archiving object only those statistic records are displayed.
The details per archive run can be displayed.
The information of most interest is usually:

Deleted DB Space in MB
Attention: The values are calculated on a record length defined in DDIC definition. This can vary
from the physical length of a record on the DB.
SAP AG
E2E300
7-76
0.74
Demo 4: Excursus: Check archiving activities < 6.10
Archiving statistics were implemented with SAP basis release 6.10,
but also on systems based on a smaller release level it is
possible to get an overview on the performed archiving
activities although it is slightly more complicated and less
precise.
SAP AG
E2E300
7-77
0.75
Tables ADMI_RUN and ADMI_FILES (1/2)
ADK writes administration data for each archiving run.
The administration data is needed for the access of archived data.
The administration data is stored in tables ADMI_RUN and
ADMI_FILES.
The content of tables ADMI_RUN and ADMI_FILES provides
detailed information about the performed archiving runs;
e.g., you get the following information per archiving object:
Dates of the performed archiving runs
Status of the performed archiving runs
Number of deleted objects
Sizes of the archive files
Administration data/tables ADMI_RUN and ADMI_FILES
can be archived with archiving object BC_ARCHIVE.
For SAP systems with basis release <6.10 to have to obtain the archiving information directly from
the archiving administration tables.
SAP AG
E2E300
7-78
0.76
Tables ADMI_RUN and ADMI_FILES (2/2)
Number of
archiving session
Date and time of

archiving session
Number of
archived objects
Status of the
archiving session
Size of the archive

file [Byte]
SAP AG
E2E300
7-79
0.77
Creating a simple Statistic
Analyzing table ADMI_FILES
using transaction TAANA with an Analysis-Variant
A_OBJECT
as virtual field of field ARCHIV_KEY
YEAR
as virtual filed of field CREAT_DATE
OBJ_COUNT
STATUS_FIL
FILE_SIZE
For a simple statistic its the best way analyzing the table ADMI_FILES with transaction TAANA
TAANA should use an analysis variant with the following fields

A_OBJECT which is a virtual field based on the original table field ARCHIV_KEY
YEAR which is a virtual field based on the original field CRET_DATE
Note: this is the date of the creation of the archive file and not the creation year of the documents
in this file
OBJ_COUNT
number of objects in this file
STATUS_FIL
value 0
Archiving is running (records will be written in archive-file)
value 1 Deletion is running (records will be deleted in the DB)

value 2 Archiving is completed (the selected records are written in the archive-file)
value 3 Deletion is completed (now the records are written in the archive-file and
deleted from the DB)
Most relevant status!
value 4 terminated
value 5 reloaded
FILE_SIZE size of the created archive file
This way you will get an overview for each archiving object with the distribution over the years of
archiving, status and number of archived objects. You can use the year as basis for the first and last
archiving run of an object. So you see if the object is current used or not.
SAP AG
E2E300
7-80
0.78
Example: Target State of Data Archiving Top 5 Tables
Appl.
Comp.
Table
Name
Table
Size
[MB]
CO
COEP
123.291
EC-PCA
GLPCA
CA
Table
Growth
per
Month
[MB]
% of
DB
(Most)
relevant
Archiving
Object
Size of
Archiving
Files [MB]
No. of
Archived
and
Deleted
Objects
No. of
Archiving
Runs
4.750
13,5
PP_ORDER
30.738
2.539
3,4
EC_PCA_ITM
EDIDS
29.003
1.311
3,2
IDOC
MM
RESB
24.044
2,6
FI
ACCTIT
17.942
1. 311
Archiving
Potential
[MB]
3,6
12
72.000
9.989
4.085,8
5.160.607
80
15.777
Detailed
Analysis
necessary
17.984
MM_ACCTIT
12.035
In this example the top tables are identified and the corresponding archiving objects
The table COEP (CO Line items) is identified as top table and their table size, monthly growth and
proportion of the total database size
If the content of table COEP is in relation to several business objects, now the most relevant
archiving object is identified. Most relevant archiving object means the archiving object by which
the most CO line items will be archived. In this case most of the line items are in relation with
production orders which could be archived by the object PP_ORDER.
You see that there are only 4 archiving runs of this object, but we have identified a high potential for
archiving. So we can recommend that the business object Production Orders must be analyzed
identifying the possibilities for a more efficient usage of the archiving object PP_ORDER.
Top 2 table is GLPCA (Profit Center Actual Line items), but the corresponding archiving object
EC_PCA_ITM is not used in the past. Regarding the data volume and the identified archiving
potential the usage of this object could be recommended.
An other top table is RESB (Reservations/dependent requirements), the data of these table could be
archived by several archiving objects. But identifying the most relevant archiving object a detailed
data analysis is necessary. Analyzing the table RESB we identify the possible archiving objects by
which the RESB data will be archived, but if the corresponding business object could be archived an
additional data analysis of tables which are relevant for these business objects must be analyzed.
SAP AG
E2E300
7-81
0.79
Example:
Archiving Potential of Top Tables per Appl. Component
Archiving Potential per Application Component
Application Component
CA
29,9
CO
84,7
CO-PC
7,6
EC-PCA
9,8
FI
34,7
FI-SL
Archiving Potential (GB)
9,8
MM
29,8
OTHERS
24,9
After the Top Tables with their archiving potential are identified, this archiving potential will be
summarized on application level
This is helpful for decision for which area the implementation or optimization of the DVM strategy
should be started
In the case above, the top areas are Controlling (CO), followed by Accounting (FI) and Material
Management (MM) and Cross Application (CA)
SAP AG
E2E300
7-82
0.80
Example: Data Volume of Top Tables per Year
Archiving Potential per Year
Year(s)
Data Volume (GB)
2005
162,4
2004
145,3
2003
53,8
2002
5,9
2001
3,3
2000
1,8
Rest of years (data archivable)

Rest of data (all years)
23,7
0,0
This example shows the distribution of the data volume from the top tables over then years.
In this example 2005 is the current year and we decide as assumption that the data of the current year
could not be archived regarding an average residence time of 12 month.
If the inquiry day of DVR is e. G. in July 2005 so we calculate that also data of the year 2004 could
not be archived. Note, this is a very rough calculation and should only give an idea about the
reduction potential.
In this example we see that the data older than 2004 are candidates for archiving and we can estimate
the reduction volume.
Rest of years (data archivable) regards data which are older than 2000.
Rest of data (all years) concern data of all years which could not be reduced by archiving, if a
corresponding archiving objects doesnt exist.
SAP AG
E2E300
7-83
0.81
SAP Data Volume Reporting can be used
as reporting tool for performed data archiving activities
as reviewing tool for your data management and archiving

strategy
SAP Data Volume Reporting provides the basis
for management reporting
for the decision of a strategy review
If a DVM strategy is implemented and performed, with Data Volume Reporting

The performed data archiving activities could be monitored and reported
Comparing the analysis results you get the information about optimization potential
New top tables indicates the implementation of additional reduction options
Growing of the data even though data reduction is used, this indicates an review of the
current used settings
The result could be used for management reporting and also for the decision-making of
optimization activities
SAP AG
E2E300
7-84
0.82
Data Volume Management: Supporting

Documentation
Supporting Documentation
Data Management Guide
Introduction to Data Archiving
Performance Aspects of Data Archiving
All documents are accessible via SAP Service Marketplace

www.service.sap.com/data-archiving
Using the link above, general available documents regarding data archiving and data management
could be found.
SAP AG
E2E300
7-85
0.83
Exercise - Data Volume Management: Perform Data

Volume Scoping & Strategy
Exercise
SAP AG 2006
SAP AG
E2E300
7-86
0.84
Exercises
DB02
Identification of total DB size and monthly growth rate [GB]
Identification of top largest tables
Identification of top growing tables
DB15
Identification of corresponding archiving objects
SARA
History on archiving runs for a specific archiving object
Overview of all archiving runs (object independent)
TAANA
Analysis of distribution of data volume by time (e.g. year)
Analysis by archiving criteria (e.g. status, company code, )
SAP AG
E2E300
7-87
0.85
Questions
List the DVM components
Describe the DVM process flow with its components
What are the KPIs to trigger DVM?
What are the criteria for starting a DVM strategy

implementation?
How to evaluate the success of a DVM implementation?
SAP AG
E2E300
7-88
Exercises
Unit:
Lesson:
At the conclusion of this exercise, you will be able to:

Identify potential for a data volume strategy.
Company IDES has determined the need to create a data volume strategy
for the SAP ECC system. Since business process Order-to-Cash is one
of the most important business processes on the system the data volume
strategy has to consider this business process.
12-1 Identify potential measures for a data volume strategy for TT5.
12-1-1 Check the database size and the database growth for system TT5.
Which transaction can you use to determine database size and database
growth?
Answer:______________________________________________________
In order to identify potential for data volume management which other points
besides the database size and database growth have you to check?
Answer:______________________________________________________
List your findings below:
Type of Information
Database Size
Database Growth
Details for TT5
Are database size or database growth sufficient to indicate the establishing of

a data volume management concept?
Answer:______________________________________________________
SAP AG
E2E300
7-89
12-1-2 Check the potential for Data Avoidance, Data Summarization, Data Deletion
and Data Archiving for the 3 fastest growing tables of last month on TT5.
Where can you find information about the potential for these tables?
Answer:______________________________________________________
Table
SAP AG
Size
Avoidance
E2E300
Summarization Deletion Archiving
7-90
12-1-3 Determine the names of the archiving objects for the 3 fastest growing tables
on TT5.
Which transaction in system TT5 can you use to find the information about
the archiving objects?
Answer:______________________________________________________
Table
Archiving Objects
Which other tables would be reduced in size by executing archiving runs for
the objects? List your answers below:
Archiving
Object
SAP AG
Tables involved
E2E300
7-91
12-1-4 Check the history of the archiving runs for the identified archiving objects.
Which transaction in system TT5 can you use to find this information?
Answer:______________________________________________________
Table
Archiving Objects
Archiving Runs already executed?
Check if there are any dependencies on other archiving objects that have to
be considered for the actual archiving runs.
Answer:______________________________________________________
SAP AG
E2E300
7-92
Solutions
Unit:
Lesson:
12-1 Identify potential measures for a data volume strategy for TT5.
12-1-1 Answer:
Use transaction DB02 to check the database size and database growth. In
DB02 choose DB Space History and Space Statistics (there Top n largest
tables and Top n growing tables) to look for the largest tables and fastest
growing tables. To get statistical relevant data choose Month for the fastest
growing tables.
Answer:
You also have to check for the largest tables and the fastest growing tables
Type of Information
Database Size
Database Growth
Top Tables
Top Growing Tables
Details for TT5

~200MB
no clear database growth visible
D010TAB
DD03L
D010INC
MC13VD0KONSETUP
BALDAT
MC13VD0ITMSETUP
Answer:
Database size has to be compared to 500GB, database growth has to be
compared to 20GB per month. Since both are below the system itself does
not indicate the need for data volume management.
12-1-2 Answer:
You can find this information in the SAP Service Marketplace quicklink
/data-archiving (or use new quicklink /ilm directly, there choose Data
Archiving Data Management Guide.
Table
BALDAT
Avoidance Summarization Deletion Archiving
MC13VD0KONSETUP no information in data management guide

MC13VD0ITMSETUP no information in data management guide
SAP AG
E2E300
7-93
12-1-3 Answer:
You can find the corresponding archiving objects via transaction DB15. Enter
the table name in field Objects for Table.
Table
BALDAT
Archiving Objects
BC_SBAL
EMMA_CASE
IHC_ARC
MC13VD0KONSETUP
MC13VD0ITMSETUP
List of tables per archiving object: To get this list enter the above found
archiving objects in field Tables in Object.
Archiving
Object
BC_SBAL
Tables involved
BAL_INDX
BALDAT
BALHDR
EMMA_CASE BAL_INDX
BALDAT
BALHDR
EMMA_CACTOR
EMMA_CASE
EMMA_CMSG_LINK
EMMA_COBJECT
EMMA_CSOLP
IHC_ARC
BAL_INDX
BALDAT
BALHDR
CDCLS
CDHDR
CDPOS_STR
CDPOS_UID
IHC_DB_PN
IHC_DB_PN_BP
IHC_DB_PN_ENQ
IHC_DB_PN_RINFO
IHC_DB_PN_STATUS
IHC_TAB_PN_CONT
SAP AG
E2E300
7-94
12-1-4 Answer:
You can check for archiving runs per archiving object via transaction SARA.
Choose Statistics.
Table
Archiving Objects
BALDAT
BC_SBAL
Archiving Runs already

executed?
no
BALDAT
EMMA_CASE
no
BALDAT
IHC_ARC
no
If you want to see an example for an archiving run, check the archiving runs
for CATPROARCH (belongs to table CATM).
Answer:
The dependency of archiving objects can be checked via the Network
Graphic in transaction SARA. (Icon
any dependencies.
). None of the archiving objects have
Check archiving object SD_VBAK to see what the network graphic looks
like for an object with dependencies.
SAP AG
E2E300
7-95
SAP AG
E2E300
7-96

Unit 7 - Overview Diagramm: Preface

Uploaded by

Document Information

Original Description:

Original Title

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

Unit 7 - Overview Diagramm: Preface

Uploaded by

Copyright:

Available Formats

0

Unit 7 - Overview Diagramm

Business Process Performance

Introduction to E2E Business

Job Scheduling Management

Data Volume Management

Business Process and Interface

Recap Customer Case

measure for performance

MRP Run 1000

MRP Run 3000

Archiving & deletion jobs often have

direct impact on job runtimes

DVM might improve performance & hence

might solve alert situations

Business Process &

SAP AG 2007, Data Volume Management / 1

Data Volume Management

Data Volume Scoping

Data Volume Strategy

Data Volume Reporting

SAP AG 2007, Data Volume Management / 1

After completing this unit, you will be able to:

Understand the elements of Data Volume Management

Have a decision basis on whether Data Volume

Develop a Data Volume Management roadmap for your

SAP AG 2007, Data Volume Management / 1

SAP AG 2007, Data Volume Management / 1

When to consider Data Volume Management?

Managing data volume and data growth for

SAP Systems and/or

SAP Solution Landscapes with

database sizes > 500 GB* or

monthly data growth > 20 GB*

* Depending on System Component

SAP AG 2007, Data Volume Management / 1

SAP ECC - TT5

Create Sales Order

Create Sales Order

Create Sales Order

Current database size of

Current database size of SAP

Post Goods Issue

Post Goods Issue

SAP AG 2007, Data Volume Management / 1

Noticed effects in the last weeks:

through Data Volume Management

SAP AG 2007, Data Volume Management / 1

Data Reduction supported by DVM have benefits regarding

through Data Volume Management

SAP AG 2007, Data Volume Management / 1

Downtime Losses by Application

Typical Loss Per Hour of

Source: Storage Magazine

SAP AG 2007, Data Volume Management / 1

SAP AG 2007, Data Volume Management / 1

Administration costs for 1 Terabyte storage are five to seven

SAP AG 2007, Data Volume Management / 1

In the end the total costs for storage must be considered

SAP AG 2007, Data Volume Management / 1

MB51 transaction: Material Document List

Vertical Markets and Industries