Basis FAQ

SAP Basis / Netweaver Interview FAQ with answers
1.
How do you troubleshoot a long running transport (or) How actions do you take when
a transport is running for a lot of time (or) How to terminate a long running transport? (or) A
transport is in truck status for unusually long period of time, What could be the reason? How
do you troubleshoot (or) Transport is not getting terminated and all your other transports are
pending to be imported. How to terminate this long running transport?
2.
What is an RFC ? What is the significance of RFC (or) How to create an RFC in SAP
system ? (or) How to different tests you do to check an RFC is functioning well in SAP ? (or)
How to delete an RFC ?
3.
How to configure printer in SAP ? (or) What is the T-code to configure printer in SAP
? (or) How to check the spool requests in SAP?
4.
How to check database size ? (or) What is the size of your R3 or BIW database ?
(or)How to check tablespace details in SAP ? (or) What all can you check or perform with
DB02 transaction ?
5.
How to view database parameters ? (or) Name some of the database parameters ? (or)
How to view database parameters change history ? (or) How to findout which database
parameters are changed after a specific date ? (or) Some parameters are changed at Database
level and after some days performance problems are encountered.You would like to revert the
parameters. How to identify which parameters were changed ? (or) How to view a value set
for a particular database parameter ?
6.
A user complained that he is facing performance issues if he is running a particular
transaction/report. He says all other transactions are running fine for him as well as for
others. How to you troubleshoot this issue ? (or) How to activate a trace for a particular user
in SAP ? (or) What is the transaction to activate trace in SAP ? (or) What are the different
traces that can be taken in SAP or ST05 ? How to do performance analysis of a particular
transaction in SAP ?
7.
Many users are complaining that their transactions are getting completed and they are
encountering TIME_OUT dumps after a very short period. Same is happening well if they are
running them as background job. How do you handle this scenario ? (or) In ST22, you are
frequently encountering TIME_OUT dumps. How do you avoid them? (or) What are the
various reasons for TIME_OUT dumps? (or) What is the parameter in SAP which limits the
maximum permitted runtime in the dialog mode?
8.
You have forgot SAP login password and do not have any other passwords to login.
How do you login to SAP ? (or) How to activate automatic sap* user in sap? (0r) Unable to
login to newly created client with sap* and default password. How to login now? (0r) Sap*
user got locked. Do not have any other user id to unlock the same. How to login to system
again?
9.
What is lock table overflow ? (0r) How to identify lock table over flow issue ? (0r)
What is the parameter to be changed to increase lock table size in SAP ? (0r) What is the
reason for lock table overflow ? (0r) How to resolve lock table overflow?
10.
What are the prerequisites and uses of config tool ? (or) What are the prerequisites
and uses of Visual Administrator ? (0r) What are the limitations of Config tool ? (0r) What is
the difference between Config Tool and Visual Administrator tools in SAP?
11.
What is spool overflow ? (0r) How to delete old spool requests ? (0r) How to
troubleshoot spool overflow ? (0r) How to avoid spool overflow issue ? (0r) How to check
spool numbers? (0r) How to set the spool number in SAP ? (0r) How to define storage
location (Temse) of spool requests ?
12.
What does spool request contain ? (0r) Where is the spool request stored ? (or) What
are different Spool statuses and their significance? (0r) Which workprocesses will create
spool requests? (0r) What is the difference between spool request and output request ? (0r)
Which workprocess will create output request or print request?
13.
What is the database administration tool supported by SAPfor oracle database? (0r)
What is BRTOOLS ? (0r) How to access BRTOOLS ? (0r) How to add or extend datafiles in
sap system based on oracle database?
14.
How to check the update status ? (Or) What is the reason for update deactivation ?
(0r) How to activate or deactivate the update ? (Or) What is the parameter to be set to switch
off automatic update deactivation ? (0r) How to troubleshoot, if update got deactivated ? (0r)
What happens for the updates that are in progress, if update got deactivated ?
15.
What is a workprocess ? (0r) What are the different types of workprocesses and their
functionality ? (Or) How to increase/decrease the number of workprocesses?
16.
What is a SAP lock ? (0r) Different types of SAP locks ? (Or) Difference between
Write lock(E) and Enhanced write lock(X) ? (Or) How to monitor SAP locks ? (Or) How to
delete SAP locks ?
17.
How to configure an Early watch Alert Report in Solution manager?
18.
Explain Oracle architecture.
19.
How to apply a SAP note?
20.
How to perform Kernel Upgrade?
21.
A user complaints to you that a background usually takes 3hrs to run but it is already
6hrs completed and still the job is running. How to analyse the issue ?
22.
Do you have experience in handling SCM system? If yes, how to you start or stop
livecache in SCM or APO(Advanced Planning and optimiser) system?
23.
If a java stack is down ? How do you troubleshoot?
24.
If in a java only system, administrator user id got locked, how do you resolve this
issue?
25.
How to create a server node in Java based SAP system?
26.
In system refresh activity, database restoration is done and sap system is up. Now,
what are the poststeps system refresh steps that you perform ?
27.
How do you analyze an expensive SQL statement?
28.
What do you know about Willy introscope agent ? What is the use of willy introscope
? What is the version of willy introscope that you have implemented ?
29.
What is the transaction to perform support pack upgrade in ABAP stack ?
30.
Your SAP systems are based on which operating system ? What is the version of
operating system do you use?
31.
What is the transaction code to be used to view your own spool requests in SAP ?
32.
Apart from update work processes what are the other work processes that can do the
update task ?
33.
What is the transaction code to be used to perform Java support pack upgrade ?
34.
How to you apply license for an ABAP stack of an SAP system ?
35.
How do you monitor livecache in SCM or APO systems (or) What is the transaction
code used to monitor livecache in SCM or APO systems?
36.
What is TREX ? What does TREX stands for ? What is TREX used for ?
37.
What is the name of the database on which your TREX runs in your landscape?
38.
What is the need of TREX in BIW system?
39.
What are the functions of TREX?
40.
What is the tool provided by SAP for performing sizing of a project?
41.
How to Unlock if SDM user got locked in SAP ?
42.
What is the memory allocation sequence to a non dialog work process in SAP ?
(background, update, enqueue and spool workprocesses in SAP? What are the SAP
parameters used to define initial roll area, extended memory, heap memory, roll area ? What
is the memory allocation sequence to non dialog work processes in Windows NT?
43.
What is the memory allocation sequence to a dialog workprocess in SAP?
44.
Name the different SAP profiles and their start sequence.
45.
How to perform CPA cache refresh in XI or PI system?
46.
How to import a transport manually at Os level ?
47.
What are the different java monitoring checks you perform daily ?
48.
What are the different SAP user types ?
49.
What are the different types of RFC communication in SAP ?
50.
How do you access service market place ?
Answer : Troubleshooting long running transport

Go to transaction STMS_IMPORT and identify the transport which is running since a long
duration.
In the below screenshot, transport with the truck symbol is the long running one
Issue could be due to following reasons :

1) Non availability of space to perform the operation (i.e filesystem or tablespace is
100% full)
Solution :
Check out if any of the filesystems (like sapmnt, oraarch etc) of the Central Instance,
Database and application servers is 100% full. If so, please add necessary space, which
resolves the issue automatically and completes the import of transport.
Also, check out tablespaces fill levels. If autoextend is off and tablespace is 100% full
then add sufficient datafiles, which resolves the issue
2) RD* jobs are not running in SAP system
Solution : Check out in SM37 whether RDD* jobs(RDDIMPDP, RDDIC3L, RDDVERSL
etc) are running or not. If not, please make sure they are scheduled and perform the import of
the transport again.
3) Update got deactivated
Solution : Checkout in SM13 whether update is active or not. If it is not active, activate it
and import the Transported to Production System.
4) There are no free background workprocesses
Solution : Check in SM50 whether all background workprocesses are in running status. If so,
you will need to wait for the free background workprocess to run RDD* jobs to complete the
import of the transport. To avoid this issue in future you may increase the number of
background workprocesses
Transport is not getting terminated. How to do terminate?

1) If you are unable to terminate a transport which is running, goto SM50 and identify the pid
of the transport process. Try to cancel the process with core or without core as shown below.
2) If it is not getting terminated from SAP level, then go to O/s level and kill.
Command for the same in AIX or HP-UX is kill -9 <PID>
If it is not getting killed from o/s level also, try to search for processes related to tp or R3trans
and kill them as well
Eg in AIX or HP-UX : ps ef |grep tp
Or
ps ef |grep r3trans
3) If it is not getting terminated from that level, you may try to kill as shown below at SAP
level :
Goto Import monitor and
Navigate as below and right click and delete entry to delete the transport which is being
imported
By any one of the above 3 methods, transport will surely get terminated. So then you can add
to queue again and re-import
2) What is an RFC ? What is the significance of RFC (or) How to create an RFC in SAP
system ? (or) How to different tests you do to check an RFC is functioning well in SAP ? (or)
Answer : How to create an RFC Connection in SAP ?
Go to SM59 transaction :
Click on create icon in the above screen, which leads to below screen
Specify RFC Destination name and description and connection Type in the above screen
Please note respective connection type to be selected from dropdown based on the connection
required. Usually 3 is for ABAP system. (Pls find screenshot below)
In the below screen, please select load balancing radio button based on your system setup (i.e
if there is load balancing configured for your system, specify it as yes otherwise no)
Please provide Target host details like hostname or ipaddress and system number as below:
As shown below, Proceed to Logon & security tab and provide following details :
Select trusted system as no, in case you would like to connect to a system with a user id and
password.
If you dont want to get authenticated by credentials specify the system as trusted system
which wont prompt to enter user id/pwd credentials in the below screen.
Please provide Language details like EN (for English), Client details, User id and password
for the system you would like to create a connection.
Please leave default values in other tabs (i.e MDMP & Unicode, Special options,
Administration) and then click on Save to complete the RFC creation.
How to Test RFC connection ?
If it functioning well it should show output similar to below screen :
If this is fine, come back to earlier screen and execute Unicode test by clicking the button.
Output similar to below screen, should be displayed if connection is OK
Also you need to perform authorization test to make sure user id / password credentials
provided are correct.
Please navigate as below and perform the test :
Navigate to Utilities -> Test -> Authorisation test and click the same to execute.
If the RFC configuration is fine, screen shot similar above will appear. Otherwise an error
will be displayed based on which you need to troubleshoot to fix the issue.
Goto SM59 and select the RFC that is to be deleted as shown below :
And click on delete icon
Click yes to confirm deletion, which deletes the RFC.

Click on Connection test tab to check the connection for the RFC
3) How to configure printer in SAP ? (or) What is the Tcode to configure printer in SAP ?
(or) How to check the spool requests in SAP ?
Answer : How to configure printer in SAP ?
Goto SPAD transaction
Click on display button of Output Devices, to display list of output devices as below :
Click on change button to view below screen and click on create button to get below screen
As shown above, Please specify :
Output device name

Shortname
Device type
Spool server
Device class details
In the next tab, please specify host spool access method, host printer details
In the other tabs, please leave the default settings and press save which creates an output
device.
How to take a print in SAP ?
To take the printout, goto any transaction and after listing the contents, click on printer icon
to view the below screen.
In the above screenshot, select the output device (i.e new device that is created now) as below
After selecting the output device, click on ticket mark to confirm to print.
After this, a spool request will get generated as above.

How to check the spool requests generated in SAP ?
This spool request can be viewed in SP01 transaction as below :
Click on execute to view the below list of spool requests
4) How to check database size ? (or) What is the size of your R3 or BIW database ? (or)
How to check tablespace details in SAP ? (or) What all can you check or perform with DB02
transaction ?
Answer : How to check database, tablespace sizes in SAP ?
Goto transaction DB02 and navigate to Space -> Space overview to view
Database name
Database system
Size
Free size
Used percentage
Number of database users
Number of tablespaces
Number of tables and size
Number of indexes and size
In DB02, navigate to Space -> Space overview to find all the above mentioned details
How to check the users that are present in database at SAP level ?
In DB02, navigate to Space -> Users -> Overview as below
How to check various tablespaces in SAP and their sizes ?

In DB02, navigate to Space -> Table spaces -> Overview to view tablespaces details as
below.
5) How to view database parameters ? (or) Name some of the database parameters ? (or)
How to view database parameters change history ? (or) How to findout which database
parameters are changed after a specific date ? (or) Some parameters are changed at Database
level and after some days performance problems are encountered.You would like to revert the
parameters. How to identify which parameters were changed ? (or) How to view a value set
for a particular database parameter ?
Answer : How to view database parameters at SAP level ?
Goto transaction DB02 and navigate to Additional Functions -> Database parameters
as shown below :
Click on Active parameters tab to view active database parameters
How to view SPFILE parameters at SAP level ?

Click on SPFILE tab to view SPFILE parameters
How to view database Parameters history at SAP level ?

Click on parameters history tab to view the parameters that are changed in the recent past.
In the above screen click on Show parameters history. It displays window as below:
Provide the date from which you would like to view the database parameter changes.
And then click on tick mark to view the database parameter changes from the selected date.
How to export the database parameters to an excel sheet ?
Click on export button (highlighted below) and select table as the output as shown in below
screen and the parameters can be exported to an excel or word as per the selection by you.
6) A user complained that he is facing performance issues if he is running a particular

transaction/report. He says all other transactions are running fine for him as well as for
others. How to you troubleshoot this issue ? (or) How to activate a trace for a particular user
in SAP ? (or) What is the transaction to activate trace in SAP ? (or) What are the different
traces that can be taken in SAP or ST05 ? How to do performance analysis of a particular
transaction in SAP ?
Answer: How to activate a Trace for a user in SAP system ?
What are the different types of traces in SAP ?
SQL Trace (Trace for SQL statements)
Enqueue Trace (Trace for enqueue/lock requests, waiting etc)
RFC Trace
Table Buffer Trace

How to activate a Trace for a user in SAP system ?
Goto transaction ST05 and you will get the below screen :
Select the type of trace you would like to activate and press activate trace to start tracing.
Please find below functionality of various functions in the above screenshot :
Activate Trace : This is used to activate the trace for the same user who is starting the trace
Activate Trace with Filter : This functionality is used to trace the activity of a different
user(other than the user who is starting the trace) and filter can be done to trace a specific
transaction or program.
Deactivate Trace : This functionality is used to deactivate the trace
Display Trace : This functionality is used to display trace
Click on tick mark to display the trace
Click on Yes to display the trace as below:
Enter SQL Statement : This functionality is used to analyse an SQL statement

Click on this pushbutton to view the below screen :
Trace Status : This area is used to inform about the status of the trace at that point of time
like traces activated, deactivated etc
Guidelines for activation of performance trace

1.
If you are tracing a particular activity of a user, please make sure that the particular
user is not performing any other activity in the system. Otherwise trace file will be difficult to
analyze. For reasons of simplicity, please request user to perform only one activity while the
trace is activated.
2.
Please make sure that no background jobs or update processes are running in that SAP
for that particular user whose activity is being traced. Otherwise trace wont be clear
3.
By default, SQL trace is selected in ST05 transaction. Incase you would like to trace
others( like RFC trace, buffer trace) please activate them also.
4.
Normally we are interested in the buffer load processes that get recorded while tracing
an activity through SQL trace. Therefore, it is suggested to execute the program or activity
that is to be traced once before actually tracing it so that all the buffer loads processes will
happen. In the next run, since buffers were already loaded SQL trace doesnt capture unnecessary details related to buffer load which makes it easy to analyze the trace.
5.
In cases of distributed SAP system, where there are number of application servers
then you need to activate the trace in the particular application server where the user is
performing the activity. In other words, trace wont get recorded if you activate trace in one
application server and user is performing the activity in another application server.
6.
If you would like to record a trace for background job or for an update request in a
distributed SAP system, it is suggested to activate the trace in all the application servers that
are present in the SAP system. This is required because you will never know to which
application server the particular request goes for execution.
If you are tracing an activity of any other user you can look at following monitors during the
trace :
Workprocesses overview (SM50/SM66)

Operating system monitor of Database server to identity any CPU bottlenecks in
database server)
Database process monitor for monitoring the execution of SQL statements
Profile parameter settings for Performance Trace (ST05):

Please note that trace cannot be taken for very long duration as the size of the trace file is
limited as set by SAP profile parameter. When the trace file is full, the oldest entries are
deleted or overwritten by the newest entries i.e. writing to the trace file is cyclical.
The SAP profile parameter rstr/max_diskspace is used to set the size of the trace file in a SAP
system. The default trace file size is 16MB
For a trace file, default file name also can be set using the SAP profile parameter rstr/file.
7) Many users are complaining that their transactions are getting completed and they are
encountering TIME_OUT dumps after a very short period. Same is happening well if they are
running them as background job. How do you handle this scenario ? (or) In ST22, you are
frequently encountering TIME_OUT dumps. How do you avoid them? (or) What are the
various reasons for TIME_OUT dumps? (or) What is the parameter in SAP which limits the
maximum permitted runtime in the dialog mode?
Answer: How to avoid TIME_OUT dumps in SAP system ?
These TIME_OUT dumps usually occur if the program has exceeded the maximum permitted
runtime without interruption. After this program will get terminated and in ST22 a dump will
get generated.
Usually SAP system will terminate the program after permitted runtime to make the work
area available to other users who may waiting and to prevent a work area being blocked
unnecessarily long time like
Eg: Database accesses without a suitable index (Full table scan)
Database access with a large result set
Endless loops (DO, WHILE) etc
In SAP, there is a parameter rdisp/max_wprun_time which limits the maximum permitted
runtime without interruption. By default this value is set to 600 seconds. However, if you are
frequently encountering more dumps in SAP system due to this, you can consider increasing
this value to 3600 seconds to avoid this issue.
How to change sap parameter ?

SAP parameter can be set using RZ10 transaction. Go to RZ10, select the respective instance
profile of the application server on which you would like to change the parameter.
From the dropdown of profile, select the instance profile (of the application server) on which
you would like to change the parameter.
After selecting the profile, select extended maintenance button and press change push button.
It displays a screen with all the parameters as shown below :
You can either search the parameter or create the parameter and then set the value to the
desired and save the same as below.
Set the parameter value in the text box provided and click copy button to copy the same and
then press back button and press copy again in the next screen. After that press the back
arrow to come to the following screen
Click on Save button to save and activate the profile.
Press no to goto the next screen
Press yes, to activate the profile.
The parameter will take effect after restart of the application server
8) You have forgot SAP login password and do not have any other passwords to login. How
do you login to SAP ? (or) How to activate automatic sap* user in sap? (0r) Unable to login
to newly created client with sap* and default password. How to login now? (0r) Sap* user got
locked. Do not have any other user id to unlock the same. How to login to system again?
Answer : How to activate automatic sap* user in sap?
In SAP, there is a parameter login/no_automatic_user_sapstar whose default value is 1. If the
value is set to 1, automatic login of sap* into SAP system using password PASS wont be
allowed.
In all of the above scenarios,
Pls set the value of parameter login/no_automatic_user_sapstar to 0 in both the default profile
and the instance profile and restart the instance. So automatic login of sap* with default
password will be enabled.
How to change SAP parameter ?

Afterwards, connect to the database and execute the following command :
In the following example am considering, oracle as the database.
sqlplus / as sysdba
SQL > Delete from SAPSR3.USR02 where MANDT=000 and BNAME=SAP*;
In the above command, SAPSR3 is the schema of the database and USR02 is the table name
and MANDT is the client and BNAME is the user id.
In case you would like to activate sap* in client 500 and your schema name is SAPBPW then
the command would be as below :
SQL > Delete from SAPBPW.USR02 where MANDT=500 and BNAME=SAP*;
Once you successfully executed this command, you can login to sap system with SAP* user
id and default password PASS.
Activating emergency user in java only system
What are the scenarios in which emergency user SAP* to be activated?
In some cases, you might have configured user management incorrectly and can no longer
logon to any application or all administrator users got locked. In these cases, you can activate
emergency user SAP* which enables you to logon to application.
Process to be followed to activate emergency user SAP*

Start the config tool
Set the following User Management Engine(UME) properties
Property
Value
Remarks
ume.superadmin.activated
True
This activates SAP* user
ume.superadmin.password
<password>
Enter the new password for

SAP* user. This option is
provided by SAP to ensure
more security so that system
is not accessible with default
password
Restart the AS Java

The SAP* user will now get activated and all others user will get deactivated. You can log on
with the SAP* user and fix your configuration as per the requirement in cases of incorrect
user management configuration.
After that, go to identity management to unlock all the locked users.
After fixing the configuration issue, SAP* user should be deactivated again as mentioned
below:
Start the config tool
Set the property ume.superadmin.activated to false
Restart the AS Java.
Please note all the above process to activate emergency user is for standalone java system.
How to handle, if administrator user id got locked in dual stack system?

In case of dual stack installation i.e. ABAP + JAVA stack it is very easy. Please proceed as
mentioned below to resolve the issue:
i) Logon to ABAP system with any administrator user or the SAP* user
ii) Either create a new administrator user for java stack or unlock the locked administrator
user using SU01
9) What is lock table overflow ? (0r) How to identify lock table over flow issue ? (0r) What is
the parameter to be changed to increase lock table size in SAP ? (0r) What is the reason for
lock table overflow ? (0r) How to resolve lock table overflow?
Answer : What is lock table over flow ? How to resolve lock table overflow issue ?
What is lock table overflow ?
SAP manages locks using lock table. The lock table contains all of the informaton related to
locks like who is holding the lock and which locks are currently held etc. The size of the lock
table can be specified by the SAP parameter enque/table_size. The size of the lock table
limits the number of locks, lock owners and lock names. If this size is exceeded, then the lock
table overflow occurs.
How to identify lock table overflow issue ?
In SM21 transaction log and ST22 dumps, if you find any error messages like
LOCK_TABLE_OVERFLOW, Lock table overflow, Internal lock administration error it
means there is a lock table overflow issue.
What is the parameter to be changed to increase lock table size in SAP ?

Parameter enque/table_size to be changed to increase or decrease lock table size using RZ10
transaction. Default value of this parameter is 32768. The min value that can be set is 4096
and max value is 102400. The unit for this parameter is KB.
How to change SAP parameter ?
As this is not dynamic parameter, for the new value to take effect, a system restart is required
after modifying the parameter.
What is the reason for lock table overflow ?
A lock table overflow can occur due to
The lock table is configured too small (i.e value set to enque/table_size parameter is
very low)
Due to improper design of application which sets a large number of locks
Number of enqueue worprocesses configured in a sap system are less and update is
very slow/hanging due to which lots of locks are accumulated in lock table
Running a custom report with improper selection criteria (like very long time periods
data pull) which sets so many locks & eventually lock table overflow occurs
How to resolve lock table overflow ?
Increase the size of lock table i.e increase the parameter enque/table_size value using
RZ10 transaction.
To determine the optimal value for this parameter, you can check the maximum locks set so
far in the history and the current number of locks set from SM12 -> Extras -> Statistics
Increase the number of enqueue workprocesses
How to increase the number of workprocesses?

A work processes is used to execute a particular type of job in an sap system.
There are different types of workprocesses as mentioned below :
DIA (Dialog workprocess) : Used for execution of dialog steps triggered by active users.
For every dispatcher atleast 2 dialog workprocesses to be configured
UPD (Update workprocess) : Used for execution of update tasks. Atleast one update
workprocess to be configured per SAP system. Also, more than one UPD can be configured
for a dispatcher
BTC (Background workprocess): Used for executing background jobs. Atleast 2
background workprocesses to be configured for an SAP system
SPO (Spool workprocess) : Used for passing sequential data to printers. Atleast one spool
workprocess to be configured for an sap system.
UP2 (Update2 workprocess) : This is similar to UPD workprocess. There is small difference
in functionality based on criticality of the update.
ENQ (Enqueue workprocess) : This is required to administer locktable in the shared
memory. Locktable contains database locks for ABAP stack of an sap system. Only one
enqueue process to be configured for an SAP system.
To increase/decrease the number of workprocesses, value to be changed accordingly for the

following parameters as per workprocess in RZ10 Transaction.
rdisp/wp_no_dia (for dialog workprocess)
rdisp/wp_no_btc ( for background workprocess)
rdisp/wp_no_spo (for spool workprocess)
rdisp/wp_no_enq (for enqueue workprocess)
rdisp/wp_no_vb (for update workprocess)
rdisp/wp_no_vb2 (for update2 workprocess)
In RZ10 transaction, select the profile of the instance, for which workprocess number to be
changed and edit the profile through extended maintenance and save the changes done and
activate the profile.
Please note that as this parameter is not dynamic one, restart of the application server is
required for the changes to become effective.
What is the difference between dynamic and static parameter
In SAP, parameters are used to set the configuration and define the functionality of an sap
system like number of workprocesses, buffer size, locktable size etc.
Basically there are 2 types of parameters :
Static
Dynamic
Static are the parameters those won't take effect immediately the value is set. Restart of an
sap system is required for them to take effect.
Dynamic are the parameters those will take effect immediately in the run time. Restart of an
sap system is not required for them to take effect.
Parameter can be differentiated whether it is dynamic or static by checking in RZ11
transaction of SAP.
In RZ11, type the parameter and display it. In the screen , there will be a check box with
description as "Dynamically switchable". If that check box is ticked, it means that it is
dynamic parameter and value can changed in run time without restart of the system. If it is
not ticked, then it is static parameter and it needs restart of a sap system for the changes to
take effect.
10) What are the prerequisites and uses of config tool ? (or) What are the prerequisites and
uses of Visual Administrator ? (0r) What are the limitations of Config tool ? (0r) What is the
difference between Config Tool and Visual Administrator tools in SAP?
Answer : What is the difference between Config Tool and Visual Administrator tools in
SAP?
Config Tool and Visual Administrator(VA) are the administration and configuration tools in
SAP Netweaver AS Java.
What are the prerequisites and uses of config tool ?
The prerequisite for the config tool is database must be running, as this tool is used to
maintain the SAP Netweaver AS Java settings in the database. It is not necessary that Java
should be running to use config tool.
Uses of config tool :
The Java Virtual Memory(JVM) settings can only be maintained with the config tool.
Configuration of services and managers can be done with config tool
Limitations of Config tool :
Remote configuration cannot be done by Config tool
Start or stop of java cannot be done through config tool
Change of parameters at run time is not possible
What are the prerequisites and uses of Visual Administrator ?

With visual administrator, we can logon to the P4 port of the AS Java. Hence both database
and java should be running. This is the prerequisite for VA.
Uses of Visual Administrator :
Configuration of services and managers can be done

Remote configuration can be done ( It means VA can be installed and used for
configuration in any host on which SAP Netweaver AS JAVA is not installed
Starting and stopping services can be done
Stopping an SAP NW As java instance can be done
What is the difference between Config Tool and Visual Administrator tools in SAP?
Java Virtual Machine parameter settings can only be done through Config tool. VA
cannot be used for this
To use VA, SAP Netweaver AS Java should be running but for config tool it is not
required
Changes to selected parameters can be done at run time through VA, which is not
possible with Config tool.
AS Java can be started/stopped by VA which is not possible by Config tool
Remote configuration can be done by VA but not by config tool
How to open config tool?

Config tool is mainly used to set JVM parameters in SAP.
In this article, am covering on how to open config tool (with screenshots) in Microsoft
windows environment :
Goto respective drive and navigate as follows
usr -> sap -> <SID> -> DVEBMGS** -> j2ee -> configtool (shown in below figure)
and double click on configtool.bat file.
This run a batch file and opens up another screen as follows and prompts you to confirm
whether you want to use default DB settings.
Click on Yes and confirm the same.

This opens up config tool, where various parameters can be viewed/maintained
Procedure of opening config tool in Unix is same as above.

i) To be navigated to /usr/sap/<SID>/DVEBM*/J2ee/Configtool
ii) Execute ./configtool.sh script
This opens up the config tool as above.
Note : Only difference is here, script need to be run instead of a bat file in windows.
11) What is spool overflow ? (0r) How to delete old spool requests ? (0r) How to
troubleshoot spool overflow ? (0r) How to avoid spool overflow issue ? (0r) How to check
spool numbers? (0r) How to set the spool number in SAP ? (0r) How to define storage
location (Temse) of spool requests ?
Answer : what is spool overflow ? How to troubleshoot spool overflow issue ?
What is spool overflow ? :
Spool request that got generated are stored in a temporary sequential file called Temse.
Please note that these are stored in Temse because these are not stored permanently. The size
of the Temse is limited by the parameter definition.
The default size of Temse is 32,000 and it can be increased till 2 billion. However, defining
very high value can effect the database performance. Due to limited storage capacity of
Temse, when this file got full, this throws an SAP spool overflow error.
If this happens, customers could not print from SAP. If you check in SM21 and ST22
transactions, you may encounter some error log or dumps like
ERROR IN SPOOL call : SPOOL OVERFLOW

SPOOL_INTERNAL_ERROR
System internal error in the spool system
How to troubleshoot spool overflow ?

To resolve this spool issue, some of the old spools can be deleted from the sap system. Goto
transaction SPAD. From the initial screen, navigate to Administration -> Clean_up_spool.
Once you click this, Spool Administration : Delete old spool requests screen will be
displayed.
In that screen, you will be prompted to choose requests for deletion like
Old spool requests older than the maximum set age

Requests already printed
All spool requests
and enter value for minimum age (in days) text box.
Select the check boxes as per the requirement (eg: delete all requests already printed and
minimum age in days equal to 30 days) and execute to delete old spool requests, which will
clear Temse and will resolve spool over flow issue.
Apart from this there are others ways of resolving spool overflow issue. They are
1) Run the report RSPO0041 from SE38 transaction to delete old spool requests
2) Run the report RSPO0043 from SE38 transaction, which checks the Temse/spool
consistency and reorganizes the spool
How to avoid spool overflow issue ?
These reports RSPO0041 and RSPO0043 should be scheduled as background jobs

with proper variants on a periodic basis which avoids spool overflow issue.
You can try to increase the spool numbers from default 32000 to a bit higher value but
please note donot set this too high as it may impact database performance
Proactive monitoring check can be made in RZ20 transaction to see how much is the
fill level of spool numbers.
How to check spool numbers ?
To check spool numbers : Goto RZ20 transaction, navigate to SAP CCMS Monitor
Templates -> Spool System.
Here you can check the status of spool servers and the used numbers percentage of spool
numbers. If you find that used numbers is greater than 80%, you can manually run above
mentioned reports or delete old spool requests from SPAD tcode as mentioned earlier.
How to set the spool number in SAP ?

Using Transaction SNRO (Number range object maintenance) and object SPO_NUM, you
can set the spool number in an SAP system.
Once you provide object as SPO_NUM, click on change icon. It displays another screen. In
that screen, click on Number Ranges push button. It displays another screen "Number range
for spooler numbers". Click on change icon here and set the value of spooler(from number
and to number). Please note that a change request may be generated here based on the client
settings(if automatic recording of changes is set in SCC4 transaction of the client)
How to define storage location (Temse) of spool requests ?
Every Temse object contains a header in TST01 table and the actual object. This can be either
stored in table TST03 or in file system. You can set a parameter rspo/store_location in RZ10
to define whether to store Temse objects TST03 table or in filesystem.
If value G is set to this parameter, it will be stored in filesystem and if it is db it is stored in
TST03 table.
12) What does spool request contain ? (0r) Where is the spool request stored ? (or) What are
different Spool statuses and their significance? (0r) Which workprocesses will create spool
requests? (0r) What is the difference between spool request and output request ? (0r) Which
workprocess will create output request or print request?
Answer : What are the different Spool statuses and their significance?
What does spool request contain ?
Spool request contains detailed information regarding printer model, formatting to be done on
the data to be output.
Where is the spool request stored ?
The spool request that is generated is stored in the Temse( temporary sequential file)
What are different Spool statuses and their significance?
Spool requests will have different statuses like
Completed (The output request printed successfully)
Waiting (Spool request is in waiting status and spool system has not yet processed the
output request and not yet sent to the host system)
Inprocess (The spool workprocess is in the process of formatting output request for
printing)
Printing (The host spool is in the process of printing the output request
Problem (This indicates there are some minor errors. It means output request printed
but contains some errors like incomplete character set etc)
Error (This status indicates some serious issues such as network error. It means the
requests have not printed and they remain in the spool system until they are deleted or until
they reach their expiration date. After expiry date, they are deleted by the reorganisation jobs.
Archive (This status is set for spool requests that are sent to an archiving device. This
status means that the spool request was already processed by the spool system and it is now
waiting to be archived)
Time (This status means that the user who has created the spool has mentioned some
specific time for output)
- ( This minus status means that the spool request is not yet sent to the host system
and no output request exists)
+ ( This plus status means that the spool request is being generated and it is stored in
the spool system )
Which workprocesses will create spool requests? :

Spool requests will be created by dialog or background workprocesses. Please note that spool
work processes donot create spool requests
What is the difference between spool request and output request ?

Spool request contains detailed information regarding printer model, formatting to be done on
the data to be output. Output request contains all the data in the format that the printer
understands.
A spool workprocess formats the data specified in the spool request and generates the output
request. Output request is also termed as print request.
Which workprocess will create output request ?
Output request will be created by spool workprocesses.
13) What is the database administration tool supported by SAPfor oracle database? (0r)
What is BRTOOLS ? (0r) How to access BRTOOLS ? (0r) How to add or extend datafiles in
sap system based on oracle database?
Answer: How to add or extend datafiles in sap system based on oracle database ?
What is BRTOOLS?
BRTOOLS is the database administration tool supported by SAP for oracle database.
How to access BRTOOLS ?
BRTOOLS can be accessed by logging into database host as ora<sid> user and calling
brtools at the command prompt.
How to add or extend datafiles in sap system based on oracle database?
Once brtools is called at command prompt, following menu will be displayed
BR*Tools main menu
1 = Instance management
2 - Space management
3 - Segment management
4 - Backup and database copy
5 - Restore and recovery
6 - Check and verification
7 - Database statistics
8 - Additional functions
9 - Exit program
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
======================================
Select option 2 - Space management from the above query and press c to continue.
It displays another screen as below :
Database space management
1 = Extend tablespace
2 - Create tablespace
3 - Drop tablespace
4 - Alter tablespace
5 - Alter data file
6 - Move data file
7 - Additional space functions
8 - Reset program status
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
=============================================
Select Option 1- Extend tablespace and press continue.
In the next screen, you will be prompted to enter tablespace name, size/location of new
datafile to be added, initial filesize, maximum filesize, autoextend (yes/no). Please provide all
the relevant details and you can see an SQL query is being built based on the inputs given by
you.
Once all the inputs are provided, press continue to execute the command and the datafile will
be added.
14) How to check the update status ? (Or) What is the reason for update deactivation ? (0r)
How to activate or deactivate the update ? (Or) What is the parameter to be set to switch off
automatic update deactivation ? (0r) How to troubleshoot, if update got deactivated ? (0r)
Answer: Update got deactivated. What are the reasons for update deactivation. How to
activate the update?
Update status check :
Update status can be checked in transaction SM13.
Reasons for update deactivation :

Update will get deactivated in cases of serious database problems.
Some of the examples of update deactivation and solutions for those are given below :
1) Update will get deactivated when oraarch is full
Solution : Trigger archivelog backup and ensure sufficient space is left in oraarch and then
activate the update manually
2) When some critical tablespaces are 100% full and database is not able to perform some
operations
Solution : Monitor the database and findout the tablespaces which are 100% full. Add
necessary datafiles and ensure there is enough free space left out in them. Then activate the
update manually
How to add datafiles in sap system based on oracle database ?
How to activate or deactivate an update in sap ?

Use transaction SM14 and goto update tab. There update status can be viewed with a push
button. If it is in deactivated status, click it to activate and viceversa.
How to switch off automatic update deactivation ?

In RZ10, set the parameter rdisp/vb_stop_active to 1 and activate the profile to switch off
automatic update deactivation incase of database problems.
How to troubleshoot, if update got deactivated ?

Please perform the following steps if udpate got deactivated :
Check all the tablespaces and ensure figureout if any tablespace is 100% full. If so,
add necessary space and activate the update as mentioned above
Check if oraarch is full. Trigger archivelog backup and ensure there is enough space
and activate the update again
Check SM21 log and ST22 dumps
Check workprocess trace for any other issues

If update got deactivated all the updates that are in progress or waiting to get executed, won't
be cancelled. They will be assigned either init or auto status. Once the database issue got
fixed and update is activated again, all these updates which are in init or auto status will
resume again
15) What is a workprocess ? (0r) What are the different types of workprocesses and their
functionality ? (Or) How to increase/decrease the number of workprocesses?
Answer : How to change the number of workprocesses?
A work processes is used to execute a particular type of job in an sap system.
There are different types of workprocesses as mentioned below :
DIA (Dialog workprocess) : Used for execution of dialog steps triggered by active users.
For every dispatcher atleast 2 dialog workprocesses to be configured
UPD (Update workprocess) : Used for execution of update tasks. Atleast one update
workprocess to be configured per SAP system. Also, more than one UPD can be configured
for a dispatcher
BTC (Background workprocess): Used for executing background jobs. Atleast 2
background workprocesses to be configured for an SAP system
SPO (Spool workprocess) : Used for passing sequential data to printers. Atleast one spool
workprocess to be configured for an sap system.
UP2 (Update2 workprocess) : This is similar to UPD workprocess. There is small difference
in functionality based on criticality of the update.
ENQ (Enqueue workprocess) : This is required to administer locktable in the shared
memory. Locktable contains database locks for ABAP stack of an sap system. Only one
enqueue process to be configured for an SAP system.
To increase/decrease the number of workprocesses, value to be changed accordingly for the
following parameters as per workprocess in RZ10 Transaction.
rdisp/wp_no_dia (for dialog workprocess)
rdisp/wp_no_btc ( for background workprocess)
rdisp/wp_no_spo (for spool workprocess)
rdisp/wp_no_enq (for enqueue workprocess)
rdisp/wp_no_vb (for update workprocess)
rdisp/wp_no_vb2 (for update2 workprocess)
In RZ10 transaction, select the profile of the instance, for which workprocess number to be
changed and edit the profile through extended maintenance and save the changes done and
activate the profile.
Please note that as this parameter is not dynamic one, restart of the application server is
required for the changes to become effective
16) What is a SAP lock ? (0r) Different types of SAP locks ? (Or) Difference between Write
lock(E) and Enhanced write lock(X) ? (Or) How to monitor SAP locks ? (Or) How to delete
SAP locks ?
Answer : How to delete an SAP lock ?
SAP lock is set by the executing workprocess when a user/job wants a change access to data.
Whenever a lock to be set the respective workprocess checks in the locktable whether a
respective lock conflicts the existing entries in the locktable. If so, a lock is refused. If there is
no conflict, then a lock is set.
There are different types of locks :
Write locks (E) : This is also known as exclusive lock mode as the lock data can be edited by
only one user. Any other requests from workprocesses to set another write lock or read lock
are rejected. A cumulate lock can be applied on the lock data by the same lock owner again.
Read locks (S) : This is also known as shared lock mode as several users can have read access
to the locked data at the same time. Additional read lock requests are entertained even if they
are from different users. However a write lock is rejected.
Enhanced write locks (X) : This is also known as exclusive non-cumulative lock mode. An
enhanced write lock can be requested only once even if it is by the same transaction.
Difference between write locks(E) and Enhanced write lock(X) is write locks can be set and
released by the same transaction several times but X type locks can also be set once even by
the same transaction.
Optimistic locks (O) : These locks are set up when the users displays the data in change
mode. Several optimistic locks can be setup on the same data. Optimistic locks are read
locks(S) at first and converted to write lock (E) when the users wants to save the data. If an
optimistic locks on a data is changed to write lock(E), all other optimistic locks on that data
will be deleted.
Locks that are set by an application program are released by the program itself or they are
released by the update program once the database has been changed.
Transaction code SM12 can be used to monitor SAP locks.
Here you have option of selecting locks based on following parameters
tablename
lock argument
client
username
In case, as part of monitoring, if you encounter some old sap locks and after thorough
analysis, you would like to delete these, it can be done in the following ways :
Select the locks and delete the lock from SM12

Identify the user who has set the respective lock and end the user session using SM04
transaction code
17) How to configure an Early watch Alert Report in Solution manager?

Answer : How to configure Early Watch Alert report
To configure Early watch alert some specific settings to be done at managing system
(Solution manager system) and satellite system( or managed system for which EWA report
to be generated)
Following are the steps to configure EWA in a satellite system :
1) Check whether latest versions of ST-A, ST-PI, ST-A/PI packages are installed in the
managed/satellite system
(This check can be done going to system->status -> Component information display in any
sap screen)
2) If they are installed, run RTCCTOOL report from SE38 transaction code of satellite
system.
Check the output of the report. If there are some errors or warnings in the output of the report,
please take corrective actions and run the report again and ensure there are no errors
3) Setup RFC connection between your satellite system and the solution manager system
An RFC connection can be made between 2 systems using Transaction code SM59
4) Setup RFC connection between your solution manager and the SAP service market place
5) Assign the solution monitoring roles to the users
6) Setup your satellite system in a solution landscape of the solution manager(SMSY)
7) Make sure SLD is configured and working fine for satellite system (using Rz70 and
SLDCHECK transactions)
8) Activation of SDCCN in satellite system (Goto SDCCN transaction. Then click on
Utilities -> Activate) then confirm for SDCC_OSS destination creation
9) In satellite system, goto SDCCN transaction and navigate to Goto -> Settings -> Task
specific.
In the resulted screen, select RFC destination and provide the solution manager RFC from the
satellite system and set solution manager RFC as the master system.
10) Addition of satellite system in solution manager system in SDCCN :
Goto SMSY transaction in solman system and then navigate to Environment -> Solution
Manager Operations -> Adminstration SDCCN to add the new service data control centre to
the solution manager.
Click on add system button to add the new SDCC to the solution manager. When prompted,
please select the respective system and client from the resulting screen and confirm
11) Early watch service session activation for satellite system:

In the solution manager system, execute transaction code solution_manager and navigate to
operations -> Earlywatch Alert and press create button. This prompts you to confirm the date
and time to run the report. Please provide the details and confirm to trigger the generation of
the report
12) Login to satellite system, goto transaction code SDCCN and press create button which
displays a screen to select a task to be executed. Select request session data task and click
continue. You will be prompted to enter the schedule time to run the report. Click now to
execute it immediately. After that you can see an early watch session running in SDCCN.
13) After completion of this session run successfully, an Earlywatch Alert will be generated
and this can be viewed in Solution_manager of Solution manager system.
18) Explain Oracle architecture.
Answer: Oracle Background Processes
Background processes are created from the oracle binary when an instance is started. As the
name suggests background processes run in background and they are meant to perform
certain specific activities or to deal with abnormal scenarios that arise during the runtime of
an instance.
From SAP perspective, the following are the 6 most important background processes of
oracle database.
Database Writer (DBWR) :
The database writer writes dirty blocks from the database buffer to the datafiles.
Dirty blocks need to be flushed out to disk to make room for new blocks in the cache. When a
buffer in the database buffer cache is modified it is marked as dirty buffer. A cold buffer is
a buffer that has not been recently used according to the least recently used (LRU) algorithm.
The database writer writes cold, dirty buffers to disk so that new blocks can be read into the
cache.
The initialization parameter DB_WRITER_PROCESSES specifies the number of database
writer processes. The maximum number of database writer processes is 20.
The database writer writes the dirty buffers to disk under the following conditions :
1.
When a checkpoint occurs
2.
Every 3 seconds
3.
When a server process couldnt find a clean reusable buffer after scanning a threshold
number of buffers
Log Writer (LGWR) :

The log writer process writes data from the redolog buffers to the redolog files on disk.
The redolog buffer is a circular buffer. When LGWR writes redo entries from the redolog
buffer to the redolog file, server processes can overwrite the entries that are already copied
with new entries in redolog buffer. LGWR writes at a faster pace so that space is always
available in the buffer for new entries.
The log writer gets activated under the following conditions :
1.
When a transaction is commited
2.
Every 3 seconds
3.
When the redo-log buffer is 0ne third full
4.
When a database writer writes modified buffers to disk, if necessary
Note : Before database writer can write dirty blocks to disk it should make sure that all redo
entries are written from the redolog buffer to the disk. This is also known as write-ahead
logging. If database writer finds that some redo-records are not written, it signals LGWR to
write to disk and waits for LGWR to complete writing the redolog buffer before it can write
out the databuffers.
Checkpoint (CKPT) :
Checkpoint signals the synchronization of all database files with the check point information.
It ensures data consistency and faster database recovery in case of a crash.
The checkpoint process regularly initiates a checkpoint. Whenever a check point occurs
following things are carried out :
1.
Updating the file headers of the data files with information about the last checkpoint
performed
2.
Update control files about the last checkpoint
3.
Initiates LGWR to flush the redolog buffer entries to redolog files.
4.
Writes the checkpoint record to the redolog file
5.
Initiates DBWR to write all dirty blocks to disk and thus synchronizes database
Archiver Process(ARCH) :
The archiver process copies online redolog files to the designation archive log location after
the occurrence of a log switch. It is an optional process. Archiver is present only when
database is running in archive log mode and automatic archiving is enabled.
You can specify multiple archiver processes with initialization parameter
LOG_ARCHIVE_MAX_PROCESSES. ALTER SYSTEM command can be used to increase
or decrease the number of archiver processes.
However it is not recommended for us to change this value, as Log writer starts a new
archiver process automatically when the current archive processes are insufficient to handle
the workload
Process Monitor (PMON) :
The process monitor performs process recovery when a user process fails. PMON is
responsible for cleaning up the database buffer cache and freeing resources that the user
process was using like releasing locks, removing process ids from active processes list etc.
PMON checks the running status of dispatcher and server processes periodically and restarts
in case any have stopped. Please note that this wont start processes that are intentionally
stopped by Oracle.
PMON also registers information about the instance and dispatcher processes with the
network listener.
PMON wakes up every 3 seconds to perform house keeping activities and should be running
always for an instance.
System Monitor (SMON) :
The system monitor performs instance recovery, if necessary, at instance startup. SMON is
also responsible for cleaning up temporary segments that are no longer in use and for
coalescing contiguous free extents within dictionary managed tablespaces.
SMON can be called by other processes in cases of need. SMON wakes up every 5 seconds
to perform house keeping activities. SMON must always be running for an instance.
Query to view background processes of Oracle :
Goto SQL prompt of oracle database system and provide following command to view
background processes.
SQL>
Select * from v$session where type = BACKGROUND;
9) How to apply a SAP note?

Answer: Applying SAP note
What is SAP Note ?

SAP releases notes on regular basis to provide the corrections/minor improvements to the
existing bugs/issues/functionalities. Since periodicity of release of Support packages is very
less, to resolve customer issues SAP releases notes to customers on regular basis to fix bugs.
What is the use of SNOTE transaction code ?
A note can be applied in SAP system using SNOTE transaction.
How to apply a note in SAP System ?
Before applying any note, please download SAP note. Go to SNOTE transaction and navigate
as shown below and download the note that is to be applied
Enter the note number to be downloaded and press execute button to download the note as
shown below
You can view the downloaded note in the New section under SAP notes as shown below.
Once the note got downloaded, to implement the note, select the note as shown below and
click on execute button to implement SAP note
After that, system prompts you to confirm that you have read the note. Please make sure you
have read the note thoroughly before you implement the note. Please find out the
applicability of the note to your system by cross-checking with the system SAP
release/version/database etc.
As shown above press Yes button to confirm that you have read the note and proceed further.
In the information popup window, press continue as shown above.

After that, systems prompts for transportable workbench request. Please click on create
request button as shown in below screen.
In the create request popup screen, please provide request details and save to create request as
shown below screens
After that, list of changes that are being made will be displayed as shown below. Click on
continue button to proceed to apply the changes
Click on continue button in the below screen to proceed further
Once the SAP got implemented successfully, it moves from New section to Processing
section as shown below
20) How to perform Kernel upgrade?
Answer: Will be provided soon
21. A user complaints to you that a background usually takes 3hrs to run but it is already 6hrs
completed and still the job is running. How to analyse the issue ?
Answer : Troubleshooting long running jobs
1) First of all identify the job that is long running and identify details like job class,
workprocess that is executing the job
How to identify long running background jobs
2) Click on the job to view the display job screen. In the screen, click on job log to
understand what is being performed by the job currently. This may give details like job is
currently extracting some data packages or processing data packages etc
3) Identify the executing server and process id of the job from the step 1 and goto transaction
SM50 of the respective executing server to view more details about the background job
running.
Figure out the status of the job like On Hold or running from the process overview. If the job
is On Hold, find out the reason for On Hold by examining the "Reason" column of SM50
transaction. Reason for On Hold could be due to CPIC/RFC/DEBUG/ENQ/PRIV/UPD etc.
Double click on the reason column for detailed information on the same and troubleshoot
accordingly. If reason is RFC, check out which RFC it is referring to and cross check whether
destination system is up or not and any other problems with that system.
If it is ENQ, check out any lock issues like lock overflow etc
If it is PRIV, check out for memory bottlenecks
If it is UPD, check out whether any update issues
If it is CPIC, check out for any network , gateway, message server and other
communication problems
4) After performing step3, if you figure out job is not on Hold and it is in running state, then
examine report column to identify what report/program is being executed by the job. Once
you got the report/program details, figure whether it sap program or custom program and take
actions accordingly.
5) Also examine Action and table columns in SM50 transaction of respective executing
server to identify what is the action( roll in/roll out /Sequential read/Physical
read/insert/update/delete etc) being carried out by the job currently and what is the table on
which action is being carried out.
If it is sequential read, figure out the cost of that sequential etc and consider for indexing etc.
If it is physical read, check out whether there are too many swaps and consider resizing
buffers accordingly. If you observed delay is due to high roll in/roll out, identify reasons for
the same and tune buffer/memory parameters accordingly.
6) Once you get the table details on which action is being carried out, figure out
How many records are existing in the table ?

Is this taking long time due to volume of records ?
Are there proper indexes on the table ?(If no proper index, consider index creation by
taking help of DBA )
Is the table having upto date statistics ? (If statistics are out of date, consider updating
statistics of that table)
7) Consider debugging the process in SM50 ( Program/Session -> Program -> Debugging ) to
figureout the issue
8) Using ST05 or ST12, a trace can be taken for background job to figure out where exactly
time is being consumed and to identify various cpu/memory bottlenecks or any buffer issues.
9) STAT/STAD transcation can be used to figure out what is the reason for high response
time and actions can be taken accordingly
10) By taking help of ABAP er, even ABAP run time analysis can be done using SE30
transaction
By following the above steps, you can pin point the issue and take actions accordingly to
minimize runtime of long running background jobs.
Identifying long running jobs
Goto SM37 transaction and select the active job status between any 2 given date/time and list
them. In the output, sort the jobs based on duration column in descending order and identify
the jobs that are running for longer duration
All other questions can be answered from the below :
Goto transaction SM37 and list the jobs based on status and time interval.
Select any job for which you want to figure out the details. Double click on the job, which
pops up "display job screen". In that screen, click on job details tab to view
Job name
Job class (i.e A, B and C)
Status of the job
Exec. Target (server/instance on which job is being run currently)
Job frequency (hourly, monthly , weekly etc)
Workprocess that is executing the job
Client on which job is running
Release time of the job
Schedule start of the job
22. Do you have experience in handling SCM system? If yes, how to you start or stop
livecache in SCM or APO(Advanced Planning and optimiser) system?
Answer: Yes, I do have experience in handling SCM system. Livecache can be started or
stopped using LC10 transaction code.
Related Link : How to start or stop livecache in SCM or APO system?
STOP sequence of livecache in SCM or APO system:
Sometimes to perform any maintenance it is required for basis administrator to shut down the
SAP system. If an SAP system consists of livecache then it is required to know the sequence
in which system to be bought down to avoid issues
Shutdown sequence:
1.
First of all shutdown livecache (Process explained below)
2.
Shut down ABAP system (as per the standard process of shutting down any SAP
system)
3.
Shut down Database system ( as per the standard process)
START sequence of livecache in SCM or APO System:

Start sequence of livecache system is exactly reverse order of shutting down process.
Start sequence:
1.
Start Database of the SAP SCM system (As per standard process)
2.
Start the ABAP stack (As per standard process)
3.
Start the live cache (process explained below)
How to Check the live cache Operational State :

Login to SAP system and goto transaction LC10.
Systems displays screen similar to below. Please select name of database connection as LCA
and click on "Livecache: Monitoring" tab to proceed further.
After this, you will be redirected to the below screen. Here you can check the operational
state of the live cache. It is green currently. It means live cache is up and running.
From the below screen, we can determine
live cache version
live cache operational state
Database server version
Operating system
What was the date/time at which livecache started in this system
When was the last livecache start/stop activity done
Automatic log backup is on or off
Database Trace/Command monitor/Resource monitor on/off status
Different directories/files belonging to livecache
Note : By clicking on the Alert monitor link (as shown in above screen), we can check
various alerts that are belonging to livecache.
Once you click Alert monitor, it opens another screen as below. From here you can click on
"open alerts" pushbutton to view all the alerts related to livecache. In addition to that, we can
drill down on various parameters in the below screen and we can identify problematic areas.
If there is an issue in any area, that will be highlighted in red as shown in screen below
How to Stop LiveCache:

To stop the livecache, In this screen, navigate to Administration -> Operating and click on
"Stop livecache" pushbutton (as shown in the below screen).
Once the livecache got stopped, the operational state button which is green earlier will turn to
red confirming that the live cache is down.
How to Start LiveCache:

To start the live cache again, navigate to Administration -> Operating and please click "Start
Livecache" pushbutton in the above screen.
Once the livecache started successfully, its operational state turns into green color indicating
that livecache is up and running.
Please note that live cache runs on a MAXDB database.
23. If a java stack is down ? How do you troubleshoot?

Answer: Will update later
24. If in a java only system, administrator user id got locked, how do you resolve this issue?
Answer:
Activating emergency user in java
25. How to create a server node in Java based SAP system?
26. In system refresh activity, database restoration is done and sap system is up. Now, what
are the poststeps system refresh steps that you perform ?
27. How do you analyze an expensive SQL statement?
Answer : Please go through below related links
Expensive SQLs and their consequences
Analyzing expensive SQLs using SM50/SM66 (scroll down for answer)
Identifying expensive SQLs using ST04 (scroll down for answer)
A few SQL statements may reduce the performance of the database as well as the SAP
system.It is the responsibility of Basis administrator/ Database administrator to identify those
statements and action them accordingly.
Expensive SQL statements are caused by many reasons like

i) Bad programming
ii) Inappropriate use of functions of SAP (like not specifying proper selection criteria while
running reports)
Expensive SQL :
Expensive SQL statements are also known as expensive selects. Expensive statements are
those statements which cause more disk reads or buffer reads to the database.
As a rule of thumb, the statements which contribute to more than 5% of total block reads for
answering are considered as expensive SQL statements.
Consequences of expensive SQL statements :
A few expensive statements can hamper the performance of the SAP system. Few
consequences are listed below :
i) While an expensive SQL statement is being executed, as it has to fetch more blocks,
already existing blocks in the database buffer are displaced to accommodate the blocks of this
statement. This impacts performance of the other SQL statements and could impact
performance of following requests
ii) As database will be busy ready many blocks to satisfy expensive SQL statement, there are
chances of slowdown of other database tasks which eventually may impact the performance
of the SAP system
iii) While an expensive SQL is being executed, a work process is blocked till the completion
of the request. So, it is not available for other requests which increases the wait time of other
processes (like waiting in the dispatcher queue)
Factors to be considered to tune expensive SQL

It is not practically possible to tune each and every expensive SQL. So, we have to identify
the statements to be tuned based on the impact of those. Impact of expensive SQL statements
on the SAP system performance depends on many factors like
i) On what frequency the expensive SQL is running?
(If an expensive SQL is running once in 6months, then it is acceptable to run but it an
expensive statement is running more frequently like 24 times a day then it is worth tuning
that statement)
ii) What is the time of expensive SQL execution?
(If an expensive SQL is running during peak load than it cause more performance issues
leading to high response time and wait times to other processes/jobs. So it is important to
consider at what time these expensive SQL are being executed. It is best to execute expensive
SQL during periods of low work load on the system)
iii) Impact of the expensive SQL on the performance of the system
( It is worth taking note of the impacts the expensive SQL statement is creating on the
response time, throughput and performance of the system. Also the duration of the
performance problem also to be considered to figureout the impact of an expensive SQL)
SAP transactions to identify expensive SQL
Based on the above factors, an expensive SQL statement can be selected for tuning.
SAP provides so many tools or transactions to identify Expensive SQL statements.
Some of them are SM50, SM66, DBACOCKPIT, ST03, ST04 and ST05
How to analyze expensive SQL statement using SM50/SM66 ?

Go to transaction SM66 and have a look at the global workprocess overview.
i) Have a look at Action column and identify any long running Sequential read/ direct read
/insertion /updation etc.
ii) If so, please note the respective report that is being run and the table that is being used for
the same. From the report we can make whether it is SAP standard report or customized
report. If it is customized, we can take help of ABAPer to see if the report can be finetuned in
cases of bad programming. Table details can be used to figure out the size of the table and
whether statistics are upto date for the table or not.
Please note : "Updatestats job should run daily so that system will have recent statistics
about all the tables. These statistics will be useful for Cost based optimizer to identify
optimized execution plan for an SQL statement"
iii) Also, please note the user who is running that process. So that, later user can be
approached and a trace(ST05) can be kept for his activity to understand his transaction in
detail which would help for finetuning.
iv) SM50 transaction can be used to view the detailed display of the process and the SQL
statement that is being executed
For example, Please refer below screenshot of SM66 :

In the below screenshot,
i) Highlighted user is running ZFI_TDS* report on RBKP table in dialog mode and
sequential read action is happening on the same.
ii) user DDIC is running RBDMONI_* report (in background mode) on table BDCP2 and
direct read is happening on the same. It has already consumed 783 seconds of CPU time.
To analyze point i) scenario in the above case, please note the server name on which this
process is running. Go to that server through SM51 and have a look at SM50 transaction.
Identify the respective PID of the process which you have suspected as expensive SQL from
the overview and double click on that process which opens up detailed display as below:
How to identify expensive SQLs using ST04 transaction ?

As shown below, go to transaction ST04 and navigate to SQL statement analysis -> Shared
cursor cache
Double-click on the shared cursor cache while leads you to the following screen.
In the above screen, please provide Buffer gets as 50,000 for example and in the List sort
options select Buffer gets radio button and execute.
It displays all the SQL statements whose buffer gets are more than 50,000 and sorts them in
descending of buffer gets as shown below
As highlighted in the above screen, identify the top 5 or 10 statements as per buffer gets.
These are expensive or costly SQL statements.
Also look at executions column and figure out the value. If value is greater for executions it
means that the SQL is frequently getting executed and it is worth tuning that statement.
Afterwards click on the corresponding SQL statement which opens the SQL statement as
below
In the above screen, click on explain icon (highlighted) which opens up another window as
below
In the above window, you can view :
Estimated costs to execute the SQL

Estimated rows to be fetched
Estimated CPU costs
Estimated IO costs
Ideally, all of these parameter values should be low for an optimized SQL statement. For
expensive SQL statements, these values will be of very high impacting system performance.
Also, in the above window find out whether FULL SCAN is present. If present it means
indexing is not proper for the table involved in this SQL statement.
Please double click on the table name or index name which is going for full scan, to view
similar window as below :
In the screen, you can note Last statistics date. If this date is too old, it is recommended to
run update statistics for this table or index. This improves performance of the SQL statement
as it provides correct recent statistics so that execution plans for SQL statement will be done
properly.
Due to outdated statistics, execution plan wont be proper leading to high row fetches,
increasing CPU and IO costs.
28. What do you know about Willy introscope agent ? What is the use of willy introscope ?
What is the version of willy introscope that you have implemented ?
Answer: Willy introscope is a java monitoring agent that is installed in a high available
system like Solution manager and all other satellite systems that are to be monitored are
connected or configured. So, using willy introscope end to end root cause analysis can be
done. In cases of performance issue of java systems, troubleshooting can be better done using
willy introscope as it provides so many details related to memory consumption, CPU usage,
system availability, paging, Garbaga collection details etc.
Willy introscope is available in different versions like 7.1 , 8.0 and latest one 9.1
29. What is the transaction to perform support pack upgrade in ABAP stack ?
Answer: SPAM is the transaction code used to perform support pack upgrade in ABAP stack.
30. Your SAP systems are based on which operating system ? What is the version of
operating system do you use?
Answer: For example, You can reply based on the operating system you are using like AIX
operating system with version 5.3
31) What is the transaction code to be used to view your own spool requests in SAP ?
Answer : SP02 is the transaction code to view your own spool requests.
Please note that SP01 is used for viewing all spool requests where as SP02 is used to view
only own spool requests.
32) Apart from update work processes what are the other work processes that can do the
update task ?
Answer : Apart from update workprocesses, dialog and background workprocesses can do the
update activity.
Hint :
Please note dialog and background workprocesses can themselves do the update activity
locally without depending on update workprocesses. This concept is known as local update.
However for this to happen an ABAP clause to be specified during programming saying
LOCAL UPDATE.
33) What is the transaction code to be used to perform Java support pack upgrade ?
Answer : JSPM is the transaction code used to perform Java support pack upgrade in SAP.
JSPM stands for Java Support Pack Manager.
34) How to you apply license for an ABAP stack of an SAP system ?
Answer : SLICENSE is the transaction code used to apply license for an ABAP stack of an
SAP system.
35) How do you monitor livecache in SCM or APO systems (or) What is the transaction code
used to monitor livecache in SCM or APO systems?
Answer : LC10 is the transaction code used to monitor livecache in SCM or APO systems.
36) What is TREX ? What does TREX stands for ? What is TREX used for ?
Answer : TREX is a search engine in the SAP netweaver technology platform. It can be used
in various system environments primarily as an integral part of SAP products like Enterprise
portal, Knowledge Warehouse and Business Intelligence(BI).
TREX stands for Text Retrieval and Information Extraction.
37) What is the name of the database on which your TREX runs in your landscape?
Answer :
Hint : This is very tricky question. Please do not answer that TREX runs with Oracle or
MaxDB etc databases. Please note TREX is a search engine. It does not depend on any
particular database.
Please answer as below:
TREX is a standalone component that can be used in a range of system environments and it
doesnot depend on any particular database.
38) What is the need of TREX in BIW system?

Answer :
In SAP Netweaver BI, the TREX engine powers the BI Accelerator, which is a plug in
appliance for enhancing the performance of Online analytical processing.
39) What are the functions of TREX?

Answer :
Functions of TREX
Supports various kinds of text search which includes boolean search, exact search, wild
card (*, &) search, linguistic search and fuzzy search
Supports text mining and classification
Supports structured data search not only for document meta data but also for mass business
data
Supports structured data search in SAP Business Objects
40) What is the tool provided by SAP for performing sizing of a project ?
Answer :
Quick Sizer is the tool provided by SAP for performing sizing of a project
41) How to Unlock if SDM user got locked in SAP ?
Answer : How to unlock if SDM user id got locked?
Sometimes, you encounter a situations like
i) SDM deployments fail and upon investigation you found that SDM account got locked.
You can only deploy again after unlocking the SDM account.
ii) User tried to login to SDM account with wrong password three t imes and account got
locked.
Proceed as follows to unlock the SDM account :
If your operating system is windows, please proceed as follows :
i) Open the command prompt
ii) Login as sidadm
iii) Navigate to the following path : <Drive>:\usr\sap\<SID>\JC<nn>\SDM\program
iv) At this path provide the following commands:
sdm jstartup mode=standalone
sdm changepassword newpassword=Enterthenewpassword
sdm jstartup mode=integrated
startserver.bat
If your operating system is Unix, proceed as follows :

i) Open a telnet window
ii) Login as sidadm user
iii) Navigate to the /usr/sap/<SID>/JC<nn>/SDM/program
iv) At this path provide the following commands :
./sdm.sh jstartup mode=standalone
./sdm.sh changepassword newpassword=Enterthenewpassword
./sdm.sh jstartup mode=integrated
./startserver.sh
42) What is the memory allocation sequence to a non dialog work process in SAP ?
(background, update, enqueue and spool workprocesses in SAP? What are the SAP
parameters used to define initial roll area, extended memory, heap memory, roll area ? What
is the memory allocation sequence to non dialog work processes in Windows NT?
Answer : Memory allocation sequence to a non-dialog workprocess in SAP
Memory allocation sequence to dialog workprocesses is same in SAP for all the platforms.
However memory allocation sequence to non-dialog workprocesses is bit different based on
Platform. In Windows NT, memory allocation sequence for non-dialog workprocesses is
same as that of dialog workprocess memory allocation sequence in other platforms.
Memory allocation sequence to non dialog work processes in SAP as below (except in
windows NT) :
1.
Initially memory is assigned from the Roll memory. Roll memory is defined by SAP
parameter ztta/roll_area and it is assigned until it is completely used up.
If the roll memory is full then
2.
Heap memory is allocated to the non-dialog workprocess. Heap memory is available
until one of the following occurs :
i) Either the limit of the heap memory for non-dialog workprocesses is reached (defined by
the SAP parameter abap/heap_area_nondia) or the entire heap memory of all workprocesses
of an SAP application server reaches its limit which is defined by parameter
abap/heap_area_total.
ii) Operating system limits of allocating memory
iii) The swap space in the host system is completely used up. However this situation should
not occur often which results in severe performance issues.
Please check swap space requirements for various platforms and please define swap space
optimally to avoid this issue.
iv) If all the above mentioned heap memory is completely used up then a non-dialog
workprocess can use the SAP extended memory defined by SAP parameter
em/initial_size_MB.
43) What is the memory allocation sequence to a dialog workprocess in SAP?

Answer : Memory allocation sequence to a dialog work process
1.
Initially , a defined roll area is used. This roll area is defined by the SAP parameter
ztta/roll_first.
Usually ztta/roll_first is set to 1 in SAP so that only technically necessary amount is allocated
to roll memory.
If the memory from the initial roll area( i.e. ztta/roll_first) is not sufficient for the user context
then
2.
Extended memory is used until the extended memory is full or until the user quota is
reached
Extended memory is defined by the SAP parameter em/initial_size_MB and the user quota
for dialog workprocess is defined by the parameter ztta/roll_extension_dia.
If this memory is also not sufficient, then
3.
The rest of the roll area is used. This roll area is defined by SAP parameter
ztta/roll_area.
Once this is also fully occupied then
4.
The system is forced to use local heap memory (Private memory). Then the work
process goes into PRIV mode
Heap memory is available until one of the following occurs :
i) Either the limit of the heap memory for dialog workprocesses is reached
(abap/heap_area_dia) or the entire heap memory of all work processes(abap/heap_area_total)
for an application server reaches its limit.
ii) Operating system limit for allocation of memory
iii) The swap space in the host system is used up or the upper limit of the operating system
address space is reached.
The memory allocation strategy for dialog work processes, aims to prevent work processes
from allocating R/3 heap memory and thus entering PRIV mode.
When a work process enters PRIV mode, it remains connected to the user until the user ends
the transaction. Most of the time, we should try to avoid the situation of work process going
into PRIV mode for better performance of the SAP system. This can be done by optimally
defining abap/heap_area_total parameter.
44) Name the different SAP profiles and their start sequence.
Answer : SAP Profiles
SAP R/3 systems uses Profiles to define the properties of an SAP R/3 Instance such as the
type and number of work processes, the size of main memory reserved for SAP R/3 and
various parameters like multiple logon, idle time out value etc
There are 3 types of profiles in SAP.
They are
DEFAULT.PFL (known as System Profile)
Start Profile
Instance Profile
All the profiles mentioned above are stored in the profile directory defined during installation
of the SAP system.
This path can be set using DIR_PROFILE profile parameter in the start profile.
Ideally the path of profile directory would be
In Unix Systems :
/usr/sap/<SID>/SYS/profile or /sapmnt/<SID>/profile
In Windows NT :
\\<SAPGLOBALHOST>\sapmnt\<SID>\sys\profile
Tip: Please note in AIX or HP-UX environment, we can go to the above profile directory
location using cdpro command at Os level.
All instances of a SAP system can read these profiles with share ( Systems based on
Windows ) or mount (Systems based on Unix) technology.
DEFAULT.PFL : This profile exists uniquely in an SAP R/3 system. It means if there are 5
application servers in an SAP system, even then there will be only one DEFAULT.PFL file.
It contains system-wide settings which include
Name of the SAP system
The database system

Name of the enqueue server
Each SAP R/3 instance to be started reads this profile first. The information specified in this
profile is very vital for the functioning of the SAP system.
START PROFILE : Unlike default profile, the start profile is specific to an instance. It
means if there are 5 application servers each will have one separate start profile with the
settings specific to an instance.
The startup process of the SAP system is controlled by the start profile that is read by the start
program [sapstart]. Here the services(eg: message, gateway, dialog , batch etc) that are to be
started are listed. Hence every instance will have separate start profile.
In other words, the start profile determines how, where and under what name individual SAP
R/3 services and processes are to start.
The naming convention of START PROFILE will be as below :
START_<instance><instance_number>_<host_name>
Eg: START_DVEBMGS00_prdserv4
For the start profile default names are assigned during the installation of an instance based on
the services that are running on the instance. For example, DVEBMGS in the start profile
above confirms that following services are available for that instance.
D Dialog
V Update
E Enqueue
B Batch
M Message
G Gateway
S - Spool
INSTANCE PROFILE : Like start profile, Instance profile is specific to an instance. It

means if there are 5 application servers each will have one separate start profile with the
settings specific to an instance.
The runtime environment of the instance is configured in the instance profile. In instance
profile parameters specific to an instance can be set like auto gui logout
time(rdisp/gui_auto_logout), number of various workprocesses (rdisp/wp_no_dia), memory
related parameters like abap/buffer_size, em/initial_size_MB, rdisp/PG_SHM,
rdisp/ROLL_SHM etc
The naming convention for the instance profile will be as below :

<SID>_<instance><instance_number>_<hostname>
Eg : SQ1_DVEMBSG00_prdsapk1
During the installation of an SAP R/3 system, the profiles are created with standard values.
Later it is Basis administrators responsibility to tune the parameters.
The source code of the SAP Kernel already sets standard default values for most of the
system parameters. However, you must specify some specific details like computer name,
system name and distribution of resources in the profiles.
The SAP profiles are read during the startup of an instance. The values defined in the system
profile (ie. DEFAULT.PFL) overwrite the standard settings in the source code. The values
defined in the instance profile overwrites the parameter values of DEFAULT.PFL for the
instance.
In case of any changes to System Profile ( DEFAULT.PFL or Default Profile), you must
restart all the instances of the SAP system as this is common for all instances.
However in case of any changes to instance profile, it is sufficient to take restart of only that
particular instance for the changes to take effect.
Sequence of SAP profiles that are read while starting SAP system :
First start profiles of various instances are read by the sapstart program
Secondly Default profile is read
Finally, instance profiles of various instances are read.
45) How to perform CPA cache refresh in XI or PI system?

Answer : CPA cache refresh and delta cache refresh
Complete CPA cache fresh :
To perform complete CPA cache refresh in PI or XI system, use the following URL :
http://<hostname>:port/CPACache/refresh?mode=full
For example :
http://sapserver12:50300/CPACache/refresh?mode=full
Delta Cache Refresh :
http://sapserver13:50200/CPACache/refresh?mode=delta
Please note in both of the above cases, system prompts you to authenticate yourself to
perform this cache refresh. You need to authenticate using PIDIRUSER user id to perform
the cache refresh.
Please note that you can only perform CPA cache refresh using PIDIRUSER user id in XI or
PI system.
If PIDIRUSER user id got locked then you will face cache refresh issues in PI or XI systems.
46) How to import a transport manually at Os level ?
Answer : How to import a transport manually at Os level?

Sometimes, there will be situations like you have to process transport imports manually. This
can be done by TP program from the operating system level.
Transport control program TP is controlled by a parameter file TP_<domain>.PFL which is
present under bin subdirectory of the transport directory.
Please note in older releases of SAP R/3, the file is termed as TPPARAM.
Before using TP for the first time, it is suggested to test the connection to the desired target
system.
To perform this test, following command can be used.
tp connect <target system> pf=<complete path of the parameter file>
If this test results are fine you can proceed further otherwise you need to troubleshoot the
same and identify the reason for the same.
In order to insert a request into the import queue of an SAP R/3 system, use the following
command:
tp addtobuffer <request> <target system> pf=<complete path of the parameter file>
If the above command is successful then, datafile and cofile of the request will get copied
under respective data subdirectory and cofiles subdirectory of the transport directory.
As the request is inserted to the import queue, it can now be imported using the following
command.
tp import <request> <target system> pf=<complete path of the parameter file>
In case you would like to import all the requests that are present in the import queue of an
SAP system in the current sequence then provide the following command at oslevel.
tp import all <target system> pf=<complete path of the parameter file>
You can add the following to specify a specific client for import:
client = <number of the client>

If the client is not mentioned, the data is copied to the client with the same number as the
client from which the data was exported.
If the client into which you would like to import a request does not exist in the target system,
the import terminates with an error message.
47) What are the different java monitoring checks you perform daily ?
Answer : Java monitoring check list 1
Java monitoring check list 2
To check Logs and Traces, navigate to System Management -> Monitoring -> Logs and
Traces
From the drop down box, different logs can be checked
Process list List of processes that are currently running can be viewed here and any long
running process can be identified and actioned accordingly.
Using Management Console for monitoring Java System :
To open management console for SAP systems based on Unix operating system, add 13 for
the port of the portal as mentioned below
http://faqsa6.comapn.com:50013
A screen similar to below screen will appear
You can drill down further on SID of the system to view database,Central and SCS instance
details as below :
Please note that Management Console can be accessed even when java is down for a sap
system.
You can check database status as below :
You can check the javanode status as below:

Status should be running here if java is up
Process list List of processes that are currently running can be viewed here and any long
running process can be identified and actioned accordingly.
SDM, Dispatcher, Server0 and server1 node status can be checked here:
Various work directory logs, availability log, application log and default trace can be checked
here :
Availability log :
Sapstart log:
Dev_jcontrol log :
Dev_server0 log :
To check the status of message and enqueue servers, check the process list under scs instance
as mentioned below :
To check various logs related to message server, enqueue server, jcmon check the logs under
SCS instance as mentioned below :
48) What are the different SAP user types ?

Answer : SAP User types
These are the 5 user types that are present in SAP
v Dialog
v Communication
v System
v Service
v Reference
Dialog: This is the most commonly used type. This user type is primarily for individuals to
gain interactive system access. A user of this type can perform dialog processing in
interactive mode, background processing, batch input processing and CPI-C services
provided there are no explicit restrictions via assignment of specific authorizations.
SAP licensing can prohibit multiple concurrent use of the same user id in production SAP
systems.
Communication: This user type is used for dialog-free communication between systems
such as RFC (Remote Function call) communication. This user is not allowed to logon to the
R/3 system or start dialog processing
System: This is the user type which can be used for dialog-free communication within a
system (such as for RFC users for ALE, TMS, workflow and CUA) and for background
processing.
A specific use of the system user type is validity period of a password wont apply for this
type. So, this can be used to run background jobs and in between RFCs so that jobs or RFC
communications wont fail due to expiry of the password.
Please note that logon in dialog is not possible used System user type.
Service: This user type is a dialog user which is available to a large, anonymous group of
users. For example, to access via ITS (Internet Transaction Server)
There wont be any check on initial password or expired passwords for this user type. Also,
multiple logons are explicitly permitted for this user type.
However this user type should be assigned with great caution and with limited authorizations
for security reasons.
Reference: This user type is in general, non-person related user. This user type cannot be
used for logon. Instead this user type will serve as a reference for assigning additional
identical authorizations to other users.
For example: In case you have to assign some identical authorizations to all internet users,
you can create a reference user with those authorizations and use this reference user to assign
identical authorizations to all other users.
49) What are the different types of RFC communication in SAP ?

Answer : Different types of RFC communication in SAP
There are mainly 4 types of RFC communication in SAP. They are
Synchronous RFC
Asynchronous RFC
Transactional RFC
Queued RFC
Synchronous RFC (sRFC) : In this type of RFC communication, the calling program waits
until the requested processing step on the remote system has ended and then continues to
work locally.
In other words, both the systems involved must be available at the time the call is made.
Asynchronous RFC (aRFC) : In this type of RFC communication, the calling program gives
the request to the remote system and immediately continues to work locally. The requested
processing step is executed on the remote system in isolation.
If the remote system cannot be reached at the time of the call, the asynchronous calls of the
RFC client are lost
Transactional RFC (tRFC) : This type of RFC communication is similar to asynchronous
RFC but by allocating a transaction id(TID) it guarantees that if a request is sent several times
because of network problems it is processed only once. Unlike asynchronous RFC, in
Transactional RFC the remote system does not have to be available at the moment the RFC
client program start the call. The data is held in the source system until the target system is
available.
The report program RSARFCSE is called in the background at regular intervals and tries to
place the unsuccessful requests, identified by their transaction id again.
Queued RFC (qRFC) : This RFC communication is an extension to the transactional RFC.
In this method, all the requests are queued up(inbound queue and outbound queue) and are
processed in a sequence only if it is certain that all preceding calls are processed correctly.
This method guarantees that all the requests are processed in the sequence in which they are
received.
This type of RFCs will be used in SCM (APO) systems for CIF queues etc where requests
have to be processed in an order.
50) How do you access service market place ?

Answer : S-User id is required to access service market place.
More details : How to search SAP notes in service market place?
1) What is SAP Business Suite?
Answer: The SAP Business Suite is a comprehensive integrated suite of business applications
that help companies, institutions, and other organizations run their business better.
SAP Business suite consists of
SAP ERP
SAP Industry Suite
SAP Net weaver

SAP ERP is an application within SAP Business Suite. All the applications from the SAP
Business Suite are powered by SAP Net weaver
2) What does SAP GRC stands for?
Answer: GRC stands for Governance, Risk and Compliance
3) What is SAPs Release and Maintenance Strategy?
Answer: As of now, SAP follows 2 release and maintenance strategies. They are
I) 5-1-2 release and maintenance strategy and
ii) 7-2 release and maintenance strategy
5-1-2 release and maintenance strategy is introduced in 2004. It means for duration of 5
years, SAP does a mainstream maintenance for a software release. Thereafter, extended
maintenance is available for 1 year at an additional fee of 2%. Thereafter, extended
maintenance is available for 2 years at an additional fee of 4%. Thereafter customer specific
maintenance will be offered case to case basis.
It applies to core applications based on SAP Netweaver 2004 and higher, as well for addons.
SAP NetWeaver 2004 and add-ons

SAP ERP 2004 and add-ons
SAP CRM 2005, SAP CRM 2007 and add-ons
SAP SCM 2004, SAP SCM 2005, SAP SCM 2007 and add-ons
SAP SRM 2004, SAP SRM 2005, SAP SRM 2007 and add-ons
7-2 maintenance strategy was introduced in 2008. It applies to new releases of core
applications of SAP Business Suite as of November 2008, as well as add-ons and
enhancement packages.
SAP ERP 6.0 and add-ons

SAP NetWeaver 7.0 and add-ons
SAP CRM 7.0 and add-ons
SAP SCM 7.0 and add-ons
SAP SRM 7.0 and add-ons
4) How does connectivity between SAP Net weaver AS ABAP and SAP Net weaver AS Java
will happen?
Answer: Connectivity between SAP Net weaver AS ABAP and SAP Net weaver AS Java
will happen via SAP Java Connector (SAP JCo)
5) What are Usage Types in SAP? Name some of the usage types in SAP?
Answer: Usage types determine the intended purpose of an SAP system. They are structuring
element for SAP software on a technical level. Usage types are realized by installing and
configuring a collection of software components. Some usage types also require other usage
types in the SAP system to operate.
Please find below the usage types present in SAP
Application server ABAP (AS ABAP)
Application server Java (AS Java)
Enterprise Portal Core (EPC)
Enterprise Portal (EP)
Business Intelligence (BI)
Business Intelligence Java components (BI Java)
Development Infrastructure (DI)
Mobile Infrastructure (MI)
Process Integration (PI)

Basis FAQ

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Basis FAQ

Enviado por

Direitos autorais:

Formatos disponíveis

SAP Basis / Netweaver Interview FAQ with answers

How to configure an Early watch Alert Report in Solution manager?

Explain Oracle architecture.

How to apply a SAP note?

How to perform Kernel Upgrade?

If a java stack is down ? How do you troubleshoot?

How to create a server node in Java based SAP system?

How do you analyze an expensive SQL statement?

What is the transaction to perform support pack upgrade in ABAP stack ?

How to you apply license for an ABAP stack of an SAP system ?

What is the need of TREX in BIW system?

What are the functions of TREX?

What is the tool provided by SAP for performing sizing of a project?

How to Unlock if SDM user got locked in SAP ?

What is the memory allocation sequence to a dialog workprocess in SAP?

Name the different SAP profiles and their start sequence.

How to perform CPA cache refresh in XI or PI system?

How to import a transport manually at Os level ?

What are the different SAP user types ?

What are the different types of RFC communication in SAP ?

How do you access service market place ?

Answer : Troubleshooting long running transport

Issue could be due to following reasons :

Transport is not getting terminated. How to do terminate?

If it functioning well it should show output similar to below screen :

And click on delete icon

Click yes to confirm deletion, which deletes the RFC.

As shown above, Please specify :

Output device name

How to take a print in SAP ?

After this, a spool request will get generated as above.

Click on execute to view the below list of spool requests

How to check various tablespaces in SAP and their sizes ?

How to view SPFILE parameters at SAP level ?

How to view database Parameters history at SAP level ?

6) A user complained that he is facing performance issues if he is running a particular

SQL Trace (Trace for SQL statements)

Enqueue Trace (Trace for enqueue/lock requests, waiting etc)

Table Buffer Trace

Deactivate Trace : This functionality is used to deactivate the trace

Display Trace : This functionality is used to display trace

Click on tick mark to display the trace

Click on Yes to display the trace as below:

Enter SQL Statement : This functionality is used to analyse an SQL statement

Guidelines for activation of performance trace

Workprocesses overview (SM50/SM66)

Database process monitor for monitoring the execution of SQL statements

Profile parameter settings for Performance Trace (ST05):

How to change sap parameter ?

Click on Save button to save and activate the profile.

Press no to goto the next screen

Press yes, to activate the profile.

How to change SAP parameter ?

Process to be followed to activate emergency user SAP*

This activates SAP* user

Enter the new password for

Restart the AS Java

How to handle, if administrator user id got locked in dual stack system?

What is the parameter to be changed to increase lock table size in SAP ?

Due to improper design of application which sets a large number of locks

How to resolve lock table overflow ?

Increase the number of enqueue workprocesses

How to increase the number of workprocesses?

To increase/decrease the number of workprocesses, value to be changed accordingly for the