Deployment strategies for the SAP Business Suite 7 Illinois Chapter Meeting Aug 28 th, 2009 Marco Valencia Vice President SAP Upgrade Competency Center.

Deployment strategies for the SAP Business Suite 7

Illinois Chapter MeetingAug 28th, 2009

Marco ValenciaVice President

SAP Upgrade Competency Center – North America

SAP Business Suite

NetWeaver IntegrationNetWeaver Integration

NetWeaver CompositionBusiness ObjectsNetWeaver CompositionBusiness Objects

EH

PEH

P

EH

PEH

P

Application Lifecycle Management, Identity Management

IndustryAdd-OnCRM SRM SCM PLM ERP

© SAP 2009/ ASUG / Page 2

Adopting the SAP Business Suite 7

Adopting the SAP Business Suite 7 2

Technology Considerations Overview

Upgrade per Application

Additional Tools

B

C

SAP Business Suite 7 – Overview1

A

Further Information & Links3


SAP NetWeaver 7.0(foundation for the SAP Business Suite)

EHPEHP EHPEHP EHPEHP

SAP Business Suite 7

Continuous Innovation

ERP 6.04CRM 7.0 SCM 7.0

PLM 7.0SRM 7.0

EHPEHP EHPEHP EHPEHP

SAP Business Suite 7 core applications: EHP 4 for

SAP ERP 6.0 (6.04) SAP CRM 7.0 SAP SRM 7.0 SAP SCM 7.0 SAP PLM 7.0

SAP enhancement packages across the SAP Business Suite 7 planned for 2010

No

n-S

AP

SAP Business Suite 7

EHPEHP EHPEHP

Composite Applications

SAP NetWeaver

Accelerated Innovation

PI 7.1 …CE 7.1

Increasing flexibility through composition


Global Industry Value

Industry Context

Sp

ec

ific

In

du

str

y A

dd

itio

ns In

du

stry

Alig

ne

d P

roc

es

se

sIntgrated Product

Development

Advanced Metering

Infrastructure

CustomerService

Insurance Claims Management

End-to-End Processes On One Platform Supporting Industry

SAP Business Suite 7 Insight to Action through Process Excellence

SAP Business Suite

NetWeaverIntegrationNetWeaverIntegration

NetWeaver CompositionBusiness ObjectsNetWeaver CompositionBusiness Objects

Eh

PEh

P

Eh

PEh

P

Pre-integrated Industry specific Processes

Flexible, Modular Upgrades to minimize disruption

Continuous Innovation for Line of Business In Your Industry

Continued SOA enablement and innovation

More Harmonized UI’s Across Applications and processes

Embedded analytics for contextualized Insight

Best-Run NOW packages to solve immediate pain

Application Lifecycle Management, Identity Management

For Increased User

Productivity

For Increased User

Productivity

IndustryAdd-On

For Increased Business and IT Efficiency

For Increased Business and IT Efficiency

For Value Focused Fast Deployments

For Value Focused Fast Deployments

For informed decision making

and Control

For informed decision making

and Control

For flexible process and

business agility

For flexible process and

business agility

For faster, focused solution

evolution with lower costs

For faster, focused solution

evolution with lower costs

For performance advancement in core industry processes

For performance advancement in core industry processes

CRM SRM SCM PLM ERP


Upgrade to SAP ERP 6.0 and SAP NetWeaver 7.0

Implement available functionality

Stable, core functionality and integration platformStable, core functionality and integration platform

SAP Business Suite ERP, CRM, SCM, SRM, PLM, IS

SAP NetWeaver

Execute on SOA: Composition Environment Enterprise Service Repository

Reposition ‘IT’-department

Faster support for changing businesses/ business processesFaster support for changing businesses/ business processes

Enterprise Services Repository

Composition Environment & Composites

Leverage/activate SAP enhancement packages

Use SAP Business Suite Gain SOA experience

Less disruptive functional enhancementLess disruptive functional enhancement

SA

P E

nh

ance

men

t P

acka

ges

2

1

3

What Do You Need? Business Process Platform


1. Innovate with minimal disruption

2. Stay compliant

3. Secure Investment

4. Drive consistent business process support

5. Prepare for a service-oriented architecture

Upgrade SAP ERP 6.0 – The First Step!

Upgrade Drivers

Adoption

Customer Adoption + 37%

Strong Momentum

38 months after release: > 11,745 productive customers

> 16,200 productive systems

SAP ERP 6.0

R/3 4.7

time

Source:MOVE/GUO


SAP ERP 6.0 is the path to SAP next generation solutions

NEW SAP BUSINESSVALUE & TECHNOLOGY

NEW SAP BUSINESSVALUE & TECHNOLOGY

Enhancement Packages Key Differentiator, SAP unique way to deliver value to customer’s business

Enterprise Services

Enhancement Packages Key Differentiator, SAP unique way to deliver value to customer’s business

Enterprise Services

FSCM, Manufacturing Execution, Sales Order Mgmt, Financial Accounting

HCM Talent Mgmt.

FSCM, Manufacturing Execution, Sales Order Mgmt, Financial Accounting

HCM Talent Mgmt.

ADDITIONAL ERP FUNCTIONALITY

ADDITIONAL ERP FUNCTIONALITY

3RD PARTY SOLUTIONS:3RD PARTY SOLUTIONS:

Redwood, Nakisa, Adobe FormsRedwood, Nakisa, Adobe Forms

SAP Business Suite 7SAP Business Suite 7

SAPERP 6.0

SAPERP 6.0


Driving Synergies Across the SuiteDelivering on one date, Innovation across the Applications

2006 2007 2008 2009 2010*

EhP1ERP 6.0

CRM 7.0

PLM 7.0

SCM 7.0

SRM 7.0

(Selected) enhancements* across the Suite

Synchronized Suite release

Enhancement Packages across the Suite

* Subject to change

EhP2 EhP3 EhP4 EhP5

EhP1

EhP1

EhP1

EhP1

Sustainability platform

Supply chain & manufacturing adaptiveness

Advanced shopping experience...

Integrated product development

Supply chain efficiency

World-class operations …

Business SuiteRelease Strategy


New 7-2 Maintenance Strategy – Planning and Investment Security

Before

New

* 7-2 strategy applies to new releases of the core applications of SAP Business Suite, starting with SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0, SAP PLM 7.0; plus SAP ERP 6.0 (EHP4) and SAP NetWeaver 7.0. Industry-specific add-on applications and SAP enhancement packages based on these core application releases will offer mainstream and extended maintenance in line with these releases.

** Enhancement Packages: Illustrative only; does not reflect exact shipment times and frequency.

Dec

Mainstream Maintenance Extended Maint. (+ 2%)*

SAP ERP 6.0, SAP NW 7.0


SAP CRM, SCM, SRM 7.0

Ramp-Up

Dec

Cust.-Spec.Maintenance


Ramp-Up

2011 20122009 2010 20142013 2015 2016 2017200820072006

7 2

EHP** EHP** EHP** EHP** EHP** EHP**

EHP** EHP** EHP** EHP**

No

v

Dec




SAP CRM, SCM, SRM 7.0

Ramp-Up

Dec



Ramp-Up

2011 20122009 2010 20142013 2015 2016 2017200820072006

7 2

EHP** EHP** EHP** EHP** EHP** EHP**


No

v

Mar

Mar

Mar

Mainstream Maintenance Ext. Maint. (+ 2%)*



Ramp-Up


Ext. Maintenance (+ 4%)*

2011 20122009 2010 20142013 2015 2016 2017200820072006

Mar

Mar

Mar

Mar

Mar

Mar




Ramp-Up



2011 20122009 2010 20142013 2015 2016 2017200820072006


2011 2012

Release and Maintenance Strategy SAP ERP

2006 2007 2008 2009 2010

mySAP ERP 2004

SAP R/3 4.6C

SAP ERP 6.0**

Dec

Mar

Dec

Mar

Mar

Mar

2013

Dec

Mar

Ext. Maint. (+ 2%)*


Customer-SpecificMaintenance




SAP R/3 Enterprise

47x110, 47x200

Mainstream Maint. Ext. Maint. (+ 2%)*



Jun

Dec


2014 2015 2016

Cust.-Spec.Maint.

* Overall payment is SAP support fee plus additional fee of 2% or 4% of the maintenance base per year.** SAP ERP 6.0 is the application release formerly known as mySAP ERP 2005.


Dec

Mainstream Maint. Customer-SpecificMaintenance

As of January 01, 2009, extended maintenance for SAP R/3 4.6C and SAP R/3 Enterprise is included in

SAP Enterprise Support and extended by one year

Extended maintenance (no add. fee,included in SAP Enterprise Support contract)

SAP R/3 3.1I – 4.6B

Ext. M.(+ 4%)*


This strategy is also valid for all industry-specific add-on applications and SAP enhancement packages for SAP ERP based on the releases above.

Extended maintenance (no add. fee,included in SAP Enterprise Support contract)

2017

Dec

New 7-2 maintenancestrategy for SAP ERP 6.0:

Mainstream maintenance extension from March 2013 to December 2015

Extended maintenance offered for two years to December 2017


Building a Business Case for SAP Business SuiteConsiderations for Prospective Customers

Place more investment into projects that make a difference No integration projects – end-to-end processes out of the box Logical, step wise expansion of your existing SAP systems Greater % of IT investment to strategic priorities of your organization

Deliver better productivity of the organization End-to-end visibility for managers – single source of truth Transparency across all operational processes – streamlined workflow Flexibility to modify processes – adapt to business change

Deliver value NOW…. SAP delivers proven value - best practices of all industries Strong network of complementary software providers – Eco-system Complete set of services available today






Additional Tools

B

C


A



Key Technology Considerations

Transition to SAP Business Suite - Business Scenarios Determine the Transition Path

Source: MOVE/GUO

Target Business Suite 7

Current

Upgrade per application

Upgrade Paths

Complexity Drivers

SAP Enhancement Packages

UnicodeA

Business scenarios in ONE application

Upgrade the respective application Activate new functionality

Business scenarios in ONE application

Upgrade the respective application Activate new functionality

Deploy further applications

Deployment Options

Upgrade DependenciesB

Mandatory Components

Business scenarios ACROSS applications

Upgrade the respective applications Deploy required additional applications

Business scenarios ACROSS applications

Upgrade the respective applications Deploy required additional applications Netweaver Scenarios

SAP Appl. BS 7 Appl.

UpgradeUpgradee.g. SAP R3 4.Xe.g. SAP R3 4.X

e.g. EHP 4 for SAP ERP 6.0e.g. EHP 4 for SAP ERP 6.0

Upgrade & DeployUpgrade & Deploy

SAP Appl.e.g. SAP R3 4.Xe.g. SAP R3 4.X

1

2

3

4

1

2

3

4

SAP Business Suite

NetWeaverIntegration

NetWeaverComposition

EH

P

EH

P

SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM

Industry Applications

Supplementary Applications

SAP Business Suite SAP Business Suite

NetWeaverIntegration

NetWeaverComposition

EH

P

EH

PE

HP

SAP ERP SAP CRM SAP SCM SAP PLMSAP SRM

Industry Applications

Supplementary Applications


Number of add-ons / industry solutions

Number of modifiedobjects

Required downtime

Source release

Number of codepages

Code freeze strategy

Testing requirements

OS / DB migration requirements

Type of upgrade (technical/functional)

Upgrade Project Complexity

Drivers

Complexity DriversUpgrade Complexity Classification (1/2)1

Dependencies to connected systems1

1 SAP and Non-SAPSource: MOVE/GUO


Complexity DriversUpgrade Complexity Classification (2/2)

# user inter-faces

# scenarios

# of modified objects

# interfaces

# user inter-faces

# scenarios


# interfaces

SAP CRM

# of SCM components

# scenarios


# interfaces

# of SCM components

# scenarios


# interfaces

SAP SCM

# required NW com-ponents

# scenarios


# interfaces

# required NW com-ponents

# scenarios


# interfaces

SAP SRM

# of users


# interfaces

# of users


# interfaces

SAP Netweaver(BW, ..)

# modules# users

# modified objects

# interfaces

# modules# users

# modified objects

# interfaces

SAP ERP

System scope

System complexity

Duration and effort of an upgrade can be determined based on system scope and system complexity1. Different upgrade complexity drivers per application to be considered.

Duration and effort of an upgrade can be determined based on system scope and system complexity1. Different upgrade complexity drivers per application to be considered.

1 Other factors influencing the upgrade effort (i.e. organizational complexity, knowledge) are considered in a later stage

1


Unicode –Upgrade Paths to Unicode

1 If No. of Code Pages in old system > 1 then the Unicode Conversion MUST be done IMMEDIATELY after upgrade.

R/3 4.6c

R/3 4.5b

R/3 4.6b

R/3 4.0b

Directupgrade

SAP ERP 6.0

non-Unicode

SAP ERP 6.0including

SAP enhance-ment package 4

Unicode

Con-version

First upgrade, then conversion to Unicode1

As-is ReleaseAs-is ReleaseExample:

SAP R/3 to SAP ERP 6.0 including SAP enhancement package 4

Example: SAP R/3 to SAP ERP 6.0 including SAP

enhancement package 4

Other, more recent releases

2


EhA EhB

EhC EhD

EhE EhF

EhA EhB

EhC EhD

EhE EhF

MES Integ.

EBPP

Sales order

HCM forms

Credit Report

Budget Execution

SAP enhancement package

User interface

Functionality

Enterprise services

Sales order Management

User interface

Enterprise services

Functionality

Traditional Upgrades SAP Enhancement Packages

“All or none” Affecting the enterprise Requires thorough testing Business case for entire release

“Pick and choose” Continuous innovation as part of regular

maintenance with support packages Modular consumption of innovation by selective

activation and testing driven by business requirements

Available for the go-to-releases of SAP Business Suite 7

For all Business Suite 7 applications: Common release schedule, incremental deployments, and minimal disruptive upgrades, allowing stepwise projects and activation.

For all Business Suite 7 applications: Common release schedule, incremental deployments, and minimal disruptive upgrades, allowing stepwise projects and activation.

SAP Enhancement Packages – Available And Synchronized For The Entire Suite3


Discover Receive an overview of

available enhancements Understand their potential

business benefits Identify enhancements

relevant for you

Test & Go Live

Activate & ConfigureCheck dependenciesActivate business functionsConfigure new capabilities

Evaluate & Decide

Prepare & Install

PLAN

BUILD

The roles mentioned on this slide refer to the SAP Standards for E2E Solution Operations.

1

4

5

3

2

Decouple technical installation from business innovation:Install SAP enhancement package combined with support pack stack as part of

maintenance activities with only minor additional effort .

Execute acceptance test (limited

to new functionality activated) Train end-users affected (limited) Go live

Choose ‘selective’ versus ‘broad’

installation approach Identify relevant installable part Download, load, and install Adjust Modifications Execute regression test

Evaluate relevant enhancements Understand their particular benefit for you Assess effort and impact of their implementation Take decision for business functions

Enhancement Packages – Lifecycle 3






Additional Tools

B

C


A



¹ Direct upgrade from these source releases to the go-to releases of SAP Business Suite 7 is supported by SAP. ² If you upgrade from SAP CRM 4.0 or 5.0 to SAP CRM 7.0, customer-specific UIs (including the underlying UI-related coding) have to be migrated separately.³ Besides the core applications, the SAP Business Suite provides also industry-specific applications (e.g. SAP Dealer Business Management, SAP Reinsurance Management) and cross-industry supplementary applications (e.g. SAP Portfolio and Project Management, SAP E-Sourcing). For these applications, the usual upgrade procedures apply. For an overview on the currently available and planned industry and supplementary applications, please refer to "SAP Release Strategy for Large Enterprises" on http://www.service.sap.com/releasestrategy

Install SAP enhancement package 4

for SAP ERP

SAP R/3 4.0B¹ and above

SAP CRM 4.0¹,² and above

SAP SRM 3.0¹and above

SAP SCM 4.1¹ and above

SAP PLM 4.0¹ and above

Upgrade to SAP ERP 6.0 and include SAP enhancement package 4 for SAP ERP

SAP ERP 6.0 plus SAP enhancement

package 4 for SAP ERP

(including SAP PLM 7.0)

SAP CRM 7.0

SAP SRM 7.0

SAP SCM 7.0

SAP PLM 7.0

Upgrade

Upgrade

Upgrade

SAP ERP 6.0

Co

re Ap

plicatio

ns o

f SA

P B

usin

ess Su

ite 7³Upgrade Paths – How to Get to SAP Business Suite 7 if You’re Running on... 4


DiscoverEvaluate & Decide

1

PlanPlan

Scenario & process component list

DESCRIPTION: The scenario & process component list allows to

flexibly illustrate possible technical realization alternatives for key business scenarios or processes

BENEFITS: Easy identification of the components needed to

realize a new business scenario Quick access and easy to use Central access point across SAP solutions

http://service.sap.com/scl

Implementation and/or Upgrade Project

2

BuildBuild

Mandatory Components – Scenario & Process Component List 1

Deployment of SAP Business Suite 7 components based on the process scenario requirements in the scenario component list, leading to different possible combinations.

Deployment of SAP Business Suite 7 components based on the process scenario requirements in the scenario component list, leading to different possible combinations.


1. Install SAP Solution Manager 7.0

2. Upgrade existing system landscape:

- SAP R/3 4.6 C to SAP ECC 6.04

- SAP BW 3.5 to SAP Netweaver Business Warehouse (BW) 7.01

3. Install and implement new components

- SAP CRM 7.0 / NW7.01 - CRM Application Server ABAP

- SAP CRM 7.0 / NW7.01 - CRM Application Server Java

- SAP SCM 7.0 - SCM Server

Selected Scenario

Goal: Customer implements value scenario “Lead to Cash”

Required Steps

Upgrade Dependencies – Evolution Path Example: Implement “Lead to Cash”2

Current system landscape

Target system landscape

Portal 7.0*

R/3 4.6C Server

SAP R/3

ABAP

Portal 7.0*

ABAP

BW 3.5

SAP NetWeaverBusiness Warehouse

Portal 7.0*ECC Server

SAP ERP

ABAP

Portal 7.0*

ABAP

BW

SAP NW BW

EXAMPLEEXAMPLE


SAP ERP/PLM

I: General Recommendation II: Reasonable Alternative

Single System Scenario Layered PLM Deployment

Use Case Single System Scenario with SAP PLM 7.0 (PLMWUI and

EHP 4) with PPM 5.0 (CPRXRPM) as Add-On Project and portfolio management, design collaboration

Benefits Reduced TCO by shared use of infrastructure Reduced administration and operation effort

Considerations PLM scenarios running in SAP ECC Server might impact:

stability & performance downtime for patching security

Use Case Product development with partners using external

("presentation only" mode) and internal ("data persistency" mode) layers

Benefits Increased network security through separation of

application servers Intranet and extranet access controlled by authorizations

inside internal application server Better scalability and load balancing capabilities

Considerations Complex system landscape and higher TCO

internal

external

Deployment Options – SAP ERP / PLM 7.0 Deployment 3


Use Case Centrally governed SAP SRM Server integrated to 1-n SAP

ERP systems Centralized procurement

Benefits Support different innovation cycles, individual availability Separation of responsibilities (e.g. less alignment effort) Independent scalability & performance Flexibility to change landscape layout

Considerations Higher TCO

Use Case Single System Scenario with SAP SRM 7.0 (with EHP4

and SRM_SERVER and SRM_EXT as Add On’s) Self-Service Procurement (classic Scenario), Temp.

Labor Service Procurement, Supplier Self Service

Benefits Reduced TCO by shared use of infrastructure and one

organizational model Master data distribution synchronously & bi-directional

Considerations Functional Limitations, e.g. no extended classic

scenario, no multi backend deployment

SAP SRM

Single System Scenario SRM Server Deployment

SAP SRM

Server

Deployment Options – SAP SRM 7.0 Deployment3



SAP SCM

Use Case Standalone, centrally governed SAP SCM Server

Benefits Support different innovation cycles, individual availability Separation of responsibilities (e.g. less alignment effort) Independent scalability & performance Flexibility to change landscape layout Full functionality available

Considerations Higher TCO

Use Case Single system scenario with EM and EWM Add-ons (with

EHP3+ and SCM_BASIS, SCMEWM , SCEMSRV as Add On’s)

Event Management, Extended Warehouse Management, planned: Transportation Management (SAP TM 8.0)

Benefits Reduced TCO by shared use of infrastructure Reduced administration and operation effortConsiderations Functional limitations, e.g. no Supply Network

Collaboration (SAP SNC) or Advanced Planner & Optimizer (SAP APO)

SCM Server Deployment Single System Scenario

Deployment Options – SAP SCM 7.0 Deployment3



SAP CRM

Use Case Standalone, centrally governed SAP CRM Server

Benefits Support different innovation cycles, individual

availability Separation of responsibilities (e.g. less alignment

effort) Independent scalability & performance Flexibility to change landscape layout

Considerations More complex system landscape

End-to-endScenarios

Self-service InteractionCenter

PartnerField

Multi-channel

Key Capabilities of SAP CRM

Marketing, sales, service and all customer interaction channels

CRM Server Deployment

Deployment Options – SAP CRM 7.0 Deployment3

I: General Recommendation


NetWeaver Scenarios –Deployment of SAP NetWeaver Portal

General Recommendation Shared usage of SAP NetWeaver Portal provides a central access to the SAP Business Suite

application systems in the customer solution landscape SAP NetWeaver Portal is deployed as a separate system to support different innovation speed

and simplified landscape setups Avoid embedded deployment of SAP NetWeaver Portal within the application system

General Recommendation Shared usage of SAP NetWeaver Portal provides a central access to the SAP Business Suite

application systems in the customer solution landscape SAP NetWeaver Portal is deployed as a separate system to support different innovation speed

and simplified landscape setups Avoid embedded deployment of SAP NetWeaver Portal within the application system

Use Cases Central role-based access to different backend

applications Sharing central portal infrastructure for portal based

applications

Benefits Centrally governed and administrated portal Shared use of central SAP NetWeaver system to

reduce administration effort

Considerations Interoperability to connected application systems

have to be checked Applications running in the portal might impact

stability & performance downtime for patching

4

Central portal


General Recommendation Integrate, store, and manage company data from multiple connected data sources in a

central data warehouse system including central definition of all queries, web templates andenterprise reports

Comprehensive set of planning and simulation capabilities with a simplified landscape setup Implement SAP Netweaver Business Warehouse and Business Explorer Web capabilities on separated

systems

General Recommendation Integrate, store, and manage company data from multiple connected data sources in a

central data warehouse system including central definition of all queries, web templates andenterprise reports

Comprehensive set of planning and simulation capabilities with a simplified landscape setup Implement SAP Netweaver Business Warehouse and Business Explorer Web capabilities on separated

systems

Use Cases Integrate, store, and manage company data from

multiple connected data sources in a central data warehouse system

Design and execute queries to analyze business information

Access analytic data based on web templates and enterprise reports

Benefits Consolidated view of company wide reporting data Comprehensive Business Intelligence capabilities for

planning and simulation Reduced TCO by shared services and infrastructure Highly scalable by separated technology stacks

Considerations Release & SP stack dependency between BI and BEx

Web²² current planning: remove support package stack dependency with SAP NetWeaver 7.0 EHP2

Central Data Warehouse

Central Bex Web

NetWeaver Scenarios – Deployment of SAP NetWeaver Business Warehouse4


General Recommendation Shared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios as well as

service enabling of the SAP Business Suite application systems SAP NetWeaver Process Integration is deployed as a central, separate system to support

different innovation speed and simplified landscape setups Avoid embedded deployment of SAP NetWeaver Process Integration within the application system

General Recommendation Shared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios as well as

service enabling of the SAP Business Suite application systems SAP NetWeaver Process Integration is deployed as a central, separate system to support

different innovation speed and simplified landscape setups Avoid embedded deployment of SAP NetWeaver Process Integration within the application system

Use Cases Integration of A2A or B2B processes between SAP

and Non-SAP systems Service enablement of SAP and Non-SAP systems

Benefits Less complexity of system landscape Central governance for meta data Less effort by central maintaining of data for

routing,mapping, connectivity, ccBPM, etc.

Central responsibility for monitoring of services and processes

Support of high volume scenarios, simplified modeling and configuration, enhanced standard support with SAP NetWeaver Process Integration 7.1

Central PI

NetWeaver Scenarios – Deployment of SAP NetWeaver Process Integration4






Additional Tools

B

C


A



Upgrade Dependency Analyzer

Check the existence of upgrade dependencies between two separately installed SAP systems in your system landscape

SAP Service Marketplace at : http://service.sap.com/uda

Integrated with SAP Solution Manager (with ST400 SP17)

Reduce risks, costs and effort

Quick access and easy to use

Central access point across SAP solutions

DESCRIPTION

ACCESS

BENEFITS


Scenario & Process Component List

Allows to flexibly illustrate possible technical realization alternatives for key business scenarios or processes

SAP Service Marketplace at:http://service.sap.com/scl

Easy identification of the components needed to realize a new business scenario



Customers starting an upgrade can find out which components can - or cannot - be combined for certain business scenarios

DESCRIPTION

ACCESS

BENEFITS


Product Availability Matrix

SAP Service Marketplace at:http://service.sap.com/pam

Reduce risks



You will find information on the availability of SAP component releases (product versions), maintenance end dates and upgrade paths, as well as technical release information

DESCRIPTION

ACCESS

BENEFITS






Deploy further Applications

B

C


A



Quick Upgrade Analysis for SAP Business Suite

It is a fast, high-level, remote upgrade assessment designed for SAP customers running two or more SAP Business Suite Components (SAP ERP, SAP CRM,

SAP SRM, etc.) looking to take advantage from the latest Business Suite 7 release level

that helps to Plan a landscape upgrade

By analyzing current customer SAP Business Suite Component systems and providing, specific impact of the upgrade in the SAP landscape dependencies between components landscape complexity high level effort estimation Roadmap and timelines

for an SAP Landscape Upgrade.

Quick Upgrade Analysis for SAP Business Suite

© SAP 2009 / Page 35


System information – Technical

Note: The following results are high-level estimates of upgrade effort and benefits based on system data collected by the transaction monitor running from 1.10.2007 and 15.12.2007 on your system. A detailed technical system review and evaluation was not undertaken.

Customer and system parameters System classification

Generaldata

Customer: 3Com CorporationSystem: 20109625Release: R/3 4.6CModules: 12

Licensedata

License: mySAP Business SuiteNumber of users: 671

Degree of modification

Simple objects: 679Medium objects: 963Complex objects: 1292Interfaces: 79

Hardware

#CPU: 12Memory: 32766 MBStorage: 574 GBLanguage(s): MDMP system

An upgrade of XXX to SAP ERP 6.0 is considered comparatively complex due to its significant size and average degree of modification.

Degree of modification

Sys

tem

Sco

pe

small

large

low high

Incr

easi

ng u

pgra

deco

mpl

exity

Dec

reas

ing

upgr

ade

com

plex

ity

Final Deliverable -

Sample

© SAP 2009 / Page 36


System information – Degree of modification

1 Complexity is derived from the modified lines of code (mLoC) 2 For customer exits, modified SAP scripts, modified DDIC objects and interfaces a complexity evaluation based on modified LoC is not possible, therefore these objects are assumed to be

medium complex

Modified objects represent a significant cost driver during an upgrade. The following objects could be identified incl. their respective complexity to upgrade

148179504

320

53124811

272

464

28011

12

657270

061

326

120

78

626200

79

14748930420

11451064

576

Modifications Modified executable programs Modified includes Modified classes Modified module pools Other modified programs Modified function blocks

Custom objects Customer programs Other program types Customer includes Customer function blocks

Customer exits

Modified SAP scripts

Modified DDIC objects Transparent tables Pool tables Cluster table

Interfaces

Low (<100 mLoC1)Medium2 (100-200 mLoC1) High (>200 mLoC1)Modified objects / complexity

N

o co

mp

lexi

ty e

valu

atio

n a

nd

mo

du

le a

ssig

nm

en

t po

ssib

leFinal Deliverable -

Sample

© SAP 2009 / Page 37


Upgrade complexity classification

In a simple model, the duration and effort of an upgrade is driven by the system scope and system complexity1

System Scope Requirement of additional NW components

Complexity / Scenario Score MDM PI EP

Self Service Procurement 1

Plan Driven Procurement

Service Procurement 1

Catalog and Content Mgmt 1

Operational Contract Mgmt 1

Sourcing

Supplier Qualification 1

Analytics

Procurement for PS 1

Application WF

System complexity

# interfaces 0-10 10-20 20+

# modified objects Scores 1 2 3

0-100 1 1 2 3

100-200 2 2 4 6

200+ 3 3 6 9

2 months 4 months

3 months 5 months

1 - 4 5 - 9

1 -

45

- 10

Sy

ste

m s

co

pe

System complexitylow high

small

largeSystem classification matrix2

1 Other factors influencing the upgrade effort (i.e. organizational complexity, knowledge) are considered in a later stage 2 The values for upgrade duration are rough estimates based on SAP Ramp-up experience for technical upgrades

Final Deliverable -

Sample

© SAP 2009 / Page 38


AS-IS Vs TO-BE Landscape (Example)

Upgrade to ERP 6.0

Portal 7.0*

ECCServe

r

SAP ERP 6.0

ABAP

SAP Netweaver Portal

Java

EP

SAP NetweaverBusiness Intelligence

ABAP

BI

Legacy SystemLegacy

SystemLegacy System

Portal 7.0*SAP MDM 3.1

ABAP

Java

SAP R3 with multiple components

Portal 7.0*

4.X

SAP R3

ABAP

SAP ITS/WAS

SAP NetweaverBW 3.X

ABAP

BI

Legacy SystemLegacy

SystemLegacy System

Portal 7.0*SAP SRM 5.0

ABAP

Java

ABAP

SAP PI

Java

EP

Portal 7.0*SAP SRM 7.0

ABAP

Java

Final Deliverable -

Sample

© SAP 2009 / Page 39


Effort Summary

BS Component Effort (PD) Duration (Weeks)Source of effort

estimationComments

SAP ERP 560 14 QUA

1. Migration from ESS/MSS to be evaluated

2. Unicode effort not part of analysis

SAP CRM 550 22 QUA

1. UI Migration Functional Effort to be evaluated. Based on # of Uis, # of scenario and # of roles implemented

SAP SRM 230 12 Questionnaire / Interview

1. Catalog Migration Functional Effort to be evaluated

2. Portal implementation not considered as part of assessment

SAP SCM 180 12 Questionnaire / Interview

1. Migration from ESS/MSS to be evaluated

SAP NetWeaver 190 12 Historical info

1. BI / MDM Implementation effort to be evaluated

Overall 1710

Final Deliverable -

Sample

© SAP 2009 / Page 40


Important links @ SAP Service Marketplace

SAP Business Suite http://service.sap.com/businesssuite

SAP NetWeaverhttp://service.sap.com/netweaver

SAP ERPhttp://service.sap.com/erp

Solution Manager http://service.sap.com/solutionmanager

New Release Strategyhttp://service.sap.com/releasestrategy

Release Notes

http://service.sap.com/releasenotes

Upgrade Information Centerhttp://service.sap.com/upgrade

Enhancement Packageshttp://service.sap.com/erp-ehp

Upgrade Technology Toolshttp://service.sap.com/upgradetech

SafeGuarding for Upgradeshttp://service.sap.com/safeguarding

Maintenance Strategyhttp://service.sap.com/maintenance

Online Help

http://help.sap.com

Training Contenthttp://service.sap.com/trainingcatalog

Going Live Checkshttp://service.sap.com/goinglive-fu

© SAP 2009/ ASUG Annual Conference / Page 42

Thank you!

Marco ValenciaVice PresidentNA UCCPhone: +1 404-943-6477

[email protected]

www.sap.com

Deployment strategies for the SAP Business Suite 7 Illinois Chapter Meeting Aug 28 th, 2009 Marco Valencia Vice President SAP Upgrade Competency Center.

Documents

sap crm

sap scm

sap plm

sap srm

composition sap

moveguo sap

business process platform

sap unique way