sap innovation summer camp come with a curiosity –...

SAP Innovation Summer Camp

Come with a Curiosity – Leave with a Plan

July 12 - 13, 2012 | SAP Americas HQ

www.sap.com/sapsummercamp

© 2012 SAP AG. All rights reserved. 2

Disclaimer

This presentation outlines our general product direction and should not be relied on

in making a purchase decision. This presentation is not subject to your license

agreement or any other agreement with SAP. SAP has no obligation to pursue any

course of business outlined in this presentation or to develop or release any

functionality mentioned in this presentation. This presentation and SAP's strategy

and possible future developments are subject to change and may be changed by

SAP at any time for any reason without notice. This document is provided without a

warranty of any kind, either express or implied, including but not limited to, the

implied warranties of merchantability, fitness for a particular purpose, or non-

infringement. SAP assumes no responsibility for errors or omissions in this

document, except if such damages were caused by SAP intentionally or grossly

negligent.

Infrastructure Track SAP HANA and Cloud Enabled Computing Center


Agenda

Migration to HANA Part 3 - Roadmap Through a Successful BW Database Migration

to SAP HANA

Influencing Factors on the Migration Path

Bundling of Changes

Migration Phases and Testing Cycles

Supporting Tools

Influencing Factors on the

Migration Path


Influencing Factors on the Migration Path Key Requirements

Requirements for the Migration to SAP HANA

Supported Source Database Platforms

Add-On Restrictions

Dual-Stack Split (if dual-stack source system)

Requirements that can be Included in the Scope of the Migration*

BW on either SAP NetWeaver 7.3 or SAP Enhancement Package 1 for

NetWeaver 7.3 (also known as 7.31) Transition to the new BW authorization concept (Role Based Analysis)

Unicode Converted System


Migration Path Influencing Factors SEM-BW Add-On Implications on BW 7.3/7.3x ABAP Upgrades

BW 7.0/SEM 6.0

Upgrade to:

NetWeaver 7.31

SEM 7.36

Possible

Consider Notes: 1539356 ( 7.30), 1681434 (7.30 7.31), 1681435* (7.03 7.31),

1531022 (SEM 604 ), and 1326576 (7.0x 7.xx)

Choose your NetWeaver BW Start Release

*Note: SAP Note 1681435is being updated to clarify what is meant by this upgrade path, as the

software component versions for the ABAP stack are the same in both 7.03 and 7.31.

BW 7.01/SEM 6.04

Upgrade to:

NetWeaver 7.30

SEM 6.34

Possible

BW 7.0x/SEM 6.0x

Upgrade to:

NetWeaver 7.31

SEM 7.36

Possible

BW 7.0/SEM 6.0

Upgrade to:

NetWeaver 7.30

SEM 6.34

Possible via NW

7.01/SEM 6.04


Migration Path Influencing Factors SEM-BW 6.04 Add-On Innovation Options

SEM-BW Technology Hub Business Suite

Back-End

SAP Business

Warehouse

AS ABAP 7.01

SEM-BW 6.04

SAP Business

Warehouse

AS ABAP 7.02

SEM-BW 6.05

SAP Business

Warehouse

AS ABAP 7.31

SEM BW 7.36

SAP Business

Warehouse

AS ABAP 7.3

SEM-BW 6.34

a.

b.

Application-driven innovation b.

a.

SAP

Business Suite 7 /

Business Suite 7i2010 /

Business Suite 7i2011

SAP NW 7.0x

Technology-driven innovation

SEM-BW 6.05 Skipped for NW 7.3

no Upgrade to 7.3

possible! !

Consolidation

with

ERP EHP6


Migration Path Influencing Factors Heterogeneous System Copy – Example Decision Trees 1/3

NW 7.0x

Start

Dual-

Stack

SEM-BW

60x

NW 7.3x

Supported

OS/DB

Split Stack

Upgrade to NW 7.03/7.31

SPS04 or Higher with SEM-

BW 736

Upgrade to NW 7.30 SPS07

or Higher*

OS and/or DB

Upgrade or Migration

Yes

No

Yes

Yes

No

NW 7.31

Start

SAP NetWeaver 7.0x Source System

NW 7.0x

Start

NW 7.0x

Start

Evaluate Loopback to

Continue to

Or optionally to Loopback to

No

NW 7.30

Start

Continue to

*Note: The current BW authorization concept needs to be evaluated to determine the appropriate target version.


Delete Java Stack!


NW 7.30

Start

Dual-

Stack

Unicode SPS =>

07

Heterogeneous Migration

to HANA

Heterogeneous Migration to

HANA with Unicode

Conversion

Implement SPS 07 or Higher

Yes

No

Yes

Yes

No

SAP NetWeaver 7.30 Source System

NW 7.30

Start

NW 7.30

Start


Loopback to

No

Implement

EhP1

(optional)

No

Upgrade to NW 7.31 SPS04

or Higher

Yes NW 7.31

Start

Continue to


Delete Java Stack!


NW 7.31

Start

Dual-

Stack

Unicode SPS =>

04

Heterogeneous Migration

to HANA

Heterogeneous Migration to

HANA with Unicode

Conversion

Implement SPS 04 or Higher

Yes

No

Yes

Yes

No

SAP NetWeaver 7.31 Source System

NW 7.31

Start


No

NW 7.31

Start

Loopback to


Step 6: Database migration and Unicode conversion

Step 4: Upgrade to 7.31 and SEM 7.36

Step 3: Dual-stack split to separate BW ABAP and BW Java stacks

Step 2: Oracle upgrade from version 10 to 11 (BW only released for Oracle 11)

Step 1: OS upgrade from HP-UX 11.23 to HP-UX 11.31

Migration Methods Example Migration Scope

Starting point: Non-Unicode BW 7.00 with SEM 6.00

on HP-UX 11.23 and Oracle 10.2

Target State: SAP NetWeaver BW 7.31 Powered By SAP HANA

Bundling of Changes Managing Multiple Systems and/or Changes


Bundling of Changes Factors for Bundling Change

Number of Systems to be Migrated One System vs. the Solution Landscape

System Dependencies

Target State and Scope Similarities

Business Criticality of Each System

Change Dependencies Software Levels – OS, DB, Application…

Stack Split – Dual Stack Systems

Unicode Conversion

Similar Technical Activities System Export/Import – Unicode Conversion, Migration

Application Changes – Upgrades, Support Package Stacks, Enhancement Packages…

Timing and Resource Availability

Access to Innovation – Business Requirements for Change

Resource Availability – Number of Resources, Resource Contracts, Subsequent Project

Requirements…

HANA Migration

Stack Split


Bundling of Changes Commonly Bundled Changes

Advantages

Faster access to innovation

Reduced landscape constellations for

testing

Reduction in the complexity and level of

effort for managing parallel changes (e.g.

production support, minor enhancements…)

Increased system availability as a result of

fewer business downtime events

Disadvantages

Perception of increased complexity and risk

Extensive downtime, if not properly

managed

Requires a concerted test management

strategy to validate the full project scope

Consolidated headcount effort required to

achieve the targeted scope


Bundling of Change Example - Migration Project Bundles

Bundle 1: Hardware Refresh and Sybase ASE Migration

Systems: Enterprise Portal, Solution Manager, & Customer Relationship

Management

Driver: Cost of Operations

Go-Live: November 2012

Bundle 2: NW 7.31 Upgrade and HANA Migration

Systems: NA and LA Business Warehouse 7.0

Driver: Access to Innovation

Go-Live: July 2012

Bundle 3: Enhancement Package Implementation, Hardware Refresh and

Sybase ASE Migration

Systems: NA Enterprise Resource Planning and Supply Chain Management

Driver: Access to Innovation / Cost of Operations

Go-Live: April 2013

Migration Phases and

Testing Cycles


Migration Phases and Testing Cycles Example Scenario using the Cloned Queue Migration Approach

BW HANA MigrationBW Hana Migration - Migration Method via parallel set up and operations

Preparation and Project setup

House Keeping/Data Deletion

Project Set Up

Blueprint

Blueprint (detailed migration execution and test plan)

Infrastructure set up

Realization

Performance Baseline / KPI Definition

Migration Cycle 1 - PRD -> Sandbox A

Performance and Volume Testing/Optimization in Sandbox A

Operational Readiness

Migration Cycle 2 - QA -> Sandbox B

Performance and Volume Testing/Optimization in Sandbox B

Migration Cycle 3 - Migration of DEV environment

Migration Cycle 4 - Migration of PRD to QAS environment

(Cut over rehearsal)

Functional and Security Testing

Performance and Volume Testing/Optimization on QAS

Infrastructure Test

Data Consistency checks and parallel operations of two

production (like) systems (Initially New-QAS vs. Existing-

PRD)

Tool Implementation and operational support

GoLive

Migration Cycle 5 - Migration of PRD environment

Handover and post golive support

Go-Live

High-Level Migration Project Plan


Migration Phases and Testing Cycles Project Overview for the Cloned Queue Migration Approach

Copy of DEV to new

DEV hardware

Focus:

•Migration of BW DEV

to HANA

•Verification of the

cookbook and of the

delta queue cloning

process (in the source

systems connected to

DEV)

•Keep old DEV for

reference

Copy of PRD to new

PRD hardware

Copy of PRD to new

QAS hardware

Focus:

•Migration of the QAS

system to HANA

•Second verification of

the cookbook and of

the delta queue cloning

process

•Perform volume testing

and functional

regression testing

Preparation:

•Refresh QAS from

PRD

•Clone the delta queues

in PRD and connect

the new BW QAS to

the cloned delta

queues in PRD

Copy of QAS to

Sandbox

Focus:

•Test of delta queue

cloning (by using the

Post Copy Automation

(PCA) tool) in the

source systems

connected to the BW

QAS

• Test of the data load

to HANA test system

Preparation:

•Perform a migration of

the BW Q-System to

HANA using the

cookbook created in

cycle 1

Copy of PRD to

Sandbox

Focus:

•Test the Upgrade and

migration steps on a

copy of production

•Create a cookbook

based on these tests

•No Test of delta queue

cloning

Cycle 1 Cycle 2 Cycle 3 Cycle 4 Cycle 5

Migration Execution


Migration Phases Example Scenario using the Cloned Queue Migration Approach

Landscape Overview

Existing NetWeaver 7.x BW Transport Landscape

RDBMS

Sandbox

RDBMS

Production

RDBMS

Quality Assurance

RDBMS

Development

Targeted NetWeaver 7.31 BW Transport Landscape

SAP

HANA

Sandbox

SAP

HANA

Production

SAP

HANA

Quality Assurance

SAP

HANA

Development



Migration Cycle 1 - Production to Sandbox

Systems in Scope

RDBMS

Sandbox

RDBMS

Production

1

2

SAP

HANA

Sandbox

3

Steps:

1.Using the existing sandbox system as the interim

environment, perform a homogeneous system copy

from production.

2.Update the necessary operating system, database,

and application levels required for the migration.

3.Perform a heterogeneous system copy to migrate the

updated sandbox system to SAP HANA. If available,

use the productive SAP HANA environment as a

sandbox for this specific migration in order to conduct

some preliminary performance testing.

4.Delete the instance on the interim sandbox

environment in order to prepare for the next migration.

4

Objective: To gain an understanding of the migration

process and specifically the nuances of the productive

environment. The steps and issues should be

documented in a “cookbook” and later used (and

enhanced) during future migrations.



Migration Cycle 2 – Quality Assurance to Sandbox

Systems in Scope

RDBMS

Sandbox

2

3

SAP

HANA

Sandbox

4

Steps:

1.Clone the delta queues in the quality assurance

source systems. Generate load in the source systems

to populate the delta queues.

2.Using the existing sandbox system again as the

interim environment, perform a homogeneous system

copy from the BW quality assurance system.




updated sandbox system to SAP HANA.

5.Process the cloned delta queues and verify.



6

Objective: To create an environment where the delta

queue cloning can be established and testing within the

customer landscape. Further document and enhance

the migration “cookbook.”

RDBMS

Quality Assurance

5 RDBMS

Quality Assurance

1



Migration Cycle 3 – Development to Development

Systems in Scope

RDBMS

Sandbox

2

3

4

Steps:

1.Clone the delta queues in the development source

systems. Generate load in the source systems to

populate the delta queues.



copy from the BW development system.




updated sandbox system to the development BW on

SAP HANA environment.




6

Objective: To create the BW on SAP HANA

development environment. It is also important to test

the delta clone procedure and further document and

enhance the migration “cookbook.”

RDBMS

Development

SAP

HANA

Development

5 RDBMS

Development

1



Migration Cycle 4 – Production to Quality Assurance

Systems in Scope

RDBMS

Sandbox

2

3

4

Steps:

1.Clone the delta queues in the productive source

systems.



copy from the BW productive system.




updated sandbox system to the quality assurance BW

on SAP HANA environment.




7.Terminate the cloned queues after set period of time.

6

Objective: To verify the migration approach, including

delta queue cloning, as well as to build the BW on SAP

HANA quality assurance environment. There should be

only minor enhancements to the migration “cookbook.”

SAP

HANA

Quality Assurance

RDBMS

Production

RDBMS

Production

1

5



Migration Cycle 5 – Production to Production

Systems in Scope

RDBMS

Sandbox

2

3

4

Steps:

1.Clone the delta queue(s) in at least one development

source system, where load can be generated to

populate the delta queue(s). Generate load in the

selected source systems.



copy from the BW productive system.




updated sandbox system to the productive BW on

SAP HANA environment.



environment.

7.Finalize the migration over the next 2-4 weeks.

6

Objective: To build the parallel productive BW system

on SAP HANA.

SAP

HANA

Production

RDBMS

Production

RDBMS

Production

1

5


Build Test Deploy

Unit Test

Regression

Test

SIT

Performance

/ Load Test

UAT

Cutover Test

System

Types

Refreshes

for QA/PPD

Unit Testing

Developer Self Test

Han

do

ve

r to

Te

stin

g

UAT

SIT 1

Pre

-Pro

d T

est

C

O

T

C

O

T

Load Test (opt.)

Regression Test First Regr.

Testing

Performance:

Single Activity Test

QG QG

SIT

2

Unit Testing during

development needs to

cover the following

elements:

• Test of new

functionality

• Single-activity

performance testing

(for selected modules)

• Regression tests

based on existing,

automated unit tests

• …..

UAT

Preview

UT

final

Refresh from

Production

Refreshes

from Backup

Refresh from

Production/backup

QA PPD

Multiple cycles

QG QG

Migration Phases and Testing Cycles Test and Quality Management – Major Release Testing Phases (Example)

The testing scope and activities

need to be aligned with the overall

scope of the project.

Supporting Tools and

Additional Information


Supporting Tools Downtime Optimization Tools for a Classical Migration

Migration Monitor • The Migration Monitor is a tool which helps you to perform and control the export and import process

during the migration. As of SAP NetWeaver 2004 SR1, the Migration Monitor is integrated into the

SAPinst system copy tool, but it is also possible to use the monitor for copying older releases by

starting it manually.

• User's Guide which is part of the tool archive (MIGMON.SAR)

Distribution Monitor • You can use the Distribution Monitor to speed up Unicode conversions by distributing the R3load

workload to multiple machines. For more information, see

• SAP Note: 855772 - Distribution Monitor

• SAP Note: 1001383 - Distribution Monitor - Known problems and fixes

• User's Guide, which is part of the tool archive (DISTMON.SAR)

SAP Migration Monitor - Parallel Migration SAP Distribution Monitor - Parallel Migration

https://service.sap.com/sap/support/notes/855772












DEV

QAS

PRD

Tool

Tool

Tool

File System

3

4

SAP Solution Manager 7.0 ≥ SP23

or SAP Solution Manager 7.1

MOpz Client

SAP Service Marketplace

MOpz Backend

SMSY

Landscape Verification 1.0 ≥ SP1

2a

Stack

Configuration

File*

2b

*Recommendation:

Create copies of the stack

configuration file to use throughout

the landscape. See the How-to guide

for the stack XML copy report (SAP

note 1600302) for details.

1

2

2c

Software

Packages Make sure that your system landscape is maintained correctly. Use Landscape Verification tool (SAP Solution Manager Add-on) and transaction SMSY (new in Solution Manager 7.1 SP5: LMDB).

Start new maintenance transaction using Maintenance Optimizer (MOpz) and plan implementation scenario.

Select target system version, implementation scenario, … .

Depending on your selection required SW components/SPS/… are automatically calculated and a plan is generated (Stack Configuration File).

Trigger download of files.

Provide your systems with the downloaded files, the generated plan and the latest execution tool (SAPehpi,..) version.

Perform your maintenance transaction by starting the execution tool on your system.

1

2

2a

2b

2c

3

4

Supporting Tools Maintenance Optimizer - A Technical Process View

https://websmp202.sap-ag.de/~sapidb/011000358700000877702011D/Guide_Stack_XML_Copy.pdf







Supporting Tools Software Logistics Toolset (aka SL Toolset)

Scope of Functionality within Software Logistics Toolset 1.0 SPS 04

For more information, visit the SAP Service Marketplace at quick link /sltoolset.

http://service.sap.com/sltoolset

http://service.sap.com/sltoolset


Supporting Tools Software Update Manager Overview

The Software Update Manager is the Software Maintenance Tool for the SAP

Business Suite 7 Innovations 2011*.

* For further information regarding replaced tools, see Replacements of outdated tools via SL Toolset –

SAP Note 1589311.


Supporting Tools Software Update Manager 1.0 SP4

Customer Situation:

Demand for unified consumption experience for system updates, with reduced

effort.

Offering:

Consolidate different software logistic tools into one unified software logistics tools

Runtime reduction: Higher degree of parallelization for certain phase types

Downtime reduction: Enhanced Shadow System capabilities for specific use cases

Changes with Latest SL Toolset Version (1.0 SPS 04):

Update to SUM SP 04, supporting additional update paths

SUM can now be downloaded via Maintenance Optimizer (see SAP Note 1626435)

near-Zero Downtime Management (nZDM) for SAP Business Suite (availability on request,

see SAP Note 1678565)

More Information:

SAP Note: Central Release Note SUM SP04 - 1626284








Supporting Tools Dual-Stack Split Overview - Capabilities and Scope

Technical Split with two options:

Splitting off

Installation of new Java-Stack without

additional database

Reusing the existing database via MCOD

Option 1: Keep DB use case (MCOD)

Splitting off

Option 2: Move DB use case (Non-MCOD)

Installation of new Java-Stack with

additional database

System copy of the Java database

persistency into the new database

Furthermore the Dual-Stack Split Tool provides:

Re-configure technical

connectivity in source and

target systems (ABAP to

Java and vice versa)

Automated Post-Configuration

For option 1): deleting the

Java-related SAP system

information within the source

system

For option 2): deleting the

Java-related SAP system

information and the Java

database persistency within

the source system

Deleting the Java-Stack

in a Dual-Stack System

Please note:

The Dual-Stack Split Tool will not touch your ABAP-

Stack in the Dual-Stack system.

The only thing changed during export is one instance profile parameter: rdisp/j2ee_start =

1 0


Supporting Tools Dual-Stack Split Tool 2.0

Customer Situation:

SAP recommends to move away from dual-stack SAP systems, where possible.

Offering:

Tool supports the copy of the Java stack into a new Java-only system, and the

former dual-stack system is reduced into an ABAP-only system.

Changes with Latest SL Toolset Version (1.0 SPS 04):

Support of further platforms (incl. IBM i)

Support of systems with Microsoft Cluster Services for all databases but SAP MaxDB

Support of dual-stack systems with a non-Unicode ABAP stack

No downtime for ABAP system during export

Consistent setting of JVM parameters as part of split procedure

More Information:

SAP Note: Central SAP Note - Dual Stack Split Tool 2.0 SP1 – 1685432









Supporting Tools Accelerating the Upgrade to NetWeaver BW 7.30

Use the predefined content for:

Upgrade to NetWeaver 7.x BW

Upgrade to ERP 6.0 EhPx (upcoming)

Upgrade to any SAP Product based on

the NetWeaver 7.x Platform

Create/modify own content (XML based)

Complete Business Suite 7

connectivity (with EhP1):

ABAP - java connection (available) for

connection BW-IP, EP, ESS/MSS, etc.

ABAP - ABAP (with EhP1) for backend

connection e.g. ERP, CRM, BW, PI, etc.

Java - Java (upcoming) for frontend

connection e.g. FPM, etc.

Note 1178800

Lower your TCO and time efforts

by Managing your Upgrade with innovative tools

2. Central Technical Configuration (CTC) for BW-Java

Automatic connection between ABAP and Java (Note 983156)

Check out the success story from the German Customer Karcher:

https://websmp204.sap-ag.de/~sapidp/011000358700000162292010E/

1. ASU toolbox (incl. BW Content)

One single truth for all pre/post Upgrade Steps

(Note 1000009)





Supporting Tools Landscape Virtualization Management 1.0 – Post Copy Automation (PCA)

Classical Steps PCA Supported Steps

BW Migration Steps from SAP Note 886102


Additional Information

SAP NW 7.3 ABAP System Copy Guide http://service.sap.com/~sapidb/011000358700001299452010E.pdf

SAP EHP1 for NW 7.3 ABAP System Copy Guide http://service.sap.com/~sapidb/011000358700001289792011.pdf

BW on HANA – System Copy Guide http://scn.sap.com/docs/DOC-12262

Deploying BW on SAP HANA Cookbook http://cookbook.experiencesaphana.com/deploying-bw-on-hana/

Orange End-to-End Implementation Roadmap https://websmp102.sap-ag.de/~sapdownload/011000358700001167432011E

Managing your Upgrade with Innovative Tools http://scn.sap.com/docs/DOC-7856

SAP NetWeaver 7.0 BI Upgrade Specifics for ABAP http://scn.sap.com/docs/DOC-11608

New Features with BW 7.30 http://www.sdn.sap.com/irj/sdn/bw-73

Links to Guides (Master and Upgrade) http://service.sap.com/instguides

NetWeaver BW 7.30 Online Help http://help.sap.com/saphelp_nw73/helpdata/en/ca/6fbd35746dbd2de10000009b38f889/frameset.htm

http://service.sap.com/~sapidb/011000358700001299452010E.pdf

http://service.sap.com/~sapidb/011000358700001289792011.pdf

http://scn.sap.com/docs/DOC-12262



http://cookbook.experiencesaphana.com/deploying-bw-on-hana/








https://websmp102.sap-ag.de/~sapdownload/011000358700001167432011E





http://service.sap.com/installnwbw72








http://www.sdn.sap.com/irj/sdn/bw-73




http://service.sap.com/instguides



Thank you

Contact information:

F name MI. L name

Title

Address

Phone number

sap innovation summer camp come with a curiosity –...

Documents