Download - Overview v6.ppt
SAP Archiving Service Offering Overview
December 2002
Implementing SAP Archiving is not a matter of if … . but when
Our belief is that SAP Archiving will be implemented at every SAP implementation. It is our mission to enable our project teams in a position to win this work and be successful at implementing SAP Archiving solutions.
It is not necessary to implement archiving for several years.
Small companies don’t need data archiving. Data archiving requires third party tools. Archived data is gone and cannot be
retrieved.
Outbound and Inbound documents are handled the same.
Business Users don’t need to involved.
SAP Archiving Misconceptions:
Recommended implementation of archiving is 6 – 9 months after go-live.
Production database size grows exponentially with business growth.
Archiving can be accomplished with network storage or HSM.
Archived data can be viewed via the Archive Information System or vendor add-ons within SAP.
Inbound and Outbound archiving are completely different processes.
80% of archiving implementation is determining legal and business requirements.
SAP Archiving Offering Overview
SAP Archiving Realities:
What is provided by this offering?
This offering is intended to provide a high level understanding of the following:
Assets provided by the offering.
The key drivers and considerations associated with an SAP Archiving Project.
The tangible Accenture differentiators for this type of implementation.
The SAP Archive Offering has been developed based on the experience of over many engagements across industries.
The SAP Archive Offering includes a “toolkit” that can be used to jump start a team at the front end of a project.
SAP Archiving Offering Overview
So What is the Offering?
Methodology
At the core, the Offering is an Methodology supported by a detailed Estimating Model, and enhanced with tangible Delivery Accelerators
Credentials & Benchmarks
Lessons Learned
KX Homepage and Knowledge Links
Strategic Delivery Considerations
Key Project Contacts
It also includes:
Proven Accenture Methodology
Deliverables
Tools
Delivery Accelerators
Archiving DART Implementation
Database Reorganization
Estimating Model
Planning Delivery
Managing
Operating
What is SAP Archiving and Database Reorganization?
Key Considerations & Benchmarks
Accenture Differentiation
Client Credentials
3 Components of Archiving and Reorg
Data Archiving
Database Reorganization
DART Data Retention Tool
•Flat •File
SAP R/3
SAP Archiving and Reorganization Components
Without a Archiving and Reorganization Strategy . . .
. . . high database growth and increased performance issues arise
A pristine environment .....
Can turn into ....
SAP Archiving and Reorganization Strategy
..... an environment out of control
What is Data Archiving?
What is DART?
What is Database Reorganization?
Data Archiving is the moving of identified data, specified by a given time frame, to an external source. This data is still accessible to users and auditors.
SAP’s Archive Development Kit (ADK) provides pre-existing programs to remove transactional and master data from the R/3 system.
ADK retrieval programs and/or third party Document Imaging tools provide the means to display archived data necessary to fulfill legal and business retention requirements.
What is Data Archiving?
Data Archiving is the process of removing data that is no longer
needed in the system, but which must remain accessible either for
business or legal reasons.
Data Purge is the removal of transaction data from the database after a specified period of time. This purged data cannot be retrieved
Document Imaging captures and stores an image of an outgoing SAP document. The image is captured when the document is printed. Document Imaging also allows inbound documents to be scanned and to accept faxes.
3 Types of Data Archiving
Common Misconceptions
It is not necessary to implement Data Archiving until the SAP system is several years old
Small companies do not need to implement Data Archiving
Data Archiving requires expensive third-party tools
Since Data Archiving is an IT project, the business users do not need to be involved.
Archived data cannot be retrieved.
Space created by Archived Data can never be reclaimed.
Misconceptions of Data Archiving
Archiving Object ArchiveFiles
Analyze
Data Archiving ADK session
Optional Storage
e.g. SD_VBAK
WORMTapeCD
- Codepage updates- ADK
R/3
Archive flat files may be stored on disk, CD, tape or WORM. If the archiving object has an Analyze program, the user may view the archived flat file
1 2
The Data Archiving Process
Documents
R/3 DB
Archiving Object ArchiveFiles
Analyze
Data Archiving ADK session
Delete Program
e.g. SD_VBAK
- Codepage updates- ADK
R/3
Archiving object’s programs write R/3 data to archive flat files and deletes corresponding data from R/3 database. The Archive file may then be delete completely from storage.
1 2
The Data Purge Process
Documents
R/3 DB
Print Spool
View Image
Document Imaging session
Storage
ArchiveLink Third-party tool
CD
R/3
Printer1
1. At the moment of print, SAP documents are sent to the print spool. If the print command to the defined printer is successful, document information is sent to and processed by the ArchiveLink.
2. The third-party document imaging tool communicates with SAP through the ArchiveLink to receive the image information. The third-party tool is responsible for the storage and retrieval of the image (although the retrieve may be executed through the SAP client.)
2
Imagefiles
ImagefilesDocuments
R/3 DB
The Document Imaging Process
WORM
ArchivingObjects
ArchiveFiles
Tivoli Storage
Manager
Archiving to an HSM Storage Solution
Sample Archiving Architecture
Documents
R/3 DB
Optional
Storage
Documents ArchivingObjects
ArchiveFiles
Arc
hiv
e L
ink
Archiving to an Document Imaging Storage Solution
OpticalJukebox
OrStorage
iXOSeConServer
Sample Archiving Architecture
R/3 DB
Scannerand/orFAX
Benefits of Data Archiving
Help Maintain Database SizeControl growth by archiving and/or purging non-critical data or aged data
Help Maintain System PerformanceBackup, restore and database administration times increase proportionally with database size
Reduce Custom ABAP requirementsSAP’s ADK (Archive Development Kit) contains all the ABAP programs needed to archive and retrieve data
Ability to store transactional data for later retrievalData needed for legal or business requirements may be retrieved via ADK retrieval programs
Stabilize and Maintain Database Growth
Reduced hardware costs – (Prime reason companies archive)
Reduced administration costs
Legal Requirements
External Audits
Tax requirements
Business Requirements
Improved response time in business transactions – (Prime reason companies archive)
Statistical Analysis
Technical Requirements
Reduced maintenance and back-up recovery
Reduced time for SAP Upgrades
Increased system stability and availability
Why is Archiving Important?
1. Scoping and Analysis
2. Preparation
3. Design
4. Implementation and Test
5. Training
6. Preparation for Go-Live
7. Go-Live
8. Post-Go-Live
Proven Accenture Methodology Involves an 8 Step Process…..
Accenture Methodology for SAP Archiving
Scoping and Analysis
Scoping and Analysis Preparation
PreparationGo - Live
Go - LiveDesign
Design
Project and Issues Management Project and Issues Management
ImplementationAnd Test
ImplementationAnd Test Preparation
for Go - Live
Preparation for Go - Live Post
Go - Live
Post Go - Live
TrainingTraining
Methodology for SAP Archiving and Reorganization
SAP Archiving is a proven solution to help maintain database performance and growth.
SAP has made many advances with Archiving with the advent of 4.6 and they are continuing to improve its capabilities. However, we still have strong experience with the older versions of SAP such as 3.1 i.
Document Imaging provides coverage for those objects where the basic SAP archiving retrieval solution may not be adequate.
Accenture is aggressively building our SAP Archiving knowledge, global resource pool, and implementation capabilities through the SAP Archiving Service Offering.
What is Accenture’s experience with SAP Archiving?
What is Data Archiving?
What is DART?
What is Database Reorganization?
DART targets and extracts period dependent financial documents and other supporting transaction and master data from SAP, that is necessary to prepare for an IRS audit.
DART extracts over 1,500 fields from more than 220 SAP tables and produces
a flat text file, can be viewed on-line in SAP, or imported into another system for
reporting purposes.
What is DART?
Tables
1
BSEGDaRTFlat File
Data ExtractALNA
TTXY View queryFlat
File
Flat
File
G/L DetailInformation
View query
View queryFlat
File
Flat
File
Flat
File
Flat
File
VendorMaster
DepreciationInformation
1
2 3
4
4
1. Extracts from SAP database
2. Produces a Flat Text file
3. View files can be created off the extract file
4. These files (extract and views) can be read on-line within SAP, or sent to another system for reporting
The DART Process
R/3 DB
The government requires companies to retain tax relevant transactional and master data for up to 10 years for audit support and reporting purposes
SAP designed DaRT to specifically fulfill this requirement to retain tax relevant transactional and master data
Collects all tax relevant information from SAP into easy-to-view, delimited flat files
Companies such as BP/Amoco, Exxon, Chevron and Microsoft rely on DaRT to fulfill their SAP tax requirements
Why is DART Important?
What is Data Archiving?
What is DART?
What is Database Reorganization?
A database reorganization is the process of solving certain storage problems that develop during the normal operation of the database.1 Such as:
Fragmentation
Index growth
Archiving
1. SAP R/3 Handbook, 2nd Edition, Jose Antoinio Hernanadez, 2000
What is a Database Reorganization?
Current StateDatabase is divided into
Tablespaces, Tables and Indexes.Tablespace
Table/IndexFragmented Space
Allocated Space
Allocated Space
SAP DB
What is a Database Reorganization?
SAP DBAfter Reorg
Goal: • Defragmentation
Top Benefit: • Improved Performance
What is a Database Reorganization?
SAP DBBefore Reorg
SAP DBBefore Reorg
SAP DBAfter Reorg
Goal: • Defragmentation• Shrink Tables/Indexes
Top Benefits: • Improved Performance• Reduced DB Size
What is a Database Reorganization?
Benefits of Reorganization
Tangible Reduced fragmentation Reduced table overhead Reduced tablespace overhead Reduced database size
Benefit Results Faster table scans and lookups Faster backup, recovery and DR from tape Faster SAP release upgrades - particularly for 4.6 upgrade Reduced hardware costs – (Prime reason companies archive) Reduced administration costs Improved response time in business transactions – (Prime reason companies
archive)
Why is Reorganization Important?
What is SAP Archiving and Database Reorganization?
What is the Value Proposition
Key Considerations & Benchmarks
Accenture Differentiation
Client Credentials
Determining Value
Define ROI and then prove it . . .
Costs of Unchecked
Growth
Costs of Unchecked
Growth - =( ) SavingsSavingsCost of Project
Cost of Project + On-going
Costs
On-goingCosts
How will the project costs be affected:
–What are the costs associated with running an environment without archiving or reorganization
–What impact will archiving and reorg have on these costs?
–What are the incremental costs associated with an archiving and reorg project?
–What is the delta savings?
Cost to Implement ArchivingCost of Growth
How to get started calculating ROI
–Find the Storage and you will find the ROI
Cost of Growth
Where’s the storage costs?
Costs of Unchecked
Growth
Costs of Unchecked
Growth
Production System
Production System
ProdDB
DBMirror
InternalDB Copy
ExternalDB Copy
Ext. DBMirror
ProductionFix
ProductionFix
DevDB
DevMirror
Test SystemTest SystemTestDB
TestMirror
BW SystemBW SystemBWDB
BWMirror
TapeBackup System
TapeBackup System
TrainingTrainingTraining
DB
TrainingMirror
Primary Copy of Database
Offsite Disaster
Recovery or Reporting
Offsite Disaster
Recovery or Reporting
Dev SystemDev SystemDevDB
DevMirror
Calculating Costs
Storage Costs
“Hard disk costs represent less than a quarter of storage costs” Giga Information Group
Costs of Unchecked
Growth
Costs of Unchecked
Growth
“Administration costs for 1 TB of storage are five to seven times higher than the storage costs”
Dataquest/Gartner
Personnel45%
Various –10%(Training, other costs)
Environment – 3%(Electricity, physical space)
Storage Management – 19%(Software and Hardware)
Hard Disk – 23%
Calculating Costs
Development Costs - costs are linked to number of archiving objects and tables to be reorganized
Scope and Analysis
Preparation
Design
Implementation and Test
Training
Deployment
Maintenance
Cost of Project
Cost of Project
Calculating Costs
Ongoing Costs – Maintenance costs associated with software and/or hardware needed for archiving and reorganization.
Examples: Software and Hardware for Imaging Solution
Software and Hardware for HSM Solution
Maintenance for above
Software Maintenance for Online Reorg Tool
On-goingCosts
On-goingCosts
Calculating Savings
CostSavings
CostSavingsGiven the development and maintenance savings associated with
implementing an archiving and reorganization solution, the following benefits will be provided:
Benefits – Overall
• Faster backup, recovery and DR from tape• Faster SAP release upgrades - particularly for 4.6 upgrade• Reduced hardware costs• Reduced administration costs• Shorter response time in business transactions
What is SAP Archiving and Database Reorganization?
What is the Value Proposition
Key Considerations & Benchmarks
Accenture Differentiation
Client Credentials
Based on our experience, the following items are the largest drivers of effort, risk, and time associated with an DRM project:
Number of SAP standard archiving objects
Number custom archiving objects.
Number tables to be reorganized.
Quiet times where no archiving jobs or reorganizations may take place.
Ability to manage scope for new archiving or reorg requests.
Regression testing approach (number of interfaces, number of other batch jobs, Stress test ).
Training approach (instructor lead vs. electronic training)
Drivers For SAP Archiving and Database Reorganization Projects
What is SAP Archiving?
What is the Value Proposition
Key Considerations & Benchmarks
Accenture Differentiation
Summary
What is the SAP Archiving Offering?
Proven Experience
Alignment with SAP
Proven Methodology
Delivery Excellence
Accenture Differentiation
“... Accenture has repeatedly demonstrated the ability to innovate and act upon applications and process-specific needs in order to help clients actually evolve within their industries.”
— Gartner Group
“We applaud their business integration approach to the marketplace—bringing Accenture’s multidimensional, global capability and capacity across outsourcing, consulting, and joint-venturing to bear flexibility on customer problems and needs.”
—The Yankee Group
“We have a number of great partners, but let’s confront a little reality. There is only one Accenture. Nobody, not even IBM Global Services, can do consulting like Accenture.”
—Microsoft CEO Steve Ballmer
“Who will dominate the third era of computing? The future might belong not to a company who makes boxes, chips, or software, but to a company that integrates these things into solutions to business problems. The future could belong to Accenture.”
—Forbes Magazine
Independent testimonials on Accenture's ability to create innovative solutions to conquer the challenges faced by its’ clients.
Industry Perspective
SAP Archiving is a proven solution to help maintain database performance and growth.
SAP has made many advances with Archiving with the advent of 4.6 and they are continuing to improve its capabilities. However, we still have strong experience with the older versions of SAP such as 3.1 i.
Document Imaging provides coverage for those objects where the basic SAP archiving retrieval solution may not be adequate.
Accenture is aggressively building our SAP Archiving knowledge, global resource pool, and implementation capabilities through the SAP Archive Service Offering.
What is Accenture’s experience with SAP Archiving?
Accenture has provided SAP Archiving services and solutions for a variety of clients that cover the spectrum of industries, geographies, and size.
Accenture SAP Archiving and DatabaseReorganization Clients
Archiving Drivers: Cost of disk space
System performance prevention
Key Archiving Challenges Obtaining user sign-off for developed objects was difficult as user departments were uncertain
which constituents actually needed the data.
Complex object development.
Accenture Role: Design, implement, and administrate SAP Data Archiving.
Project staff was 100% Accenture (other than business owner involvement for sign-off).
Accenture Contact Details: Engagement Partner: Michael L. Orlowicz
Project Contact: Matt J. Wilsman
SAP Archiving Contact: Tim S. Sheehy
Mrs. Smith's Bakeries produces and markets frozen desserts, as well as breads, rolls, buns and snack cakes for sale to retail and foodservice customers.
SAP Version: 4.6c
Status: Ongoing (Outsourcing Engagement)
Metrics (in archive scope):
Users: ~ 1,000
Sites: 10
Countries: 1 (USA)
Primary Geographic Location: Atlanta, GA
Modules: FI, CO, MM, PP, SD
Standard Archiving Objects: 8 in Production
Database: Oracle 8.1.7.3
Allocated DB Size: 730 GB
DB Size Before: ~ 500 GB
DB Growth: Originally 7-8 GB/mo. Now 3 GB/mo.
Last DB Reorg: Spring 2001
Reorg Downtime: 5 hours
Online Reorg Tool: TS-Reorg
DaRT Version: Release 1.07, Patch Level 04
Initial Archiving Effort: 6 months
Project Summary: As part of a Design/Build/Run model, Accenture implemented SAP in the areas of FI, MM, PP
and SD. This initial work was done using consulting resources and then followed by a Run team incorporating outsourcing practice personnel. The need for Archiving was identified and a portion of the outsourcing team's capacity was dedicated to this initiative.
Training was accomplished via live demonstration at client location.
Engagement Credentials:Mrs. Smith’s Bakeries
Engagement Credentials:BP Downstream
Archiving Drivers: Cost of tape backup of a 3+ TB database
SAP R/3 4.6c Upgrade
Key Archiving Challenges Sharing of Development and Test environment lead to reduced test time
Aggressive roll-out plan was not realized due to several month-end and quarter-end freezes.
Clients version of SAP, 3.1h, was un-supported by SAP. Therefore, little support was available.
Accenture Role: Manage, implement, and administer SAP Data Archiving and LiveReorg online reorg tool.
Manage, design, implement, and administer Project staff was 40% Accenture, 40% PWC, 10% BP (also business owner involvement for sign-off).
Accenture Contact Details: Engagement Partner: Mark R. Willford
Project Manager: Rebecca L. Crowell
BP has undergone a transformation referred to as “Program One BP” which includes the migration of North America BP users onto the existing SAP R/3 3.1h footprint currently installed within the former Amoco business. A 4.6c upgrade project is underway and archiving is needed to reduce the footprint to the smallest manageable size as well as reduce operational costs of a large database.
SAP Version: 3.1h
Status: Live and actively monitored as of 10/19/02
Metrics (in archive scope):
Users: ~ 1,000
Sites: 10
Countries: 1 (USA)
Primary Geographic Location: Chicago, IL
Modules: FI, CO, MM, AM, SD
Standard Archiving Objects: 8 standard, 1 custom
Database: Oracle 8.1.7.1
Allocated DB Size: 4.0 TB
DB Size Before: 3.2 GB
DB Growth: Before 122 GB/month, after TBD
Last DB Reorg: Unknown
Reorg Downtime: Unknown
Online Reorg Tool: LiveReorg (by Quest Software)
Initial Archiving Effort: 6 months
Project Summary: BP began a cost reduction effort with the goal to reduce the cost of operations by reducing or
halting the growth of the 3 TB+ Downstream SAP database.
The SAP Data Archiving and Reorg project was started to address business drivers of cost reduction and to prepare a smaller foot print prior to a SAP 4.6c upgrade.
The data was be extracted out of SAP and passed to an HSM system for fast retrieval or purged all together depending on business/legal requirements. Online reorganization followed archiving to return as much disk space as possible back to the OS.
Archiving Drivers: Cost of disk storage Improve system performance Lesson DBA maintenance windows
Key Archiving ChallengesObtaining end user buy-in on notion that not all data needed to remain online.
Roles Accenture - Design, Implement, and Manage. Client – Regression testing on SD and FI modules, UAT, and training. Project staff: 4 Accenture, 1 IXOS, 1 Accenture sub-contractor.
Accenture Contact Details: Partner Contact: John H. Soles Project Contact/SAP Archiving Contact: Stephen M. Rowat
Canada Post Corporation (CPC) and its affiliate are entrusted with nearly 10 billion messages and parcels annually. These items are processed through 25 major plants and many other facilities for delivery to over 13 million addresses in Canada. Together with its affiliated companies, Canada Post ranks 39th among Canadian businesses in terms of consolidated revenue and is the sixth largest employer in Canada. Canada Post has commercial, operational, and financial links with over 200 postal administrations around the world. In 2000/2001, its revenues were $5.9B (Canadian).
SAP Version: 4.6dStatus: Successfully Completed October 2002Metrics (in archive scope): Countries: 1 (Canada)Primary Geographic Location: Ottawa, CanadaModules: SD, FI, CO/PA, and some MMStandard Archiving Objects: 9Custom Archiving Objects: 3Database: Oracle 8.1.7DB Size: 1.5 TBUpside Down Tables: 10Technical Architecture includes ArchiveLink and IXOS Online Reorg Solution: Quest LiveReorg(Reorg of one sales order table prior to archiving increased performance 100 fold by ordering data by most likely access path.)HSM may be used if HP jukebox runs out of spaceProject Length: 10 months
Project Summary: Accenture brings relevant knowledge of the current SAP system situation, as well as deep SAP
archiving skills through the Global Business Solutions (GBS) group. The client recognizes Accenture as a major service provider with a solid track record and approached both SAP and Accenture to do this work. SAP was unable to respond with suitable resources or high level approach.
Phase I Quick Hit: Began with the IDOC archiving object to significantly reduce the size of the IDOC tables (500 GB reduction). Archiving CO_ITEM yielded another quick 25 GB. Benefits include improved performance to the batch processes currently affected by the size of the IDOC tables. Phase I SD Archiving: Implemented approximately 8 SD Archiving Objects. Phase II FI/CO Archiving: Implemented approximately 8-10 FI/CO Archiving Objects.
HTML training manual placed on client’s Intranet
Engagement Credentials:Canada Post
Archiving Driver
Cost of disk space. (The client had bought a 9 TB EMC frame and expected to fill it within a 1 ½ yr.
Key Archiving Challenges
Managing the new items to be archived was tedious as it required intensive analyses of data, tables, and relationships with other objects.
Roles Accenture - Planning
Client - Detailed Design, Implementation, Management, and Support.
Project staff was 67% client and 33% outside contractor.
Accenture Contact Details Partner/Project Contact: Mark D. Ernst
SAP Archiving Contact: Keith L. Hogie
Tenneco Automotive is the world's largest producer and marketer of ride control and exhaust management products and systems, producing three of every ten mufflers and 50 percent of the shock absorbers sold each year in the worldwide aftermarket. In the original equipment market, they work with more than 25 manufacturers on a global basis. The company also serves more than 500 aftermarket customers, including wholesalers and retailers. The Lake Forest, IL, company operates 81 facilities in 22 countries on six continents.
SAP Version: 4.5bProject Completed: November 1999Metrics (in archive scope): Users: ~ 300
Sites: 14
Countries: 2 (USA and Canada)
Primary Geographic Location: Lake Forest, IL
Modules: FI, CO
Database: Oracle 11.0 (64-bit)
Allocated DB Size: 600 GB
DB Size Before: 450 GB
Reorg Frequency: Once per mo. – once per quarter
Reorg note: COEP was upside down
Reorganized Tables: COEP, ACCT, ACCTR
Scheduled Weekend jReorg Downtime: 8 hours
Imaging Solution: FileNet
Project Length: 4 months
Project Summary
Tenneco Automotive recognized the growing need for--and potential competitive advantages of--a common, worldwide information system. For decades, Tenneco Automotive had been operating with disparate legacy systems that were home grown or acquired through acquisition. Accenture was engaegd to roll out SAP to replace these systems. SAP Archiving planning was included as one of many facets of this large project. The client used this plan to archive their system.
Engagement Credentials:Tenneco Automotive
Regression Testing Tenneco had 4 environments (Development, System, Test, & Production) with one client each.
Testing was performed in the non-Production environments.
Stress testing was a function of monitoring the impacts during day-to-day use of the non-Production environments.
Archiving DriversRapid database growth of 75 GB/month and proximity to Euro Conversion, where a reduction of the
DB size was a must in order to perform the conversion in only 3 days.
Key Archiving Challenges Proximity of Euro Conversion with need to dramatically reduce DB size. Complex Altadis user layout of responsibilities (many business processes and departments
sharing the same SAP modules). This made decisions difficult as it was complex to unify archiving criteria.
Accenture Role: Complete leadership of the project: strategic definition, design, implement and manage. The overal project was staffed by Accenture people. The client provided a coordination manager
and a user representatives. IXOS provided a consultant for specific issues regarding their tool.
Accenture Contact Details: Engagement Partner: Puri Paniagua Project Contact: Miquel Terrasa SAP Archiving Contact: Rocío Chacón
Altadis is the sole manufacturer, importer and distributor of tobacco products in Spain—distributing to more than 16,000 tobacconists throughout Spain. The company manages the monopoly of wholesale distribution of fiscal and postage stamps, as well. They also have interests in the food sector.
SAP Version: 3.1i
Status: Successfully Completed Nov. 11, 2002
Metrics (in archive scope):
Users: 600 +
Sites: ~ 50
Countries: 1 (Spain)
Primary Geographic Location: Madrid, Spain
Modules: SD, MM, WM, FI, CO, PP, & PM
Standard Archiving Objects: 17
Custom Objects: 1, plus several custom Z tables
Database: Oracle
DB Size Before: 1.4 TB
DB Size After: 0.7 TB
There were periodical reorganizations every weekend during the implementation phase.
WRITEs are performed during normal business hours, while DELETEs are executed at night.
Reorg Downtime: Weekend
The technical architecture includes iXOS.
Project Length: 11 months
Project Summary: Phase 1: Defining a Global Archiving Strategy for Altadis Spain Defining archiving
requirements, analyzing database size & growth, performing analysis of external storage systems, defining Altadis’ global archiving & historical information strategy and action plan (Feb. – Mar. 2001)
Phase 2: Implementation Implementing the short term actions defined in the previous phase. The project included: design, implementation, and execution of archiving objects (SAP standard & custom, ADK), development and archiving of reports (spool lists), integration with IXOS/ArchiveLink and coordination with a Euro conversion project in to reduce database size with planned conversion dates (Mar. –Dec. 2001)
An instructor lead Accenture team transferred functional and technical know-how to Altadis
Engagement Credentials:Altadis (Spain)
Archiving Drivers: Save time and money spent on system back-ups
Reduce database size
Improve system performance
Key Archiving Challenge
Future knowledge transfer. (Transfer of knowledge between parties when the responsibilities of the Application Management evolved.)
Accenture Role: Design, Implementation, and Project Management.
Project staff: 80% Accenture and 20% Client
Accenture Contact Details:
Contact SAP Archiving and Reorganization Offering lead Rebecca L. Crowell for more information.
This client is a mobile systems supplier. One business segment is responsible for all systems that deliver wire and mobile communications processes, infrastructure and software. Their current IT environment has evolved gradually as business has grown. The result is a complex picture of multiple applications and IT platforms that are expensive to maintain and incapable of supporting the new operational model. Accenture has been asked to help in restructuring this IT landscape. SAP Archiving was one facet of this project.
SAP Version: 4.6c
Status: Successfully completed August 20, 2002
Metrics (in archive scope):
Modules: MM, SD, FI, CO, Workitems, IDOC
Standard Archiving Objects: 11
Database: Oracle
DB Size Before: 200 GB
DB Size After: 10% decrease in initial archive runs
Technical Architecture includes IXOS
Standard SAP Reorg Tools were evaluated for database reorganization, but are not currently used.
Length of Project: 4 months
Broad Project Summary:
The aim is to greatly improve customer services by introducing a simplified, direct business model, common supply chain processes and by eliminating waste. The program requires the introduction of a new application system, to support the new business model and processes and also to facilitate the introductions of internet based capabilities.
SAP Archiving Project Summary: • The archiving project was implemented to improve overall system performance as the database
continues to grow, decrease the amount of time and money required for online backups, reduce requirements for additional disk space, and decrease the time required for client copies.
Instructor-led training.
Engagement Credentials:Example High-Tech Client
Proven Experience
Alignment with SAP
Proven Methodology
Delivery Excellence
Accenture Differentiation
1972SAP begins marketing software
1980s
Accenture works with European companies to implement SAP software
1985SAP engages Accenture to identify enhancements to its financial software required for the US
1987SAP and Accenture establish joint venture company, SAP Consulting
1988
On-line SAP training developed by Accenture
1993
SAP markets alliance formed SAP “Most Valuable Partner”
status achieved1999
2002
Our 30 year relationship with SAP has realized a significant number of industry firsts and business application achievements.
A History of Working Together
Accenture is the only firm to have received the SAP Award of Excellence from 1995 – 2000.
1992Accenture became a charter member of SAP’s new R/3 Consulting Partner Alliance Program
Accenture and SAP announce strategic development agreement for the IS-Telecom product
Accenture and SAP develop software for the European Public Utility industry
1989
Accenture signs strategic alliance with SAP Portals
2001
Accenture & SAP
Proven Experience
Alignment with SAP
Proven Methodology
Delivery Excellence
Accenture Differentiation
1. Scoping and Analysis
2. Preparation
3. Design
4. Implementation and Test
5. Training
6. Preparation for Go-Live
7. Go-Live
8. Post-Go-Live
Proven Accenture Methodology Involves an 8 Step Process…..
Accenture Methodology for SAP Archiving
Scoping and Analysis
Scoping and Analysis Preparation
PreparationGo - Live
Go - LiveDesign
Design
Project and Issues Management Project and Issues Management
ImplementationAnd Test
ImplementationAnd Test Preparation
for Go - Live
Preparation for Go - Live Post
Go - Live
Post Go - Live
TrainingTraining
Methodology for SAP Archiving and Reorganization
Proven Experience
Alignment with SAP
Proven Methodology
Delivery Excellence
Accenture Differentiation
Delivery Excellence
Accenture has developed a portfolio of tools, processes, assets, and
accelerators to help reduce the cost and risk associated with planning,
managing, and delivering an SAP Archiving project.
Value Proposition
SAP Archiving Estimating Model
Solution and Vendor Analysis
KX Assets and Templates
SAP Archiving Estimating Model
The SAP Archive Estimating Model was developed based on the Archive Methodology and ties directly to its phases and task packages
The model generates an estimate in workday, achieved by following seven high level steps and entering project specific details and estimating factors
High level costing can be calculated using average daily rates for the various resource mix percentages.
1. Confirm scope and assumptions
2. Develop project complexity factors
(management,organization, and system complexity)
3. Develop Estimating Factors
4. Refine Estimate
5. Review Estimate for reasonableness
6. Determine appropriate resource mix and staffing plan
7. Develop Timeline
Steps to complete an estimate:
Solution and Vendor Analysis
SAP File System
HSM Storage
Document Imaging Storage
There are three options for providing storage for SAP Archiving:
Which option is right for your project?
What should be considered?
Are you only trying to meet archiving requirements?
Is cost the primary concern?
Answers to these questions and others will impact your decisions. The Solution and Vendor Analysis provides insight to how each solution meets your requirements.
What is SAP Archiving?
Key Considerations & Benchmarks
Accenture Differentiation
Summary
Summary
For more information, contact the following: Sze-wing Lee, Partner [email protected] Ken Soren, SAP Global Capability Director
[email protected] Rebecca Crowell, Associate Partner – Offering Lead
[email protected] Joseph Kuo, Manager – Offering Development Lead
[email protected] Steve King, Manager – Offering Content Lead
Please visit the SAP Archiving Offering Homepage on the web for more detailed information, reusable assets, and sample deliverables:
SAP Archiving Homepage
Assist in selling opportunities Jump Start SAP Archiving and Reorganization project planning activities Provide proven delivery accelerators to reduce cost and risk Provide consolidated contacts, best practices, and reusable knowledge capital
The SAP Archiving Service Offering will:
‘Tis Better to be Proactive..
..than
be reactive
The Last Word