• No results found

Sap Adm328 en Col15 Nw 7.31 Part Nw

N/A
N/A
Protected

Academic year: 2021

Share "Sap Adm328 en Col15 Nw 7.31 Part Nw"

Copied!
274
0
0

Loading.... (view fulltext now)

Full text

(1)

SAP EHP Installation and Upgrade

PARTICIPANT HANDBOOK INSTRUCTOR-LED TRAINING Course Version: 15

Course Duration: 5 Day(s) Material Number: 50123906

(2)

SAP Copyrights and Trademarks

© 2014 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

• Microsoft, Windows, Excel. Outlook, and PowerPoint are registered trademarks of Microsoft

Corporation.

• IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System zlO, System z9, zlO, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/0S, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+. POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF,

Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and lnformix are trademarks or registered trademarks of IBM Corporation.

• Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

• Adobe, the Adobe logo, Acrobat. Postscript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

• Oracle is a registered trademark of Oracle Corporation

• UNIX, X/Open, OSF /1, and Motif are registered trademarks of the Open Group.

• Citrix. ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

• HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C". World Wide Web Consortium, Massachusetts Institute of Technology.

• Java is a registered trademark of Sun Microsystems, Inc.

• JavaScript is a registered trademark of Sun Microsystems, Inc .. used under license for technology invented and implemented by Netscape.

• SAP, R/3, SAP NetWeaver, Duet. PartnerEdge, ByDesign, SAP BusinessObjects Explorer,

StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

• Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal

Decisions. Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of

(3)

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without

representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are

those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

(4)
(5)

Typographic Conventions

American English is the standard used in this handbook.

The following typographic conventions are also used.

This information is displayed in the instructor's presentation

Demonstration

Procedure

Warning or Caution

Hint

Related or Additional Information

Facilitated Discussion

User interface control

Window title

©Copyright . All rights reserved.

a

A

0

Example text Example text v

(6)
(7)

Contents

xi Course Overview 1 2 8 11 19 20 24 29 30 35 41 42 48 57 65 66 73 77 78 85 88 91 95 96 100 102 107 111 113 Unit 1: Unit 2: Unit 3: Unit 4: Unit 5: Unit 6: Unit 7:

Introduction to SAP System Architecture

Lesson: Describing the Architecture of an SAP System

Lesson: Identifying the Update/Upgrade Options Available in SAP Lesson: Identifying Key Elements of an SAP Update/Upgrade

SAP Target Release Selection

Lesson: Identifying the SAP Solution Manager Maintenance

Optimizer

Lesson: Performing the Maintenance Transaction Update/Upgrade Preparation

Lesson: Performing Pre-Upgrade Steps

Exercise 1: Perform Pre-Upgrade Steps

SUM Part Preparation

Lesson: Analyzing the Uses of the Software Update Manager (SUM) Lesson: Using the SUM to Prepare for Updating/Upgrading

Exercise 2: Use the SUM to Prepare for Updating/Upgrading

SUM Part Update/Upgrade

Lesson: Evaluating the Phases of the Update/Upgrade Process

Lesson: Assessing the Usage of the Shadow System Modification Adjustment

Lesson: Evaluating Modification Adjustments

Lesson: Performing SPDD

Lesson: Performing SPAU Exercise 3: Perform SPDD

Update/Upgrade Troubleshooting

Lesson: Identifying the Types of Update/Upgrade Phases Lesson: Troubleshooting Job Phases

Lesson: Troubleshooting Transport Phases

Exercise 4: Correct Errors from ACT _UPG

Lesson: Troubleshooting Bulk Import Phases

Lesson: Evaluating Update/Upgrade Recommendations

(8)

117 Unit 8: Incremental Table Conversion

118 Lesson: Identifying the Goals of ICNV

123 Lesson: Performing ICNV

127 Unit 9: Add-On Handling

128 Lesson: Explaining the Handling of Add-Ons

135 Unit 10: Downtime

136 Lesson: Evaluating Downtime

139 Lesson: Assessing Update/Upgrade Process Downtime

146 Lesson: Identifying Near Zero Downtime Maintenance (nZDM)

Capabilities of SUM

152 Lesson: Handling Downtime Phases

155 Exercise 5: Manage Downtime

163 Unit 11: Update/Upgrade of the SAP System Landscape

164 Lesson: Performing an Upgrade Analysis

171 Lesson: Evaluating the Upgrade of a 3-System Landscape

181 Lesson: Identifying the Landscape for Activation of Business

Functions

187 Unit 12: Business Function Activation

188 Lesson: Assessing Business Functions

197 Lesson: Using Business Function Prediction (BFP)

201 Lesson: Analyzing the Transport of Business Functions

203 Unit 13: Unicode Conversion

204 Lesson: Using Unicode

210 Lesson: Performing a Unicode Conversion

214 Lesson: Assessing a Combined Upgrade and Unicode Conversion

223 Unit 14: Follow-Up Activities

224 Lesson: Performing Post-Update/Upgrade Steps

(9)

233 234 238 243 248 253 260

Unit 15: Usage of Tools and Services

Lesson: Choosing the Appropriate Update/Upgrade Tools Lesson: Identifying the Tools Supporting Updates/Upgrades Lesson: Identifying Technical Update/Upgrade Implementation Tools

Lesson: Identifying Change Management Tools Lesson: Identifying Test Tools

Lesson: Identifying Additional Upgrade Information Sources and Services

(10)
(11)

Course Overview

TARGET AUDIENCE

This course is intended for the following audiences:

• Program/Project Manager

• System Administrator

• Technology Consultant

(12)
(13)

Lesson 1

Introduction to SAP System

Architecture

Describing the Architecture of an SAP System

Lesson 2

Identifying the Update/Upgrade Options Available in SAP Lesson 3

Identifying Key Elements of an SAP Update/Upgrade

UNIT OBJECTIVES

• Describe the architecture of an SAP system

• Identify the update/upgrade options available in SAP

• Identify the key elements of an SAP update/upgrade

2

8

11

(14)

Unit 1

Lesson 1

Describing the Architecture of an SAP System

LESSON OVERVIEW

This lesson covers the architecture of an SAP system.

LESSON OBJECTIVES

After completing this lesson, you will be able to:

• Describe the architecture of an SAP system

SAP Business Suite, SAP ERP, and SAP NetWeaver

SAP Business Suite

SAPERP

----t-f----SAP CRM SAP ERP

SAP SCM SAP R/3/ ECC

SAP SRM SAPXSS SAPBW (SAP PLM) SAP Portal SAP Pl SAP MOM SAP NetWeaver

---Figure 1: SAP Business Suite SAP ERP. SAP NetWeaver

• The SAP Business Suite consists out of the solutions SAP ERP (Enterprise Resource

Planning), SAP CRM (Customer Relationship Management), SAP SCM (Supply Change Management). SAP SRM (Supplier Relationship Management) and SAP PLM (Product

(15)

Lesson: Describing the Architecture of an SAP System

• You can not update or upgrade (to) SAP ERP in general. You can upgrade (to) ECC or XSS and

so on.

Releases of SAP Business Suite and SAP Solutions inside

SAP Business Suite 7

SAP ERP 6.0 EHP4 SAP CRM 7.0 SAP SCM 7.0 SAP SRM 7.0

(SAP PLM 7.0)

SAP Business Suite 7i2010

SAP ERP 6.0 EHPS SAP CRM 7.0 EHP1 SAP SCM 7 .0 EHP1 SAP SRM 7 .0 EHP1

SAP Business Suite 7i2011

SAP ERP 6.0 EHP6 SAP CRM 7.0 EHP2 SAP SCM 7.0 EHP2 SAP SRM 7.0 EHP2

SAP Business Suite 7i2013

SAP ERP 6.0 EHP7 SAP CRM 7.0 EHP3 SAP SCM 7.0 EHP3 SAP SRM 7.0 EHP3

lC·��]

Figure 2: Releases of SAP Business Suite and SAP Solutions inside

• This slide shows some examples of which releases of the solutions are part of a certain release

of the SAP Business Suite.

• For example SAP Enhancement Package 7 for SAP ERP 6.0 (SAP ERP 6.0 EHP7) and others

are part of SAP Business Suite 7 Innovations 2013 (SAP Business Suite 7i2013).

SAP Releases

SAP R/3 4.6C SAP R/3 Enterprise 4.7

• (') ii: a. � (/) SAP_HR (46C) SAP R/3 4.6C SAP_APPL (46C) SAP_ABA(46C) SAP _BASIS (46C)

• List of software components is not complete Figure 3: SAP R/3 4.6C SAP R/3 Enterprise 4.7

©Copyright . All rights reserved.

SAP RJ3 Enterprise 4.7 SAP_HR (470) SAP_APPL (470) SAP _ABA (620) SAP _BASIS (620) SAP NetWeaver 2004 3

(16)

Unit 1: Introduction to SAP System Architecture

• SAP ECC was called SAP R/3 in older releases.

• This slide shows - as an example - the release of the software components of an SAP R/3 4.6C

and an SAP R/3 Enterprise 4.7.

• SAP _ABA 620 and SAP _BASIS 620 are part of SAP NetWeaver 2004.

SAP ECC 6.0 SAP ECC 6.04

• 0 0 w CL � (/) SAP_HR (600) SAP ERP 6.0 SAP_APPL (600) SAP _ABA (700) SAP _BASIS (700) SAP NetWeaver 7.0

• List of software components is not complete

Figure 4: SAP ECC 6.0 SAP ECC 6 04

• u u w CL � (/)

SAP ERP 6.0 EHP4

-SAP_HR (604) SAP_APPL (604) SAP _ABA (701) SAP _BASIS (701) SAP NetWeaver 7.0 EHP1

• This slide shows - as an example - the release of the software components of an SAP ECC 6.0

and an SAP ECC 6.04.

• SAP ECC 6.04 is part of SAP Enhancement Package 4 for SAP ERP 6.0 (SAP ERP 6.0 EHP4).

• SAP _ABA 701 and SAP _BASIS 701 are part of SAP Enhancement Package 1 for SAP

NetWeaver 7.0 (SAP NetWeaver 7.0 EH Pl).

• SAP Enhancement Package 4 for SAP ERP 6.0 is part of SAP Business Suite 7 (BS7).

(17)

• () () w CL 4'. (j) SAP ERP 6.0 EH

EA-HR (606) SAP_HR (604) EA-APPL (606) IS-OIL (606) S('P_APPL (606) SAP _ABA (731) SAP_ BAS IS (731)

- - - -

--SAP NetWeaver 7.0 EHP3

.. List of softv·tare components is not complete

Figure 5: SAP ECC 6.06 and SAP ECC 6 07

• () () w CL 4'. (j)

Lesson: Describing the Architecture of an SAP System

SAP ERP 6.0 EHP EA-HR (607) SAP_HR (604) IS-OIL (617) SAP_APPL (617) SAP_ ABA (7 40)

• This slide shows - as an example - the release of the software components SAP ECC 6.06 and

SAP ECC 6.07.

• SAP ECC 6.07 is part of SAP Enhancement Package 7 for SAP ERP 6.0 (SAP ERP 6.0 EHP7).

• SAP _ABA 740 and SAP _BASIS 740 are part of SAP NetWeaver 7.4.

• SAP Enhancement Package 7 for SAP ERP 6.0 is part of SAP Business Suite 7 Innovations

2013 (BS7i2013).

Upgrade versus Update

SAP R/3 4.6C I SAP R/34.7 ---___

__!

_ _ _ ���-��-�-�·�--- --- ---1 SAP ECC6.0 I SAP ECC 6.04 SAP ECC 6.05 SAP ECC 6.06 SAP ECC 6.07

Figure 6: Upgrade versus Update

•••

Upgrade with SAP

Enhancement Package =Upgrade

...

)

'Install SAP Enhancement Package' =Update

• To perform an upgrade with SAP Enhancement Package is called an upgrade.

(18)

Unit 1: Introduction to SAP System Architecture

• To install parts of an SAP Enhancement Package is called an update.

• When changing the release from SAP ECC 5.0 and below to an up to date release this is

considered as an upgrade.

• When changing the release from SAP ECC 6.0 and above to an up to date release this is

considered as an update.

• Updates and upgrades are almost the same from a technical point of view. But there are

differences in the associated project.

Consolidation of AS ABAP 7.03 and AS ABAP 7.3

SAP ERP 6.0 EHP SAP Ne!Weaver 7.3 EHP

---...-· -

-SAP _ASA (731)

ldentic SAP _ASA (731)

SAP _BASIS (731)

....:

' SAP _BASIS (731)

SAP Ne!Weaver 7.0 EHP3

t

Figure 7: Consolidation of AS ABAP 7 03 and AS ABAP 7.3

SAP NetWeaver 7.3

EHP1

t

• SAP Enhancement Package 3 for SAP NetWeaver 7.0 (SAP NetWeaver 7.0 EHP3) and SAP

Enhancement Package 1 for SAP NetWeaver 7.3 (SAP NetWeaver 7.3 EH Pl) both contain (besides many more) the software components SAP _ABA 7.31 and SAP _BASIS 7.31.

• For example the software components SAP _ABA 7.31 and SAP _BASIS 7.31 of an SAP ECC

system are considered to be part of SAP NetWeaver 7.0 EHP3. the software components SAP _ABA 7.31 and SAP _BASIS 7.31 of an SAP BW system are considered to be part of SAP

NetWeaver 7.3 EHPl.

• There are technical differences between SAP NetWeaver 7.0 EHP3 and SAP NetWeaver 7.3

EHPl based AS ABAP systems - not shown on this slide. For example there are small

differences in the default architecture of the enqueue process and message server ore the existence of a start profile.

(19)

Lesson: Describing the Architecture of an SAP System

SAP NetWeaver 7.0 EHP3

ASABAP

based SAP systems

7.31

SAP NetWeaver 7.3 EHP1

'

* no new installations of dual stack systems possible for SAP Business Suite applications!

Figure 8: SAP NetWeaver 7.0 EHP3 versus SAP NetWeaver 7.3 EHPl

• SAP Enhancement Package 3 for SAP NetWeaver 7.0 (SAP NetWeaver 7.0 EHP3) and SAP

Enhancement Package 1 for SAP NetWeaver 7.3 (SAP NetWeaver 7.3 EH Pl) both contain (besides many more) the software components SAP _ABA 7.31 and SAP _BASIS 7.31 of an AS ABAP system.

• But they contain different software components of AS Java systems!

• Remember that new installations of AS ABAP +Java systems (dual stack systems) are not

possible any longer for any SAP Business Suite systems. LESSON SUMMARY

You should now be able to:

• Describe the architecture of an SAP system

©Copyright . All rights reserved.

(20)

Unit 1

Lesson 2

Identifying the Update/Upgrade Options

Available in SAP

LESSON OVERVIEW

This lesson covers the update/upgrade options available in SAP. LESSON OBJECTIVES

After completing this lesson, you will be able to:

• Identify the update/upgrade options available in SAP

Installation and Activation of SAP Enhancement Packages

Example: SAP Enhancement Package 7 Installation and Activation

EA-HR (600) SAP HR

{600)

Start release 1 l11stallation of EHP components with regular maintenance

"""''""'"

EA-APPL

IS.O

IL

EA"."HR

I

:�::;�"'""':;:�IL

(600) (600) l (607)

. :

(600) (600)

c:>

SAP _APPL (900)

W t:��RJ

SAP _APPL (600)

I - """ -SAP ABA (740) 2. Activation of business functions Bnhe!� "1.rcibrr 'Fr.f'lf)'(':I'! !rtr.u:ll�n ccn:_"l� EA-APPL IS-OIL (600) (600) SAP HR (664) SAP _APPL (600) SAP ABA (740)

SAP BASIS (700)

SAP BASIS (740) SAP BASIS (7401

Selective, component-wise installation: With SAP enhancement packages you can selectively update software components. Matching combinations of software components, as well as Pl/Portal/SW-content and Java software components are grouped by Technical Usages.

As the number of software components are limited, e.g. a separated

installation of logistics and financials (both are located in the core software component SAP _APPL/EA-APPL) is not possible.

Strict separation of technical installation and the implementation of the new functionality: Explicit activation separately for each Business Function (with SAP Enhancement Package 7 for SAP ERP 6.0: -1000 Business

Functions).

However, only SAP ECC, SAP CRM Server, SAP SCM Server and SAP SRM Server are switchable.

(21)

Lesson: Identifying the Update/Upgrade Options Available in SAP

separate installation of logistics and financials (both are located in the core software component SAP _APPL/EA-APPL) is not possible.

• Step 2: Strict separation of technical installation and the implementation of the new

functionality: Explicit activation separately for each Business Function

Hint:

However, only SAP ECC, SAP CRM Server, SAP SCM Server, and SAP SRM Server are switchable.

Switch Framework Enables Optional Activation of Business Functions

With the Switch Framework it is possible to control the activation of SAP ERP objects.

Activating a Business Function triggers switches.

The switch controls whether the switch-controlled code is executed or not at runtime.

The Switch Framework is a proven concept (already used to retrofit Industry Solutions in ERP 6.0).

Switch Framework

Fundament: Enhancement Framework is the solution of SAP NetWeaver 7.0 to

allow adaptations of development objects without touching them.

All enhancements offered by Enhancement Framework

can be switched by the Switch Framework.

All reports, includes, classes, function modules, and Web Dynpro ABAP Uls can be changed and enhanced using the Enhancement Framework.

The new BAdl is also integrated in the Enhancement Framework.

Figure 10: Switch Framework Enables Optional Activation of Business Functions

• With the Switch Framework it is possible to control the activation of SAP ERP objects.

• Activating a Business Function triggers switches.

• The switch controls whether the switch-controlled code is executed or not at runtime.

• The Switch Framework is a proven concept (already used to retrofit Industry Solutions in ERP

6.0).

• Fundament: Enhancement Framework is the solution of SAP NetWeaver 7.0 to allow

adaptations of development objects without touching them.

• All enhancements offered by Enhancement Framework can be switched by the Switch

Framework.

• All reports, includes, classes, function modules, and Web Dynpro ABAP Uls can be changed

and enhanced using the Enhancement Framework.

• The new BAdl is also integrated in the Enhancement Framework.

©Copyright . All rights reserved.

(22)

Unit 1: Introduction to SAP System Architecture

LESSON SUMMARY

You should now be able to:

(23)

Unit 1

Lesson 3

Identifying Key Elements of an SAP Update/

Upgrade

LESSON OVERVIEW

This lesson covers the key elements of an SAP update/upgrade. LESSON OBJECTIVES

After completing this lesson, you will be able to:

• Identify the key elements of an SAP update/upgrade

Update/Upgrade as a Project --CIO/Busi Challc-• Stretched resot.rees • Global challenges • Complex system landscape

• No margin for 1.111>lanned downtime

• Business needs

changing constantly

• New technologies

• Shrinking budget

Figure 11: Upgrade Project: Key Questions

0 f'l,.al Prtpei�cttian

0

Will the upgrade g o live on time?

Will the solution still do

what we design ed it to? How do we minimize the

disruption to business?

Have we identified all

the potential risks?

Will the system perform at optimal levels?

• Ensure a smooth system landscape transition

• Plan your IT infrastructure

• Manage parallel changes

• Adapt applications

© Copyright . All rights reserved.

b

�:::.:..

Go Uve & Support nges Business process complexity System configuration Integration Modin cations Competency gaps Interfaces Data inconsistency System performance 11

(24)

Unit 1: Introduction to SAP System Architecture

• Ensure business continuity

• Perform data operations • Minimize business downtime

Upgrade project started

Upgrado

Olscovory Upgrade Implementation

Mlnlmb:e costs

D&fille busintss and

l

IT requirements

Oet111e

strategy and risks of Upgrade Project

Upgrade Roadmal!

"'========:>:

Document current

))

solution and set-up

project

Spe.:ify implementation scope and solution

Olldjustmeon1 neeods

lmplement and �dju$t solution

Figure 12: Upgrade as a Project- Plan, Build, Run

Perform integration Mid $-y$fem te,ts and plan cutover

Upgrade project completed

Execute production system Upgrade &

support

• The Upgrade project does not start with the kick-off. Before an upgrade project some tasks has to be done for defining business and IT requirements, define an upgrade strategy and create a business case for the upgrade project during discovery and evaluation phase before the project starts itself.

• Three different phases of an upgrade project:

• Plan, Build, Run.

(25)

Lesson: Identifying Key Elements of an SAP Update/Upgrade

Update/Upgrade Complexity

Number of modified objects

Number & type of ext. interfaces

Source release

OS I DB migration requirements

Number of codepages

Figure 13: Complexity Drivers

Business related levers Impact: medium to high

Upgrade project complexity

drivers

IT related levers Impact: medium to high

Type of Upgrade (Technical/functional)

\ I

Code freeze strategy ] Number of Add-ons I Industry Solutions \ :J Testing requirements Required downtime

• An upgrade project is more or less complex, depending on several drivers. There are IT related and business related complexity drivers.

-

NWPI

I

NWEP Release Depend end Topics • Upgrade: Industry Solutions • Compatibility: Add-On$ • Conversion: MDMP ... 3-10h ... 4-5 mths • Transition: Mobile Scenarios • Infrastructure: Jav11 Deplo)'ment •> CRM 2007: UI Migration •> CRM 2005: VMC d•ploymont ... 5-12h' 't'2-6h T2-8h T1-6h 't'3-4 mths T3-4mths T2-3 mths T1-3 mths • Downtime: • Business LlveCache do .. vntlme: Ramp do••r'nl • Compalibility: ramp up of LC Build, interfaces com routine$, SPs • Business downtime: Higher requirements •> 8'1V7.0: Web Reponing deployment

l.egend: effort/dura11on Is 't' lower than )I> comparable to A higher than ECC reference

Figure 14: Comparison of Upgrade Experiences in Business Suite and NetWeaver

'f'1-6h

T1-3 mths

• SAP Business Suite and SAP NetWeaver products are compared with average SAP ECC

Upgrade project.

©Copyright . All rights reserved. 13

(26)

Unit 1: Introduction to SAP System Architecture

• The average SAP ECC upgrade project is defined based on figures from SAP Upgrade

Experience Database from Nov 2008 (-290 entries) for upgrades to SAP ECC 6.0.

• Comments:

* SCM downtime: 2-6h SCM Server+ 3-6h Live Cache export/import.

Update/Upgrade Delivery

EHP Facts

• Only one SAP enhancement

package level per system

One application system can only consist of one SAP enhancement package level (e.g. SAP

Enhancement Package 5 for SAP ERP 6.0 li.Q.C SAP Enhancement Package 6 for SAP ERP 6.0). Hence installed SAP enhancement package components have to be updated with every future SAP enhancement package implementation.

• Industry Solutions

Customers v1ho have activated an industry business function set have to include the corresponding SAP enhancement package industry software component during installation.

• EHP Installation and

functional activation Is partially non-reversible

Technical Delivery • SAP enhancement packages

are •cumulative•

When installing the la.test SAP

enhancement package you will automatically get all functionalfy delivered with previous ones.

Technically the SAP enhancement

package installation delivers only changed objects to your system (delta shipment).

Project Perspective

• ModHlcatlon Adjustment

During installation of SAP

enhancement packages modifications

must be adjusted- even if no business function has been activated.

• Regression Test required

The Installation of an SAP

enhancement package requires a full regression test - even if no business function has been activated.

• Effort Estimation

Most customers say that the Installation effort Is a bit hlgherwlth SAP enhancement packages (without activating business functions) compared to pure SAP Support Package updates.

Figure 15: Things You Should Know Before Installing SAP Enhancement Packages

Facts you should know about SAP enhancement packages:

• Only one SAP enhancement package level per system is possible.

• Activated industry solutions have to be included in the update.

• SAP enhancement packages are 'cumulative'.

• Modification Adjustment is necessary even if no business function has been activated.

• A full regression test is required in any case.

• The effort of an update is higher than a pure SAP Support Packages update, but less than an

(27)

Lesson: Identifying Key Elements of an SAP Update/Upgrade

To manifest the long-term predictability of the Business Suite and in support of the Innovation Strategy and Roadmap the standard maintenance will be extended

SAP extends mainstream maintenance for the Business Suite core applications through December 2020 J EHP4 IHP3 P2 HPf SAP NotWoavar 7.x • • • • • • • • • • • • • • • • 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 20°17 2018 2019 2020

1The SAP Busineis Suite 7 ilciucles ttte core application$ (SAP ERP 6.0 EHP4, SAP PLM 7 .0, SAP CRM 7 .0, SAP SCM 7.0, SAP SRM 7 .Oj,

supplementary applications and industry applications.

Figure 16: Long Term Predictability: Maintenance Extension for SAP Business Suite

• To manifest the long-term predictability of the Business Suite and in support of the Innovation

Strategy and Roadmap the standard maintenance will be extended.

• SAP extends mainstream maintenance for the Business Suite core applications through

December 2020.

• For details check the Product Availability Matrix at service.sap.com/pam.

Update/Upgrade Approaches

Upgrade Update

--•

up to 50 o/o less business downtime

--+

up to 62 °/o less project run time

�-

---..

.

up to 58 °/o shortend prnject phases

More details at: http://service.sap.com/ehp-db

• St.<olt<:fld P'V.�!: tl\S;es 1.p :� �" iYe:a-a: cosed b1..:0:1 ·n both ··n-r :>10 I �.. "''· r�luc�11 • •)f 810 3 .. �.;.d,

:r;pit\1J';t 01:.1•Y.ti:ll ff�.n.:. to 2 ... $-;, �o t'IE< ard HP;<>'t lr«TI 2:: ''r.\lff<

· J,,•;1? n.: p,�·� 1::-J'•J'.tJ!; h.·, �;.p F?.'.)-1�:'1•1 �A.PF"(:�: f. f, Sl)r'u Upgrade Exptrieru:;cOat:tbasc

• :!a;� O:' l' Jedr.te� rr�r) SAP ECCt.: :t SAPECC: 0� 13 04 ! O:; !l)Uro,) Enhaneetr1ent Packa9• Exp•1lenceDatabat•

Figure 17: Upgrade versus Update

• An update causes less business downtime than an upgrade - but the same technical

downtime.

(28)

Unit 1: Introduction to SAP System Architecture

• The project run time of an update project is much shorter than the project run time of an

upgrade project.

• Project phases of an update project are shorter than of an upgrade project.

Upgrades are large projects with progressive scope

Affecting the whole enterprise Demanding in-depth knowledge of Business models • Processes Application landscapes • Application modification

• Requiring strict planning

and precise timing

Technical Upgrade Fast • Low costs and manageable impact • Protect investment New Functionality

v

Take your time

D

Generate value as you go Service-oriented architecture

v

Discover, prepare and get even more value

Think BIG and start SMALL!

Figure 18: Possible Upgrade Approaches Think Big And Start Small

• Technical Upgrade: Reduction of Modifications

Project phases of an update project are shorter than of an upgrade project.

Replace modification with standard functionality: Up to 50°/o of all modifications

Technical and functional optimization: Archiving, master date clean-up, interface optimization

• Functional: Focus

Modernization of the Core SAP ERP. Stabilization of the basis Individualization of the user interface

• Strategic: Focus

Standardization

Harmonization Consolidation

(29)

Lesson: Identifying Key Elements of an SAP Update/Upgrade

Website Name URL

Business Suite Innovations 2011 SAP Find Innovations

(central entry page for innovation related content)

SAP Roadmaps

Enhancement Package Info Center

Business Function Prediction Upgrade Info Center

Best practises for Application Life-Cycle Management

Solution Browser Enterprise Support

-7 Services Offerings

Figure 19: Important Links

http:l/service.sap.com/innovations2011 https:l/service.sap.comlfindinnovation http:l/service.sap.com/roadmap ERP: http:l/service.sap.com/ero-ehp CRM: http:l/service.sap.com/crm-ehp SCM: http:l/service.sap.com/scm-ehp SRM: http:l/service.sap.com/srm-ehp PLM: http://service.sap.com/plm-ehp http:l/service.sap.com/BFP http:l/service.sap.com/upgrade http:l/service.sap.com/alm http:l/sapsolutionbrowser.com http:l/service.sap.com/enterprisesupport SAP Enterorise Support Services

How can I identify the added value from SAP Business Suite 7i2011? How can I identify the added value from my

investment?

Value Insight Session: http://service.sap. comMs

Where do I get the know how I need?

Where do I find information about the SAP Application Life­ Cycle Management?

What are the advantages of SAP Enterprise Support and

which services can I benefit from?

Who does SAP help to support me by evaluating the innovations delivered by the newest SAP enhancement packages?

How can I implement and activate new business functions with

SAP Solution Manager?

Where do I find delta training?

I

Figure 20: Service Marketplace LESSON SUMMARY

You should now be able to:

• Identify the key elements of an SAP update/upgrade

©Copyright . All rights reserved.

Online Knowledge Products; http://service.sap .com/OKP http://service.sap.com/aim

SAP Enterprise Support and Services;

bltp"//servjce.sap com/enteronsesupport

SAP Enterprise Support Services

SAP Accelerated Innovation Enablement:

http://service.sap.com/aie

Enhancement Package Information

Center (tab "Activate")

http://service.sap.com/erp-ehp

SAP Education Curriculum:

http://www.sap.com/services/education/c atalog/ero/curriculum.epx?context=%5b %5b0elta EHP%5d%5d%7c

(30)
(31)

SAP Target Release Selection

Lesson 1

Identifying the SAP Solution Manager Maintenance Optimizer

Lesson 2

Performing the Maintenance Transaction

UNIT OBJECTIVES

• Identify the functionality of the SAP Solution Manager Maintenance Optimizer

• Perform the maintenance transaction

© Copyright . All rights reserved.

20

24

(32)

Unit 2

Lesson 1

Identifying the SAP Solution Manager

Maintenance Optimizer

LESSON OVERVIEW

This lesson covers the SAP Solution Manager maintenance optimizer.

LESSON OBJECTIVES

After completing this lesson, you will be able to:

• Identify the functionality of the SAP Solution Manager Maintenance Optimizer

Placement in Entire Process: Maintenance Optimizer

a

Solutl� Monag"' "''" to•got �'"''

Needed Technical Usages of SAP Enhancement Package 6 for SAP

-ERP 6.0 and corresponding SAP Support Packages

2

3

SAP Notes: pre Update/Upgrade steps -See Update Guide

Upgrade Guide: pre Update/Upgrade steps

ASU Toolbox: pre Update/Upgrade steps -SAP Note 1000009

SUM: preparation steps

SUM: resolving negative checks -Roadmap steps up to 5.4

SUM: Update/Upgrade -Roadmap steps from 5.5

SAP Notes: �ost Update/Upgrade steps -Se U dat Guid

Upgrade Guide: post Update/Upgrade steps e P e e

ASU Toolbox: post Update/Upgrade steps -SAP Note 1000009

(33)

Lesson: Identifying the SAP Solution Manager Maintenance Optimizer

Stack XML File for Update/Upgrade

1 Prepare SAP

Solution Manager

system

SLD

If SLD and LMDB/SMSY

are configured correctly,

Maintenance Optimizer

'Nill calculate the

packages for every SAP

system that is part of the

solution 2 Calculate software packages and generate configuration file with Maintenance Optimizer 3 Update/upgrade au

SAP systems that

are part of the

maintenance transaction SUM SAINT SAP ERP ABAP Package �-. Configuraiion File r-­ (stack XML) SUM JSPM SAP ERP Pon al Java SUM SAJITT SAP ERP ABAP Sample SAP system landscape

Figure 22: Overview: Main Steps of SAP Enhancement Package Installation Procedure

SUM JSPM

SAP ERP

Pl

Java

• The SAP Solution Manager creates a customer specific stack XML which contains the

information about the queue of selected software components and SAP Support Packages.

• Now the installation tools use this information to bring the specific system to a well-defined and consistent system state. The tool to use for installation depends on the type of software component:

• ABAP and Java software components are updated/upgraded using the SUM.

• Portal Content is installed using the JSPM tool

• Pl Content is usually uploaded from within the Integration Repository.

• BW Content is applied as Add-on or SAP Support Package.

• Alternatively ABAP components can be installed using the SAINT tool and Java software

components can be are installed using the JSPM tool.

• Please note that there might be limitations.

(34)

Unit 2: SAP Target Release Selection

re Update ., .. 3.wd .sap,.<orp 0 ed as Adm1 - rat.or

SOFfWARE UPDATE MANAGER

1---121---; 3 �----1

Welcome Specify Credenli�s Select T•uet

Select Target System Version

Select the 1arget version definition for 'fOur�em

Stack configuration file (XM.l)

Needed components of

update/upgrade are defined within SAP Solution

Manager system

® Select this option when you have prep a.red a staat using the r.tainlenanee Optimizer. Ensure that all ard\ives and the stack oonflguration file itself are slofed in the same download dire dory .

Manuauy prepared direetory

O Seltct this option When you have manually pres:iared a nat directory containing the component updates and patches )'OU want to 3J)'Ply

to the system.

S1aekftlt or Oilectoty

Figure 23: Request for Stack Configuration File

How is this stack

XML file created?

A properly installed SAP Solution Manager system is required to generate the xml and txt.

x x

SiO M!'/fnlfl te.C0.2009 1111·0.: �I

c:;:en M!'ll!l"1 l(;.c)(;;:(l(l9 11.z1·0; �1.FO_l0"10..lC<.9HO:.nG•

l'llf ...,,,.,.,Miii llUJll200\I 11 :t1 C)j $WJOr.M._\.l�_·.1111NIJ6:!$'lll('fllJtl:ll bl

Copy the xml file, so it can be accessed by SUM

$0PYWAftE UPll&n MANAGER

• a � m • "·"'"'... : ... �(· .. - i;,,...,1_ .: ... ,,.., ,.,..,.;,,... an .. � .. S.lt11d 1 ofJ!J'M Sy\SlOl'lfVvn: 'fl ,-... -... ....;�·i<iii-, -·-···--- --··· -,._,_ _ _,ltt'""••» .. •1¥.!"'"""'"""'-(--•�lol..-.-nJll'lo� L.���.��!���1'!!.�····---···---·· --_MJ\> __ .,...

0_.. __ ftttM.._., ... ,,.,,, ... O>tf, (\ll a..•c.. _,...�u·-... ,� .. t ,:a.o .... •-•• nll' ... ,..._

Figure 24: Generation of Stack Configuration File: Copy xml File for SAPehpi

(35)

:kr"''>"'1 -:::.

� • Ila • c ,.. or t•�· y.ey .. lt(ts" @ .. Q. 0

Maintenance Optimizer Transaction B000000002

..

-o ....

Lesson: Identifying the SAP Solution Manager Maintenance Optimizer

p.

... ,_,.,

• 'Maintenance'

stands for 'apply SAP Support Packages'

• 'Enhancement Package installation'

stands for 'Update'

�-

-• 'Upgrade with Enhancement Package Installation' stand for 'Upgrade'

Figure 25: Start Maintenance Transaction in Solution Manager Workcenter "Change Management"

The xml and txt files are created in the EPS\in.nCopy subdirectory of the Solution Manager's transport directory.

LESSON SUMMARY

You should now be able to:

• Identify the functionality of the SAP Solution Manager Maintenance Optimizer

©Copyright. All rights reserved. 23

(36)

Unit 2

Lesson 2

Performing the Maintenance Transaction

LESSON OVERVIEW

This lesson covers the maintenace transaction.

LESSON OBJECTIVES

After completing this lesson, you will be able to:

• Perform the maintenance transaction

Technical Usages

·-·--� ... " »

-- ·-- ... ""'""'- ... � ... :.

1io.t1 1(1oh.oo...ll �· ;o."1 r,,....<J

,,,,,. ... �--�� � ---'----����-''""'to' ... r .. ..,_,. ___ • �Bi!-,....-"' •L._..:.. T....,_ .. ,...._ • rn•ma: ··• .. ""¥ifW!ts.." ;;;..1 ... ""' .... ... .. ... ...,.,.. ., r,i,,_ ....,.."""'� •0.W­ ,�-· ··--... ... ·- -

--• Select the needed/used

Technical Usages .. � l,; u u ---- -- .. --· --- __ .. ---· t'""' •"•W(T'J(._ • ,_ ___ . U!..''"'..1.-.J.�'-?'l!I!"'!. -� ...,+••!i.,,,.,_,, __ .,.,,... .. _ .... .,.-o -·"'-• - r _ ... '"llt-1,..h• c &Jila ... @� ... ;- --- ---... (e -'W'M"t• ... ... -... ., 0 -···- ._., ___ ,, ... , ...., ... ,,.._. to.c....;._, -.. - l&oaJ� ·� --(/ •Mv • P"l h--.. ""'-s.�• ... ., ___ _ ·­ ·-

-• Technical Usages may be --+--t11�:� =.

�==-@' - ... _ ·-... _ . .,.,, ·�-.-... --.,.� c� ...- �-·-�-Ci � , __ .,. ra-. ,.._ ....;.. """"' ... _._ f1 �� �•-<•_,..VA-loo ··-• selectable

• not selectable· because the

needed SAP system is not part of this maintenance transaction

• pre-selected

Figure 26: Selecting the Technical Usages

Selective Approach

·Ii'� -- •w

--r toolo1-..w ·--a

, ...,.� • to-� ·-<.---«·• ·--@-t ., • * rt ·--":"--' .. �nl._, ?_ .... -P f.w.W-ca t;ll )<O- _._ ...,. ,.... ... wi� � $«-•!W..I ·-" ... �-c� _11o ... -" ... _,_ t.wJr� , ... -� - ... ,_ .... __ ,,._).,_ ... . .,. •... _ f#--· �-·�

(37)

Lesson: Performing the Maintenance Transaction

Selective Approach

• Custom er's IT strategy for update/upgrade:

• Update only what is needed for activating a business function that the business decided to use.

• Use synergy effects with your maintenance cycles to av oid a separate regre ssi on test.

• Proceeding: Update.exactly those technical usages that are nee.ded to activate the business functions that

are in scope for your project.

• AdVantages: Minimize risk for this implementation project

· Less potential adjustment efforts as less software components are touched Broad Approach

Customer's IT strate gy for update/upgrade :

Whith Tedi ,.ic•I Us.ses sliouldt i•dudefor die SO.P ECC Sfl'.tem 1 The bu siftes.s. espert:s. can't tell whid. Bu siness

F1111dio11(s) d.C¥ w•n'tto use letero• ..

• Proacti11ely add relevant scope of new functions to be in best shape to activate

further business functions as soon as these are requested by the business.

• Use synergy effects with your maintenance cycles to avoid a separate regression test.

• Proceeding for SAP ECC: Flat installation approach

Technical lnsJallatlon Look at the technical usages offered and exclude the ones that you do not use on this SAP system.

For the remaining technical usages, check if the enhancements inside potentially add value for you

If yes, also choose these technical usages.

• Advantages: Minimize initial effort for analyzing new functions

• In best shape for new implementations.

Figure 27: Two Alternative Installation Approaches

• Selective approach:

-Evaluate content of SAP enhancement packages in advance (service.sap.com/erp-ehp) and select required functionality

-Select required SAP Support Package Stack and select all required parts (technical usages) of the SAP enhancement package

• Broad approach:

Exclude all technical usages that reflect topics that you do not use in your system.

For the remaining technical usages, briefly verify if these include interesting capabilities for your end-users. To find out which Business Functions are part of a Technical Usage read

SAP note 1324838 -there you will find the respective mapping.

• Remember: All Installed SAP enhancement package components have to be updated with

every future SAP enhancement package installation. Potentially additional adjustment effort and downtime must be considered.

• Check if any add-ons are installed and if these are released for the new release.

• For customers with an activate industry business function set: The corresponding industry

component must be included into the update/upgrade.

• Ongoing innovation as part of maintenance strategy: Update all relevant software components

together with SAP Support Packages.

• Demand driven Innovation: Activate Business Function when required.

All Installed SAP enhancement package components have to be updated with every future SAP enhancement package installation. Consider potential additional adjustment effort and

downtime.

©Copyright. All rights reserved.

25

(38)

Unit 2: SAP Target Release Selection

Business Function

A 'Business Function' is

the activatable unit

within the SAP ECC

Server

Business Functlen 1

Real Estate Managemen� Technical Name: •-

"""-RE_GEN_Cl_ 1 Buelness Funotlen -2 New General ledger Accounting Technical Name: FIN_GL_Cl_1 Busi11ess Func:ti•n ·3 Lean Manufacturing Technical Name: LOG _PP _LMAN ...

Figure 28: Mapping Process (Example)

Technical Usage

A 'Technical Usage· groups software

components which must be installed together.

Media

ABAP Product

lnstan�e Media

nancials

ABA P Product Instance Leasmg/Col'l(rae-t AIR & A/P

HCM Self Services

ASAP Product Instance

Hi.man Capital r·1lanagement

JAVA Pro dl..lct Instance

SAP XSS <Self SeMces)

Main Instances & Software Components

SAP l!CC S.rvor

BF , EA·APPL 61 '(

B� �p _APPL 617

Central 6Pl>lic�lion EA·HR607

SAP_HRro4

ERECRUIT S.00

SAP note 1818596-SAP Enhancement Package 7 for SAP ERP 6.0: Required SWC contains the following attachments:

BF· TU_mapplng_EHP _2· 7 _f_ERP _6_ V1 .pdf Business functions • Technical usage • Product instances TU.SF _mapplng_EHP _2• 7_f_ERP_6_V1.pdf Technical usages • Business functions • Product instances Mapping-Inst-TU· SWC_EHP7_V2.pdf Product instances • Technical usage • Software components

Figure 29: Relation between Technical Usages Business Functions and SWC's

(39)

Lesson: Performing the Maintenance Transaction

SAP Support Packages

SAP ERP 6.0 EHP 6 (SWC version 606)

l

Equlvalent (same correction level}, tlm&-synchronlzed SAP SPs

SAP ERP6.0

(SWC version 600) SPS 9 SPS 10 SPS 11 SPS 12 SPS 13 SPS 14 SPS 15 SPS 16 SPS 17 SPS 18 SPS 19 SPS 20

Equivalent SAP Support Packages time

• Are time-synchronized SAP SPs for different versions of one software component (SWC)

• Contain identical corrections for capabilities that both versions have in common

• Differ only with respect to corrections for new capabilities (provided by the higher SWC version}

Example:600SPS 20: 602SPS10: 603 SPS 9: 604SPS10: 605SPS 6

• Also see SAP note 1064635

Figure 30: Equivalent SAP Support Packages

• Update/upgrade means bringing a subset of software component versions (SWCs) to a higher

version, e.g. from 600 to 606. With update/upgrade you initially reach a certain correction level. This corresponds ('is equivalent') to an SAP SP Stack level of the underlying SAP ECC

6.0. The only efficient way to install the eventually missing SAP SP stacks is to bind them to the update/upgrade. By doing that you should always go to the latest available SAP Support Package Stack in one step.

• As a consequence customers have to adjust possible modifications and test the application

after the installation, however this was the same with the pure SAP Support Package Stack installation. Efforts should be expected to be comparable or slightly higher.

• Please note whenever a customer patches his SAP ECC system. it is always recommended to

use the SAP Solution Manager Maintenance Optimizer. This tool automatically identifies the relevant installation files (SAP Support Packages) according to the current SAP system status and thereby ensures a consistent SP stack level.

LESSON SUMMARY

You should now be able to:

• Perform the maintenance transaction

©Copyright. All rights reserved.

27

(40)
(41)

Update/Upgrade Preparation

Lesson 1

Performing Pre-Upgrade Steps

Exercise 1: Perform Pre-Upgrade Steps

UNIT OBJECTIVES

• Perform pre-upgrade steps from SAP Notes

• Perform pre-upgrade steps from topics in the Update/Upgrade Guide

• Perform pre-upgrade steps using the ASU Toolbox

© Copyright . All rights reserved.

30 35

(42)

Unit 3

Lesson 1

Performing Pre-Upgrade Steps

LESSON OVERVIEW

This lesson covers the pre-upgrade steps.

LESSON OBJECTIVES

After completing this lesson, you will be able to:

• Perform pre-upgrade steps from SAP Notes

• Perform pre-upgrade steps from topics in the Update/Upgrade Guide

• Perform pre-upgrade steps using the ASU Toolbox

The Pre-Upgrade Step within the Upgrade Process

The Five Major Technical Steps

1 Solution Manager: select target release

Needed Technical Usages of SAP

Enhancement Package 6 for SAP

-ERP 6.0 and corresponding SAP

Support Packages

CD Upgrade Guide: pre Update/Upgrade steps

8

SAP Notes: pre Update/Upgrade steps -See Update Guide

:S

ASU Toolbox: pre Update/Upgrade steps - SAP Note 1000009

a.

::::>

3 SUM: preparation steps

SUM: resolving negative checks -Roadmap steps up to 5.4

SUM: Update/Upgrade -Roadmap steps from 5.5

SAP Notes: post Update/Upgrade steps - . Upgrade Guide: post Update/Upgrade steps See Update Guide

(43)

Lesson: Performing Pre-Upgrade Steps

Pre-Upgrade Steps from SAP Notes

1.3.2 SAP Notes • Update Guide

...

T op•l'JMf<' 1111d pNl\l<nl rhr wpd.11\•of �0111 S/11':.�'Slt'lll. \OU '"llllfl'Wol'il."i\:Mmanal lill�mu1io1111 1s l1oi indudcd m 1h1�.&.�.:l111�1:1. Th.oto•nfonn�hon t:. ll\J 1l1is:r«'SAPKu1t\ tn SAr S11pp,,n l'o1u ("t:;p· 11110-rYIN.li.l;). CCll'l'lcto11>. «1mc-.:.fwhl(.h-wn1 m.n:.: U'.1ti l\'folY'-h\U'lUfl •1n1h 11\1" pt'tp.u;irion�. IJ..�i� 1hr•tni1d 5,�frl'l.Jtt L'pd.11r M;in.1:j?t1 N.:.1c. 1ht•ff" .Ul':'.(p.u11u• SAf NN�fo1 1 cl;11Jb:M'•'pr6lll' :il<' .. 0011:-;. \\ hl'I\ \OU .w111.1li' prrfonn ;he up1:l.11f'. }•HI 111.i1 .,,,,_...; 1

s.'.>l\l(' .1(1dif)(>nJI S.\.P ;-\Qr<s, Th(';(' $,\r K<>•<'S.AI� n,nnc-,i .u 1h<' 11ppr�pri.lrt

SAP Mete� to" Prepari•e Ule Up...._•

'qn 11111�1 requc�11h('. follo\\ ms.S.\f' )(at("J tn1111 SAl'S11 1

1wt1.·l°d111'l": Vt<•� ·-· ··-·�· c ... . ., W:i:a:itl�t�l�l�l!w

rcr ....-c '"'""'•�'•" Uolt Uc ��•le ol yw-•P•cif1c -l•ut.;.,., >« tll< loll_,.,, "''Cl>'

}..U' 11«1><_, t .' •••• , •.,, , ".,,, • ... ., • , , • •,. • , , . , ., •,, , •• • , • • ., �l'lot:SI

t.: r.::!:. �����i: �:: :::: ::: :::: ::: :::::: :::: ::: :::::::::;:J!!!�·

Wllctloc-r r.$., ... ... , ... , ... ::n:.111

�l'I '" ""'"lttt

�:;::Et! • Actions often refer to a

""'CU' t- '""

!:: ·� 'I ,_1.0 , ::: tn' dedicated SAP note

• Topics can depend on

1=--1 • the start release ·the operating system

·�· • the used business functions

� 1844234 ·Max.DB: ZUS.atz:infOnnatlon -SOf Symptom • I Important General Information

Vff'tlon .) ... V �fdlttl uno� 18-01.20r}. tdM Otl.boCll Symptom ""� lltl-tMOt"M"•OO .;,« (l!tll) (0 �1li'/1,15;"ffprt.:t:"�ts�fij�s G

� .. ilc.!!9>!• • II Corrections to the uide

• Ill Preparing the Update

• IV Problems During the Update Process g,� SA.P-ll\-,tU tl!��lt $;�("1H4hdt /lfXCB-$0Cllf1�(i'lt Z�:s:«.h111fo...e.uo11e11 :IO'I

lO\rflw•r" Upd,,...,. )(""•!l"r (SI..¥) o1 .. r \•o,r...ion 1.n �.._...t """�"9<' O't. V Problems After the Update

Figure 32: Steps from SAP Notes

• One major Update/Upgrade Note is listed in the Update/Upgrade Guide. The first SAP Note

refers to a second SAP Note.

• The major database-dependent Update/Upgrade Note is also listed in the Update/Upgrade

Guide.

• All three major Update/Upgrade Notes contain topics that have to be performed before and

after the Update/Upgrade.

(44)

Unit 3: Update/Upgrade Preparation

Pre-Upgrade Steps from the Update/Upgrade Guide

If SA

·-4 Preparation

th1<?>•••(chto... .. ,.. .... _,,,,�.,-.. ,., .. ,,.i-.. f"•�•..., ••'"'t .. ..,,..u,...,..1,.Nf•"'

�·" *'r-!•ot ,,. .. ,...,., ...,._ l_u,. P"'P'"' r.,...., 11p6'-.c .. 1oa. die-·�� .. m 11.., P�""n"f"''"°'"'

C'.>te(ul lfl.!'"""W. oi ... II <h< l><o:o piu ... :o«h>'1HUn: "'"""""' U'Nl'O, a t .. v•w.>o

.. •:1$<10• ... t.. """"""* ttt!"'•"""' <1< ... ;;...i '"db.doc .. _ .. ..._, ... t><dooe ... '"'

r•f'#'•�-1lu1 ••••t•01<•i•"" "1-..r"'"""" wlodi • .. 4"<�.\><J.•" •"•#ltl•MI p.W11twpecil1<.i...- -n..,u • .,.,,.,..,;,re1t,�..i.., ohc \t..1<•Go0.il(•• v..,._..,.,..,..., CO>-.lt, «cp,.n.d� j;,,,) o .. t f"""""

n..�...,, .. up.;, .. ).to...,.,�,.,,.., ... k ..,,l,.,t"'°"'°' '"' =«•=•.., .... m

,.,..,...,...,_.u, r.,, ... ..r...-.... ,...,..,.,,. ...,.,.,.,1..,.?''.r...tt.y...,:.; ... �,...vf"' .... M"''C"'·

:« 11>c<l•=.,,.-.... n: • ,,_., .. :..f!...,.¥Jr:.ro"'1'•lt>•��1

'( "" pc1&.tm ok '"""' .. 'flt' 6':01!<>"""''.,.-!"" ''" 1 ti.. AJ.,., .. .-lipd.oc \.l"""'C"'

• �WKn}t•olot,.,,..�w.o�

• ('.l..�., ... f ... ...,.. ... �

• a..u,a.� .... ,.,. ... ""�'

• l\d c-...,�n....ic ... 11,,-a.:�·"f*S.- Mo:....1Jtiw��1�-�

Wool"f•lot o,. .... ., ;��tr a.,._ .... , lt>.tlt.:!I

�l·-�1'$1 .... -i .. V,,uh./A.�-.1..,:,--�.";·� °"""""'� • \t.•"1"'1'-"'""' ... ,,..., .. 1 .... 1��Jj • c:o:..i..., .... �,� ... �·-·"" �'-�'� • i:-J.,...vosv •• 11-... � • :.ol""f""ctr'"'""''l ... ,....lJJJ."lt.!A!!J • .;.i...ci.,,-.. c--1<1""""' ,., ,lt!e.!!.J .. • C'Jt.�.wx...i....;�...i ..... ,. .... • !lrfollofilit •1:14.'Tilll rr ... -t->P:r.I • l::;:::::::.:.:r:�.:.:�. �t:;·"" �-·· ... �·-.---··-·:..:.>-�I . M.olo"f tlwp..,...., ,._., ... !_._,, ... l;;,o!!.EJ l!'.::'.:11��-�·2'::�··�-· ... � ... M--•_.,. ... __ , H .. � • .:...o--� ... ';#>I • a..c.,•a...,...n..wr•JJ..";f-"{-.. !£.!!!!!!

• Actions are explained on the

following pages of the update

guide in detail

• Topics sometimes refer to an

SAP note or to the SAP Online Documentation

I

Figure 33: Pre-Upgrade Steps in the Update/Upgrade Guide

The ASU Toolbox Update

!fZ" Note1000009-ASU TOOlbox2008

lloohll�lf!!!!'! !Tl ·- " VllQM>r. Y*IW!Ce 27.06.2014: IT!1!] I o-·•,,c1 Coatoet.e11s II t4-� v,,.._ 11 $$CR I COtO SA.flliOM: .lGOl.OOS

I ""'ii

-COMC111:. �M� I 1it•111t(.p.11, I t:k•u� I St•��� I .tiu�Nn:s I..,��

1..m1_0»0,.0lC$�.1.1 El A1111d1m.01S - llfN.,.,... L11ngu.,. (I hl••11•

!

"' ...,. "'""' '""' "' I ASH €6' 79¥ U. 2 "! ... " � " I? "" ... -II) S)Jt• .. •••

e; ., qg e0e•r.a01te tit J'>fl Ell!! $11

'

01"'91\•-"-<a.!Q:nl�o.fi"#l:J• D

Appbll()n $p«1flc llPflt'MH THll>Ox

IT]

"""

"""

'

'""'

l

"-·: s.'<i._....old .>.W <.

"W"

�I Y•ll)U•

2v

·�

bot"; a.o.i:su;r. ! . l!>.T,,:] '"'1

rf1

Gi!l-i;,1o:!!l!>.et UMn1G.VP�O:µt.>ts / .,.� .. :"i:71,,,

� .... (o>i(i .. Yl.�A".(�' inn Ol,�..ltoUI ••

--o;�,..,.,.,. .... "'ill\1>ES..-1¥ -�1. "�°"II

�Oli.��t:&1..:001�� 1'•e lft;)).�11>Sf

1;1'1J lltl.0$�ri l.>'-(tCtt'•U'OO �•l <f!;m:QU;ll

'111�1t•Jill.l'h:.t'.,,_(Ollll-W'O' lt•l "::o.ne.�11!)1

t!j

_, ,I -, ... 1 .... • I I I I =i_ "' ., 3 .

--

J

J i;:i.• •• <v.�";J;H•R..:•"'

8J

�- -,.tooJ1 .I ·1 �-IAAl>IUtM I

I

(45)

Lesson: Performing Pre-Upgrade Steps

Pre-Update Steps Using the ASU Toolbox

-•�-- ---- ----·J_• .. 0._0_ 0 e __ _

_ QMM ·��n'.'..'.:�:'...".�m �� $�•'.._ _________________________ JiizZIDllll111C:Zlillllm:l!l!llllZllllZll131111111111 �e

A$V���;A$,feR�Juii

Ou.u: ..... El &

� ...

'l· 'i'•��--»;;,;,.e-; • .. t.:!ill..,r.-_,,.::ii>o:::' ...

.. QOoli;lr:n • �-�®':l1Jic(011>»1a.'> · ���;1c-..,....tQCIG,.� · . ���lrr•vP��... , ,,, ___ ';j'jl::11 0.-w� 1 • l!f ,0 "11 \IMAA 0 O;<')ll# • 9'•���-:-0•f:lllD!'IDrm,.. a . 9'�of»llw."'""UO!o�· •'i-1�1o•n1..,.�Q11t� .,.

• f/l�,jU-.(••lCol'O'..<\tiO)

• �- """'<'r""�1uQ1i• ,..,.

·1J>-!Joy,if< 'Du Ir!)'

• ·E�t"f'e-r.1<1:botfi'!DC ""' · 'J',,,."1'04-o,,•••?ID .... ,t.,. : i==-���;1 ,:� • ���•;'1�,..,� C•loo•w • • i:--.. .. ,, ... � • 'J>W�frf�• f"-•� •l::!n1r"'-�I.\ ·�f<CS'�S:o:Jt ''"" .. .. .. • • • • .. • .. .. • .. .. .. • ·�-�u.>:-��-rf'«p (·.Q.. -11110U')•)!lt"( • '•�v.-.. · 7•..iJOr.ou l IJ. ' .. ·-1\•lt•lf' �IU'rUI 011 <)1111 • . e(Moc ... �. .. .�°"*"" liZllllllilil=:=lllll : !! �<M�W�Willt"-�.WOl$J,li.iJ>llkl.�

't(�•l!e>lt�!11¢..ot•o:-n;.e� l!tllo t:IU.W

�:ho .. �. IJl,C:OI ,_._ .. ,,�»>)) '-1»�1• "''*'""" � .. � � 4'_t'GISI' '·'llt•O ,_, '4�tw l\�"" '"-"-1',f;tf$.U ""''J(o» "''J'f"•i 11.:.t�:u 'tl�• "-�·� '$.}'In;..., "'::1� •\yff<ijll • Benefit: Reduction of

runtime and downtime

Figure 35: Upgrade Preparation Using the ASU Toolbox

©Copyright . All rights reserved.

" t..t...-.o <'-"II� • Oii;

� ,���:«'. W:l'#tnt<J '"'(: '-""""'"°*".S:•t.puat .. •,..l ();m.st»1�J(l'l!«I ·- . ': ;:. . !:::: I -. JS:: i := ! 'iE° i ---� .. --... ... � ... -·-.!:.�--- ·-=;;-� .. ::" '":;- �-·--33

(46)
(47)

Unit 3

Exercise

1

Perform Pre-Upgrade Steps

Business Example

You are performing an update from SAP ECC 6.0 to SAP ECC 6.07. Prepare the update using the relevant SAP notes, the topics from the Update/Upgrade Guide, and the ASU Toolbox.

1. Prepare the update using SAP Notes. The relevant SAP Notes can be found in the Update/ Upgrade Guide (SUM Guide, Chapter 1.3.2 SAP Notes.

Note:

Use the SAP Notes that are printed in the course material. Do not use the SAP Notes delivered on the SAP Service Marketplace. The printed SAP Notes are shortened and changed for the needs of this course.

• SAP Note 1843776 (Central Note - Software Update Manager 1.0 SP09 [lmt_005])

• SAP Note 1737650 (EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note)

• SAP Note 1844234 (MaxDB: Additional Information - Software Update Manager 1.0 SP09)

The first and the third SAP Notes can be found directly in the Update/Upgrade Guide. The second SAP Note can be found within the first SAP Note.

2. Prepare the update according to the topics in the Update/Upgrade Guide, Chapter 4, Preparation.

3. Prepare the update by using the ASU Toolbox. Perform at least one task as an example.

Note:

Wait to perform this step until after the tool import of the SUM has finished, because newer versions of the ASU Toolbox-related transactions are being imported.

© Copyright . All rights reserved.

(48)

Unit 3

Solution

1

Perform Pre-Upgrade Steps

Business Example

You are performing an update from SAP ECC 6.0 to SAP ECC 6.07. Prepare the update using the relevant SAP notes, the topics from the Update/Upgrade Guide, and the ASU Toolbox.

1. Prepare the update using SAP Notes. The relevant SAP Notes can be found in the Update/

Upgrade Guide (SUM Guide, Chapter 1.3.2 SAP Notes.

Note:

Use the SAP Notes that are printed in the course material. Do not use the SAP Notes delivered on the SAP Service Marketplace. The printed SAP Notes are

shortened and changed for the needs of this course.

• SAP Note 1843776 (Central Note - Software Update Manager 1.0 SP09 [lmt_005])

• SAP Note 1737650 (EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note)

• SAP Note 1844234 (MaxDB: Additional Information - Software Update Manager 1.0 SP09)

The first and the third SAP Notes can be found directly in the Update/Upgrade Guide.

The second SAP Note can be found within the first SAP Note.

a) In SAP Note 1843776, review Section I, Important General Information, Section II,

Corrections to the Guide, and Section Ill, Preparing the Update. Then, consider these

actions:

• Non-central instances: profile merge after upgrade (not a preparation task)

• Implement SAP Note 1720495 before SPAU (not a preparation task)

• Check Server Group SAP_ DEFAULT_ BTC

• Check the registration of sapevents.dll

(49)

Lesson: Performing Pre-Upgrade Steps

• Prevent the potential loss of HR data in table T77SO (import transport request

DCCK900003)

• Set A UT OST ART =O

• Clean up profile directory

b) No preparation actions have to be considered from SAP Note 1737650 except applying the newest SPAM/SAINT update. But this will be checked and done by SUM anyway. You can either apply the newest SPAM/SAINT update now or let SUM perform this action.

c) No actions have to be considered from SAP Note 1844234.

2. Prepare the update according to the topics in the Update/Upgrade Guide, Chapter 4, Preparation.

a) For Section 4.3, Checking the Software Requirements, no action is required.

b) For Section 4.4, Making Preparations at the Database Level, assume that the optimizer statistics are up-to-date.

c) For Section 4.5, Checking the Structural Requirements for ABAP, check the profile parameters.

d) For Section 4.7, Setting the Operation Mode for the Update, define operation modes.

e) For Section 4.8, Checking the Consistency of the Host Name, perform the check using transaction SM51.

f) For Section 4.9, Checking the Number of Background Processes, no action is required. g) For Section 4.10, Deleting the Autostart Parameter, no action is required.

h) For Section 4.11, Filling the Download Directory, create the download directory and copy the following into it: the MOpz download, additional SAP Support Packages, and the stack XML file.

Note:

You must rename the host in the stack XML file. Open the stack XML file with Notepad and perform Replace All to change all instances of twdfOOOO to your

host name.

3. Prepare the update by using the ASU Toolbox. Perform at least one task as an example.

Note:

Wait to perform this step until after the tool import of the SUM has finished, because newer versions of the ASU Toolbox-related transactions are being

imported.

©Copyright. All rights reserved.

(50)

Unit 3: Update/Upgrade Preparation

a) According to SAP Note 1000009, download the attached file, ASU_ERP.zip, to your PC

and unzip it.

b) Log on to your SAP ECC system. client 100.

c) Call transaction /n/ASU/START and choose Import New ASU CONTENT DEFINITION.

d) Import the new ASU content.

e) Choose Create New Task List and Jump to Task List.

f) From the Manual PRE Upgrade Steps, you may want to choose Backing Up Wage Types in

(51)

Lesson: Performing Pre-Upgrade Steps

LESSON SUMMARY

You should now be able to:

• Perform pre-upgrade steps from SAP Notes

• Perform pre-upgrade steps from topics in the Update/Upgrade Guide

• Perform pre-upgrade steps using the ASU Toolbox

©Copyright. All rights reserved.

(52)
(53)

SUM Part Preparation

Lesson 1

Analyzing the Uses of the Software Update Manager (SUM)

Lesson 2

Using the SUM to Prepare for Updating/Upgrading

Exercise 2: Use the SUM to Prepare for Updating/Upgrading

UNIT OBJECTIVES

• Analyze the uses of the SUM

• Use the SUM to prepare for updating/upgrading.

© Copyright . All rights reserved.

42

48 57

(54)

Unit 4

Lesson 1

Analyzing the Uses of the Software Update

Manager (SUM)

LESSON OVERVIEW

This lesson covers analysis of the SUM. LESSON OBJECTIVES

After completing this lesson, you will be able to: • Analyze the uses of the SUM

Placement within the Entire Process: SUM

The Five Major Technical Steps

1 Solution Manager: select target release

Needed Technical Usages of SAP Enhancement Package 6 for SAP

-ERP 6.0 and corresponding SAP

Support Packages

Cl) SAP Notes: pre Update/Upgrade steps -See Update Guide

E 2 Upgrade Guide: pre Update/Upgrade steps

·- ASU Toolbox: pre Update/Upgrade steps -SAP Note

1000009

;g.

SUM: preparation steps

\.:_A

SUM: resolving negative checks -Roadmap steps up to

5.4

SUM: Update/Upgrade -Roadmap steps from 5.5

SAP Notes: post Update/Upgrade steps

- .

Upgrade Guide: post Update/Upgrade steps See Update Guide ASU Toolbox: post Update/Upgrade steps -SAP Note 1000009

References

Related documents

SAP HANA Assessment for ERP, CRM, SCM, SRM, BW on HANA Technical Planning/Upgrade SAP HANA Sizing/Configuration Technical Upgrade Operational Concept Functional Upgrade

Comparative in vitro evaluation of contact activity of fluralaner, spinosad, phoxim, propoxur, permethrin and deltamethrin against the northern fowl mite, Ornithonyssus

By focusing infill along Activity Corridors we can enhance the public transport connectivity between Perth’s Activity Centres and can transform these areas into vibrant High

Little or no variance in size was noted for many of the six-sided phytolith viewed in the juvenile and mature assemblages (see Table F.20). This led me to believe that the majority of

① ① Customer Customer Value Value ② ② Shareholder Shareholder Value Value ③ ③ Human Human Capital Value Capital Value Narrowly defined Narrowly defined corporate

All regressions include country and wave fixed effects, as well as individual-level controls: age, age-squared, education level, gender, marital status.. Supplementary

Much like the repetition of “you” (meaning Odysseus) in previous poems, the emphasis on “she” (Penelope) here continues to diminish Circe’s role in the narrative, despite the

It is a natural question to ask about the location of zeros -from the point of view of the electrostatic interpretation- for polynomials orthogonal with respect to a perturbation of