Interview questions
Q 1) What is difference b/w SAP Note & SAP support Pack?
SAP NOTE
When a user of SAP system finds a bug in the SAP product he reports the same to SAP support team,
SAP developers check the same and develop a correction for the same. This correction is sent to the
customer in the form of a SAP NOTE.
SAP SUPPORT PACK
If the similar bug is reported by multiple clients or end users, then SAP recognizes such bugs, corrects
them and collects all these corrections in one place and adds some enhancements to the earlier version
of SAP and then calls this as a SUPPORT PACK. In simple words collection of SAP NOTES is a SUPPORT
PACK.
Q 2) What is OSS? How to open OSS system?
OSS(online services system):
(OSS is a online service system through which SAP provides all the patches...
If there is any corrections or enhancements then SAP releases OSS notes..)
OSS are online sap support notes. These notes are available online for solving critical problems in sap
system. We may use the already existing notes or may add our own queries.
In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID
and password.
Q 3) Different types of SAP OSS notes ?
There are three types of OSS notes.
Descriptive – in this notes you can find a description of a problem and how to resolve it with means of
customizing or different settings in the system. Kind of these notes are FAQ’s, general notes for
something – there is collection of OSS notes related to any problem.
Code correction – these notes are easily to implement with SNOTE transaction.
Mixed type – in this case there are some manual corrections or customizing in the system described in
the note and also code correction implementation. Implementation could be before or after manual
corrections – this is described in the note and is very important in some cases.
Q 4) What is client 000 in SAP R/3?
SAP comes with some pre-configured clients.
Client 000 – Client 000 is considered to be a SAP reference client and contains the client-independent
data of R/3. Special admin tasks are performed here as user SAP* or DDIC.
A Client 000 is defined as the SAP standard and the customer cannot change it. This client serves as a
copy template for the creation of further clients.
Client 000 contains all standard configurations, parameters, standard transactions, etc that are normally
used in the SAP R/3 business environment.
Client 001 - Client 001 is a copy of client 000 with the difference being that the data is client-dependent.
Do not change any settings here. It should remain standard.
After a new installation both 000 and 001 clients are identical, but after an upgrade 000 will have
additional customizing data. Lot of customer sites does not use 001 client at all.
Client 066 - Client 066 is used to perform "Early Watch" service for customer systems.
This client enables SAP to remotely access the customer system. SAP provides this service to the
customer to improve the system performance. Client 066 should not be changed or deleted from the
system.
NOTE- Apart from these 3 pre-configured clients, there could be some more clients from SAP depending
upon the Add-on installed. For e.g. if IS-OIL is being installed, all the IS-OIL related activities are done
through client 065
Q5) How do you start SAP R/3?
To start R/3, run the shell script startsap from the home directory of user adm. startsap starts the
saposcol process, which is the statistics collector for operating system resource data, if it is not yet
running.
startsap calls the script startdb, which starts the database if it is not already started.
startsap then starts the central instance. The R/3 System administrator can start additional instances
and application servers.
To start the instances independently of the database, use the script startsap. startsap has the following
options:
startsap r3: Checks if the database is running; if it is, only the instance is started
startsap db: Starts only the database
startsap all: Default entry; starts both the database and the R/3 instance
Q 6) What are the different type of work process ?
The following work process in SAP R/3
1) Dialog (D): each dispatcher needs at least 2 dialog work processes (not shown above)
2) Spool (S): at least 1 per R/3 System (more than 1 per dispatcher allowed)
3) Update (V): at least 1 per R/3 System (more than 1 per dispatcher allowed)
4) Background (B): at least 2 per R/3 System (more than 1 per dispatcher allowed)
5) Enqueue (E): exactly 1 per R/3 System (only 1 E work process is required and allowed)
Q7)In what sequence are profile parameter read?
R/3 processes read the appropriate parameters from a C source in the R/3
kernel
The default profile /usr/sap//SYS/profile/DEFAULT.PFL is read; profile values already defined in the C
source are replaced with the values in the default profile
The instance profile /usr/sap//SYS/profile/__ is read; profile values already defined in the default profile
or in the C source are replaced with the values defined in the instance profile
This procedure ensures that system parameter values reflect the instance profile and the values in the
default profile and the C source.
Q8) What are the step involved before stopping R/3 system?
Before stopping any R/3 system following steps are basic steps to be
performed:
1. Before the R/3 System is stopped, the R/3 System administrator should check the:
Check if any background jobs from any application server are active or have been triggered externally.
2. Use transaction SM37
3. Check if the background work process (BTC) is running in any application server.
4. Check if any update records are open when the system is stopped, the records are rolled back and set
to status in it.
5. At startup, the records are processed again.
6. The administrator must decide whether to interrupt the jobs or wait until they are finished.
7. Give system users advance warning of the system shutdown.
8. To create a system message, you can use transaction SM02.
9. Before shutting down the system, use transaction SM04 to check whether users are still logged on,
and ask them to log off.
10. The R/3 System administrator and administrators of external systems should also inform one
another about data transfers between their respective systems.
Q9) diff b/w Database Independent Files & Database Dependent files?
a) Database Independent Files
This is of the nomenclature SAPEXE_<Patch level>-<release date>.SAR
b) Database Dependent files
This is of the nomenclature SAPEXEDB_<Patch level>-<releasedate>.SAR
