SAP BASIS FAQs for Freshers
1) What will happen if the Central instance of the system failed?
Ans: Central instance failed SAP MMC will not start
2) Where will we install the central instance, in the server or in a Specific computer?
Ans: One can create background job by the fallowing ways:
- By the transaction code SM36
- You can create background job by the "start program in the background" option of transaction code SA38( ABAP: execute the program) and SE38 ( ABAP editor).
- Through an external interface
- Internal Interface
3) Did only the standard jobs can be performed as background jobs or else how to create a new background job?
Get More Questions and Answers with Explanation related to SAP BASIS at SAP BASIS Forum.
4) How the message server differs from the Dialog work process?
5) How will you differentiate SID and central instance, according to their use?
Ans: Types of users present in SAP
Dialog, Communication, System, Service, 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 won’t apply for this type. So, this can be used to run background jobs and in between RFCs so that jobs or RFC communications won’t fail due to the expiry of the password.
Note :- 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 Internet Transaction Server (ITS)
There won’t 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.
6) What is the role of variants? Can we able to provide a new name of variants we created?
Read Here for more SAP BASIS Transaction Codes.
7) What is the role of operation modes, why should we need a tag (B/W dialog to background process) if we have a background job facility?
8) How to select a software package of java and oracle version for the SAP system we are installing (Did the client provide the version of the software or we have to find it)?
Ans: Client will provide full details regarding java version and oracle version.
9) Where and why we are using DDIC and SAP*?
Ans: One can use ddic and sap* beacuse those are deafult users ids created at time of installation, we use su01 to login.
10) What is Microsoft management console?
Ans: The SAP Microsoft Management Console (SAP MMC) provides a common framework for system management. It integrates previously separate tools in a common user interface for centralized system management. Although the SAP MMC itself does not offer any management functionality, it provides an environment for incorporating and accessing management tools. Tools are integrated in the SAP MMC withsnap-ins for standardized access to functions.
SAP has developed the SAP Systems Manager snap-in let you monitor, start or stop the SAP system centrally from the SAP MMC. SAP recommends you to use the SAP MMC because it simplifies system administration and provides many new features.
You can use the SAP MMC for both ABAP and Java systems. If you use a Java system you can ignore references to ABAP. If you use an ABAP system you can ignore references to Java.
The SAP MMC offers the following features:
- You can monitor and control any number of SAP systems and application servers and ITS instances with a single tool if they are running on Windows. You can also monitor SAP instances running on different platforms.
- Once you have configured the console, you can save the configuration in a file and easily forward it to other users.
- The dual DCOM interface ISAPControl of the start service and IITSWatchdog of the ITS watchdog service let a third party use the functionality - for example from C, Java or Visual Basic - and let you integrate it into your own tools or scripts without having to use proprietary SAP mechanisms.
- The start service is available on all platforms and offers a new Web service interface, called SAPControl with better control and monitor capabilities. Some of the new snap-in features require the new Web service interface. You can access the Web service interface in your own applications from a Web service-enabled programming environment like C, Java, ABAP or .NET. The old ISAPControl DCOM interface has become obsolete but is still supported under Windows.
- The SAP MMC lets you to Display all SAP trace files, start profile, instance parameters, the system environment and SAP environment
- Display the most serious alerts in the alert tree (AS ABAP transaction RZ20)
- Display the current status tree (AS ABAP transaction RZ20)
- Display and acknowledge current alerts (AS ABAP transaction RZ20)
- Display the SAP syslog for a functioning, offline, or malfunctioning SAP system (AS ABAP transaction SM21)
- Display the ABAP work process overview (AS ABAP transaction SM50)
- Display the ABAP and ICM queue statistics (dpmon)
- Display Application Server Java (AS Java) processes, caches, threads, web sessions, EJB sessions, remote objects, application aliases, and shared memory tables
- Display Java virtual machine garbage collection and heap memory information of the Application Server Java
- Display ICM threads, connections, caches and proxy connections
- Start or stop one or all application servers of a system with a mouse-click
- Restart the service without having to restart the application server
- Log on to an application server
- Start analysis tools in the SAP System for nodes in the alert tree
- Control Java or ABAP processes
- Modify dynamic profile parameters
- Start the following third-party tools, if available, to manage an application server or ITS instance:
- SSH client
Read Here for More SAP BASIS Interview Questions