Date

SAP CONFIDENTIAL
Opportunity Roadmap - Fact sheet
<Opp.name> <Client name>
Opp / Pipe ID Company Current Mastercode Opp Owner Closing last * 1.000
Phase Month change EUR

Organization of Opportunity Team Clients Need To Act Overview of our Offer

Management Sponsor of MU  Business Situation (facts), Their Problem,  Solution Scope
Impact, Need to Act; What if they do nothing?  Field Service Value Proposition
Responsible Consulting Manager  SAPs USPs (differentiators)

Opportunity Team (+ Role)

 N.N. (Bid Manager)
 N.N. (Solution Architect)
Client
 N.N. (Industry Expert)
Actual Status/Results Risks/ Threats
 N.N. (…)  abc  abc
Project Name … …
 Customer Responsible (GAD, GAM, AE,
CEM/CP)
 N.N.
Opportunity Owner

CEM / CP
Involved Partner name

AE / AM Competitors Next Steps

Education Revenue X€
1. …. 1. …
Date
Solution Fit Y 2. …

Customer Feedback G

Conditions/Budget R
Margin X%
Staffing/Delivery R
Price-/Project Type Fixed Price
Probability (personal
35 %
© 2011 SAP AG.
judgment)
All rights reserved. GD Days X days 1
SAP Data Archiving Approach

We categorized the analysis as follows:

 Identification of low hanging fruit

 Determination of a long-term Data Archiving/Growth Management

strategy for RQ1 (Copy of Production System)

© 2011 SAP AG. All rights reserved. 2

Analyzed Production DB and determined

 The DB tables that were unnecessarily large, and that immediate

measures that could be taken to address this issue
 The application areas that needed to be archived
 The configuration of the R/3 system which was causing the growth
 The skill set required to ensure a successful archiving project
 Conducted a detailed technical analysis of the application areas
 Provided a list of Industry-wide data retention policies

© 2011 SAP AG. All rights reserved. 3

Overview of RQ1

Database is just over XXX, with XX% free-space

As a summary of the archiving analysis, the following areas have been
identified as areas requiring attention:
 Document Management
 Special Ledger
 House-keeping – Basis Areas
 Production Planning
 Financial Accounting
 Profit Center Accounting
 Profitability Analysis
 Sales & Distribution
 Controlling
 Human Resources
 Warehouse Management
 Plant Maintenance
 Project Systems

© 2011 SAP AG. All rights reserved. 4

Phase I – Quick Wins

Application Area Tables/Archiving Object Description

Document Management CV_DVS Document Management System

System
Materials Management MM_ACCTIT MM- Accounting interface posting data

Basis IDOC Intermediate Documents

Basis BC_SBAL Archiving object for application log

Basis TST03 TemSe data

Basis APQD/APQI Data Definition Queue

Business Workplace SOFFCONT1/SOC3/ SAP Office/Business Workplace Tables

SOOD/SOST/SOOS
Basis ARFCSDATA ARFC Call Data (Callers)

© 2011 SAP AG. All rights reserved. 5

Phase II – Long Term Data Management

Application Archiving Object Description Business IRS- Relevant for Industry-wide

Area Impact most companies retention
Average

Special FI_SL_DATA Totals and line Medium No Current +

Ledger items in FI-SL Previous Two
Years
Production PR_ORDER Process order Medium No Current +
Planning Previous Two
Years

Financial FI_DOCUMNT Financial High Yes Current +

Accounting Accounting Previous Two
documents Years

Profit Center EC_PCA_ITM Profit ctr. Medium No Current +

Accounting accounting: Previous Two
actual and Years
plan line items

Profitability COPA1_WWPA Costing-based Medium No Current +

Analysis CO-PA, Previous Two
operating Years
concern
WWPA
© 2011 SAP AG. All rights reserved. 6
Phase II – Long Term Data Management
(continued)

Application Area Archiving Object Description Business IRS- Relevant for Industry-wide
Impact most companies retention
Average

Sales & RV_LIKP Delivery Medium Yes Current +

Distribution Documents Previous Two
Years
Controlling CO_COPC Archiving Medium No Current +
product Previous Two
costing data Years

Sales & SD_VBRK Billing Medium Yes Current +

Distribution Documents Previous Two
Years

Materials MM_MATBEL Material Medium Yes Current +

Management Documents Previous Two
Years

Controlling CO_ITEM CO line items Medium No Current +

Previous Two
Years

© 2011 SAP AG. All rights reserved. 7

Phase II – Long Term Data Management

Application Area Archiving Object Description Business IRS- Relevant Industry-wide

Impact for most retention
companies Average

Cross – CHANGEDOCU Change Medium Yes Current +

Application Documents Previous Two
Years
Sales & SD_VBAK Sales Medium Yes Current +
Distribution Documents Previous Two
Years
Human Resources PA_CALC HR: Payroll High No * Country-
accounting specific
results
Human Resources PA_TIME PA: Time data - High No * Country-
Results of specific
analysis
Controlling COPA2_WWPA Account-based Medium No Current +
CO-PA, Previous Two
operating Years
concern WWPA

Quality QM_CONTROL Q check Medium No Current +

Management transaction Previous Two
data Years

© 2011 SAP AG. All rights reserved. 8

Phase II – Long Term Data Management (ctd)

Application Archiving Description Busines IRS- Relevant Industry-

Area Object s Impact for most wide
companies retention
Average
Warehouse RL_TA MM-WM: Medium No Current +
Management Warehouse Previous
management: Two Years
Transfer
orders
Plant PM_ORDER Service and Medium No Current +
Maintenance maintenance Previous
orders Two Years

Project PS_PROJECT Project Medium No Current +

Systems system: Previous
Operative Two Years
structures

© 2011 SAP AG. All rights reserved. 9

Agenda

 Summary of SAP Findings

 Archiving Project Phases

 Next Steps

 Q&A

© 2011 SAP AG. All rights reserved. 10

Phases of an Archiving Project

Build Data Design and Imple-

Test
project team analysis conception mentation

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

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

© 2011 SAP AG. All rights reserved. 11

Archiving Staffing Requirements

Project Manager:
Responsible for communicating and driving project at customer site
Heavy involvement throughout the life of the project

Functional Expert resource involvement

Responsible for resolving conflicts between objects to be merged
Responsible for providing functional guidance throughout project within their area
of expertise
Responsible for establishing testing procedures to be utilized during testing
cycles
Low involvement in Project Design Phase
Heavy involvement when Drawing up Concept phase
Low involvement in Technical Analysis Phase
Heavy involvement in Testing Cycles

© 2011 SAP AG. All rights reserved. 12

Archiving Staffing Requirements (ctd.)

Basis Resource Involvement

Responsible for setting up tools/authorizations on productive system in
preparation of the Project Design Phase
Responsible for System Refreshes during technical/testing cycles
Heavy involvement in establishing a Multi-client Test system
Heavy involvement in establishing/enhancing Multi-Client Productive system
Moderate involvement during technical/testing cycles

Executive Level involvement

Steering committee meeting bi-monthly
Involvement levels as needed to ensure successful project

© 2011 SAP AG. All rights reserved. 13

Agenda

 Introduction
 Overview of Archiving Functionality

 Introduction to DART

 Summary of SAP Findings

 Archiving Project Phases

 Next steps

 Q&A

© 2011 SAP AG. All rights reserved. 14

Action Items and Next Steps for Archiving
project

Setup an archiving team

At least one resource from each functional area for archiving should be identified
as an archiving team member. Also, a Project Manager, Basis representative(s),
DB Administrator, Internal/External Auditor and R/3 security representative

DART (Data Application Retention Tool)

Before any archiving or deletion of data should be initiated, determine whether a
DART project needs to be implemented

Retention Sign Off

A compromise should be reached between with the functional and technical
people with regard to retention of the data. Large databases are difficult to
manage, and space and performance are adversely affected if there is little/no
data cleanup or maintenance in place

© 2011 SAP AG. All rights reserved. 15

Action Items and Next Steps for Archiving
project

Determine subsequent access needs to the data

Before any data should be removed from the R/3 database, subsequent access
needs to the data must be identified and addressed

Testing – DART, Archiving Functionality, Archive Information System

Testing and evaluation of DART (if required) and Archiving functionality should
take place as soon as possible. The archiving team members should be aware
what it involved at a technical and functional level for each application area

Good housekeeping procedures

The first time an archiving project is undertaken, it can be considered a mini-
implementation, after that it becomes a regularly scheduled task, like any other
basis job(s) on the system

© 2011 SAP AG. All rights reserved. 16

Archiving Checklist

Analysis
Build the archiving project team
Conduct a technical analysis of the database
Determine the archiving objects required
Identify the dependencies between the object(s) (Transaction ‘SARA’  Network
Graphic)
Determine the residence time(s)
Determine what subsequent access needs (if any) will be required
Establish an authorization concept
Estimate the anticipated data volumes

© 2011 SAP AG. All rights reserved. 17

Archiving Checklist (ctd.)

Design and Conception

Determine the sequence in which the data should be removed from R/3
Evaluate the storage media
Create an operational concept for the management of archived data

Implementation and Go-Live

Implement customizing
 Application-specific customizing (residence times)
 Logical Filename and logical file path (transaction file)
 Archiving object-specific customizing (transaction SARA)
 ArchiveLink customizing (if a third-party archive system is required)
Testing under realistic conditions

© 2011 SAP AG. All rights reserved. 18

Archiving Checklist (ctd.)

Creating a procedure description for:

 Accessing archived data
 Implementing reporting
 Analysis of archived data
Training end-users
Execute archiving
Execute post-processing for each archiving session (check whether
reorganization is necessary, update statistics, backup of archive files)

© 2011 SAP AG. All rights reserved. 19

Thank You!

Contact information:

F name MI. L name

Title
Address
Phone number