Introduction to Data Archiving in SAP R_3 Enterprise

8/12/2019 Introduction to Data Archiving in SAP R_3 Enterprise

http://slidepdf.com/reader/full/introduction-to-data-archiving-in-sap-r3-enterprise 1/39

DATA ARCHIVING

IN SAP R/3 ENTERPRISE

DATA ARCHIVING

IN SAP R/3 ENTERPRISE

Georg Fischer PM Data Archiving

SAP AG



SAP AG 2003, SAP NetWeaver Data Archiving, Georg Fischer / 2

Agenda

Data Archiving Projects

Access to Archived Data

Data Archiving Basics

Information and Contacts

Introduction




Data Archiving

Database

Application

Data

Data Objects

Archive and Delete

Access

Store

Offline/

Nearline

File SystemOnline

Archive Files

Display

Storage System




Benefits

1ystem AvailabilityFaster and easier upgrade to

higher software releases.

Shorter runtime for backup

and recovery.

2se of Resources

Reduced hardware costs forDisk, CPU, Memory as well

as administration costs.

Value Generationthrough Data Archiving within SAP NetWeaver

3esponse TimesShorter response times in dialog mode

for all employees.




Reflection

20 GB

Freeing Up Storage Space

Data files

10 GB

Archiving

Compression to 20 %

2 GB

2 GBBack up

on tape

System

copies

80 GB

Total amount of storage space saved: 97,5




Distribution of Storage Costs

“Hard disk costs represent less than a quarter of storage costs.”(Giga Information Group)

“Administration costs for 1 Terabyte storage are five to seventimes higher than the storage costs”(Dataquest/Gartner)

Various

(Training, other costs)

10%

Environment

(Electricity, physical space)

3%

Storage Mgmt

(Soft- & Hardware)

19%

Hard disk

23%Personnel

45%




Agenda





Introduction




Data Archiving and Storage

Database

Data objects

SAP 3rd Party (optional)

mySAP.com System External Storage System

Archive

System

HSM

System

Alternative

Storage system

ArchiveLink

Application data

File system




Data Archiving versus Optical Archiving

Incoming

Documents

Outgoing

Documents

Archive files

Print lists

Hyperlink




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

ADK Adjustment of code page, number format, structurechanges, compression, file handling, job scheduling

mySAP.com

Applications

A p pl i c a t i on

D a t a

Data Base

Archive Files




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

Programs

DataCustomizing




Agenda





Introduction




Accessing Archived Data

Database

SAP System Archive Files

ADK

100%

DRB Application

Business view

Retrieval from DB + Archive

Business processes

Index / Archive Info Structure

AS

Indexing

Retrieval of archived data

Technical display for all archiving objects

Display of object lists




Archive Information System

Flexible creation of archive file indexes

Configurable info structures stored in transparent database tables

Manually filled using selected archive file(s)

Automatically filled during archive delete phase

Retrieval of archived data

Technical view for all archiving objects

Document lists Based on info structures

Based on ad hoc evaluation of selected archive files

Generic tool also for customer developments




Archive Explorer




Document Relationship Browser

Document

RelationshipBrowser

Display

Database

User Display

• Archive Explorer

• Transaction ALO1

• User role SAP_DRB

• Application transactions

Archive

Files

Application

Data

Infra-

structure

Display of business processes

across archive and databaseboundaries




Document Relationship Browser




Personalization in the User Administration




Personalizing the Browser Display




Display Archived Data




Delivery




Delivery - Processing




Orders




Orders - Conditions




Exception: Reload to Database

2cenario

Reload immediately after data

archiving

Restoring the database due to

an error (incorrect selection, incorrect

customizing of residence

periods)

ScenarioReload some time after data

archiving

Can result in business

inconsistencies

Reload function is not availablefor all archiving objects




Agenda





Introduction




Finding the Right Time

1 “healthy” SystemData Archiving should not be

seen as the last resort forpreventing total system collapse

after all other means have been

exhausted.

2arly planning

Ensure that the performanceof your systems remains

efficient.

3nterdisciplinary processData Archiving requires a high degree of

cooperation between user and IT departments.




Table Growth in Accounting

Database Size

050

100150200250

300350400450500

1 9 9 8 1 2 0 1

1 9 9 9 0 1 0 1

1 9 9 9 0 2 0 1

1 9 9 9 0 3 0 1

1 9 9 9 0 4 0 1

1 9 9 9 0 5 0 1

1 9 9 9 0 6 0 1

1 9 9 9 0 7 0 1

1 9 9 9 0 8 0 1

1 9 9 9 0 9 0 1

1 9 9 9 1 0 0 1

1 9 9 9 1 1 0 1

Date

[ G

B ]

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.9801.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




Phases of an Archiving Project

Data

analysis

Design and

conceptionTest

Implemen-

tationBuild

project team

Project leader

IT area

User area (audit)

Applicationrepresentative

External

Table size

Growth rate Accompanying

archiving object

Dependencies

Legalrequirements

Residence time

Accessrequirements

Authorizations

Storagesystem/medium

Documentation

concept(audit)

Archivingconcept

Business

Technical

Implementation

plan Activities

Schedule

Long-termarchivingschedule

Management

of archivefiles

Test phase

evaluation Preparations

Implementation

Follow-up

SAP Notes

Transports Variants

Serverconfiguration

Customizing

Storage system

Carry outarchivingsession

Postprocessingif required




Considerations Before Data Archiving

Is the data

still required?

Can the

data be

summarized?

Can the data be archived?

Yes Summarize

data

Noo

No

Data remains

in the

database

Archive

data!

Deactivate

the creation

of the data

Yes

Yes

Yes




Customer Example

Starting pointApprox. 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 (October 2000)

>200 gigabyte archived




Customer Example

0.00

100.00

200.00

300.00

0 1 .

0 3 .

1 9 9 9

0 1 .

0 4 .

1 9 9 9

0 1 .

0 5 .

1 9 9 9

0 1 .

0 6 .

1 9 9 9

0 1 .

0 7 .

1 9 9 9

0 1 .

0 8 .

1 9 9 9

0 1 .

0 9 .

1 9 9 9

0 1 .

1 0 .

1 9 9 9

0 1 .

1 1 .

1 9 9 9

0 1 .

1 2 .

1 9 9 9

0 1 .

0 1 .

2 0 0 0

0 1 .

0 2 .

2 0 0 0

0 1 .

0 3 .

2 0 0 0

0 1 .

0 4 .

2 0 0 0

0 1 .

0 5 .

2 0 0 0

0 1 .

0 6 .

2 0 0 0

0 1 .

0 7 .

2 0 0 0

0 1 .

0 8 .

2 0 0 0

0 1 .

0 9 .

2 0 0 0

DB growth:

~15 GB/month

'Without'

Archiving

Initial

Archiving

Reduction:

~60GB

With regular archiving

DB growth: ~7 GB/month

Allocated DB content

400.00

500.00

600.00

700.00

Expected size

without Archiving

Allocated DB size

A d




Agenda





Introduction

D t ti




Documentation

Managing SAP Archiving ProjectsData Prevention Checklist

Guide to Data Archiving in mySAP Retail

http://service.sap.com/data-archiving

Media Center Literature

P t ti




SAP Data Archiving Introduction


Data Archiving and mySAP Retail

http://service.sap.com/data-archiving

Media Center Presentations

Presentations

SAP Customer Trainings




SAP Customer Trainings

BIT660 Data Archiving

Level 3

3 Days

BIT670 Data Archiving - Retrieval

Level 3

2 Days

BIT680/WDE680 (USA/Germany)

Level 3

1 Day

Copyright 2003 SAP AG All Rights Reserved




No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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 AG 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.

Copyright 2003 SAP AG. All Rights Reserved

Introduction to Data Archiving in SAP R_3 Enterprise

Documents

Transcript of Introduction to Data Archiving in SAP R_3 Enterprise