EUROPEAN IT Landscape

SAP TECHNICAL Management

EDUCATION
CONFERENCE 2002

Lecture

Sept. 30 – Oct. 2, 02 Bremen, Germany

Data Archiving in mySAP.com

Georg Fischer
SAP AG

Agenda

Î Introduction

Î Data Archiving Basics

Î Data Archiving Projects

Î Information and Contacts

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 2

1
 Data Archiving

Online File System Offline/

Nearline

Access

Display Database

Application Data Data Object

Archive Files Storage System

Archive and Delete Store

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 3

Benefits

Value Generation
when using mySAP Technology Data Archiving is
achieved by:

1 System Availability
Faster and easier upgrade to
higher software releases.
Shorter runtime for backup
and recovery.
2 Use of Resources
Reduced hardware costs for
Disk, CPU, Memory as well
as administration costs.

3Response Times
Shorter response times in dialog mode
for all employees.

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 4

2
 The Importance of Data

The top concern for 90% of all IT managers:

“Managing data and information overflow intelligently”
(CSC Ploenzke AG)

“Globally, data storage is becoming a major branch of industry and

the central focus of information technology”
(Dataquest, GartnerGroup Research Note: Storage will dominate server spending)

„ Relative hardware investment

‹ 1998: 57% servers, 43% storage
‹ 2003: 30% servers, 70% storage

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 5

What Does Data Storage Cost ?

“Hard disks are inexpensive! If I need more database space, I’ll add
another disk to my storage system.”
(Customer statement)

Production System

Test System (1, 2, ...) Euro-System ???-System

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 6

3
 Distribution of Storage Costs

“Hard disk costs represent less than a quarter of storage costs.”

(Giga Information Group)

Various
(Training, other costs)

10%

Personnel Harddisk

45% 23%

Storage Mgmt
Environment
(Soft- & Hardware)
(Electricity, physical space)
3% 19%

“Administration costs for 1 Terabyte storage are five to seven times

higher than the storage costs”
(Dataquest/Gartner)

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 7

Storage Costs

1 Storage Costs
German and American customers report storage
costs (without personnel costs) of US$ 4,000 –
US$ 15,000 per gigabyte in a productive database.

2 Outsourcing
German customers report
outsourcing storage costs of DM
1,000 per month and per gigabyte.

3 Cost Effectiveness
The average price for 1 gigabyte of enterprise disk space
was US$ 9600 in 1991. In 2001 the price is US$ 290. This
represents an annual improvement of 42%.

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 8

4
 Agenda

Î Introduction

Î Data Archiving Basics

Î Data Archiving Projects

Î Information and Contacts

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 9

Data Archiving and Storage

mySAP.com System External Storage System

ArchiveLink Archive
Database System

Application data
Data objects File system HSM
System
Alternative
Storage system

SAP 3rd Party (optional)

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 10

5
 Data Archiving versus Optical Archiving

Incoming Outgoing
Documents Documents

Hyperlink

Archive files
Print lists

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 11

Archive Development Kit – ADK

Development tool for Data Archiving solutions

„ SAP AG
‹ Application developers integrate archiving functionality into the application
„ Customer
‹ Archiving solutions for customer-specific tables and extensions
Data
Application

Data Base mySAP.com

Applications

Adjustment of code page, number format, structure

ADK changes, compression, file handling, job scheduling

Archive Files

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 12

6
 Archiving Object

Definition of logical units in business processes

All programs required for archiving, for example preprocessing, read, write
and delete programs

Definition of required Customizing

Archiving Object

Customizing Data

Programs

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 13

Write and Delete

SAP Database Write program

Archive file

Delete program Archive file

Delete program

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 14

7
 Access to Archived Data

Using print lists

(in combination with an optical storage system)

Reporting from the application

Accessing single objects from the application

Implementing the Archive Information System – AS

(SAP Note 99388)

Implementing the Document Relationship Browser – DRB

(SAP Note 217404)

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 15

Archive Information System

Browsing through archive files

Configurable index based on info structures

„ Ad-hoc access to archive files
„ Using database tables for fast access

Direct access to single data objects

Access to original documents via SAP ArchiveLink

Early availability as transport down to SAP Release 3.1I

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 16

8
 Archive Information System

Archive Information System

Archive Retrieval
Archive Explorer
Configurator

Create Read
Archive
Information
Structure

Archive files

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 17

DRB - Document Relationship Browser

Simultaneous access to archived and online data

Early availability as transport down to Release 3.1I

All common archiving objects are connected

„ SD: Sales activities, Sales orders, Delivery documents, Billing
documents
„ FI: Accounting documents
„ CO: Controlling documents
„ MM: Purchase requisitions,
Purchase orders,
Material documents,
Logistics invoice verifications

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 18

9
 Starting Point for DRB

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 19

Browser Display

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 20

10
 Exception: Reload to Database

The reload function is not available for all

archiving objects

1 Scenario
Reload immediately after data
archiving
2 Scenario
Reload some time after data
archiving
„ Restoring the database due to „ Can result in business
an error inconsistencies
(incorrect selection, incorrect
customizing of residence
periods)

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 21

Data Archiving in mySAP CRM 3.0

Based on established Data Archiving Practices

„ Use of Archive Development Kit (ADK)
„ Integration of archive information system

Based on SAP Web Application Server 6.10

Data archiving highly integrated into mySAP CRM object definition

„ System status controls the archiving process
‹ Separation of the archivability check and the actual archiving
„ Date of the last archivability check in the header table of the CRM object
‹ Good performance by optimizing the access

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 22

11
 Data Archiving in mySAP CRM 3.0

Optional
„ Archivability check runs permanently in the background
„ Set status to “to be deleted” or carry out direct physical deletion

CRM Archiving Objects

„ Activities only
„ One Order
„ Business Partner
„ Product

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 23

Data Archiving in mySAP BW 3.0

Two possibilities:
„ Access archive files using mySAP BW
‹ General recommendation: first fill BW structures, then archive
„ Archiving mySAP BW structures

Archivable Objects
„ InfoCubes
‹ Data archived as flat structures
„ ODS objects (A Version)

Deletion process
„ Read data from archive for verification
„ Delete verified data from InfoCube
„ Removing data from aggregates
‹ Invalidate aggregates and rebuild
„ Benefit: performance and administration

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 24

12
 Data Archiving in mySAP BW 3.0

Business Information Warehouse

InfoCube ODS

PSA

BW Extractors

R/3 Extractors

SAP BW SAP R/3

Archive-Files Archive-Files

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 25

Agenda

Î Introduction

Î Data Archiving Basics

Î Data Archiving Projects

Î Information and Contacts

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 26

13
 Find the Right Time

1 A “healthy” System
Data Archiving should not be
seen as the last resort for
preventing total system collapse

2
after all other means have been
exhausted. Early planning
You should ensure that the
performance of your
systems remains efficient.

3 Interdisciplinary process
Data Archiving requires a high degree of
cooperation between user and IT departments.

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 27

Table Growth in Accounting

Database Size
500
450
400
350
300
[GB]

250
200
150
100
50
0
19990501
19990201

19990601

19990801

19991101
19981201

19990101

19990301

19990401

19990701

19990901

19991001

Date

Date Actual Size in GB Monthly Growth in GB

01.01.1999 33.17 1.90
01.02.1999 36.09 2.92
01.03.1999 73.78 37.69
01.04.1999 137.96 64.18
01.05.1999 190.01 52.05
01.06.1999 256.99 66.98
01.07.1999 324.87 67.88
01.08.1999 376.00 51.13
01.09.1999 428.37 52.37
01.10.1999 438.06 9.69
01.11.1999 470.25 32.19

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 28

14
 Phases of an Archiving Project

Build Data Design and Implemen-

Test
project team analysis conception tation

„ Project leader „ Table size „ Documentation „ SAP Notes „ Test phase

„ Growth rate concept „ Transports evaluation
„ IT area „ Accompanying (audit)
„ Variants „ Preparations
„ User area (audit) archiving object „ Archiving
„ Server „ Implementation
concept
„ Application „ Dependencies ‹ Business configuration „ Follow-up
representative „ Legal ‹ Technical „ Customizing
„ External requirements „ Storage system
„ Residence time „ Implementation
plan „ Carry out
„ Access ‹ Activities archiving
requirements session
„ Authorizations ‹ Schedule „ Postprocessing
„ Storage „ Long-term if required
system/medium archiving
schedule
‹ Management
of archive
files

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 29

Considerations Before Data Archiving

Yes Can the Yes

Is the data Summarize
data be data
still required?
summarized?

No No Yes

Deactivate Can the data be archived?

the creation
of the data
No Yes

Data remains Archive

in the data!
database

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 30

15
 Customer 1

Starting point
Approx. 290 gigabyte DB size and approx. 15 gigabyte DB growth per
month

Aim
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
19 archiving objects from FI, CO, MM, SD, and HR

Result (at October 2000)

>200 gigabyte archived

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 31

Customer 1

700.00

Expected size
without Archiving
600.00

Allocated DB size
500.00

400.00

Allocated DB content
300.00

'Without' Initial
Archiving Archiving With regular archiving
200.00

100.00
DB growth: Reduction: DB growth: ~7 GB/month
~15 GB/month ~60GB
0.00
01.04.1999

01.06.1999

01.07.1999

01.09.1999

01.02.2000

01.03.2000

01.04.2000

01.08.2000

01.09.2000
01.03.1999

01.05.1999

01.08.1999

01.10.1999

01.11.1999

01.12.1999

01.01.2000

01.05.2000

01.06.2000

01.07.2000

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 32

16
 Customer 2

Starting point
Approx. 300 gigabyte DB size and approx. 5 gigabyte DB growth per
week

Aim
“To archive high impact areas as aggressively as possible and
establish a procedure and infrastructure for a repeatable, ongoing
archiving process”

Archiving
Project divided into 4 phases
Archiving objects from FI, CO, MM, SD, PCA, IDOC

Result
Project phase I approx. 100 gigabyte archived (1999)
Project phase I – III approx. 160 gigabyte archived (2000)

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 33

Customer 2

1400,0

1200,0 Expected Growth

without Data Archiving

1000,0
Volume (GB)

800,0

Actual Growth
600,0 with Data Archiving

400,0

200,0

0,0
99

00

01

02

03

04
01
00

01

02

03

04
99

00

02

03
n

n
kt
b

b
kt

kt

kt

kt
Ju

Ju

Ju

Ju

Ju

Ju
Fe

Fe

Fe

Fe

Fe
O
O

Timeline

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 34

17
 Agenda

Î Introduction

Î Data Archiving Basics

Î Data Archiving Projects

Î Information and Contacts

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 35

Documentation

Managing SAP Archiving Projects

Data Prevention Checklist
Guide to Data Archiving in mySAP Retail

http://service.sap.com/data-archiving
„ Media Center ⇒ Literature

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 36

18
 Presentations

SAP Data Archiving Introduction

Data Archiving Projects
Data Archiving and mySAP Retail

http://service.sap.com/data-archiving
„ Media Center ⇒ Presentations

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 37

SAP Customer Trainings

Î BC660 Data Archiving

„ Level 3
„ 3 Days

Î BC670 Data Archiving - Retrieval

„ Level 3
„ 2 Days
Î BC680/WDE680 (USA/Germany)
„ Level 3
„ 1 Day

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 38

19
 Feedback

http://www.sap.com/teched/bremen/

Î Conference Activities

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 39

Q&A

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 40

20
 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 41

Copyright 2002 SAP AG. All Rights Reserved

„ No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
„ Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
„ Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of
Microsoft Corporation.
„ IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®,
OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix
and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
„ ORACLE® is a registered trademark of ORACLE Corporation.
„ UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
„ Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and
other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
„ HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
„ JAVA® is a registered trademark of Sun Microsystems, Inc.
„ JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
„ MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One.
„ SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries
all over the world. All other product and service names mentioned are trademarks of their respective companies.

 SAP AG 2002, TechED_02 Bremen, PT4D2P5, Georg Fischer / 42

21