Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2
Support Package Manager/SAP Add-On InstallationSupport Package Manager (SPAM) and SAP Add-On Installation Tool (SAINT) are…
…transactions in an SAP system used for importing
support packages and installing or uninstalling add-ons
SPAM is used exclusively to import support packages
SAINT is used for installing or updating SAP or 3rd party
add-ons
A new feature in SAINT allows some add-ons to be
uninstalled
NEW : Some SAP add-ons
can be uninstalled !
Used for single support
packages or small queues
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Support Package Manager/SAP Add-On InstallationWhat is the purpose of the Support Package Manager?
Importing support packages (corrections) in a
consistent way
Ensures the correct sequence of a bunch of support
packages for different software components (checks for
cross-component dependencies)
Performs system checks to ensure a smooth import
Protects modifying optional software components against
SAP standard corrections
Protects customer developments from being overwritten
Quick and efficient import
Can be controlled by a stack configuration file
Possibility to perform the import in the background
Different possibilities to shorten the import time
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 4
Support Package Manager/SAP Add-On InstallationWhat is the purpose of the SAP Add-On Installation Tool?
Installing, upgrading, and uninstalling optional
software components (add-ons) in a consistent way
Supports the installation/upgrade/uninstallation of several
software components in one step
Ensures the preservation of the maintenance level during the
upgrade (equivalence support packages)
Ensures the correct sequence of installation, upgrade, and
support package for different software components (checks
for cross-component dependencies)
Performs system checks to ensure a smooth import
Quick and efficient import
Can be controlled by a stack configuration file
Possibility to perform the import in the background
Different possibilities to shorten the import time
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
Support Package Manager/SAP Add-On InstallationBasics about Online Correction Support (OCS) packages
Content and attributes are packed into OCS packages
Online Correction Support (OCS) packages describe themselves and
the required environment for their import
There are different types of OCS packages – support packages,
installation packages, upgrade packages, and language packages
Attribute change packages (ACP) extend the import conditions of the
add-on
The content is a standard ABAP transport request
Imported with transport tools tp, R3trans (executables on OS level)
Tip ! When installing or upgrading add-ons,
always include the ACP package
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 6
Support Package Manager/SAP Add-On InstallationArchitecture of SPAM and SAINT
ABAP Stack
SPAM &
SAINT
Import
Managertp
Adapter
UI LogicRemote Access
Handler
tpR R
RSAP GUI
Remote Consumer
RRFC
Validation Engine
Queue
Calculator
Conflict Checker
R3transR
DB
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
Support Package Manager/SAP Add-On InstallationImport conditions
Import preconditions and attributes of an OCS package describe (alternative) software logistical
system environments in which they can be applied
Two kinds of elementary import preconditions
Preconditions for software component versions
Preconditions for OCS packages
Possible truth values “T”rue, “F”alse, “M”inimum
Elementary import preconditions are connected
by logical operators (AND, OR)
Allowed system environments are described by such (in principle arbitrary) complex logical
expressions of elementary import preconditions
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 8
Support Package Manager/SAP Add-On InstallationQueue calculator
The queue calculator
Checks the complex import preconditions
Fulfills them by forming queues of OCS packages
It is an iterative and recursive process
Iterations over the component versions requirements
and OCS packages
Fulfillment of import preconditions by adding packages
to the queue in a recursive process
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 9
Support Package Manager/SAP Add-On InstallationThe conflict check
Purpose
Checks whether (optional) software components modify objects of
other software components
Ensures that Conflict Resolution Transports (CRTs) are part of the
queue when modified objects are changed by support packages
Procedure
Calculates any conflict partners according to the component layer
hierarchy
– Modifications are only allowed from a higher layer to a lower layer
– This determines what is the modifier and what is modified
– The modifier is responsible for resolving a conflict
Collects the object lists that have to be compared
Does the object list comparison using an efficient algorithm
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 10
Support Package Manager/SAP Add-On InstallationThe import manager
The import process is divided into phases with a fixed
sequence
A phase has to be finished successfully before the next can start
If a phase is aborted, the import process resumes in this phase
Import scenarios define whether a phase is executed or not
SPAM and SAINT have different import scenarios
Import phases are collected in import modules
“Preparation”, “Import 1”, “Import 2, “Postprocessing”
Execution of the import modules can be controlled by start options
(dialog, batch, immediately, at a given time)
The physical import is done by the standard transport tools tp
and R3trans
Specifics of the OCS package import are controlled by special tp
parameters set by the import manager
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 11
Support Package Manager/SAP Add-On InstallationWhy uninstall add-ons using SAINT?
Customers and partners want to remove or disable
installed add-ons to avoid the following issues:
Add-on is no longer updated by SAP or partner
Add-on is no longer licensed by customer
Add-on was installed for testing purposes and therefore
never licensed
with the consequence that
Add-on stops the next upgrade processes (e.g. not
supported in target release)
Add-on cannot be taken out of maintenance
Add-on causes legal issue
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 12
Support Package Manager/SAP Add-On InstallationUninstallation of add-ons
Technical uninstallation
checkDeactivation
Customer data treatment
De-configuration
Technical uninstallation
Executed
in SAINT
General checks
Creation of the local deletion package
Deletion package-specific checks
Export of the deletion package
Import of the deletion package
Postprocess-ing
Manual actions, described in a
de-implementation guide/note
Test scenario
in SAINT
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 13
Support Package Manager/SAP Add-On InstallationRequirements for uninstallation
System must be ready
Kernel >= 720
tp/R3trans versions (see SAP Note 2011192)
Usual system checks known from SPAM/SAINT
Add-on must not be required by other installed add-on
Add-on must be released for uninstallation
Requires attribute DEINSTALL_ALLOWED plus the SAP Note
and appropriate NEED_SPAM_LEVEL on add-on installation
package
Optionally DEINSTALL_PLUGIN attribute can point to add-on-
specific ABAP class, which can e.g. check system or usage-
specific restrictions
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 14
Support Package Manager/SAP Add-On InstallationTroubleshooting SPAM and SAINT
Before importing support packages, ensure that the customer transport
system is configured correctly (transaction STMS)
Ensure the settings are configured as desired; click “Extras”, then
“Settings”. Online help for each setting is available by clicking
If errors do occur, you can find more
information about them in the logs
Never reset the import queue outside of
SPAM or SAINT; to do so can lead to
system inconsistencies that may not be
recoverable
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 16
© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2
Note Assistant (SNOTE)Note Assistant is a tool…
… that helps implement of one or more SAP
Notes simultaneously.
The transaction used to access the tool is
SNOTE.
The tool implements the automatic correction
instructions.
The SAP Notes have to be loaded in the tool
first.
SAP Notes are small corrections intended to fix
ABAP errors.
SNOTE is only available for ABAP stack
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Note Assistant (SNOTE)SAP Notes…
… give you instructions on how to correct errors and configure systems, and explain functionality
or provide release information.
SAP Notes contain the following blocks
Symptom: A brief description of the error/ information that is provided in the SAP Note
Reason and Prerequisites: The root cause of the error and conditions in which the SAP Note can be
applied
Solution: A brief resolution or a workaround to the problem
Software Components: The validity of the SAP Note provides a support package range
Correction Instructions: The actual corrections that are implemented in the system by SNOTE
Prerequisites: List of prerequisite SAP Notes, if any
Support Packages: The support packages that deliver the corrections provided by an SAP Note
References: showing referred notes
Side Effects if any; and lastly
Language: The language of the SAP Note
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 4
Note Assistant (SNOTE)Correction instructions describe…
… the changes to be made on standard objects.
Each correction instruction contains multiple Context
Blocks, Insert Blocks, and Delete Blocks.
The Context Block is a unique set of lines of code,
and is used to identify the lines of codes to be
modified.
The Delete Block contains lines of code that have to
be deleted from the original code.
The Insert Block contains the new lines of code
(corrections) that will be inserted in the object.
Each correction instruction is assigned to a number.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
Note Assistant (SNOTE)SNOTE toolbar
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 6
Note Assistant (SNOTE)Implementing a SAP Note
Load the SAP Note in your system (Upload/Download).
Check the validity of the SAP Note
Read the SAP Note description thoroughly and check
for manual pre-implementation steps.
Implement the corrections.
Perform post-implementation steps.
Test if the SAP Note has corrected the error/provided
the functionality.
Set the processing status to complete.
Release a transport request to the follow-up systems in
the landscape.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
Note Assistant (SNOTE)Implementing correction instructions (1/2)
Click Implement button in SNOTE.
Assign a transport request to the SAP Note.
The transport request will have the objects:
R3TR NOTE(SAP Note)
R3TR CINS(Correction Instructions)
and the objects modified.
Dialog box with traffic light signals appears
with the list of objects that are being modified
by the SAP Note.
Green traffic light: All corrections can be
implemented without changes
Yellow traffic light: A few corrections can be
implemented, rest need manual changes
Red traffic light: Changes cannot be included
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 8
Note Assistant (SNOTE)Implementing correction instructions (2/2)
Confirm the dialog box if all changes
can be copied.
The correction instructions will be
implemented in the objects, but the
objects will be inactive.
Another dialog box appears
containing the list of objects to be
activated. The objects are
syntactically checked and activated.
Once all the objects modified by the
SAP Note are active, the
implementation is successful.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 9
Note Assistant (SNOTE)Splitscreen editor
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 10
Note Assistant (SNOTE)Resetting an SAP Note is…
… to deimplement a SAP Note from the system
Click Reset Implementation of SAP Note.
A dialog box with traffic light signals appears with
the list of objects that are being modified by the
SAP Note.
Confirm the dialog box if all changes can be de-
implemented.
Another dialog box appears containing the list of
objects to be activated. The objects are
syntactically checked and activated.
Once all the objects modified by the SAP Note are
active, the de-implementation is successful.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 11
Note Assistant (SNOTE)Implementation status of an SAP Note
Completely implemented: The corrections in the SAP Note have been implemented completely in your
system
Incompletely implemented: Not all the relevant correction instructions have been implemented, or some
correction instructions have only been partly implemented
Obsolete version implemented: An older version of the SAP Note is implemented in the system, a newer
version is downloaded in the system
Can be implemented: The SAP Note contains correction instructions that you may need to implement in
your system
Cannot be implemented: The SAP Note does not contain any correction instructions that you can
implement in your system
Obsolete: After you implemented the corrections in the SAP Note, you imported a support package that
also contains these corrections. The errors have now been removed
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 12
Note Assistant (SNOTE)Troubleshooting
The Note Assistant provides information when an error takes place. There
is a “?” (question mark) button in the left which provides information on
how to resolve that particular error. Some of the common errors that can
be seen in the Note Assistant tool are:
Object cannot be locked under request: Note Assistant makes sure that
an SAP Note is implemented under one request. To do this, it enters the
transport object R3TR NOTE in the request and locks the SAP Note under
this request. You can then edit the SAP Note or its objects in this request
only. If the objects are already locked in other requests, you first need to
release them. You can then edit the object again.
Note is inconsistent: An SAP Note can include corrections to multiple
objects. Transporting individual objects may cause an SAP Note to be
implemented incompletely. In this case, the status of the SAP Note is
displayed as inconsistent. You should then check the implementation
status of the SAP Note and implement it again if necessary.
Note not in worklist after download: The SAP Note may already have
been downloaded and processed. Search in the Note Browser to find all
SAP Notes in the system.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 14
© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2
Database Migration Option (DMO) of Software Update Manager (SUM)Database migration option (DMO) is used when…
You want to migrate your existing
ABAP system to the SAP HANA
database
Your SAP release needs to be
upgraded prior to migration
SAP upgrade and database
migration to SAP HANA are to be
performed in one tool!
Option of Software Update
Manager – not a new tool
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Database Migration Option (DMO) of Software Update Manager (SUM)DMO-specific actions during Extraction roadmap step
Provision of target database type
and migration key
Decision about using the
Migration Repetition option for
testing
Decision about the Table
Comparison option with SUM
Decision about the landscape
reorganization for SAP HANA
scale out
Implementation of SAP Notes
required by SUM
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 4
Database Migration Option (DMO) of Software Update Manager (SUM)DMO-specific actions during Configuration roadmap step
Provision of connection
parameters and users of the
target database
Installation of target database
client on the DMO host
Extraction of kernels for both the
source and target databases
Upload of additional packages,
customer change requests, and
modifications
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
Database Migration Option (DMO) of Software Update Manager (SUM)Important phases during Preprocessing roadmap step
EU_CLONE_MIG_UT_SIZES - Determine table sizes for uptime migration (repository)
EU_CLONE_MIG_DT_SIZES - Determine table sizes for downtime migration (app tables)
EU_CLONE_MIG_UT_CREATE - Create tables on target database for uptime migration
EU_CLONE_MIG_DT_CREATE - Create tables on target database for downtime migration
EU_CLONE_MIG_UT_PRP - Create directories and control files for uptime migration
EU_CLONE_MIG_UT_RUN - Migrate repository into target database
EU_CLONE_MIG_DT_PRP - Create directories and control files for downtime migration
EU_CLONE_MIG_DT_RUN - Migrate application tables into target database
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 6
Database Migration Option (DMO) of Software Update Manager (SUM)Utilities for DMO (extended UI)
DMO Migration Preparation
DMO Migration Control Center
DMO Migration Post Analysis
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
Database Migration Option (DMO) of Software Update Manager (SUM)Performance optimization techniques
Provide XML from previous
DMO runs in the parameter
/clonepar/clonedurations and
reduce table splitting time
Use the Benchmarking tool
Downtime optimization by
migrating application tables in
uptime
Optimal parallel process
configuration
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 9
© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2
Downtime Minimization Capabilities of SUMNear Zero Downtime Maintenance + inclusion of customer transports during upgrade
Features available in Software Update Manager
(SUM)
A main improvement to significantly reduce
business downtime
Free and does not require a license
Already generally available for customers
24 hours availability is expected
Every hour of downtime
is expensive
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Downtime Minimization Capabilities of SUMBusiness impact of downtime
Minimizing the planned
downtime is the main focus
of SUM advanced mode
business downtimeproductive use
cool downsystem maintenance by
Software Update Manager
tests /
verification
ramp
up
cust.
trans.
technical downtime
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 4
Downtime Minimization Capabilities of SUMFeatures to enable downtime reduction in ABAP-based SAP systems
Parallel operation of production system and
shadow system
Import of the substitution set into the shadow
tables during production operation (extended
shadow) enables the following in uptime
near-Zero Downtime Maintenance (nZDM)
Customer Transports import
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
Downtime Minimization Capabilities of SUMWhat is it? How does it work?
Uptime
Shadow
operation
Technical Downtime
Move application tables that are touched by the upgrade/update to the shadow system (approx. 8,000 tables)
Extended (second) shadow instance: MAIN_SHDIMP/SUBMOD_SHD2_RUN/*
Equip them with a change recording replication (Record & Replay technique)
DB changes in production system during maintenance create triggers; changes are recorded
Replication of DB changes: shadow instance tables are updated after the update phases
Extended shadow
operation
Sw
itch
tab
les a
nd
kern
el
Conversion, main import, XPRAs
Execute
XP
RA
s / A
IMs
(XP
RA
s UP
G)
Import c
onte
nt
appl. ta
ble
s(Tabim
UP
G)
Adju
st c
entra
l S
AP
NW
table
s(xncv-phases)
Adju
st a
pplic
atio
nta
ble
s(parconv
upg)
Postp
rocessin
g
DD
Ls
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 6
Downtime Minimization Capabilities of SUMCustomer transports – what are they? How do they work?
Uptime
Shadow Operation
Business Downtime
Valid
atio
n
Ram
p U
p
Custo
mer
Tra
nspo
rts
Postp
rocessin
g
Custo
mer
XP
RA
s, A
IMs
Conversion,
Main Im
port
XP
RA
s, AIM
s
Sw
itch
Repository objects of the customer
transports are integrated into the
shadow operations
Non-repository objects of the customer
transports are integrated into the
Main Import phase of downtime
(minimum downtime)
Cust. R
eposito
ry
Obje
cts
Technical
Downtime
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
Downtime Minimization Capabilities of SUMLab: SAP ERP 6.0 EHP6 upgrade
System Details:
OS/DB: AIX/Oracle
DB size: 1.7 TB
System clone with customer data
Source:
ERP 6.0 SR3
Target:
ERP 6.0 with EHP6
Technical Usages:
Central Applications
Human Capital Management
IS-Utilities
Strategic Enterprise Management
Generation of ABAP loads during uptime
Source: SAP Labs measurements
hours
Minimum
Downtime
Overall
Uptime
5:41
2:31
Update with nZDM + customer transport
Update w/o nZDM + customer transport
Significant downtime reduction when using the capabilities of Software Update Manager for the Business Suite
7i2011
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 8
Downtime Minimization Capabilities of SUMHow is it activated?
nZDM can be activated in SUM by
choosing the “Advanced” option on the
tool configuration as described in
chapter 3.10 of the SUM guide.
Main SAP Note: #1678564
Customer transports can be included as
described in chapters 3.22 and 5.8 of
the SUM guide, regardless of the
configuration option.
Main SAP Note: #1759080
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 9
Downtime Minimization Capabilities of SUMOverview of importing customer transports
Technical details:
All customer transports are considered, incl. SPAU & add-ons
Depending on the transport object types, objects are
automatically managed in uptime or downtime of the standard
SUM maintenance procedure
Flexible regarding size and quantity of customer transports
No additional hardware requirement
Integration into Transport Management System (STMS), SPAU &
SPDD, Change Request Management (ChaRM)
SAP Note 1759080
This feature integrates the customer transports in the installation procedure. The business downtime is reduced
significantly by using the shadow instance for certain customer transport objects
SCN blog:
Customer Transports Import
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 10
Downtime Minimization Capabilities of SUMHow to use customer transports in SUM
Functionality available in
preconfigured standard or advanced mode
One buffer file for all transports
Client-dependent and client-independent
SPAU / SPDD
repository
customizing
Additional parameters for transport profile
use table logging for which clients
create a version
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 11
Downtime Minimization Capabilities of SUMCommon questions
How are the transports imported?
The transports are imported with “import all”, which is similar to the mass transports in TMS. This means, each import step is
performed for all transport requests. All requests are imported into the target systems in the order they were exported.
Does SUM use TMS for customer transports?
In SUM, R3TRANS is used for both SAP transports and customer transports.
Does SGEN in the shadow consider customer transports as well?
SGEN is also executed for the included customer transports.
If an object in Transport Request TR1 is expected to end with RC8, how does SUM react?
Return Code 8 (RC8) needs manual activities for the dedicated transport. The issue which blocks the transport request has to
be corrected or the transport request has to be skipped. For the subsequent system, the correction should be in the right
sequence in the buffer, thus no further activity is needed.
How do you import a correction to the shadow in case of RC8?
SAP Note #610311: Importing modification adjustment in second upgrade
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 12
Downtime Minimization Capabilities of SUMOverview of nZDM
This feature enables the main import running in the shadow during
uptime to minimize the business downtime significantly by using
the shadow instance for the main import
Technical details:
Record & Replay technique for business transactions based on
database trigger technology to ensure synchronization between
shadow and production system
Minimizes manual effort:
All steps run automatically in the background
Needed tables are selected automatically
Minimal additional hardware requirement due to shadow technique:
DB space is independent of system size
Only some additional DB space needed (80 – 350 GB)
SCN: SAP DOC 32544
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 13
Downtime Minimization Capabilities of SUM Important phases of near-Zero Downtime Maintenance
RUN_CRR_INI – Fill CRR framework tables
RUN_CRR_LOGTABS – Create log tables
RUN_CRR_TRIG – Create trigger for change recording in log table
TP_ACTION_CP2STAB – Initial transfer
RUN_CRR_FUNC – Generate function modules for continuous transfer of changes
RUNASYN_CRR_TRANSFER – Continue replication of changes to shadow tables
RUN_CRR_STOP – Stop continuous transfer
RUN_CRR_LAST – Replicate last non-replicated changes (downtime)
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 14
Downtime Minimization Capabilities of SUMThe CRR_CONTROL tool
Control of change recording by allowing
the user to
Monitor the data transfer
Stop the data transfer
Restart the data transfer
Include and exclude tables from data transfer
Adjust the CRR process
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 15
Downtime Minimization Capabilities of SUMTroubleshooting while using near-Zero Downtime Maintenance
Using transaction CRR_CONTROL
Errors documented in notes and on the Upgrade
Troubleshooting Wiki:
“System Upgrade And Update Troubleshooting Wiki”
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 16
Downtime Minimization Capabilities of SUM Latest improvements in SUM
Big tables are excluded automatically from nZDM
Related SAPup parameter (default values):
– set_max_tab_size = ON;
– isu_max_tab_size = value in KB (default 50 GB)
Performance issues related to big CRR tables are solved
SUM seemed to be stopped:
Issues related to long-running conflict handling on dedicated tables are solved
Rework of CRR transaction:
To handle transaction performance issues the replication count can be restricted
Potential errors due to start / stop of CRR processes solved
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 18
© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise EditionThe 3 transition scenarios to SAP S/4HANA
New Implementation: New or existing SAP
customer implementing a new SAP
S/4HANA system with initial data load
System Conversion: Complete conversion
of an existing SAP Business Suite system to
SAP S/4HANA
Landscape Transformation: Consolidation
of current regional SAP Business Suite
landscape or selective data transformation
into one global SAP S/4HANA system
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise Edition System conversion
System conversion is the process of transitioning an existing SAP ECC system to SAP
S/4HANA, on-premise edition
Software Update Manager (SUM) is the tool for this transition, either with or without DMO
If the source is already on SAP HANA DB, it is SUM w/o DMO
If the source is not yet on SAP HANA DB, it is SUM with DMO
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 4
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise Edition Benefits of system conversion
Migration without re-implementation
No disruption for existing business processes
Re-evaluation of customization and existing process flows
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise EditionKey steps for system conversion
Perform Pre-Checks Maintenance Planner, SAP S/4HANA Transition Checks, Customer Code Checks
ConversionSoftware Update Manager
Configure SAP FioriGeneric Configuration + App-Specific Configuration
Post Stepse.g. Custom Code Adaption
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 6
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise EditionPreparation steps on start release
Analyze used business processes – mapping to SAP S/4HANA innovations
Maintenance planner checks
Identify required integration scenarios of target state
Run pre-transformation checks
on source system: Used functionality,
supported industries, available add-on,
custom code
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise EditionSAP S/4HANA transition checks…
Involve implementation of all the
relevant SAP Notes (e.g.
2182725 - S4TC Delivery of the
S/4 System Conversion
Checks) as mentioned in the
Conversion Guide
Ensure detailed consistency from an application
perspective before conversion
Are performed on the source system before the SUM
process
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 8
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise EditionTechnical Implementation steps
“Installation” of SAP S/4HANA
– SAP HANA database
– SAP S/4HANA application core
Customizing adjustment
Adjustment of technical infrastructure
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 9
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise EditionSoftware Update Manager phases
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 10
Conversion of SAP ERP Systems to SAP S/4HANA, On-Premise EditionSemantical adoption
Adapt custom code to comply with SAP S/4HANA scope &
data structure
Adapt business processes to leverage new SAP S/4HANA
innovation functionality
Adapt integration (if applicable)
Implement SAP Fiori UIs
Introduce new SAP S/4HANA innovation scenarios
Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 12
© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Top Related