Interview Questions For SAP Basis
Interview Questions For SAP Basis
Interview Questions For SAP Basis
Private mode is a mode where the heap data is getting exclusively allocated by the user
and is no more shared across the system. This happens when your extended memory is
exhausted.
OPS$ is the mechanism the <SID>adm users uses to connect to the database .
Why do you use DDIC user not SAP* for Support Packs and SPam?
Do _NOT_ use neither DDIC nor SAP* for applying support packages. Copy DDIC to a
separate user and use that user to apply them.
on Unix:
$ for i in *.SAR; do SAPCAR -xvf $i; done
A "transactional RFC" means, that either both parties agree that the data was correctly
transfered - or not. There is no "half data transfer".
What is the use of Trusted system. I know that there is no need of UID and PWD to
communicate with partner system. In what situation it is good to go for Trusted
system ?
E. g. if you have an R/3 system and a BW system and don't want to maintain passwords.
Same goes for CRM and a lot of other systems/applications.
But keep in mind, that it's not only a technical issue whether to switch to asynchronous.
The application must also be able to handle that correctly.
Which table contains the details related to Q defined in SPAM? Is there a way to
revert back the Q defined? If yes, How?
There is a "delete" button when you define the queue. If you already started the import
it's no more possible since the system will become inconsistent.
The developer key is a combination of you installation number, your license key (that
you get from http://service.sap.com/licensekey) and the user name. You need this for
each person that will make changes (Dictionary or programs) in the system.
SAP Exchange Infrastructure (SAP XI) is SAP's enterprise application integration (EAI)
software, a component of the NetWeaver product group used to facilitate the exchange of
information among a company's internal software and systems and those of external
parties. Like other NetWeaver components, SAP XI is compatible with software products
of other
companies.
SAP calls XI an integration broker because it mediates between entities with varying
requirements in terms of connectivity, format, and protocols. According to SAP, XI
reduces integration costs by providing a common repository for interfaces. The central
component of SAP XI is the SAP Integration Server, which facilitates interaction
between diverse operating systems and applications across internal and external
networked computer systems.
How to see when were the optimizer stats last time run? We are using win2k, oracle
9, sapr346c.
Assumed DB=Oracle
Select any table lets take MARA here but you should do the same for MSEG and few
others to see whether the dates match or not.Run the following command on the
command prompt:-
This gives you a straight answer .Else you can always fish around in DB14 for seeing
when the optimzer stats were updated.
What are SAP Notes? Where do I can find them? How to use it?
OSS is the online service system provided by SAP for support activities, like sometimes
some issues which we can't resolve, then we have to send it to SAP, it is only sent
through OSS and then SAP will login to our servers for doing the R&D of the issue.
SAP notes are the update information in SAP, frequently released by SAP.
OSS notes are online documents published by SAP in their web site
http://service.sap.com, aimed to take care of the following:
- Product errors
- Product modifications
- Product upgrades
- FAQs
- Consulting notes
- Customizing notes etc.
The notes contain, among other things, program corrections, methods for table/field
additions, deletions /corrections, customization changes etc.
Once in a year or so, SAP comes out with upgrades which will include many of the notes
issues between the provious upgrade and once being issues.
Certain notes (which are limited to code correction) can be implemented in a simple way
using transaction SNOTE.
OSS notes are the corrections and suggestions given by SAP for standard
objects(Like programs, Function modules).
Some notes contain critical information about the component and have to be used in
addition to the component guides that are delivered to the customer.
Some other notes provide corrections to the code as a fix before a support package is
released. The subsequent SPs contain the corrections that were delivered through notes
before. Hence it is important to check the current SP level of your system and the SP
level with which the corrections come before applying the notes.
Some notes provide just manual corrections (in which case the procedure to make the
manual corrections also need to be specified in the notes) and other provide automatic
corrections (which are applied through TA SNOTE).
In order to fix one of the problem in R/3 system, SAP will asked you to download an
OSS notes which is a ".car" file.
Copy the the data file generated in the data transport directory
( ej: = /usr/Sap/trans/data).
Copy the the cofile file generated in the cofiles transport directory
( = ej: /usr/Sap/trans/cofiles).
Upload the support package with SPAM transaction and the support package will show
"New support packages".
**********
1) UNIX only:
2) Windows NT only:
Log on as user <SAPSID>ADM.
cd \USR\SAP\TRANS
CAR -xvf TMP\<ARCHIVE_NAME>.CAR
After you run SPAM you MUST run STMS and check the transport queues
**********
As per 315963 note you can direct made the changes in the program or you can apply the
support pack.
a) If you want to apply correction then first you need to register the object in SAP, so that
you will get the Access key and then you can make the changes.
b) If you want to import the support pack then you need to down load from SAP market-
place. and this is in CAR file. and then you need extract the same using CAR utility.
ex: CAR -xvf abc.car
or
you can directly apply the patch from SAPGUI, login to 000 client and then you can load
the patch from Presentation server.
For example if you want to apply patch 07 and you are having 05 then you need to
apply 06 and then apply 07.
**********
It would definitely be better to apply the latest spam/saint spam manager, tp, R3trans and
possibly a new kernel patch.
This is not a simple task to complete on the fly. By applying SAP support packs, you
may run into problems with SPDD and SPAU adjustments. Also include the fact that the
support packages may break one of your transactions. You may want to test this in your
sandbox environment, if you have one, before tackling it.
In most situation when you apply support packages, it can takes about 3 weeks to fully
test the support packages before you can apply them to the production system.
Do test your "golden" transactions to make sure that they are not broken. If you are not
familiar with SPDD and/or SPAU adjustments than do not attempt to load support
packages.
You may be better off just to modify the SAP object in question via OSS note.
What is the tcode to compare 2 roles in order to find out the duplicate transaction
code?
For role comparison both the roles must be in the same system, in same client.
If the roles are in different system, then transport the role into one of the system and do
comparison. If no transport connection defined then, you can use the upload and
download option in the PFCG.
3. Click on Across systems option it will give option to select the sys name under Remote
Comparison there enter the SYS ID between which system you want to do comparison
and put the role name in compare role section then execute it will give you the result.
4. If there are any difference between then the t-codes it will be in red color otherwise in
yellow?
How do I use SUIM to compare Roles which are different Clients of the same
system?
The RFC destinations are client independent but the login details provided in the RFC
destination are client dependent right?
So all you need is to define to RFC destinations (looping) pointing to the same system.
In one of the RFC destinations, you can provide the user ID details of the source system
client while in the other, you can provide the details of the target client.
So now all you have to do is goto SUIM --> Comparisons--> Cross systems and provide
the RFC destination details and the role names.
or
Go to PFCG --> In menu click on utilities --> Click on role comparison tool or use t-code
PFCG_CMP
Give the role name and select the comparison destination give destination and execute.
Transaction SUGR - have a look. Purpose for example is to give certain system admin
rights to unlock / change password only to a given user group. You assign user group to
an user id via SU01.
User group can be used for different reasons and in different way.
In the latest versions of SAP, actually two types of usergroup exist, the authorization user
group and the general user groups.
Naturally the main reason of user groups is to categorize user into a common
denominator.
The general user group can be used in conjunction with SUIM and SU10, to select all the
users in a specific group. User can only be member of one authorization user group but
several general user group.
One of the Primary uses of user groups is to sort users into logical groups.
User Groups also allow segregation of user maintenance, this is especially useful in a
large organisation as you can control who your user admin team can maintain - an
example would be giving a team leader the authority to change passwords for users in
their team.
The most important factor identified is that the lack of user groups is an indication that
there may be problems with the user build process. This is very "fuzzy" but is a bit of a
warning flag.
The Auditors job is to provide assurance that SAP is set up and administered in a way
that minimises risks to the financial data produced. If the only thing they have picked up
on is the lack of usergroups then you will be fine.
If you are in any doubt whatsoever ASK THE AUDITOR. They would have produced a
report listing why they feel there is a risk by not having User Groups implemented. If you
feel that the risk is mitigated by other measures then let them know. It works best as a 2
way process and both parties can learn something.
saplicense -get
- Login as '<sid>adm'
- Unix > startsap all (this will startup the SAP and database system)
Note :-
startsap R3 - will startup SAP only
startsap DB - will startup database only
- Check if there are any users or processes executing in the SAP System
(use transaction code SM50 and SM04 - delete their session before shutdown)
- Login as '<sid>adm'
- Unix > stopsap all (this will shutdown the SAP and database system)
Note :-
stopsap R3 - will shutdown SAP only
stopsap DB - will shutdown database only