SAP Basis Certification Sample Questions

Question:
When creating a logon group for Logon Load Balancing, which of the following CANNOT be specified?
Answer:
 A.  Maximum allowable response time.
 B.  Maximum number of users who may be logged on to the instance.
 C.  Name of the instance defined for the logon group.
 D.  Maximum number of sessions per user.
 E.  Name of the logon group

Question:
Which R/3 System user is used for starting external programs using SAP background jobs?
Answer:
 A.  DDIC
 B.  SAP*
 C.  SAPR3
 D.  SAPCPIC
 E.  <sid>adm

Question:
Name the R/3 System transaction used for mointoring a spool requests.
Answer:
A. SM50
B. SM51
C. SPAD
D. SP01
E. SM37

Question:
Which of the following is authorized to maintain R/3 user id parameters?
Answer:
 A.  Only the R/3 system administrator.
 B.  All R/3 users having an account in the same R/3 client.
 C.  Only the user himself.
 D.  Only the R/3 system administrator and the user.


Question:
Given a LAN with an R/3 Central Instance with database (Node: host1, Instance Name:DVEBMGS01, SAPSID:C11), and R/3 Dialog Instance (Node: host2), and several R/3 Frontend PC's what is the name of the profile where the SAPDBHOST parameter is defined?
Answer:
 A.  C11_DVEBMGS00_host1
 B.  The SAPDBHOST parameter is defined in the database startup profile.
 C.  TEMU.PFL
 D.  DEFAULT.PFL
 E.  START_DVEBMGS01_host1

Question:
Given and R/3 Central Instance with all services installed, using Instance ID01, and having the SAP ID of C11.  What is the name of the directory where the work process trace files are written (for Windows NT replace the "/" with "\")?
Answer:
 A.  /usr/sap/C11/DVEBMGS01/data
 B.  /usr/sap/C11/DVEBMGS01/log
 C.  /usr/sap/C11/DVEBMGS01/work
 D.  The trace files are written in internal database tables.
 E.  The trace files are written in the home directory of the database.

Question:
Which of the following functions is NOT possible using the SAP Online Service System (OSS)?
Answer: (All is possible)
A.  Execute online searches for R/3 Notes.
B.  Register problems with the SAP Hotline.
C.  Lookup SAP training dates and course offerings.
D.  Register changes to SAP objects.
E.  Apply for official Internet address from SAP.

Find The List of Users Logged in to SAP System

How to find out the list of users logged in to sap system for the last 5 days?
Solution:
1. TCode st03n
2. Then check that screen shot path
3. Then put Date, Time period from and to

Another T code you can used is STAD

What Is The Use of Solution Manager

What is the use of solution manager, and what we can do with solution manager?
Now a days solution manager is mandatory.  
1. it is used for generating keys and downloading support packages 
2. it is used to document  user  requirments and preparing senarios what needs to to be adopted using solution manager, where the blue print is the part of solution manager 
3. it is used for reporting, solution desk,to manage the change requests and use to monitor entire landcape Central message processing in the SAP Solution Manager:  
- Display customer data, problem description, priority, attached documents, Service Level Agreements (SLA)
- Assign processor
- Send messages to the creator and other processors
- Forward message to other processors or support units
- Create documents and URLs
- Attach documents
- Status assignment and monitoring
- Create a worklist with selection conditions

Things To Check When SAP System Down

How to troubleshoot my sap system when it was down?  What are the things I have to check?
A Basic Technical Troubleshooting:


Perform initial analysis.
Identify if something has changed (software or hardware installation, scripts, profile parameters, database structure).


System (hardware) is down:
- Check console messages.
- Reboot and keep important system log files.
- Check hardware components.
- Analyze with diagnosis tools.
- Escalation procedure: call hardware support.
- Check main log files.
- Analyze with diagnostic tools.
- Start up/shut down log files.
- Check operating system log files.
- Identify other problems (startup/shutdown, disks and operating systems, database, operational R/3, performance).

Startup and shutdown problems (R/3 and application servers):
1. Check processes or services at operating system level.
2. Check whether database is up.
3. Check connection with database (i.e., tnsping, R3trans). 
4. Check whether file systems are full. 
5. Check for network problems in the server network. 
6. Check backup log for problems after backup. 
7. Check for problems after system crash. 
8. Check for problems with PDC file server. 
9. Check files permissions and authorizations. 
10. Manually start up or shut down database and then the application server. 
11. Check hosts and services files.

Operating system problems:
1. Check operating system log and event viewers.
2. Check disks and file systems.
3. Check directories and permissions.
4. Check path names.
5. Check security.
Database problems:

- Starting and stopping database
- Refer to startup problems.
- Check database specific error log file.
- Database storage status
- Check database error numbers.
- Check database alerts.

R/3 application operational problems:
1. Check whether all users are affected.
2. Check whether there is no work at all, or whether work is just limited. 
3. Check whether application servers are available (SM51). Check with standard monitoring transactions: SM50, SM04, SM12, SM13, ST22, SM37, and SP01. 
4. Check trace files on work directory (/usr/sap/<SID>/<instance>/work). 
5. Check SAP systems alerts. 
6. Analyze database problems.

Specific operational problems:-
Problems with printing:
A. Check network.
B. Check SP01/SPAD spool request logs.
C. Check system log.

Problems with batch input:
A. Check directories and files.
B. Check SM35 logs.
C. Check system log.

Problems with lock entries:
A. Check lock entries.
B. Check update process.

Problems with update process:
A. Check update process.
B. Check database.
C. Check network connections.

4. Problems with enqueue:
A. Check database.
B. Check instance parameters.
C. Check operating system processes.

5. Problems with message server:
A. Check processes.
B. Check network.
C. Check log files at work directory.

6. Problems with background processing:
A. Check job log.
B. Check background system consistency.
C. Check file systems.
D. Check system log.

7. Performance problems:
1. Perform workload analysis.
2. Perform debugging.
3. Perform runtime analysis.
4. Perform SQL trace.
5. Check for operating system problems.
6. Check disks for input/output bottlenecks.

Resolution process:
1. Search or SAPnet notes for hints, solutions, or workarounds. 
2. Escalation: enter message on SAP hotline or SAPnet. 
3. Enter problem on hardware partner hotline. 
4. Follow problem actions and SAP indications. 
5. Apply patches and corrections; test and verify results.

Tcodes used for Daily System Monitoring

After running daily system monitoring transaction, what should we check for:


In st22 look for the core dumps if any and report to the respective consultants and try to know why it happened.
In sm21 try to check for errors.
In sp01 try to see if any spool jobs have failed.
In st02 look if any swaps are happening, swaps are not good for performance.
In st04 look for Database alert logs and Performance.
In st03 look for ratio hits.
In sm59 look for connectivety tesing if there are other systems also connected to your SAP R/3 system
In db13 look if the jobs have run successfully.
In sm37 look for any cancelled scheduled job and take action appropriately.
In sm12 look for any pending locks from the previous days.
In sm13 look for any hanged updates, or updates pending for long or updates in PRIV mode.

SAP Administrator Daily Activities

SAP DAILY ACTIVITIES
1] Check that all the application servers are up:
 sm51           SAP Servers
 sm04/al08    Logon Users


2] Check that daily backup are executed without errors
 db12 Backup logs: overview


3] SAP standard background jobs are running successfully. Review for cancelled and critical jobs.
 sm37 Background jobs--- Check for successful completion  of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.


4] Operating system Monitoring
 st06


5] Extents monitoring
 db02 Database monitoring--Check for max-extents reached


6] Check work-processes(started from sm51)
 sm50 Process overview-- All work processes with a running  or waiting status.


7] Check system log
 sm21 System log-- Set date and time to before the last log  review. Check for errors ,warning, security, message-bends,   database events.


8] Review workload statistics
 st03 Workload analysis of <sid>
 sto2 tune summary instance


9] Look for any failed updates
 sm13 update records


10] check for old locks
 sm12 lock entry list


11] Check for spool problems
 sp01 spool request screen-- check for spool that are in  request for over an hour.


12] Review and resolve dumps
 st22 ABAP Dump analysis


13] Checking .trc file in SAP trace directory for block corruption on daily basis.
 C:\ORacle\sid\saptrace


14] Archive backup
 brarchive -f force -cds -c
 Insert the archive backup tape


15] Review NT system logs for problem
 -> NT system log- look 4 errors or failures
 -> NT security log- failed logon 2 sap servers
 -> NT Application log -look 4 errors or failures 

Scheduling a New Job in SAP

What are the steps to schedule a new job run?


1.  Log on to the appropriate SAP instance and client using BATCH_USER.
2.  Go to transaction SM36.
3.  On the Define Background Job screen, fill in the Job name field with the new job name. 
Select a Job Class priority of A for High, B for Medium, and C for Low. 
It is SAP’s recommendation that all client-owned jobs begin with a Z for identification purposes.  And most Basis people recommend the next two characters be the initials for the SAP module for which the SAP instance runs.  Like ZBC* for a Basis job, and ZHR* for a Human Resources job. 
Click on the Specify start condition button or press F5.
4.  On the Start Time popup, click the Immediate button to start the job right away, or click the Date\Time button to specify a date\time in the future for which the job run. 
Click “on” the Periodic job radio button and then click the Period values button if you want to schedule to job to run on a periodic basis. 
Provide the periodic values and click Save back to the main Define Background Job screen.
5.  On the main Define Background Job screen, click the Step button.
6.  On the Create Step 1 popup, fill in the ABAP program Name and any Variant needed to run the program – you had to have created the variant using BATCH_USER before using it here.  Then click Save once more.
7.  Back on the Define Background Job screen, check that all the job information is correct and then click the Save button one last time.