SAP BASIS INTERVIEW QUESTIONS:1) How to increase maximum no.of SAP sessions per user?

Important Note: Not recommend to changing the defaults settings and hence not responsible for further consequences occurred due to change in default settings. Please confirm with ur BASIS team before making any change in settings. As most of us know that there is a limit on the no.of SAP sessions per user. The limit for this is of 6 sessions per user. If you want to increase the maximum of sessions per user, Go to t-code RZ10. Enter the appropriate Profile name xxxx and Version xxxx using F4 help and click on Extended maintenance and click on Display. It will open the following screen. Click on Change mode so that you can make the change in no.of sessions. Check if there is any parameter rdisp/max_alt_modes. If not, click on ADD parameter and change the no.of sessions. Else, Click on Change and change the no.of sessions. In my case, I am creating new parameter and hence when I click on New parameter following screen will appear.

2) Change system time zone Login to system and go to the t-code SM30. Enter table name TTZCU and press maintain. Please agree with the warning screen and continue with yes. Here you can maintain system time zone and default time zone. To select a time zone press F4 help and select your time zone, and click on continue. Save your changes and check after restarting SAP R/3 via system status.

3) Differences between the transactions SE09 and SE10. SE09 is a t-code for Workbench organizer. Workbench organizer is the set of utilities for development change management. All development changes are tracked via Workbench organizer.

SE10 is for Customizing Organizer. CO is the set of tools for customizing change management. All ccs are tracked via CO. SE01 is the main screen of the Change and transport Organizer. From here the administrator can achieve all tasks related to transport requests such as create, change, view logs, display client/delivery transports, etc. SE09 and SE10 can also be accessed from here. However, not all developers might be granted access to this transaction.

4) Do we need to really log-out and log-in again to make authorization changes effective? Whenever any changes were made to the user authorizations, normally it is required to log-out and log-in again to make these changes effective. Here is an alternative. Execute the report RSUSR405 in SE38. This would refresh all user-related buffers and changes to the authorizations are made effective immediately. 5) List of transactions executed by a User in a specific period of time. To get the list of transactions executed by a user in a specific period of time: 1)Go to ST03. Select choose for analysis. Choose only one application server at a time in case you have multiple application servers. Choose time period of your choice. 2)In the next screen from menu choose GO TOPROFILESUSER PROFILES. Here you will get the list on users who have worked on that application server. 3)Double click on the required user and you will get all the transactions he/she has executed. 4)In case you select TOTAL in step1 and then follow the steps 2 and 3 you will only get the list of application server on which the user has worked and not the treansaction details.

6) Generating Solution Manager Key?

Following are the steps to generate solution manager key (please note that from ECC5.0, it is mandatory to generate key from solution manager and use it in the SAPINST screens): Go to transaction SMSY. Right click on system entry and select Create new system.

Enter the system name (3 chars), Product (SAP ECC), Product version (can select from the list). Save your entries. Select System --> Other Configuration. Here enter the SID you have created earlier. Enter the Server name or the host name. Click on generate "Installation/Upgrade". Now copy this key on to the SAPINST screen when it prompts for the Solution Manager key.

7) SAP idle session time out / Logging off inactive users? Logging off the inactive users is not set up by default. Setting up the feature of logging off the users improves the security as unattended terminals do not stay active indefinitely. To activate automatic logging off, do the following:Go to Profile Maintenance by choosing Tools --> CCMS --> Configuration --> Profile Maintenance or the transaction RZ11. Maintain the parameter rdisp/gui_auto_logout. Enter the required number of seconds of inactivity before the user is logged off automatically. To deactivate automatic logoff, delete the parameter from the profile(s) or set the value '0'.

8) Understanding the clients 000, 001 and 066? Clients 000, 001 and 066 are standard clients that are pre-delivered by SAP. These clients are not supposed to be used in development, quality and production environments.

Client 000 is basically used as working client only when you do support pack upgrade or ABAP load generations (SGEN) and implementing additional languages, etc. Otherwise, client 000 should not be used as a working client. The same applies to client 001. But the only exception with 001 is, with Solution Manager, 001 will be your working client. You will do all configurations and obtain support from SAP through this client. With other Systems like BW and CRM, this client (001) will not be a working client. Two standard users (SAP* and DDIC) are defined in the clients 000 and 001. The client 066 is used only for EarlyWatch functions (Monitoring and Performance). The

user EarlyWatch is delivered in client 066 and is protected using the password SUPPORT. This password needs to be changed for security purposes.
9) Understanding Background Job Processing? In background processing, the SAP System automatically runs any report or program in the specified time or time intervals. The background processing system starts your job and runs the program(s) that you specify. Afterwards, you can check whether your job was executed successfully and display a log of any system messages. Features:

Running a report in the background does not tie up the SAP sessions you are currently working with. You can shift the execution of reports to the evening or other periods depending on load on the SAP System. Background processing is the only way you can execute long-running jobs.

Background jobs run in a special type of work processthe background work processthat is different from dialog work processes in two ways: A dialog step has a run-time limit that prevents users from interactively running especially long reports. By default, the system terminates any dialog step in a transaction that exceeds 300 seconds. Although the limit can be changed (in the system profile parameter rdisp/max_wprun_time ), it is always in effect for dialog work processes. No such limit applies to background work processes. Background work processes allocate memory differently than dialog work processes so that background work processes can become as large as they need to in allocated memory to allow for processing large volumes of data. 10) Tips on Patch installation?

Patches shouldn't be directly applied on the production system (PRD). We first need to apply it on the development (DEV) system and test the same. Whenever there are patches available for installation, Please make sure that:

Whenever you are applying ABAP and BASIS patches, it is recommended to have one version less than the latest. After you apply these patches, plan for your kernel upgrade which will work better in sync with the new BASIS and ABAP patches. Also, need to check for any SAPGUI patch available, otherwise dumps might error. ABAP+BASIS+Kernel+SAPGUI should be planned together and to be implemented together.

When applying Application Patches, we need to be very careful. This might affect the total functionality and your business process may get affected. Specially when

you have modified many SAP objects to suit your business. 11) Verifying whether a system is Unicode or non-Unicode?

We can verify whether a system is Unicode or non-Unicode by using the command JCMON . This provides you with the version information similar to the following: E:\usr\sap\EP7\JC01\exe>jcmon -------------------jcmon information -------------------kernel release 700 kernel make variant 700_REL DBMS client library compiled on NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10 compilation mode UNICODE compile time Nov 21 2005 20:42:48 update level 0 patch number 0 source id 0.033

--------------------supportedenvironment --------------------database(SAP,tableSVERS)700 operatingsystem WindowsNT5.0 WindowsNT5.1 Windows NT 5.2

12) What is difference between restore and recovery?

Restore is what you do with backups. Take the backup file and turn it back into a database. Recovery is something that SQL does every time it brings a database online. It goes through the transaction log and ensures that the database is transactionally consistent (all transactions that had committed when the DB shut dows are reflected in the data file, all transactions that had not are rolled back). That process of analysis, roll forward, roll back is called recovery.