Search this blog for other interesting articles

Saturday 4 July 2015

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





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




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)


 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



 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



22 comments:

Unknown said...

Awesome Post

Unknown said...

hello sir its good if you can elaborate more on BDLS and SGEN what is the prupose of it and DB refresh steps will be good for freshers to understand

Niks said...

Hello Sir, What if we dont run BDLS? and let the sm37 jobs keep running in the background...Will it have any impact in the Source system? In short, Logical name will be source system name and it will run on target system, will it impact source/target system in anyway?? Thanks! :)

Anonymous said...

Please elaborate DB refresh step by step as you explain each and everything in miraculous way that people at any level can easily understand it.

Thank you :)

Anonymous said...

Hi Durgaprasad,

Explanation given is awesome....please explain the DB restore part step by step with screenshot, If you can explain that will be the great help.

Thank you

king khan said...

Hi durgaprasad sir,
Please explain database backup and restore with screenshots step by step.. thanks in advance

king khan said...

Hi Durga prasad ,
please can u explain database backup and restore step by step with screenshots..thanks a alot in advance

Anonymous said...

Hi Durgaprasad Ji , I am facing problem in step number 5 & 6

Please can u explain with screen shot of
5) Delete/recreate TMS for target system using SE06
6) Configure SAP transport system (using STMS)

thanks in Advance .

Unknown said...

awesome supper sir....

Unknown said...

This post is really awesome sir....

Unknown said...

Really nice

Unknown said...

Hello Sir, i am newbie to SAP basis. please explain me how to take snapshot in SAP.
Thanks and Regards
Wajid Khan

Anonymous said...

Why do you SGEN with a DB restore? It is not needed in this case.

For all those asking about DB restore part, the method of restore will vary a lot between different DB vendors, different backup products and even local (customer) preference. I don't think the blogger should include that detail in this blog. Bottom line is you need to get the database restored.

Qadar said...

Q1)which user master data i have to export (TARGET SERVER or SOURCE SERVER < PRD >
Q2)And in which server like source or target ...i have to do this activities
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)

I will wait for your reply ( mqadar989@gmail.com) is my mail id

Unknown said...

its is very useful ine sir...thanks

Unknown said...

Hi Sir,
I am on learning stage in Basis.
Still I am getting small confusion on system copy...I'll tell you what I have understood... Suppose my source system is production and target system is quality..so we need to export the user master data of Quality system by using Scc8...But here my doubt is to which system we are exporting?? What is my target system for my exporting??? And one more doubt is.. after done with system copy the entire data of my production is placed in Quality..but still production system data kept remain same in production system right.. because we are doing copying...So here what we do with production system???? If I'm not wrong will do copy again from Quality to Production ???
Please give some detailed information
Thanks in advance :)

Unknown said...

Hello Sir,

It's Awesome post.
But could you explain the BDLS in detail as post processing step.

-Thanks & regards,
Jai Ichale


Unknown said...

Transaction code BDLS is a Tool: Conversion of Logical System Names. This program is used to convert a logical system name, which has already been defined or used in this system, to a new name. The program determines all the relevant tables and converts the corresponding entries.

Unknown said...

Nice..

Anonymous said...

Hi Sagar,

You always do the system copy from production to quality so that if you have any changes to be transported to production, you can test the changes in quality that has got production data. You export user master record of quality system and save it in a TR and you import the same again to quality after your system copy as you want your production data into quality not the production users.

Unknown said...

Hi, I have a requirement from Basis team to create the Production user Ids (just create id and lock them, no roles) In QA that matches exactly to production after QA refresh with production data. I would like to know do we need to match the production user ids in QA after every refresh.if so, why? any valid reason why we need to match the production ids in QA? please advise me.

Unknown said...

thank u

Search this blog for other interesting articles

Please subscribe & activate link received to your email id to receive latest articles

Enter your email address:

Delivered by FeedBurner