LESSON OVERVIEW
This lesson covers the phases of the update/upgrade process.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
• Evaluate the phases of the update/upgrade process
Placement in Entire Process: Phases of the Update/Upgrade Process
Solution Manager: select target release
Needed Technical Usages of SAP Enhancement Package 6 for SAP -ERP 6.0 and corresponding SAP
Support Packages
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: post Update/Upgrade steps - . Upgrade Guide: post Update/Upgrade steps See Update Guide ASU Toolbox: post Update/Upgrade steps -SAP Note 1000009
Figure 58: The Five Major Technical Steps
The technical update/upgrade procedure can be described with these five major steps.
Resource Consumption of SUM
SOFYWll•Ke UPO•tE MJlor.tACEff
SGFTWARE UPDATE ft" cunf<glltlOllll"' =-.. �···
���, ...
'i'lt<•'P«"•�N"""4ot"kll;.-�10,..):#fNlo\-Lesson: Evaluating the Phases of the Update/Upgrade Process
-11-lll-l!:--R--R--R--R--R-;�.. �WI "'"'"' <11-1>• r... ..,.__ f,i,_,,.._
I°" lnfOott.\llurt h•_ .. ,... C-onltfU.-011 ·lntomndl• 8•11Mf•nv
•ff°"!ll'lll••""...-C.l"IW:ll•.o:••in._.,. .. ,,....,..,...,_,.,,,, .... ,..,....,, .,....,,.,.,,.,,.,..1'<� 0 lo'llll� Ot(�l''tcJlo(ktMlll ....
,.,. __
-····""-Ull!U 0<1u-•OMf'oll0:0."1'
Figure 59: Resource Consumption of SUM
"t�"t--7t:•'""'
�· ... �·'f("'*"l:"".-,""1111(1,0")
SGEN on shadow system available for updates/upgrades to SAP systems based on:
- SAP NetWeaver 7.02 (from SPS 09) - SAP NetWeaver 7.03
- SAP NetWeaver 7.31
Selection Standard/ Advanced has no influence on SGEN
SAP GUI for New Release
SAP GUI for new release must be available for users working on the update/upgrade
Standard and High Resource Use
upume Downtime
Figure 60: SAPGUlforNewRelease_lmage ppt
©Copyright . All rights reserved.
SAP GUI for new release must be avallable for all users
Production Downtime Standard and High Resource Use
Production Downtime Low Resource Use
Low Re$Ource 0$e Uptlme Oe>wnftme
67
Unit 5: SUM Part Update/Upgrade
Update/Upgrade Process
Initialization Extraction Configuration Checks Preprocessing Execution Postprocesslng Finalization
DB and SUM directory must be restorable to state at end of production!
� Standard/Advanced, archiving off ,,
-0 Standard/Advanced, archiving on Downtime
Figure 61: Update/ Upgrade Process Overview
Downtime
Cf> " "
2 0 c: 0 c: 0 1-1 c: 0 0 ::!!
�
I � >I ::!!� 0
:::>l z1
c: ro 0 ::!!
t!: ro t!: 0
Figure 62: Important Phases of the Upgrade
c: 0 ro c: ro
• EU_IMPORT* Copies substitution set from Upgrade CD to the shadow tables
Lesson: Evaluating the Phases of the Update/Upgrade Process
• ACT _UPG Activates all ABAP dictionary objects. that are not part of the standard upgrade DVDs
• PARDIST _SHD Starts distributor
• DIFFEXP*l Import of objects into shadow repository exported by DIFFEXP*
• SHADOW_IMPORT* Imports upgrade and language data into the new tables, imports included Add-on and SAP Support Packages into the shadow tables and the new tables
• MODPROF _TRANS Stops SAP system and changes profiles
• EU_SWITCH Switches to new Repository
• PARCONV _UPG Converts application tables and activates their nametab entries
• PMVNTAB_UPG Converts application views and activates remaining nametab entries
• TABIM_UPG Import of additional transport requests
• XPRAS* Executes XPRAs
Single System
Figure 63: Important Phases of the Update
Downtime
>' ::!:
�
0 �
• RUN_RSDBSCPY Clones tables from original to the shadow system
"'
• ACT _UPG Activates all ABAP dictionary objects. that are not delivered activated
• PARDIST_SHD Starts distributor
"'
• SHADOW_IMPORT* Imports SAP enhancement package objects. also imports upgrade and language data into the new tables, imports included Add-on and SAP Support Packages into the shadow tables and the new tables
• MOD PROF_ TRANS Stops SAP system and changes profiles
©Copyright . All rights reserved. 69
�
Unit 5: SUM Part Update/Upgrade
• EU_SWITCH Switches to new Repository
• PARCONV _UPG Converts application tables and activates their nametab entries
• PMVNTAB_UPG Converts application views and activates remaining nametab entries
• TABIM_UPG Import of additional transport requests
• XPRAS* Executes XPRAs
Transports for Modification Adjustment
QAS, PRO automatically - via transport request -In OAS and PRO
Integration of the created transport
Figure 64: Transports for Modifcation Adjustment
bin/umodauto.lst data/R ...
cofiles/K ..
buffer/SAP
• If objects need to be adjusted, use the transactions SPDD and SPAU. All modifications made by customers are then merged with the new SAP object versions to retain data; otherwise, the new SAP version will be activated and data may be lost.
• Downtime minimized: The system is available during the activation phase. The activation takes place on the shadow system.
• When the update/upgrade is completed, the SAP system is successfully running at the new release level. Customer-developed objects and modifications have been preserved.
Lesson: Evaluating the Phases of the Update/Upgrade Process
Incremental Table Conversion (INCV)
Configurable conversion process
• Exclusion times
• Progress prediction
ICNV
Figure 65: Incremental Table Conversion (ICNV)
Reduction of
update/upgrade downtime
• Large tables are now converted during uptime
• During downtime only switch to new structure necessary
• Can handle modified tables
Easy handling
• Takes place after modification adjustment with SPDD
• Fully integrated
into update/upgrade process
• With each new release, the structure of the tables in your database changes. These table conversions used previously only occurred during the update/upgrade downtime (for
example, phase PARCO NV). By using incremental conversion, you can convert many of these data records before the update/upgrade downtime.
• Advantages of ICNV:
Reduced downtime during the update/upgrade, because a large number of tables will be converted during uptime.
You can return to the SAP standard more easily for modified tables.
You can use incremental conversion especially for large tables.
• Incremental table conversion is performed using transaction ICNV. You can use the following functions:
Display the tables determined by SUM (tables for conversion with ICNV) Choose which tables you want to convert incrementally.
Start the conversion.
Monitor the conversion.
Estimate the runtime of the conversion.
• You can define the time during which ICNV should not be executed (for performance reasons).
• ICNV gives you information about the progress prediction.
©Copyright . All rights reserved. 71
�
Unit 5: SUM Part Update/Upgrade
Selection of conversion candidates:
• Modified tables that will be converted are included
• Tables can be excluded from ICNV even at this point (for example: a hot spot with frequent updates I deletes)
0 c
.2 c t> (t) (/) c (t) �
lll)t •Jllftlff \;c>),$
l;l!P t<1Jf'tC4 tr-lf��rt\..�J)�(
0
Figure 66: Transaction ICNV: Selection of Conversion Candidates
@Petfor• JCNV
• By calling transaction ICNV, all potential candidates are displayed with their current selection status. You can decide which of the pre-selected tables should be processed by ICNV.
• Tables can be excluded from being processed by ICNV with 'Do not perform ICNV'. This should be used for tables with a high number of updates and I or deletes. because in this case the ICNV can be inefficient. The delete operations are especially critical. The load on the database is doubled by performing a delete on a table processed by ICNV.
This efficiency check must be done manually. There is no tool that excludes 'hot spot tables' automatically!
LESSON SUMMARY
You should now be able to:
• Evaluate the phases of the update/upgrade process