Overview & Business Context

When customers move their SAP systems to RISE with SAP, the migrated systems receive a new GUID or are moved to a different customer network. As a consequence, monitoring and operational configurations built up in SAP Focused Run are lost, requiring significant manual effort to recreate them from scratch on the new system.

This document describes the Configuration Copy Capability — a feature that enables customers to copy all relevant SAP Focused Run configuration from an existing (old) system to a newly registered (migrated) system, across customer networks.

Key benefit: Customers avoid manual reconfiguration after a RISE move. All relevant monitoring configuration is copied to the new system automatically, and data collection is activated on the target system.

This function is available with SAP Focused Run 5.0 FP03.

Scope

The configuration copy capability covers the following boundaries:

  • Configuration is copied from the old system to the new system. The old system remains unchanged.
  • Both systems coexist in parallel until the customer decommissions the old one.
  • After the copy, data collection is activated on the new system.

No historical monitoring data is transferred — only configuration.

Deactivation of data collection on the old system is an optional separate step.

Out of Scope: Transfer of historical monitoring data is not part of this capability. Availability metrics that depend on a URL context must be recreated manually, as the URL changes when a system moves to SAP RISE.

SAP Focused Run applications in scope

SAP Focused Run usecaseReport name
Real User Monitoring/RUM/RISE_CONFIG_MIGRATION
Job & Automation MonitoringREPT_JAM_COPY_CONFIGURATON
Integration & Exception Monitoring/IMA/RISE_CONFIG_MIGRATION
Service Availability ManagementREPT_SAM_COPY_CONFIGURATION 
IT CalendarREPT_SAM_COPY_CONFIGURATION
Configuration & Security AnalysisCSA_COPY_CONFIG

SAP Focused Run applications out of scope

SAP Focused Run usecaseReason
System MonitoringReconfiguraiton covered by Simple System Integration reexecution.
Self MonitoringReconfiguraiton covered by Simple System Integration reexecution.
System AnalysisReconfiguraiton covered by Simple System Integration reexecution.
Analytics & IntelligenceReplace system in Dashboards.
Health MonitoringURL change
Synthetic User MonitoringThere is already a capability to move the robot configuration from one SDA to another.
EWA InfrastructureActivation covered by Simple System Integration reexecution.
Maintenance Certificate ManagementMaintenance certificates are handled by RISE - no manual activity needed
Guided Procedure ManagementMigrate/Copy scheduled GPs

Implementation approach

A report-based approach, using the LMDB system selection framework. After the configuration copy, Simple System Integration (SSI) must be executed for the new technical system to update the configuration on all relevant SDAs.

Each use-case team provides a dedicated ABAP report using the shared LMDB infrastructure. The report presents a selection screen with the following parameters:

Old System ParametersMigrated System Parameters
P_CN_OLD — Old System Customer NetworkP_CN_NEW — Migrated System Customer Network
P_E_OLD — Old System Extended SIDP_E_NEW — Migrated System Extended SID
P_ST_OLD — Old System TypeP_ST_NEW — Migrated System Type

Process description

End-to-End Process

The following steps describe the end-to-end configuration copy process performed by the customer's operations team after a SAP RISE migration:

  • Register the new technical system in LMDB
    The new (migrated) technical system must be fully registered in the LMDB of the customer's Focused Run instance. This applies both when the system remains in the same customer network and when it has been moved to a new customer network.
  • Optional — Rename Extended SIDs for consistency
    If the customer needs to retain the original Extended SID for consistency with third-party tools (e.g., mapping in ServiceNow), the old system — or both systems — should be renamed before executing the report. The new system should then be assigned the previously used Extended SID of the old system.
  • Execute the configuration copy report
    The customer starts the use-case-specific ABAP report (via SE38) and selects both the old technical system and the new (migrated) technical system using the LMDB-based input help. The report copies all relevant standardand system-specific configuration from the old system to the new system.
  • Optional — Deactivate data collection on the old system
    Once the new system is confirmed to be operational and collecting data, the customer can optionally deactivate data collection on the old system as a separate step. The old system configuration remains intactuntil the customer chooses to decommission it.

Usecase specific information

Configuration & Security Analysis (CSA)

Exemptions

Exemptions are created in CSA to ignore a check during policy validation. It is possible to apply exemptions for all systems or for individual systems. Hence, during the copy configuration, the new systems need to be added to the existing exemptions.

 

Alert Management

Alerts are created in CSA based on policy validation results, and the scope may contain system details. Hence, during the copy configuration, the new systems need to be updated in the alert scope.