The SAP Software Update Manager (SUM) tool helps
automate the upgrade and update processes for SAP systems, including tasks like
EHP updates, S/4HANA conversions, SPS updates, and full upgrades. Here’s a
closer look at the detailed SUM phases, sub-phases, and their roles in
supporting an efficient, low-downtime upgrade process
SAP SUM Phases and Roadmap
1. Initialization Phase
- Purpose: Set up the foundational elements for the upgrade, including selecting the appropriate roadmap and loading necessary files.
- Key Activities:
- Upload Stack XML File: The XML file contains metadata about the target
software version and components needed for the upgrade.
- Select Roadmap:
Based on the scope (EHP update, upgrade, or S/4HANA conversion), select
the roadmap that will guide the SUM process.
- Shadow Instance:
Not yet created; focus is on preparing the main instance.
2. Extraction Phase
- Purpose:
Gather and prepare all required upgrade files, notes, and patches,
ensuring compatibility with the existing system configuration.
- Key Activities:
- Extraction/Extraction: Extract upgrade files from the SAP Support Portal.
- System Status Check: Verify the health of the current system before making any changes.
- Parameter Input: Define necessary parameters, such as instance details and target configurations.
- Check for Notes: SAP notes provide specific
fixes and enhancements needed for the upgrade.
- Shadow Instance:
Still in preparation phase; main system operations continue.
3. Configuration Phase
- Purpose:
Configure system settings, set up integration points, and install a shadow
instance for uninterrupted operations.
- Key Activities:
- Configuration and Language Selection: Choose system language and configuration options relevant to the upgrade.
- Shadow System Setup: A shadow instance is created, acting as a temporary environment where upgrade processes run without disrupting production.
- Prepare Shadow Control Data:
Control data for shadow instance activities is set, enabling smooth
transition and coordination with the main instance.
- Shadow Instance Role:
Begins operation here, processing tasks separately from the production
system to minimize disruptions.
4. Checks Phase
- Purpose:
Conduct detailed system checks, validating compatibility with custom code,
third-party integrations, and infrastructure.
- Key Activities: Space Calculation: Ensure sufficient storage and database capacity to handle upgrade files.
- General Check: Perform compatibility and integrity checks on custom developments and add-ons.
- Preliminary Upgrade
Processing: Confirm system readiness for the upgrade.
- Shadow Instance Role:
Run tests on custom developments and other critical components, validating
them in a separate environment.
5. Preprocessing Phase
- Purpose:
Transition the system to an upgrade-ready state by setting up background
tasks, migrating data, and locking the main system when needed.
- Key Activities:
- Initialization
and Configuration: Set configurations specific to this stage,
preparing the shadow instance for intensive upgrade activities.
- Modification Transfer:
Transfer any code or configuration modifications to the shadow instance.
- Shadow System Installation: Activate the shadow system, making it fully
operational and ready for upgrade tasks.
- SPDD and Activation:
Review and adjust any system dictionary (SPDD) objects to ensure they’re
compatible with the upgrade.
- Transition to Downtime: Prepare the main system for planned downtime by
queuing any final tasks.
- Shadow Instance Role:
Runs key components of the upgrade, keeping the main instance live as long
as possible.
6. Execution Phase
- Purpose:
Execute the core upgrade on the main instance, taking it offline briefly
while the shadow instance supports critical functions.
- Key Activities:
- Downtime Setup: Set the system into downtime mode, which means restricting end-user access temporarily.
- Switch Tables and Kernel: Swap essential database tables and kernel files to align with the upgraded system.
- Conversion and Main Import: Conduct necessary data conversions and import primary components into the main instance.
- Transition
to Uptime: Restart the main system, making it accessible to users in
its upgraded form.
- Shadow Instance Role:
Supports remaining functions and allows rapid switch-over, minimizing
downtime by keeping essential services operational.
7. Post-Processing
Phase
- Purpose:
Validate the upgraded system, ensuring custom developments, integrations,
and critical functions are re-integrated correctly.
- Key Activities:
- Post-Processing
Finalization: Re-integrate custom developments and verify system behavior
in the new environment.
- Data Integrity Checks:
Confirm data accuracy, performance stability, and smooth functionality of
custom code.
- Cleanup and Transition to Production: Remove temporary files, clear logs, and enable the
system for normal operations.
- Shadow Instance Role:
Completes its function here, merging final updates and enabling the main
system to resume full operation post-validation.
Key Performance
Analysis: UPGANA File
Once the upgrade completes, the UPGANA file
(located at /sum/abap/analysis/log/UPGANA) provides details on each phase's
duration. Uploading UPGANA to the Technical Downtime Optimization Launchpad
displays insights on which phases took the most time, identifying optimization
areas for future upgrades.
Key processes for optimization include:
- ACT_UPG:
Upgrade activation steps.
- SUBMOD_SHDDBCLONE/DBCLONE: Cloning the shadow database, a crucial step that can
consume time.
- TABIM_SHADOW_INC:
Importing tables and data to the shadow instance.
- TABIM_UPG:
Completing the main table import.
- XPRAS_AIMMRG:
Data migration and integration process that includes activating objects in
the target environment.
- PARMVNT_APPL_VIEWS:
Adjusting views for application-specific parameters.
Analyzing this data can inform strategies for
optimizing certain phases, such as better hardware allocation for database
cloning or improving scripts for custom code checks.
0 Comments