Professional Documents
Culture Documents
-Deepak Kumar
Senior Consultant, Infosys Technologies Ltd.
Agenda
Key decisions
Recommendations
Proposed Roadmap
Scope of Work
Determine current and projected dB growth
Identify largest and high growth tables
Identify relevant Archiving objects
Identify tables without Archiving objects
Archiving requirement essentials and key decisions
Evolve a housekeeping framework
Recommendations and Proposed Roadmap
Agenda
Key decisions
Recommendations
Proposed Roadmap
No
Data Prevention
Yes
Yes
Data Aggregation
be aggregated ?
No
Yes
Data Deletion
Housekeeping
Framewwork
really needed ?
No
Data stays
in dB
No
Yes
Data Archiving
be archived ?
Periodic
be deleted ?
Data Prevention
Data is generated that is not required by business
Deactivate certain tables in SAP from being updated
This prevents online db to be updated unneccessarily
Should be done after business confirmation
Example: Spool can be deleted automatically after their output
(TST03), Summarised accounting data from MM to FI module
Table ACCTHD,ACCTCR ,ACCTIT etc.
Data Aggregation
High volume data can be aggregated as totals with sufficient
levels of details
- Have data aggregated at header level instead of also
having at item levels
Obtain business confirmation for the identified data
Data created in future would only be agregated. Previous
data may still need to be archived
Example: Profit centre accounting data (table GLPCA), CO line
items by period (table COEP) , profitability analysis tables
SAP R/3 : Archiving Requirement Essentials
Data Deletion
Data which is not required for archiving is deleted shortly after
its creation
Ensure the data to be deleted is not refrenced by other set of
data
For tables where deletion is performed, check database
indexes for fragmentation if system response is slow.
Regenerate indexes on weekly basis
Example: SAP office data (table SOC3), RFC call data (table
ARFCSDATA), Spool data (table TST03) etc.
SAP R/3 : Archiving Requirement Essentials
Agenda
Key decisions
Recommendations
Proposed Roadmap
Archive Files
External Storage
System
Archiving
Object
File System
Online dB
Optical
Archive
Data Archiving
Benefits of Archiving
Important for long term database management
Improved system response time and performance
Faster backup and recovery time, Faster release upgrades
Reduced time for client copies and client refresh
Enhanced Users productivity
Reduced maintenance and administration cost Lower TCO
-Administration cost are 5 7 times more than the cost of
storage hard disks
-Better usage of resources e.g. Network, CPU, memory
because of reduced data in dB - lower or no investments
SAP R/3 : Archiving Requirement Essentials
Archiving Object
Archiving object are SAP standard objects that facilitates the
process of archiving (have linked programs)
Archiving object defines which database tables must be
handled together as single business object
1 Archiving object = 1 Business object
Business Object
Archiving Object
Material Document
Sales Order
Sales Invoices
FI Documents
Workflows
MM_MATBEL
SD_VBAK
SD_VBRT
FI_DOCUMNT
Workitem
Agenda
Key decisions
Recommendations
Proposed Roadmap
Current dB Size
Allocated Space 605 GB
Used Space 586 GB
% Used : 97
550
500
450
400
Alllocated Space (GB)
Size (GB)
Linear Growth +
New Projects
Dec- Jan- Feb- Mar- Apr- May- Jun- Jul- Aug- Sep- Oct- Nov- Dec04 05 05 05 05 05 05 05 05 05 05 05 05
Time
(Facts and Figures for illustration purpose only)
400.00
300.00
DB Allocated Space
DB Used Space
200.00
100.00
Jun-05
Apr-05
Mar-05
Feb-05
Jan-05
May-05
Time
Dec-04
Nov-04
Oct-04
Sep-04
Aug-04
Jul-04
Jun-04
May-04
Apr-04
Mar-04
Size (GB)
500.00
Finalise with
Business
and IS
Description
TST03
SOC3
13.91
11.73
Spool Data
SAP Office
Deletion/Prevention
Deletion/Archiving through program and
not through Archiving Object
ARFCSDATA
3.15
Deletion/Prevention
Program/Report Name
RBKP
SAPLMRMC
EDIDC
RBDAPP01
SWWWIHEAD
RSWWCOND
EBAN
SAPLZEPB_PMFUNCTION
DB AccessTime as % of
overall Response Time
(Above 40)
RBDAPP01
88.2
RSWWCOND
80.8
SDBONT06
44.4
MIRO
64.9
Agenda
Key decisions
Recommendations
Proposed Roadmap
Object Creation
Residence Time
SAP Online dB
Residence Time :
Time between Object
creation and moving to
archive
-Business requirements
-IT requirements
Retention Time
External Storage System
Retention Time :
Time between moving to
archive and deletion from
archive
-Legal/Audit requirements
-Internal requirements
-Business requirements
The Retention period would need to be agreed with Business, Legal and
Audit departments. The requirements varies from country to country.
(Facts and Figures for illustration purpose only)
Note_317219_FI Ledger.txt
Step 2: Enter
search/relevant
parameters
Technical View
2.
Business view
3.
Agenda
Key decisions
Recommendations
Proposed Roadmap
Formulate Recommendations
Identified largest tables/archiving object should be archived
Identified tables where archiving is not possible should be
managed using other data management procedures
Data management approach should be followed as
applicable:
-Data Deletion, Data Prevention, Data Aggregation
-Evolve and Implement Housekeeping Framework
-Data Archiving
Recommendations (contd.)
Third party dB analysis tools are recommended as these
follow focussed approach and would save effort and time
Finalise data residence and retention time in consensus with
Business and Data retention policy before archiving
For External storage system, jukebox with mutli-storage
media should be used to store archived data
Tables with unsatisfactory performance should be first
checked for indexes fragmentation
SAP R/3 : Archiving Requirement Essentials
Recommendations (contd.)
Analysis of Interdependencies and data distribution across
Archiving object and associated tables should be performed
Apart from project testing procedures, initial test run should
be performed in the production system for sample load
Data retrieval strategy should be based on requirements from
Business, Auditors, Customer Service and IS
Archiving Project team should have R/3 technical and
functional expert, audit and business representation
SAP R/3 : Archiving Requirement Essentials
Recommendations (contd.)
Evaluate impact of performing archiving in R/3 on other
systems/applications of landscape and vice versa
Example: If archiving is being performed in R/3 system, its
impact on other applications like APO,EBP,BW should be
considered
Perform archiving on sample/small data set in production
system before executing final archiving
Consider Z tables for archiving (if relevant)
Document & Compare performance parameters before and
after the Archiving project
Agenda
Recommendations
Proposed Roadmap
Proposed Roadmap
Pre-project Activities :
-Evolve Housekeeping Framework
-Finalize norms and convention for Archiving object
configuration/technical settings
-Finalize residence and retention time with Business, Legal
and Audit departments
-Finalize data and frequency of retrieval from Business,
Legal and Audit users
-Formulate the Archiving jobs execution strategy
-Plan for Test systems readiness
-Plan for Hardware Infrastructre (e.g. Storage System)
SAP R/3 : Archiving Requirement Essentials
Pre-Project Activities
Analysis Phase
Implementation Phase
Thank You