SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs Headline Animator

SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs


Wednesday, 8 July 2015

How to import SAP profiles (as part of post installation / post refresh steps)?

This article answers following queries:

  • How to import SAP profiles after installation of sap system?
  • How to import SAP profiles after system refresh?
  • What transaction code is used for importing profiles in SAP?
  • When it is required to import profiles in SAP?
  • How to delete existing SAP profiles after system refresh?
  • How to check all consistency of profiles in SAP system?


----------------------------------------------------------------------

When it is required to import profiles in SAP?

Generally, we import SAP profiles under 2 circumstances:

  • After new SAP system installation (as part of post installation steps)
  • While performing system refresh activity (as part of post refresh steps)


After system refresh, the target system will have SAP profiles of source system. So, we need to delete the old profiles and import new SAP profiles of the target system.

How to delete existing SAP profiles after system refresh?


To delete existing profiles of SAP system, go to transaction RZ10 and select the profile to be deleted as shown below:







After selecting the profile to be deleted, navigate to Profile -> Delete -> All Versions -> Of a profile (as shown below). This will delete the profile



























Please carry out above step for all the old profiles (Default, Start profiles, Instance profiles) that are existing in the system and delete all of them

How to import SAP profiles (as part of post installation / post refresh steps)?


RZ10 tcode is used for importing SAP profiles. Go to RZ10 transaction and navigate to Utilities -> Import Profiles -> Of active servers (as shown below) 





This will import all the profiles of active servers in the SAP system and below profile check log will be displayed. This log contains details whether all profiles are imported correctly or not.





How to check all consistency of profiles in SAP system?

To check consistency of all profiles of active servers, we have go to transaction RZ10 and navigate to Utilities -> Check all profiles -> Of active servers































This will display profile check log with details of any inconsistencies



Monday, 6 July 2015

How to prevent SAP background jobs from running?

This article answers following queries:

  • How to prevent SAP background jobs from running?
  • On what circumstances, we need to hold background jobs from running?
  • How to change status of jobs from Released to Scheduled?
  • How to un-schedule duplicate jobs in SAP?
  • How to hold the jobs in SAP from execution?

---------------------------------------------------------------------

If the background job in SAP is in released state, it will run at the mentioned time or when respective event occurs (as per the job definition). If for any reason, you would like to hold the job(s) from execution, you can do the same using SM37 transaction.

In real time scenarios, you may need to hold few jobs from execution like

  • After system refresh, you may have to hold jobs from execution in target system because the target system consists of source system jobs and they shouldn’t run. So, it is suggested to hold all the jobs from execution and release only required jobs and basis standard jobs(housekeeping jobs)
  • Sometimes, there might be duplicate schedule of same job and you want to hold the duplicate job to prevent multiple executions

In these cases, to hold the jobs to prevent from execution, we need to set the status of those jobs from “Released” to “Scheduled”. To do the same, we have login to SAP system and go to transaction SM37 which will result in below screen.



































In the above screen, select the job status as “Released” and keep all other options as shown above and execute. This will list down all the released status jobs.


From the list, select tick those jobs that you would like to prevent from execution and change the status from “Released to Scheduled” as shown below:



Then all the selected jobs status will be set as “Scheduled” and those jobs won’t get executed till you release them again.






Sunday, 5 July 2015

What is the use of database utility in SAP?

This article answers following queries:

  • How to remove entries from the tables in SAP?
  • What is the use of SE14 transaction in SAP?
  • What is the use of database utility in SAP?
  • How to invoke database utility in SAP?


------------------------------------------------------------------------

The database utility is the interface between the ABAP Dictionary and the relational database underlying the R/3 System. This tools allows you to edit database objects derived from objects of the ABAP dictionary.

Using database utility, we can create, delete and adjust to changes to database objects definition in the ABAP dictionary.

SE14 transaction is used for invoking database utility.

As part of post system refresh activities, we need to remove entries from specific tables (mentioned below), activate and adjust the database.

Table List

ALCONSEG
ALSYSTEMS
DBSNP
MONI
OSMON
PAHI
SDBAD
SDBAH
SDBAP
SDBAR
TPFET
TPFHT
TLOCK
SWNCMONI
SAPWLSERV
SWNCMONIINDEX

Process for removing entries, activating and adjusting the database is mentioned below.

Go to transaction SE14. It will result in below screen.



Please provide table name in the object name text box and select “Tables” radio button and click on edit as shown above. It will result in below screen.








































In the above screen, make sure Processing type is selected as “Direct” and select “Delete data” radio button and click on “Activate and adjust database” button (as shown above).




The above message will appear at the bottom of the screen indicating success of the transaction.

In the above example, I have documented the process to be followed for deleting entries of ALCONSEG table. However, as part of post system refresh activities, this process to be carried out for each of the above mentioned tables.



How to create “transport of copies” related transport request in SAP?

This article answers following queries:

How to take backup of Printer settings, processing groups, logon groups, logical systems, operation mode settings, RFCs, AL11(sap directories), SE03 (transport organizer tools), SM69, oaco(archive related) settings?

How to create “transport of copies” related transport request in SAP?

What is the use of “transport of copies” related transport request in SAP?


Which transaction is used to create transport request in SAP?

-----------------------------------------------------------------------------------

SE01 transaction is used to create transport request in SAP.

As part of pre-refresh steps, we need to take backup of target system’s

  • Printer settings (SPAD)
  • Processing groups (RZ12)
  • Logon groups(SMLG)
  • Logical systems (BD54)
  • Operation mode settings(RZ03/RZ04)
  • RFCs related information(SM59)
  • AL11(sap directories)
  • SE03 (transport organizer tool settings)
  • Batch processing relation information (SM61)
  • Customer entries information (SM69)
  • Archive related settings (OAC0)


If we have backed them up in a transport request, it is easy for us to import them later in the target system. If we haven’t backed them up, we may have to manually create all these entries which will be a tedious and time consuming task. So, we have to backup all these entries.

In the backend, all the above configurations will be stored in specific tables. If we can identify and include those tables in a transport request and export, then we can import it back whenever these settings are required during post refresh.

 We need to create a transport request of type “Transport of Copies” to serve this purpose


To create the same, Go to SAP transaction SE01 à Create Request à select Transport of Copies



Click on Green Check Mark in the above screen.

This will prompt you to create a transport request as seen below



Please provide Short Description for the transport request (in the above screen) and input the appropriate client in Target. Other fields will get populated automatically.

This will create a transport request as shown below.  
























Double Click the transport number and add the tables information (highlighted in yellow in the below paragraph) in the respective columns of the transport request. After that, these configurations can be imported in post refresh stage.


          AL11  – User Directory Entries are contained in the following tables

          R3TR TABU USER_DIR                    Keys   *

          SE03 – System Change Options are contained in the following tables

          R3TR TABU TRNSPACEL     Keys   *
          R3TR TABU DLV_SYSTC      Keys  *

          SMLG/RZ12 – Logon Groups and Processing Groups are contained in the   
          following table.

          R3TR TABU RZLLITAB         Keys   *

         SM59 Connections – RFC connections are contained in the following tables

          R3TR TABU RFCATTRIB      Keys  *
          R3TR TABU RFCDES           Keys  *
          R3TR TABU RFCDOC          Keys  *

          SALE – Logical Systems are contained in the following tables

          R3TR TABU TBDLS          Keys   *
          R3TR TABU TBDLST        Keys    *

          SM69 – Export Customer Entries contained in the following table

          R3TR TABU SXPGCOSTAB  Keys   Y* & Z*

          Oca0 – Archive Settings

          R3TR TABU CREP_HTTP     Keys   *

          SPAD – Printer Settings

          R3TR TABU TSPSV               Keys   *

          SM61 – Batch Processing    

          R3TR TABU TSRVGRP          Keys   *
          R3TR TABU TSRVLST           Keys   *


          RZ03/RZ04 – Operation Modes  & RZ20 settings

          R3TR TABU TPFBA               Keys   *
          R3TR TABU TPFHT               Keys   *
          R3TR TABU TPFID               Keys   *

           
Include all the above tables details in the transport request and save.   

NOTE:  Please make sure to release this transport before the refresh starts.  Otherwise the cofile and datafile will not generated and you will not be able to import this transport later. If we can’t import request, then we may have to create/maintain all these configurations manually which will be tedious and complex task.