_________________________________

_________________________________
_________________________________
_________________________________

Advanced Data
Archiving and Data
Management
Techniques for
SAP Administrators

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Jim Malfetti
Brandywine Data Management Group

_________________________________

2008 Wellesley Information Services. All rights reserved.

Introduction

_________________________________

We will explore many advanced archiving topics that will

benefit companies that have already started their
archiving activities, as well as those just getting started
We will explore the analysis phase of the archiving
project in great detail, as well as the prototyping through
implementation phases
We will also explore nonstandard solutions to common
archiving problems that are offered by various SAP
Certified Partners
Brand new SAP archiving functionality will also be
explored, as well as the future direction of SAP with
regard to archiving, Information Lifecycle Management
(ILM), BI, etc.
2

What Well Cover

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

_________________________________

Support of ongoing archiving activities

Advanced analysis techniques
Prototyping, testing, and production scheduling
Nonstandard requirements and typical solutions
Nonstandard retrieval of archived data
Archiving projects of the future
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
3

Scheduling and Monitoring Archiving Jobs

_________________________________

Preprocessing jobs
Write jobs
Delete jobs
Post-processing jobs
Store jobs
Archive Information System (AIS) load program
PBS indexes (possibly)
Data Retention Tool (DART) extracts and
views (possibly)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
4

New Objects

_________________________________

Most companies already have 15-30 archiving objects

in production
Mature projects typically add 6-8 new archiving objects
per year
Many new large or fast-growing tables can be addressed
through SAP Note-available programs and not archiving
objects
Complete database, table, and index analysis is required
at least once a year

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
5

SAP Note Identification and Application

_________________________________

SAP Notes must be reviewed for archiving objects even

after initial implementation
Many SAP Notes that are not contained in Support
Packages have multiple application paths depending on
if youve already archived data or are preparing to,
for example
Support Packages most likely contain SAP Notes that
affect existing archiving objects
Not all Support Package corrections and enhancements
are automatically available, some require explicit
activation of Business Configuration (BC) Sets Don't

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Forget
6

Storage Administration

Maintaining storage media

_________________________________

WORMS
New Magnetic Media (e.g., Hard Disk Write Once)

_________________________________
_________________________________

Maintaining file systems, directories, etc.

Creating new logical archives
Upgrading SAP

_________________________________

_________________________________
_________________________________

May require upgrading of third-party Content Server software

May require upgrading of storage protocol (RFC HTTP)

_________________________________
_________________________________

Upgrading archive servers and other hardware

_________________________________
_________________________________
7

SAP Upgrades

_________________________________

New data archiving functionality available:

_________________________________

SAP R/3 4.6C

SAP R/3 4.7
SAP NetWeaver 7.0 BI Nearline Storage (NLS)
SAP ERP 6.0 (ILM)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Well discuss new archive file

routing in the last section!

_________________________________
_________________________________
_________________________________
8

New Applications

SAP CRM considerations

_________________________________
_________________________________

Archiving is available and recommended in most cases

Image integration is likely

_________________________________
_________________________________

SAP BW

_________________________________

Many standard extractors cannot load from archived SAP

R/3 data
f Can be done, but it is a mini-project
SAP BW data can be archived using the familiar ADK process
or the new NLS interface available in SAP NetWeaver 7.0 (usage
type BI)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
9

Other Impacts on Archiving

Company acquisitions, mergers

_________________________________

Combining archive systems and strategies

_________________________________

Company spin-offs, subsidiaries, downsizing

_________________________________

_________________________________

Special archiving requirements

SAP consolidation projects

_________________________________

Merging SAP systems

Merging SAP archived data

_________________________________

_________________________________
_________________________________
_________________________________
_________________________________
10

New Projects

Information Lifecycle Management

_________________________________
_________________________________

Expiring data
f Certificate of destruction
Identifying data
f Legal discovery
Holding data
f Exceptions to retention rules and destruction

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Material Safety Datasheet (MSDS) solution

_________________________________

Avoid unacceptable growth in specific tables

f DRAO
Maintain integrity of documents and standard retrieval
transactions

_________________________________
_________________________________
11

What Well Cover

_________________________________

Support of ongoing archiving activities

Advanced analysis techniques
Prototyping, testing, and production scheduling
Nonstandard requirements and typical solutions
Nonstandard retrieval of archived data
Archiving projects of the future
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
12

Research Historical Database Growth

_________________________________
_________________________________

Launch DB02
and click on
Space
statistics

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Txn
DB02

_________________________________
13

Projected Database Growth

_________________________________
_________________________________

Projected Database Growth

_________________________________

6000

_________________________________

5000

GBs

4000

2000

_________________________________

3000

_________________________________

1000

_________________________________

0
0 5 - 05 - 05 r- 05 -05 -0 5 l-05 - 05 - 05 - 05 -0 5 -0 5 -0 6 - 06 - 06 r- 06 -06 -0 6 l-06 - 06 - 06 - 06 -0 6 -0 6 -0 7 - 07 - 07 r- 07 -07 -0 7 l-07
v
t
t
v
r
r
r
n
c
n
n
n
c
n
ny
b
y
b
y
b
Ju
J u A ug S ep Oc No De
J u A ug S ep Oc No De
J a Fe Ma Ap Ma
Ju
Ju
J a Fe M a A p M a
Ap Ma
Ju
J a Fe Ma

_________________________________

New functionality June 2005

_________________________________

Upgrade to mySAP ERP June 2006

_________________________________

New Business Unit (acquisition) October 2006

14

Identify Largest and Fastest-Growing Tables

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Launch DB02
and click
on Space
statistics

_________________________________
_________________________________
15

Identify Largest and Fastest-Growing Tables (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
16

Identify Largest and Fastest-Growing Tables (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
17

Identify Largest and Fastest-Growing Tables (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
18

Identify Largest and Fastest-Growing Tables (cont.)

_________________________________
_________________________________

Download the
report to a local
spreadsheet file

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
19

Identify Largest and Fastest-Growing Tables (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
20

Identify Largest and Fastest-Growing Tables (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
21

Identify Largest and Fastest-Growing Tables (cont.)

_________________________________

Look at both table size and growth rate

_________________________________

Fastest-growing tables may not be your largest tables

f Might be due to new functionality

Don't
Forget

_________________________________
_________________________________

Size in KB

Top 25 Tables by Growth

_________________________________

18,000,000
16,000,000
14,000,000
12,000,000
10,000,000
8,000,000
6,000,000
4,000,000
2,000,000
0

_________________________________
_________________________________

Size

_________________________________
APQD
S871
BSAS
S022
AFVC
SOC3
COKA
JEST
COBK
CKIT
S852
AFVV
RESB
JCDS
RFBLG
MSEG
AUSP
CDCLS
BSIS
ACCTIT
COSS
COEP
COSP
CKIS
GLPCA

_________________________________

Table Name

_________________________________
22

Other Considerations

Tables with poor performance may not always be the

largest tables

_________________________________

Therefore, it is important to identify your performance

bottlenecks

_________________________________
_________________________________

Identify most active tables

_________________________________

ST03(N) Database performance

_________________________________

ST10 Table call statistics

_________________________________

_________________________________

Identify response time issues

_________________________________

ST05 Performance trace

_________________________________

Identify tables or programs in slow transactions

_________________________________
23

Map Tables to Archive Objects

_________________________________
_________________________________

DB15

_________________________________
_________________________________

Txn
DB15

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
24

Identify Your Archiving Objects

_________________________________

Map archiving objects

to your tables ...

_________________________________
_________________________________
_________________________________

Txn
DB15

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
25

Identify Your Archiving Objects (cont.)

_________________________________
_________________________________
_________________________________

Warning

_________________________________

Tables in yellow will require

additional analysis

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
26

Multiple Archive Objects per Table

_________________________________
_________________________________

DB15

_________________________________
_________________________________
_________________________________

_________________________________

Which is the correct object?

_________________________________
_________________________________
_________________________________
_________________________________
27

Multiple Archive Objects per Table (cont.)

Some common tables map to more than one

archive object

_________________________________
_________________________________

Choosing the correct archiving object is not obvious, and

will require additional analysis
Sometimes more than one archive object may legitimately map
to one table (e.g., CDCLS)

_________________________________
_________________________________
_________________________________

Depends on:

_________________________________

_________________________________

Release of SAP R/3

Actual composition of data in table

_________________________________

Example tables are:

_________________________________

COEP, COEJ, COSP, COSS, COST, GLPCA

CDHDR, CDCLS, AUSP, VBAP, NAST, etc.

_________________________________
28

Multiple Archive Objects per Table (cont.)

CO tables

_________________________________
_________________________________

Profit Center Accounting or Special Ledger?

_________________________________
_________________________________
_________________________________

Purchasing or sales?

_________________________________

VBFA, VBPA, VBUK, VBUP

CO_COSTCTR, CO_ITEM, PP_ORDER, or PS_PROJECT?

CDCLS, JCDS Change docs

JEST, JSTO Status
KOCLU Condition records

_________________________________

GLPCA

_________________________________

_________________________________

Orders, deliveries, or billing?

_________________________________

RESB Reservations
29

Archive Object Mapping for CO Tables

_________________________________

Tables COEP, COEJ, COSP, COSS, COST

_________________________________

Each of these tables may map to multiple archive objects

SAP has developed a series of programs that will map these
tables to appropriate archive objects (RARCCOA1,2,3)
SAP Note 138688 will describe the procedure for mapping each
CO** table to the appropriate archive object

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
30

Archive Object Mapping for CO Tables (RARCCOA2)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
31

Archive Object Mapping for Table GLPCA

_________________________________

Table GLPCA

_________________________________

This table maps to either Profit Center Accounting or

Special Ledger
This table may contain both PCA and SL data
SAP has developed a program that will help reveal the
composition of data from table GLPCA (ZAGLPCA1 and
ZAGLPCA2)
EC_PCA_ITM
f Ledgers 8a, 8c, 8e, or 8z
FI_SL_DATA
f Ledgers 0F (ZZ + Z tables)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
32

Archive Object Mapping for GLPCA (ZAGLPCA2)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
33

Notes and Tools

Understanding data type/distribution

_________________________________
_________________________________

SAP Note 203545 GLPCA

SAP Note 317219 Special Ledger
SAP Note 316468 ACCTIT

_________________________________
_________________________________
_________________________________

Performing data distribution analysis

TAANA ( 4.6C)
SE11
SE16
Third-party analysis tools (PBS Analyzer, IXOS Analyzer)
SAP Note programs

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
34

Transaction TAANA

_________________________________

4.6C table analysis: Assists with table to object

mapping, document distribution, and data type analysis

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
35

Final Mappings

_________________________________

Add final archiving objects

that were identified.
In the case where more than
one archive object maps to
the same table, split the table
size and growth
proportionally to your
findings.
Some other shared tables like
CDCLS, NAST, and AUSP will
remain. To map these tables
to the appropriate archive
object(s), with 100%
accuracy, data composition
must be determined.
36

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Final Technical Analysis Results

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
37

Technical Analysis Tips

Dont just think your largest tables are your largest

archive objects

Tip

_________________________________
_________________________________

Map at least your top 200+ tables to archive objects

f Surprising how many smaller tables add up to one large
archive object

_________________________________
_________________________________

Sxxx tables can be mapped to Sxxx archive objects

Z table could be covered by FI_SL_DATA
Dont overestimate the effects of archiving

_________________________________

_________________________________
_________________________________
_________________________________

Not every table mapped to an archive object will be subject to

deletion by that archive object

_________________________________

Further time distribution analysis will reveal how much

data is archiveable, based on residency rules

_________________________________
38

Analysis Summary

Complete analysis should be done at least yearly.

_________________________________
_________________________________

Every six months is better!

SAP Data Management Guide is a great resource

for analysis.
Many tables may be addressed through SAP Note
programs, not archiving objects.
ASUG discussion forum is a great resource
for information.
PBS Software GmbH offers a Database Analyzer solution
and is the only certified SAP Partner solution available.

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

39

What Well Cover

_________________________________

Support of ongoing archiving activities

Advanced analysis techniques
Prototyping, testing, and production scheduling
Nonstandard requirements and typical solutions
Nonstandard retrieval of archived data
Archiving projects of the future
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
40

Seven Steps to Your Data Archiving Project

_________________________________
_________________________________

Technical
Analysis

Build Project
Team

Functional
Analysis

_________________________________

Craft
Archiving
Strategy

_________________________________

_________________________________
_________________________________

Prototype

Testing

Implement

_________________________________

_________________________________
_________________________________

We covered steps 1-4 in my

other session, A Detailed
Introduction to SAP
Data Archiving

_________________________________
41

Prototype

_________________________________

Prototype

Prepare Development client

Transports to QA

Exchange directory, file names, etc.

Prepare QA environment for archiving

_________________________________
_________________________________

Logical archive, file size, automatic, job

variants, etc.
Object-specific config (document life)
Apply SAP Notes

Archive as you would in production

_________________________________

Split jobs by retention

_________________________________

Build Archive Information System (AIS)

structures, test Document Relationship
Browser (DRB), etc.

_________________________________

_________________________________

Configure archiving objects

_________________________________

_________________________________

Prepare all supported retrieval methods

_________________________________

Share prototype with user community

42

Testing
Testing

_________________________________

Four key tests

1. Initial test plan

2.

_________________________________

Validating representative archivable data in

QA environment
Identifying data that needs cleansing
Applying SAP Notes in QA
Representative cross-section of data
Can be performed before first workshop
with business

Unit test plan

End-user testing scenarios

Testing online transactions, reports,
and scenarios
Testing retrieval of archived data

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

43

Testing (cont.)
Testing

_________________________________

Four key tests (cont.)

3. Mass test plan

4.

Multiple jobs
Archive as you would in production
(splitting jobs)
Goal is to extrapolate production test
run times

Production test plan

Run archive object EXAMPLE first to test

exchange directory and storage
communications
Ensure jobs behave as expected in production
Ensure all configuration, customizing, and
SAP Notes are correct
Dont forget to activate your AIS structures! 44

Testing Tips

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

_________________________________

Testing

Functional analysts should create the test

plans/scripts

A group of end users should perform

testing

Tip

And define online data and archived data to

support them

Theyre less familiar with the design

This is a form of training
Helps divide the work!

Functional analysts should then compare

test results with initial analysis/tests
Always obtain final end-user acceptance
and signoff
45

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Implement

_________________________________

Implement

Prepare production archiving schedule

_________________________________

Ensure all configuration is applied

and correct
Ensure that you have proper authorizations
New functionality allows interruption of write
job for some objects

_________________________________
_________________________________
_________________________________
_________________________________

Prepare required retrieval methods

_________________________________

Activate InfoStructures

_________________________________
_________________________________
_________________________________
46

Implement (cont.)

Implement

Storage considerations

_________________________________

Do you have enough room in the exchange

directory?
Is a backup procedure in place?
If you are using WORM (optical) jukeboxes, do
you have enough platters, or open slots?

_________________________________
_________________________________
_________________________________
_________________________________

Define production variants

Execute and monitor your archiving jobs

_________________________________

_________________________________
_________________________________

External scheduling possible

f SAP Notes 458670, 133707, 205585

_________________________________

Plan future archiving schedule

_________________________________
47

What Well Cover

_________________________________

Support of ongoing archiving activities

Advanced analysis techniques
Prototyping, testing, and production scheduling
Nonstandard requirements and typical solutions
Nonstandard retrieval of archived data
Archiving projects of the future
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
48

Standard Technical Dependencies

_________________________________
_________________________________

SARA

Transaction code SARA

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Check the Network Graphic for technical dependencies

49

Detecting Technical Dependencies

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Check SAP Note 391350 for more information on the Network Graphic
50

Technical Dependencies Solutions

Implement the archiving objects in order

_________________________________
_________________________________

Flexibility

Self-imposed dependencies

_________________________________

Unique implementation order

_________________________________

_________________________________

Analysis required for strategy

Additional checks are sometimes possible

_________________________________

Can create custom archiving objects with dependencies

Industry-specific archiving objects and additional
dependencies

_________________________________
_________________________________
_________________________________

ISU_BILLZ

_________________________________
51

Detecting Functional Prerequisites and Issues

Need basic understanding of potential issues

_________________________________
_________________________________

DART, SAP BW, interface prerequisites

_________________________________

Testing might reveal:

_________________________________

Business complete issues

Business process disruption
Additional retrieval requirements

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
52

SAP DART Dependency for Live SAP R/3 Data

Data Retention Tool (DART)

_________________________________
_________________________________

Identify DART requirements as early as possible.

DART can only be loaded from online SAP R/3 data!
DART extracts cannot be created from archive files.

_________________________________
_________________________________
_________________________________

Common nonstandard DART requirements

Create DART extracts from archived data.

f Can be done as a mini-project
Source DART-relevant archived data into temporary tables
or an Archive Information System Structure
Can be very complex and stress the system
f PBS CDART solution
Requires purchase of software

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
53

SAP BW Dependency for Live SAP R/3 Data

SAP Business Information Warehouse (SAP BW)

_________________________________
_________________________________

SAP BW data can only be loaded online data

There is no standard way to load archived SAP R/3
into SAP BW

_________________________________
_________________________________

Archive Information System bridge

_________________________________

Create an Information Structure

Run transaction RS02 to create a DataSource in SAP R/3
Replicate the DataSource to SAP BW and assign to InfoSource
Schedule the extraction via an InfoPackage in SAP BW

_________________________________
_________________________________
_________________________________
_________________________________

This is a great choice for data that is readily available in AIS

structures, and when you have the space and resources to
load the data

_________________________________
54

Should We Archive Master Data Records?

Master data is traditionally not archived aggressively

_________________________________
_________________________________

Master data usually has too many technical dependencies and

prerequisite archive objects
Most companies only archive master data records that were
created in error

_________________________________
_________________________________
_________________________________

However, some companies do occasionally have the

need to archive material, vendor, and customer
master records

_________________________________
_________________________________

Can be a very complex project

_________________________________
_________________________________

In standard SAP, once a master data record is archived, you

can no longer create new master records with reference to
Issue the old one ...

_________________________________
55

Creating Material with Reference to an Archived Material

_________________________________

1. Standard SAP will not

allow a user to create
new material with
reference to an
archived material
master record (MM01)
2. PBS CMT (Material
Master Data,
Batches/Special Stocks
Module) transaction
code/PBS/ZHRM allows
a user to create new
material with reference
to an archived material
master record

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
56

What Well Cover

_________________________________

Support of ongoing archiving activities

Advanced analysis techniques
Prototyping, testing, and production scheduling
Nonstandard requirements and typical solutions
Nonstandard retrieval of archived data
Archiving projects of the future
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
57

Building a Successful Retrieval Strategy

Business teams/end users need access to data that has

been archived
Myth: SAP cant access data once its archived

_________________________________
_________________________________
_________________________________
_________________________________

Result: Many companies keep too much data online

f And do not comply with retention policies

_________________________________

Truth: SAP contains standard retrieval options

_________________________________

They are sufficient most of the time

Custom development and third-party solutions offer even more
options ...

_________________________________
_________________________________
_________________________________
_________________________________
58

Options for Retrieving Archived SAP Data

Standard retrieval options

_________________________________
_________________________________

Single document display

Document relationship browser
Archive information system
Analyze reports
Printlists
Display of original outgoing document (.pdf)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Additional custom or third-party retrieval add-ons

_________________________________

Custom Archive Information System/DRB enhancements

Custom retrieval reports and programs
PBS archive add-ons

_________________________________
_________________________________
59

Available Retrieval Solutions

_________________________________

Standard SAP retrieval is evolving to provide archiveenabled reporting and transactions

Although more rare, there are legitimate circumstances
where standard SAP retrieval is not sufficient
PBS Software GmbH offers a packaged add-on
corresponding to groups of archiving objects that
provides additional access options

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Provides access to archived data in near replicas of the original

transaction most seamless access available
PBS offers the only SAP-certified solutions for access to
archived data

60

_________________________________
_________________________________
_________________________________
_________________________________

PBS Retrieval for Archived Purchase Order

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Standard SAP
Transaction Code ME23
will not allow the user to
display an archived PO
PBS CMM (Purchasing)
Transaction Code
/PBS/ME23 will allow the
user to view archived PO
in the original view

_________________________________
_________________________________
_________________________________

* Indicates PO
was archived

_________________________________
61

PBS Retrieval for Archived Purchase Order (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Double-Click

_________________________________
Drill-down
relationships
remain intact

_________________________________
_________________________________
62

Other Custom Retrieval Solutions

Archive Information System modifications

_________________________________

Custom InfoStructures
Custom field catalogs

_________________________________
_________________________________

DRB modifications

_________________________________

Offers limited opportunity

_________________________________

DART views

_________________________________

Custom DART views and extracts can be developed not only to

meet tax or audit requirements, but for internal business
reporting needs as well

_________________________________
_________________________________
_________________________________
_________________________________
63

What Well Cover

_________________________________

Support of ongoing archiving activities

Advanced analysis techniques
Prototyping, testing, and production scheduling
Nonstandard requirements and typical solutions
Nonstandard retrieval of archived data
Archiving projects of the future
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
64

Current and Future Archiving Integration

Upgrades

_________________________________
_________________________________

One customer has 150 archiving objects in production

_________________________________

Expiring qualified data in accordance with retention policies and

other regulations
Preserving data subject to Legal Holds (LH)

Image integration

_________________________________

ILM projects

_________________________________

SAP (new archiving functionality)

Storage media or devices
ArchiveLink storage servers

More and more archiving objects

_________________________________

The same common ADK archiving foundation, as well as NLS

_________________________________
65

Current and Future Archiving Integration (cont.)

_________________________________

Special archiving requirements to remove Company Codes

(CCs), for example

_________________________________
_________________________________

Merging SAP systems

Merging SAP archived data

_________________________________

Decommissioning legacy systems

_________________________________

COLD and ArchiveLink integration

_________________________________

_________________________________

SAP consolidation projects

_________________________________

Combining archive systems and strategies

Company spin-offs, subsidiaries, downsizing

_________________________________

Company acquisitions, mergers

_________________________________
_________________________________

New document types or workflow, may change DB/Table

dynamics and require new data archiving objects

DART, SAP BW, SAP NetWeaver 7.0 (usage type BI), CRM

_________________________________

Outgoing documents

Invoices
POs, etc.

_________________________________
66

Current and Future Archiving Projects

_________________________________

ILM projects

_________________________________

Identifying expired data

Expiring data by retention
f Certificate of destruction
Identifying data that needs to be excluded from destruction
f Legal hold orders
File splitting?
Preparing for expiration before archiving
f Archive File Routing SAP NetWeaver 7.0

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
67

New SAP XML Archiving for ABAP and Java

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Source: SAP, 2006

68

ADK vs. XML Archiving

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Source: SAP, 2006

69

New SAP WebDAV-like Archive Hierarchy

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Source: SAP, 2006

70

Information Lifecycle Management Requirements

_________________________________

The information lifecycle ...

Documents
or data are
created in
SAP R/3

Creation of
subsequent
data or
documents

_________________________________
Data or
documents
are cleared
and business
complete

_________________________________

Online
residence
time
requirements
expire

_________________________________
_________________________________
_________________________________

Data is
archived

Archived data
is retrieved
and viewed by
users

Retention of
online and
archived data
or documents
expire

_________________________________

Data or
documents
are
destroyed

_________________________________
_________________________________
_________________________________
71

How to Destroy Data in SAP

_________________________________

1. Expired data must be archived

_________________________________

2. Expired data must be located

_________________________________

3. File can be deleted if on file system

_________________________________

4. File can be physically destroyed if located on a

_________________________________

unique platter

_________________________________

Assuming no other data resides on that platter with a

shorter retention period or legal hold

_________________________________

5. Run archive object BC_ARCHIVE to clean up final

_________________________________

traces of data in SAP

6. Perform retrieval cleanup (AS InfoStructures, PBS
indices, etc.)

_________________________________
_________________________________
72

Preparation for Archive Management Data Deletion

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
73

Archive Management Data Deletion

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
74

Legal Hold Orders

Legal hold order

_________________________________

Process by which an organization must preserve and prepare

all forms of electronic information when litigation is anticipated
or confirmed
Federal Rules of Civil Proceedings (FRCP)
f Updated December 1, 2006

_________________________________
_________________________________
_________________________________
_________________________________

No fancy SAP solution yet

_________________________________

_________________________________

ASUG has formed an influence council to gather the

requirements for this and other related ILM issues

_________________________________

Procedures can be established to hold data in SAP

_________________________________

Standard options may increase legal liability

_________________________________
75

Plan for Retention Before Archiving

_________________________________

Example Scenario:

_________________________________

Archive Object FI_DOCUMNT

f Retention rules:
7 years for company code 1000
10 years for company code 1100
FI_DOCUMNT customizing only allows one content repository
f Unable to store archive files to different content repository in
SAP releases < SAP NetWeaver 2004
f Unable to selectively hold some data and expire other data
in most archive files

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
76

Need for Archive File Routing

_________________________________
_________________________________

Archive Object: FI_DOCUMNT

Company Code

Retention

100

7 Years

1100

10 Years

1200

15 years

Content
Repositories

_________________________________
_________________________________
_________________________________

F1

_________________________________

Previously, this functionality

was not available, until

SAP NetWeaver 7.0

_________________________________

F2

_________________________________
_________________________________
F3

_________________________________
77

SAP NetWeaver 7.0: Archive File Routing on Different Levels

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Source: SAP, 2006

78

What Well Cover

_________________________________

Support of ongoing archiving activities

Advanced analysis techniques
Prototyping, testing, and production scheduling
Nonstandard requirements and typical solutions
Nonstandard retrieval of archived data
Archiving projects of the future
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
79

Resources

SAP Insider regular and special features columns:

Performance and Data Management, Information
Lifecycle Management (SAP Insider)

www.sapinsideronline.com

Quarterly, Yearly (Jan-March 2007 and 2008 edition)

_________________________________
_________________________________
_________________________________
_________________________________

www.asug.com/forums/

_________________________________

ASUG Annual (spring) and TechEd (fall)

_________________________________

ASUG Archiving Discussion Forum

_________________________________

_________________________________

BITI Archiving Track

Archiving Your SAP Data (seminar training CD)

_________________________________

www.sapinsidermultimedia.com/products/archiving_data

_________________________________
80

Resources (cont.)

SAP Data Management Guide

_________________________________
_________________________________

http://service.sap.com/ilm * > Data Archiving > Data

Management Guide

_________________________________

Your storage system vendor

Helmut Stefani, Archiving Your SAP Data (SAP PRESS,

July 2007, 2nd Edition, ISBN: 978-1-59229-116-8).

Brandywine Data Management Group

_________________________________

IXOS, Mobius, PBS, etc.

_________________________________
_________________________________
_________________________________
_________________________________

www.BrandywineDMG.com

_________________________________
_________________________________
* Requires login credentials to the SAP Service Marketplace

81

7 Key Points to Take Home

Most companies already have 15-30 archiving objects in

production and are increasing at a rate of 6-8 new
archiving objects per year
Complete analysis should be done at least yearly

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Every six months is better!

Many tables can be addressed through SAP Note

programs, not archiving objects
Third-party retrieval is sometimes required

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
82

7 Key Points to Take Home (cont.)

_________________________________

Prerequisites such as DART and SAP BW cannot be

ignored without increasing your organizations liability
Data retention/ILM issues are becoming more important
drivers than simply reducing the size and growth rates
of tables
Even if your organization has a current archiving
strategy, it should be revisited to ensure new matters,
such as compliance or new functionality, are taken
into consideration

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
83

Your Turn!

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

How to contact me:

Jim Malfetti
Jim@BrandywineDMG.com

_________________________________
_________________________________
_________________________________
84

Notes:
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________

Notes:
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________

Notes:
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________

Wellesley Information Services, 990 Washington Street, Suite 308, Dedham, MA 02026

Copyright 2008 Wellesley Information Services. All rights reserved.