What is the difference between homogeneous system copy and
heterogoneous system copy?
This article answers the following queries:
What is System refresh?
What is the difference between homogeneous system copy and heterogeneous system
copy?
What is the difference between System refresh and System copy?
What is the need of System refresh?
----------------------------------------------------------------------------------------
System Refresh:
System refresh is nothing but copying an SAP system to another.
Let us say the system from which copy is being done is called as source system and system in
which data to be copied as target system.
If the target SAP system already exists then this is known as system refresh.
Difference between homogeneous system copy and heterogeneous system copy:
If the target SAP system doesn’t exist and you are building a new SAP system on the same o/s
and database then this process is called as homogenous system copy. In case the o/s and
database are different in your source and target SAP systems, then that process is
calledheterogeneous system copy or migration.
What is the need of System refresh?
In real time scenarios,
i) If Quality system data is outdated with Production system, testing may succeed in
quality system but may fail in Production system. So, it is required that Quality system should
have same data as Production system, so that better testing can be done in Quality system whose
data is similar to production. So, it is suggested to refresh quality system with production system
data periodically.
ii) Theremight be a requirement to perform a production system upgrade (like support pack /
version upgrade.) Instead of performing upgrade directly on actual production system, it is better
idea to setup a mock / test system similar to production system with the actual data and perform
the upgrade there first. After performing upgrade on mock system, some details related to errors
likely to occur, actual time it took for upgrade, major issue if any can be identified so that
necessary precautions can be taken while performing the upgrade on the actual production
system.
iii) Incase a newly inducted team should be given training, instead of providing training to them on the
actual system( DEV/QA/PRD), a system refresh can be done and a test/training system can be
setup and access can be given to those systems. This makes sure that no damage is done to
DEV/QA/PRD systems.
Will explain you the steps involved in System refresh(with screenshots) in the next article
How to perform System Refresh activity in SAP ?
This article answers following queries:
How to perform system refresh activity in SAP?
What are the steps involved in system refresh of SAP system?
What is the SAP system refresh procedure?
Explain post system refresh activity steps
What are the pre refresh activity steps?
----------------------------------------------------------------------
System refresh is nothing but copying an SAP system to another.
Let us say the system from which copy is being done is called as source system and
system in which data to be copied as target system.
System refresh activity comprises of following 3 phases
Pre refresh activity
Refresh activity (Database restoration)
Post refresh activity
Note : Please click on Red links to understand more details of that step
Pre-refresh Activity:
Before performing system refresh, following steps need to performed
1) Export of user master and authorizations from all SAP clients on the target
system (SCC8)
This step is required because once the source system data is replaced in the target
system, the user and authorization details of target system will be overwritten by source
system user master. So, in case we need to retain target system user master, we have
to take backup of the same using SCC8 tcode.
2) Please take snapshots of
Client settings (SCC4)
Logon groups (SMLG)
Processing groups (RZ12)
AL11, SE03 and SM61
Printer details (SPAD)
Operation modes (RZ03, RZ04 and SM63)
RFCs (SM59)
Partner profiles (WE20) and ports (WE21)
Logical systems (BD54)
Services that are active (SICF)
These screenshots are to be captured because after system refresh, we need to check
and maintain the same settings in target system
3) Using SE01 transaction, create transport request forbacking up of AL11,
SE03, SMLG(Logon Groups), RZ12(Processing Groups),SM59(RFC’s), SM69,
SPAD, SM61, RZ03
Refresh activity (Database restoration)
1) Please stop the target sap system and handover to database team
2) Database team will restore the data from source system to target system and validate
3) Once everything is fine, database team will handover system to SAP Basis team
Post refresh activities:
1) Disable batch processing (by setting batch work processes as 0 at Os level)
2) Start sap system and login with sap* user
3) Install SAP license
4) Prevent batch job from running by setting all jobs from released to
scheduled (using SM37)
5) Delete/recreate TMS for target system using SE06
6) Configure SAP transport system (using STMS)
7) Import user master for all clients (which was done as part of pre-refresh steps)
8) Import transports related to AL11, SE03, SMLG, RZ12, SM59, SALE and SM69
backup (which was done as part of pre-refresh steps)
9) Execute BDLS transaction
10) Remove entries from few listed tables using SE14 transaction
11) Delete old SAP profiles and import new profiles using RZ10 transaction
12) Perform spool consistency check using SP12 transaction
13) Delete old update records using SM13 transaction
14) Delete/Reorganize transaction RFC’s using SM58 transaction
15) Delete batch job logs by executing RSBTCDEL report using SE38 transaction
16) Delete Old spool requests by executing RSPO0041 report using SE38 transaction
17) Create/modify necessary partner profiles using WE20 transaction
18) Modify necessary ports using WE21 transaction
19) Perform mail configuration using SCOT transaction
20) Delete old mail related entries using SOST transaction
21) Execute SGEN transaction or run RSGENINVLAS report (no variant is required)
using
SE38 transaction
22) Make necessary services active through SICF transaction
