Saturday, 4 July 2015

How to export user master and authorization profiles in SAP system?

This article answers following queries:
  • How to export user master and authorization profiles in SAP system? 
  • Which tcode is used for user master export in SAP system?
  • Which profile to be used to export user master in SAP system?

SCC8 transaction can be used for export of user master and authorization profiles in SAP system.

Please login to target system and go to SCC8 tcode. SAP_USER profile to be used to export user master and authorizations in SAP system.

So, please select profile as SAP_USER and input the correct target system and target client in which user master needs to be imported later.

After that click on “Schedule as Background Job” pushbutton.

It will result in below screen. 

Select the 

1) Source client which you would like to export
2) Select background server (optional). If it is not selected, load balancing will happen and client export can happen on any available background server. 
3) Please tick "immediately" checkbox (as shown below)
4) Please tick "No Printer Dialog" checkbox (as shown below)

and execute

It will result in below screen asking confirmation to continue.

Please click continue pushbutton to start the export of User Masters.  

We should follow above process and export users from all clients that are available in SCC4. User master export may not be required for clients 001 and 066 (as these are standard clients). 

Please make note of which Export contains which client’s user data so that you can import them later again (as part of post refresh steps)

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