A Successful SAP MigrationMichael A. MooreBrach’s Confections, Inc.

Session Code: 904

A Successful SAP Migration

Michael MooreManager of Systems Administration

Brach’s Confections, Inc.e-mail: michael.moore@brachs.com

Introduction

One of America's leading manufacturers of confections and fruit snacks Wholly-owned subsidiary of K. J. Jacobs A.G. based in Zurich, Switzerland

Principal offices in Woodridge, Illinois and Chattanooga, Tennessee

Implemented SAP in 1995

SAP Modules: FI, CO, SD, MM, PP, PA, HR

Add-on’s: BSI Tax Factory, Gentran EDIwww.brachs.com

About Brach’s

Joined Brach’s in March 2000

Areas of responsibility include: SAP hardware SAN Storage infrastructure SAP BasisSAP SecuritySAP Change ControlInformix databaseData center backup & recovery Corporate disaster recoverySAP Data Archive infrastructure

About the speaker

Reduce SAP infrastructure expense by 50% without negatively impacting end users and maintaining a fixed cost structure for 36+ months.

The challenge

Purchase exiting hardware

Replace with lower cost but similar hardware

Implement a heterogeneous SAP system

SAP Migration

The options

Existing landscape

SAP R/3 release 4.6c (64-bit kernel)

420 Gig Informix 7.31 database

HP-UX 11.0

SAN was on separate lease

Existing hardware consisted of:

One HP V2250 12-way for SAP database and CIFive HP K580 4-way’s for application serversOne HP K580 for SAMBA shares

We reviewed lease buyout, current system utilization and on-going maintenance costs. It was determined that this hardware model could not sustain the company for an additional 36 months.

Purchase existing hardware

In order to meet the financial goals without requiring a migration – a heterogeneous environment was reviewed and tested:

The model:- upgrade UNIX database/SAP CI hardware- multiple MS Windows application servers- additional application servers for DEV, QAT

Successful testing was completed

Heterogeneous landscape

Reviewed sizing estimates and costs from Dell, Compaq, Sun and IBM

Costs were obtained for turnkey SAP migration, staff training, and additional support during transition

Substantial savings could be gained by changing hardware platforms even when migration costs were included.

DECISION: Investigate further ($$$)

SAP Migration

Can we do it over a weekend?

Identify the Requirements/Impacts/Risks:Non-SAP software available for target platform?Will staff accept the change? Training?Two Production outages requiredUsers available for testing?Questionable performance on new h/wHow to ensure migration moves ALL data

Migration Concerns

Test the export process for timing ($$).The reality is the export should take longer than the import – or something is wrong!

Work with new vendor to provide test hardware

If possible, test with similar hardware as proposed and identical storage.

Prove the concept

The SAP Standard Application benchmark uses concurrent usage estimates to propose hardware models. [http://service.sap.com/sizing]

IBM has the Insight tool which runs against the current implementation to gather data points every 5 minutes. Run this tool at peak times to ensure proper sizing.

Sizing estimates

New system landscape

SAP R/3 4.6c (64-bit kernel)

Informix 7.31

IBM AIX 4.3.3

Existing SAN storage

SAP Certified Migration partner*familiar with source and target platforms

Obtain SAP Migration toolkit and target platform installation media and patches (service.sap.com/swcat)

Schedule the OS/DB Migration Service* Submit SAP Migration Plan*

Create new SAP R/3 profiles for target platform

* - required for Production migration, requires Migrator’s Certificate number

Prepare for the migration - 1

Available disk space for export (15% of data in database)

Request Migration Keys (one for each system – DEV, QAT, PRD)

Prepare for printer definitions on new system (scripts)

Prepare for OS/DB backups on target system

SAP upgrades must be completed 6 weeks before migration

Once you receive hardware – request SAP license!

Prepare for the migration - 2

This is an important document that details the migration project and responsibilities of the customer, migration partner and SAP.

SAP support is obligated to fix the migration tools. The certified migration partner is responsible for delivering the knowledge required to use the migration tools.

SAP Planning Guide

Sign R/3 Migration Services contract

Propose dates for GoingLive Migration Check

Prepare overall project plan with dates

SAP approves migration plan (5 days)

Setup remote access to target platform

Identify backup/restore mechanism for target platform

Must have Certified Migrator contracted to submit plan to SAP – certified by SAP release that you are migrating.

Project Plan

SAP Remote service required by SAP for all migration projects.

Identifies source and target environments, schedule and certified consultant (they check against their records and certifications are release dependent)

Customer proposes date for the Pre-Migration check

At a minimum two Production migrations are required – one test two weeks prior to actual Go-Live migration

Each session will receive a Green, Yellow or Red light

SAP Migration Project Audit

Migration Toolkit

Install Migration Toolkit for exportApply patches

/usr/sap/put (migration tools and doc)

/PRDMIGRATE (LABEL.ASC)../DB (DDLINF.TPL)../DB/INF (*.EXT files)../DATA (*.STR, *.TOC, *.nnn)

Ready to begin

R3SETUP- master programCEDBMIG.R3S – R3SETUP migration control fileR3load- utility used to unload/load data (creates TOC, LOG and data dump files)R3ldctl- utility used to create R3load control files (DDLINF.TPL, *STR, SAPVIEW.STR)DDLINF.TPL – DDL for target database SAP<TABART>.STR – table/index definitions from ABAP DictionarySAP<TABART>.cmd – command file ( DDL to use)SAP<TABART>.ext – initial extent sizes (can change these)SAP<TABART>.TOC – contents of the data dump file(s) [includes row count]SPLITSTR.PL – command file to split STR files to increase performancebuildinf.pfl – size of the dbspaces to create during installation

Programs and Command Files

DBEXPORT.log.## - created for every run of “R3SETUP –f DBEXPORT.R3S”

DBEXPORT.R3S.## - updated control file used for next run

SAP<TABART>.log – specific log for each set of tables

Database and Operating System Error logs

Database performance – monitor and tune

Monitor the process

Ensure R/3 will not restartAll updates are completedAll users are logged offEnsure no jobs are running or releasedRelease all remaining locksRelease all unconfirmed repairsEnsure op mode switch will not occurSet client 000 users Stop R/3 and leave database running

SAP note 143059

Pre-Export Checks

Create R3LOAD control files (DDLINF.TPL, SAP<TABART>.STR, SAP<TABART>.EXT)

Create templates for DB Sizes to be created on target system (DBSIZE.TPL)

Create export command (*.CMD) files for each data class

Begin database unload (process each file by order of file creation)

Overview of the export process

Start export “R3SETUP –f DBEXPORT.R3S”

Stop at step SPLITSTRFILES_IND_IND

Split STR files manually

Restart export “R3SETUP –f DBEXPORT.R3S”

Data export will begin…

Migration process - Export

Key to R3load migration performance!!!

Determines order of export process- NT: ordered by name- UNIX: ordered by creation time stamp

Determines where tables are placed on target system

Tables not in the ABAP Dictionary will not be migrated SAP Note 46272

SAP<TABART>.STR files

Tool to use: SPLITSTR.PL

What? Control files for export/import process

Why split? To increase throughput

Example syntax:splitstr.pl limit=500M –p <target_dir> -d <source_dir>

Requirements: Perl5 (http://www.perl.com)

SAP Note: 200444

Split STR files

Install database and R/3 software

Set migration key

Create database (DBSIZE.TPL)

Generate R3LOAD import command files

Start the data import …

Update statistics

Change database log mode to logging

Overview of the import process

Already complete the installation up to the data import step

Move exported data and command files to target system- ftp binary mode- no need for additional compression

Start the import forcing a stop after data loaded but before update statistics

Manually perform a parallel update statistics

Restart R3SETUP –f CEDBMIG.R3S and run to completion

Migration Process - Import

Verify other filesystems are available (/usr/sap/trans)Run transaction SICKRun Transaction SPAD Initialize CTS with the Database Copy optionReset DDIC, SAP* and SAPR3 passwordsVerify kernel level, Support Package levelsRegenerate all programs and screensInstall SAP licenseUpdate SAP printer configuration (if hostname changed)TEMSE consistency checkReschedule jobsReset Operation ModesMaintain RFC destinationsBegin verification testingSTART THE FIRST BACKUP!!

Post-Import Steps

Complete a functional test with super users similar to a post upgrade test

Check all bolt-on’s:EDIBarcode software interfaces (RFC)BSI Tax FactoryEasy ArchiveDocument Management

Verification Testing

Black-out period for changes (1-2 weeks) (exception: may need to relocate tables to different dbspaces)

Change control – new baseline

Schedule Post Migration GoingLive Check (4-6 weeks later)

Migration over

Summer 2001 – review hardware vendors and arrange for test equipmentOctober 22-26th – vendor onsite to test exportNov – Feb: data reduction effortsMarch 14th order placed for IBM equipmentJune 6-8th – first test DEV migrationJune 28-30th – first Production migrationJuly 5th-7th – final DEV migrationJuly 12-14th – Production Go-Live

Our Timeline

Improving performance - 1

Migration Tool parametersinitial number of parallel import/export processes equal

to 2.5 times CPU count

disk layout

O/S parameters: on HP-UX increase dbc_max_pct

Update statistics before export

For the large tables remove ORDER_BY_PKEY from DDLINF.TPL.

CAUTION: NOT OFFICIALLY SUPPORTED so TEST, TEST, TEST!!!

We did this for GLPCA, ACCTIT, COEP and BSIS and reduced the export time from 26.5 hours to 12.25 hours!

SAP Notes: 216777 and 118059

How to do this:copy the DDLINF.TPL file to DDLINF2.TPL filemodify DDLINF2.TPL and remove the ORDER_BY_PKEY statementmodify the SAPxxx.cmd files to use the DDLINF2.TPL file in CEDBEXP.R3S (???) in the section DBEXPR3LOADEXEC_IND_INF set the value WRITE_FORCE=NO, otherwise the modified command files will be overwritten

Improving performance - 2

Understand R3SETUP and control fileCEDBMIG.R3S is ordered by [labels]

Stop processing in R3S command file at a desired point :

[EXE_BOGUS]CLASS=CExitStepEXIT=YES

STATUS=Error – rerun a stepSTATUS=OK – skip a step (i.e. Update Stats)

SAP Note: 118059

Saving time when testing

ExportR3ldctl had to be recompiled – number of TABART’s to account for.

NOTE: R3ldctl is also located in /sapmnt/<SID>/exe which is in the PATH. If this file is changed, must replace in both places!

DBSIZE.TPL will not be created correctly if Informix Fragmented Tables are used. Must be modified manually for size information.

ImportCheck and recheck permissions after completing the ftp (import directory = 755)

Number of raw devices allocated – R3SETUP changed to support >100 chunks

R3load could not account for more than 64 data classes

First import will fail.Database space size will be insufficient. Import will be slow. Modify the DBSIZE.TPL file to ensure dbspaces created on 2 Gig boundaries (chunks) and modify ONCONFIG for improved load performance, increase TEMP space!!!

Problems encountered

Avoid network issues – for all production migrations work from the console

Target platform time synchronization

Duplicate keys when loading

Will need at least 4-6 weeks to debug Migration Toolkit

After export/import tools are fixed – do the migration at least three times to tune the process

Provide super-users a stable system to test with (including print)

Good thing: import is restartable!!

Other

The less data there is to migrate the shorter the outage.

Look in http://service.sap.com/data-archiving for the Data Prevention Checklist for opportunities to substantially eliminate data from typically large tables (ACCTIT, GLPCA, …)

Data reduction/prevention

SAPservice.sap.com/sizing

Dell: http://www.dell.com/us/en/biz/topics/power_ps4q99-sap.htm http://www.dell.com/us/en/biz/topics/products_sap_center_pedge_software_sap_center.htm

IBM:www.ibm.com/erp/sap/insight

HP/Compaq:http://h40045.www4.hp.com/

Sun:http://www.sun.com/solutions/global/SAP/

Vendor sizing web sites

SAP OS/DB Migration Service Remote Project Audit

Heterogeneous OS and DB Migration of R/3 Systems – Planning Guide

SAP Installation Guide for target platform

SAP Notes (BC-INS-MIGR3)82478 - overall note on R/3 migration543715 – non-R/3 and incremental migrations200444 – splitting STR files16083 – standard jobs16875 – TemSe cleanup88842 – NOCHECK.TXT118059 – create separate unloads for large tables/orderingSeveral additional notes for EBCDIC conversion

http://service.sap.com/osdbmigration

SAP Documentation

In summary, we met our goals of reducing costs 50% while actually increasing performance up to three-fold.

Reasons for success:selected an experienced partnerhad executive buy-inTEST TEST TEST!!postponed go-live date three weeks

Closing and Questions

Thank you for attending!Please remember to complete and return your evaluation form following this session.

Session Code: 904