Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
From SM51,we can Check whether all SAP servers are running or not
When application server is not available, we can‘t find the host name for the server.
we can also get the information about number of users logged to the instances
We can estimate the current activities and the resulting load on the instance
And also we can monitor list of all app servers, sever info, Queue info and SNC status in SM51
We can also view the status of all active/inactive instances using RZ03
We can check for load distribution and average response time and quality ratio ……… (in SMLG---
press F5 for load distribution –now we can see log on groups, instance ,status, response time,
number of users per instance ,quality of load balancing and dialog steps of each instance.
If any application server is goes down for any reason, user can still connect the group which will
assign the best application server (SPACE –default log on group).
1
5. Checking for ABAP Dumps in ST22
2
7. Check for any terminated updates in SM13
We can check for any hanged updates, or updates pending for long or updates in PRIV mode
We can check the system update records with error status or which have not yet been processed.
Based on the type of error ,request the user repeat the data entry which performs the update
All update requests are stored in VBLOG table
we can monitor the cancelled update requests and all update requests in SM14
10. Check for the terminated back ground jobs and log time running jobs in SM37
We can check the status of the job, if it is in active state for long time, we need to cancel that
job(job-cancel)
If it is still in active state we need to check the status in Job menu
Still it is in same state we should kill that particular work process from SAP level(SM51) or OS level
(DPMON)
If one particular job is cancelled more than 20 times ,a mail should be sent to the user
3
11. Check for Spool requests SP01
Look for spool jobs that have been ―in process‖ for an hour.
Checking for problems with spool and output request
Check logs and possible causes of printing problems
Check the output request attributes, the log files, and the size of the print job
Check whether the device type and what the access method is for the device.
Deleting old spool requests or scheduling the background job which automatically deletes them, If
there are more than 50 spool errors, then they have to be deleted.
We can monitor the system alerts from RZ20-doubleclick on the corresponding monitor-in that
screen click on the Open alert.
We can set the thresholds /alerts and our own monitors in RZ20-extras menu-click on activate
maintenance function-in that we can create threshold with colors
We can also monitor database alert log in ST04-Detailed analysis-error log,
in OS level -Oracle/SID/sap trace/back ground directory
We can find the all data base errors and warnings in DB16
4
System log in SM21
PERFORMANCE TUNING:
Large Load Time Program (PXA) and Screen (CUA) buffers are too small
Large DB request Time Can problem with Expensive SQL statements , missing indexes
,CPU/Memory bottle necks and DB server
Large CPU time Can be problem with processing large tables and frequently accessing
R/3 buffers
Large processing Time CPU bottle necks, Net work problem and common problems
Response Time Time taken by the user request from dispatcher to GUI
Wait Time 10% of Average Response Time
Roll –wait Time 200 ms
Load Time 10% of Average Response Time
DB request Time 40% of Average Response Time – Wait Time
CPU time 40% of Average Response Time – Wait Time
processing Time Not much larger than CPU Time
Response Time Time taken by the user request from dispatcher to GUI
Wait Time Work processes request is waiting in dispatcher Queue
Roll –In User context data moves from the roll area to work process
5
Roll –Out process of user context data from the work process to Roll area
If single user or single transaction getting this (large response time) performance problem, we
need to tune the program which is causing large response time
From ST03, The average response time for dialog-step should not be more than 1000 ms
o We can Check for the top programs which are causing high data base request time and
programs with high CPU time, mainly we concentrate on customized programs
o If the average DB request time is more than 500 ms
It can problem with missing indexes on tables and expensive SQL statements
We can check for missing indexes in DB02 (detail analysis-missing indexes), if we find any missing
indexes .., we can raise the ticket to ABAPers to re-create the indexes for proper fields.
And also Check the expensive SQL statements in St04,which are taking High disk reads(> 5% of
total physical reads), High buffer gets/misses(> 5% of total reads) monitoring (detailed analysis
menu-SQL request tab),if we got any expensive SQL statement ,we need to optimize that SQl
statement by ABAP‘ers
o If the CPU time is greater than 400 ms
o It can problem with wrong logic of the ABAP program
o We can analyze the time consuming transaction using STAT and raise the ticket to ABAPers
to make correction of wrong logic or reprogram
---------------------------------------------------------------------------------------------------------
If all transactions are getting the (large response time) performance problem we need to analyze the
programs which are causing large Wait Time, large roll- wait time, and large load time, large DB request
time, large CPU time and large processing time.
If the average Wait time is more than 50 ms
It can problem with long running jobs.
We can identify the long running jobs by using SM50 or SM66 and tune that long running job or
terminate them.
Work processes are blocked by long running reports, this problem occurring frequently we need to
increase the work processes.
6
The average number of free work processes available in the system should be sufficiently to ensure that
user‘s queries are processed with out delay
//-----(if user start programs such as reports with very long response times, the affected work processes
may be occupied for several minutes. This may mean that number of remaining work processes is not
sufficient to process the queries of other users, which could cause wait times.)—
It can problem with Program (PXA) and Screen (CUA) buffers are too small
From ST02, We can check for the Buffer quality ,it should be more than 90%,If it is less than 90%
We can check for Swaps on buffer, swaps should be in red color and not more than 5000 swaps day, if
we getting more swaps on buffers
We need to increase program and screen buffer sizes
//----- (Program (PXA) buffer: This buffer stores the compiled executable version of the ABAP
programs, also known as program loads. abap/buffersize
Screen (CUA) buffer: This buffer stores menu data, buttons and related SAPGui functionality-
rsdb/cua/buffersize) ---//
Memory management
If any work process is entered PRIV mode than the system performance will be very poor, in this situation,
We need to restrict the memory usage by increasing user context data, in order to restrict we have
some parameters for Dialog and Non-dialog step.
The main areas for user context data is roll area, extended memory and heap area
Roll area—Stores the initial part of user contexts like work process information, Authorization
information, user context data initial size is 150 to 200 MB.
Extended memory—Uncompleted transaction information and Stores the main part of
user context
Heap/Local memory—Stores the variable part of user context data
Dialog work process user context data memory allocation (ST02)
1. Ztta/roll_first :Size of the 1st allocated memory area from the roll area
2. Ztta/roll_extension : amount of memory that a work process can request in extended memory
in bytes,2GB(NT),one by 3rd of extended memory for other systems
3. Em/initial_size_MB : Initial size of extended memory in MB
4. Ztta/roll_area: Size of roll area in bytes 6.5 MB for UNIX systems, 2MB for NT.
5. Abap/heap_area_dia:Size of Heap memory in bytes that dialog work process can request, 2GB
(default)
6. Abap/heap_area_total : maximum heap memory for all work process in bytes
7. Abap/heap_limit:If a work process requests more memory than the value of this parameter
allows, the work process is automatically restarted (200 MB)
8
Applying Support Packs
1st ,check the current levels of support pack levels in our system
(SPAM-select all support packages)
Now down load the relevant support stacks from Sap market place(services/sap.com/sp-stacks)
Un car the all .CAR files in usr/sap/trans> directory at OS level using SAPCAR –xvf <car files>
Now 2 files (.ATT & .PAT )will be copied automatically in EPS/IN folder in trans directory
So we need to check the available space in trans directory
Ensure that no users logged in.
Now logon with 000 client with user DDIC and go to SPAM
Now import the down loaded files in to the Queue (SPAM-support packages-download packages-from front
end/from application server)
We need to take the back up of the system before applying the support packages
We should apply the support pack layers one by one ,based on dependencies double click on the support
pack and click continue and confirm
I think practically most of the cases there was problem when apply all support packages in groups;
especially when the package size is quite big and quite complex such as SAPKH
If we have small size of packages ;I think it is fine to group the packages but no more than a certain number let say
no more than 5
9
To enable our developers to adjust modifications, go to the SE01 and create a request that includes
task for the developers
Then go to SAINT—Extras menu –adjust modification, to go to either transition SPAU or SPDD.
Kernel Up gradation:
10
TMS CONFIGURATION
TPPARAM (Usr/Sap/Trans/bin)
Transport parameter file must be configured for the transport control program ‗tp‘ to function properly.
This includes entries for each of the r/3 system transports like trans dir, DB name DB type, and
Message server port number
Transport layer is used to reporting all development objects and assigned to all the objects that come
from the development system.
Repair mode: modifying an object in the system in which it is created.
OS level Transports: We can transport the change requests at OS level by using TP program and R3 Trans…
TP ---/usr/sap/trans>
‖-tp addtobuffer <change request no> <SID> pf=TP_DOMAIN_<SID>.PFL‖
―tp import <change request no> <SID> client=<client no> pf=TP_DOMAIN_<SID>.PFL‖
11
Return Codes:
0 –Successful
4---Warning message
8---Error message
12—serious error
13-OS terminate the transport
TP commands:
tp export <change request>: The complete objects in the request from the source system will be
transported. This command also Used by SAP System when it releases a
request.
tp r3e <change request>: R3trans export of one transport request.
tp sde <change request>: Application defined objects in one transport request can be exported.
tp tst <change request><SAP system >: The test import for transport request can be done using this
command.
tp createinfo <change request>: This command creates a information file that is automatically done
during the export.
tp verse <request>: This command creates version creates versions of the objects in the specified
request.
tp showbuffer <sid>: Shows all the change requests ready to be imported to the target
system.
tp count <sid>: Using this command users can find out the number of requests in the
buffer waiting for import.
tp go <sid>: This command shows the environment variables needed for the connection to
the database
of the <sid> or target system.
12
tp showparams <sid>: All the values of modifiable tp parameters in the global parameter file. The
default value is shown for parameters that
Tp showbuffer<sID> : show all change requests ready to be imported to the target system
Tp count<SID> number of requests in the buffer waiting for import
Tp importall<SID>: Imports all the request from buffer to the target system
Tp put<SID> imports all the request from buffer to the target system and locks the
system
tp sapstart <sid>: To start the R/3 system.
tp stopsap <sid>: To stop the R/3 system.
tp dbstart <sid>: To start the database.
tp dbstop <sid>: To stop the database
tp locksys <sid>: This command locks the system for all the users except SAP* and DDIC. The
users that have already logged on are not affected by the call.
tp unlocksys <sid>: This command unlocks the system for all the users.
tp lock_eu <sid>: This command sets the system change option to "system can not be changed"
tmporarily.
tp unlock_eu <sid>: This command unlocks the system for all the changes.
tp backupall <sid>: This command starts a complete backup using R3trans command. It uses
/usr/sap/trans/backup directory for the backup
R3trans commands:
13
BACK UP
ON-Line backup—taking the backup of archive logs and as an incremental backup we have to take
the backup of redo logs for the time taken for archive logs backup, in this case no down time
needed.
On line back up is not consistence, it might have some negative effects on performance, so it‘s
better to schedule at night times where there is not much online activity
OFF-Line backup---Take complete Archive +redo logs, in this case down time is required.
Off line back up is consistence.
Backup Scheduling
Go to DB13, we can schedule database backup using DBA planning calendar by selecting a particular
date.
Double click on the date and select the action to be performed and click ―start immediately‖.
It will ask for storage location, these location can be either tapes or disks, the location can be set
the parameter ‗backup_dev_type=Tape‖ in backup profile ―initSID.dba‖(oracle home\dbs) and
―start ―the backup
The status of the backup can be checked in DB12
BACKINIT:
Is the inter face that connects 3rd party S/W tool to SAP in order to take back up on tape drives.
This technology mainly used to take OFF-LINE back up for 24*7 environment systems
Legato server intimates the legato client regarding the back up
This legato client takes a snapshot of information of production system and stored in bits and
bytes,(which is more easier and no time taking when compared to normal offline back up).
Snapshot image taken will be mounted on another storage system, (while data stored in the
difference of time (incremental) back up will be taken with another snapshot and stored in a
different disk in the storage system.)
After completely taking the snapshot of complete data and incremental data, they both are
clubbed together to give a complete full back up image in the storage system.
Now this back up image on storage system is complete back up of production system and this is
taken as on tape libraries
_______________________________________ _________________________
14
Backup Database (SAPDBA) Backup Offline Redo logs
(SAPDBA)
__________________________
_______________________________________
Backup parameters:((init<SID>.sap)
backup_mode = all backup_type = offline
backup_dev_type = tape backup_root_dir = D:\oracle\RP1\sapbackup
stage_root_dir = D:\oracle\RP1\sapbackup archive_function = save
archive_copy_dir = D:\oracle\RP1\sapbackup archive_stage_dir = D:\oracle\RP1\sapbackup
new_db_home = X:\oracle\C11 tape_address = /dev/nmt0
expir_period = 30 util_par_file = initRP1.utl
mount_par_file = initRP1.mnt tape_copy_cmd = cpio
15
disk_copy_cmd = copy split_cmd = "<split_cmd> [$]"
tape_size = 1200M tape_size_arch = 1200M
Tablespace administration
Table space: Table spaces are logical storage objects, contains the database data and indexes
Indexes: Indexes are objects associated with tables that are used to speed up the search and execution of
SQL
statements, creating or deleting indexes does not affect the associated table.
Extent: Collection of oracle blocks We have some Storage parameters for Extent
INITIAL (First extent): It‘s the size of the first extents, it should be large enough. we need to
set ―compress
extents = NO‖.
NEXT (New Extent): The size of the new extent. this value can be calculated automatically by
TGORA ,IGORA tables and suggested next extent sizes for the data base objects. the number of extents
reaching the lmit, we can change the NEXT parameter value to large size ,‖max_next_sze‖
= max 2GB in init<SID>.dba file.
MAXEXTENT: The maximum number of allowed extents for the segment. It‘s generally set to 100
for oracle block
MINEXTENT: It‘s the starting number of the extents when the object is created. It‘s normally
always set to 1.
Block: It‘s the smallest physical storage unit in the data base. Tables and indexes are stored in individual
data blocks. The
size is defined in parameter ‖db_block_size‖ in init<SID>.ora file, default 8k
16
Table space Increasing
If the Usage % of any table space is more than 90 %( DB02), then we have to increasing the table
space by adding a table file.
Using SAPDBA tool, we can increase the table space
In command prompt, enter SAPDBA and select the option C for ‗space administration‘ in that, select
option ‗F‘ to ―alter table space and add data file‖
The system will first ask if we want to use file systems or raw devices for the new data file.
On this new screen shows the table space name in the header and it also displays some default
values for the new data file.
And if we want reset the default values by selecting the options like File system or raw device ,Select
path and Display current files
We need to set ‗auto extend ON‖ to utilize the available space automatically.
During the table space name for which we want to increase ,we can check for free space available
free space on the disk for a mentioned table space and ‗start‘ then ‗continue‘
We can specify the size of the table space by checking the After the new data file has been
successfully created, the sapdba program will automatically show the menu for backing up the
database
If there are any errors while this process is running, an error message will be displayed and alert file
and the log file generated in the sapreorg directory(oracle /SID/sapreorg/space<SID> file)
______________________________________________________________________________
17
Alter tablespace add data file (SAPDBA)
3. Application tablespaces:
4. Customers tablespaces:
To create a new client we need to log in as user SAP* in client 000 with password PASS
o By using SCC4 –we will get the all clients available in the system
o Click on the change icon to the display mode
o Click on the ―new entries‖ button on the application tool bar to define the client
o And enter client number with meaningful description ,role of the client which can be
production,testing,customizing and training
o Specify the change and transport for client-dependent objects
Changes without automatic recording—the client can be customized but system will
not automatically generate change request
Automatic recording of changes
No changes allowed—does not allow any modifications on the client
No transports allowed
o Specify the Client – independent object changes
Changes to repository and client-independent customizing allowed
No changes to client –independent customizing objects
No changes to repository objects
No changes to repository and client-customizing objects
o And we can set the protection levels for client copy and comparison tool]
Level 1: no restriction
Level 2: no overwriting
Level 3: no over writing and external adaptability—client is protected against read
access by other clients
o Finally we have to select some restriction
Currently locked due to client copy and Protection against SAP upgrade
Clint copy profiles
SAP_ALL--- All client specific data.
SAP_APPL---Customizing and application data
SAP_USER-- User master records and authorization profiles
SAP_CUST---Copy customizing data
SAP_UCUS-- User master records and Customizing
SAP_UAPP---All users, customizing ,master records and transaction data
Background reports while client copy (in new client only) RSCLXCOP RSCLCCOP
19
Client locking:
tp LOCKSYS pf=tp param path ------>lock all users except DDIC
We can perform the local client copy by using SCCL-Where we copy the data into the new client
from another client with in the same system
We can do Remote client copy by using SCC9—where we copy the data into new client from
another system and data can also be filled into the new client from another system by transport
request.
―Logging into the new client with user SAP* and password PASS, and specify the source client and
select the profile as per our requirement, this profile indicates what kind of data from the source to
copy into the new client.
Use the Test run option. Test run include an estimate the data to be moved (Client size, errors and
estimate time).
After these steps, click on the execute tab, depending on the data this process may take several
hours, So we should run in background and if possible in night.‖
Check the client copy log in SCC3
20
We can do the client export/ import using SCC8/SCC7—To export/import the client to different
network R3 system 0r other landscape R3 system….,
if the client already exists in the target system, we should first delete it
―Logging into the source system & client, and select the profile as per our requirement, this profile
indicates what kind of data from the source to copy into the new client, and specify the Target
system
When the export is finished ,we get 2 data files as RO9xxxxx.SID ,RT9xxxxx.SID and 3 control
files like KO9xxxxx.SID(client –independent objects), KX9xxxxx.SID(client –dependent long text)
and KT9xxxxx.SID(client –dependent tables)
Now we have to import these files manually in target system using the tp program, the order is
SIDKO9xxxxx SIDKT9xxxxx..
After importing the KO, KT, we have to run transaction SCC7 in the target system for importing
process, in which text files are automatically imported.
Before 4.0, we should run the RSCLIMP report in target system for import, when this report executed
the screen will ask us to enter SIDKTxxxxx.
21
Background jobs
Go to SM36,Give the ―jobName‖, select the Job class(A<B and C) and select the ―Target server‖ in
which this job has to be performed
Give the ― Start condition‖ which can be ―immediate‖, on a specific time‖,‖ after job‖ and ―after
event‖
If we want to run this periodically check the ―periodic job‖ check box
We can select an ABAP program or External program and save it
Than the particular job is schedule on particular time.
Classes: A-High priority –data transfer to and from external R3 application and time critical
B-middle priority –periodically started jobs…,
C—low priority –other jobs
States/Phases:
Scheduled-------the job has been saved .Start time has not been defined yet.
Release---------the job has been scheduled. Start time has been set. Job is waiting for an event
Ready-----------Job is ready to start execution. Start time has been reached
Active------------The job is currently being processed
Finished---------The job has been completed
We can check the job logs/status in SM37
22
OPERATION MODES
we can define operation modes to have many work processes during normal working hours which can be
automatically switch to background work processes during night for processing back ground jobs scheduled
at night times. (SAPMSSY2-system program)
To configure the operation modes using RZ04,
1. Define operation mode
2. Define the instance
3. Assign the instance and work process distribution to the operation mode
4. Set the operation mode time table
Manual switching: RZ03->click on ―operation mode‖ tab ->select shift and click on ―choose‖ tab
in this screen go to ―control‖ menu and select the ―switch operation mode‖ option in that click on
―selected servers‖.
TemSe (SP11 &SP12)—contains Spool data and background job logs and output requests
Temse location: ―rspo/store_location‖
If Value =db, stored at TST03 table in data base
If value =G, stored at usr/sap/<SID>/SYS/Global directory.
23
Spool server: if we have at least 1 spool work processes, called spool server
Print server: is holds print information, scheduled print jobs and print drivers
Spool Request :(SP01) contains administrative information like, printer name, number of pages to be
printed and spool Data Location.
Out put request: Spool data + administrative information
This system is used for scurrility administrators to display all security related information and also
record the security related information by using audit log.
The security audit log records areas such as successful and unsuccessful dialog log-on attempts,
RFC log-on attempts, changes to user master records, and transaction starts.
If we want to configure AIS in the system, we can easily track the system with respect to
auditing information.
We can use this system to generate Quarterly and yearly reports.
To activate audit log , we need to change the ―rsau/enable‖ parameter value as 1
We can monitor the audit log in SM20-security log-choose-all audit logs
We can configure the AIS by using SM19
Static configuration---need to restart after configuration
Dynamic configuration—No need to re start
1. Authorization—If a user has to be validated at logon then we have to enable this type of communication
2. Integrity---We can secure the changes of data by enabling this type of communication
3. Encryption—If entire communication has to be done in secure way ,then we have to select this type of
communication
We can enable SNC to users by indicating ―SNC name‖ and type of communication in log on pad for
particular server(SAP logon-new item-advanced)
24
Real time Problems
After releasing my change request, we can't find the change request in the queue
Go to STMS, select over view menu, in this menu we have import queue by selecting this sub
menu we will get all imported queues.
In that screen, we can select particular queue and go to extras menu choose the other request
option by using that we added the new request which is not available before.
And also for solving this problem we use to import the change request forcibly by applying U126
flag in TP program.
In TemSeTable There was one entry that repeated itself literally hundreds of times.
We can delete that particular entry by executing RSTS9803 report- (SAP notes 48400 and 11070)
In a PRD system, we have only one SPOOL Work process is enabled, there will be delays in
getting printout if printing in bulk is given.
We solved this by increasing No. of SPO to 2 and change the system parameter to load balance
the Spools
Very recently, we are unable to transport the requests, when we are trying to transport the
change requests they were hanged.
If you do a transport (tp import) and it fails it may leave entries in TRBAT and TBATG. Delete the
entries from these two tables before trying anymore transports. If you leave the entries in these
two tables all your transports will hang
We got a problem when applying a support package
Tables PAT01 and PAT03 stores the support package list and its phase respectively. We
can delete table contents for PAT03 (Truncate table sapr3.<table name> ; ) and update
table PAT01 the status which is unknown, so, We can go back and continue applying the patch
with no risk
25
If a print job has been printed out but contains unreadable characters and When nothing is
output the printer and output controller is in a wait status
Then we can check what the access method is for device. And also we can check the system log
(SM21) and look for time out messages and also check that all application servers running spool
work processes are reachable (SM51).
Oracle Errors
ORA-600-----internal errors
May be Block is corrupted in the hard disk
RAM issues and Disk errors
ORA-155-(Snapshot too old) >>>>Roll back / Undo segments size is not sufficient.
Dead locks >>>Need to increase the max trans on Objects
26
OS level Commands
Differences
27
Client independent Client dependent
ABAP programs ,R3 repository objects customizing, application data and user data
available through out entire system available from one client only
SPAU SPDD
Adjusting (modifying) repository objects Adjusting data dictionary objects
SAPevt SAPxpg
Is SAP event trigger program, used to To start external programs from R/3 , and sending
send events to the back ground job back job information.
scheduler for the release and execution
of background jobs
Message server Gateway server
To exchange the data and internal Allows the communication between R3, R2 and
messages external applications, by using CPIC protocol.
The message server routes the Exchanges larger amount of data between application
messages B/W application servers servers
SAP_ALL SAP_NEW
this profile allows the user to perform this profile provides general access
all To any new profiles and authorizations
functions in the system which are included in a new release of SAP.
It should not be granted to any users created by users after installation of SAP
in
The production environment.
V1 V2
Synchronous Asynchronous
Dialog waits for end of update Dialog does not waits for end of update task
task(success or failure can be handled) Can be processed later
Must be processed first Not time critical
Time crucial when no V2 update processes is configured , V1
Immediately update the critical data processes takes over V2 processes
Instance profile Default profile
if we change the parameter of instance if we change the parameters in default profile, it will
profile, it will affect that instance only affect the complete system
details about work process and has the default parameter values
instances
Remote client copy Client export/import
The data is exported to operating The data is exported to operating system in source
system in source client and imported to client and imported to target system a copy of data is
target system available in the operating system level for further
copies
000 001 066
Is the reference client Is a copy of 000,can 006 is a special client used to perform
with sample data use to start the the early watch
Sap recommends not customizing work or Default user is EARLY WATCH
to work in this client use also as a reference password SUPPORT
for productive purpose client
except for those
administrative tasks
SAP* DDIC Early watch
SAP* is the standard DDIC user is This user is used by SAP‘s early
28
SAP system super responsible for the watch experts.
user, does not require maintenance of the It has access to monitoring and
a user master record ABAP dictionary and performance data only
because it‘s defined in software logistics. Default pass word is SUPPORT
the code it self. This is the only user
SAP* has the SAP_ALL that can log into the
profile with all R/3 system, while a
authorizations. new release is being
password is 06071992 installed
password is 19920706
TABLES
Reports
SAP Notes:
0024092 Distribution of background jobs on application server
0006604 Deleting jobs at OS level
29
0039412 Number of work processes to configured
0031395 System parameters
0048400 To delete particular entry in TemSe
0016083 Standard jobs, reorganization jobs
0019706 Tuning the spooler
30
Communication B/W R3 system and BW System
Solution manager
Contains all SAP systems information and manages the land scape
We can do customization and synchronization with solman
We can monitor the solutions and service desk which includes system checking ,availability help desk
and ticket monitoring
And also solman gives the project management support like implementation support and upgrade
support. using SOLAR_PROJECT_ADMIN T-code(click on create and give the project name ,type
and just save it)
We can get the solman initial screen with SSM2 T-code.
SMSY
We can add the systems and configure the system land scape for solman using SMSY T-code
We can generate installation key (SMSY –system land scape menu –other object-system-click on key
symbol.)
And also we can create a connection between R3 systems and solman(check the RFC connection and
create logical system and click system tab in that click the create new with assistant option and
continue
32
RFC Connection
RFC Types
SRFC (Synchronous RFC): When connecting form GUI to SAP it used SRFC protocol
A SRFC (Asynchronous RFC): One dialog work processes may take one LUW (logical unit of work) and then
dialog work processes may take 2nd LUW
TRFC (Transactional RFC): It will complete the process in one shot.TRFC will send acknowledgement and
they will stored in data base level and guarantee execution.
QRFC (Queued RFC): This is order execution or sequence execution, in this RFC we have return
parameters and also guarantee execution.
X-RFC (XML over HTTP): For taking packets to the internet
Adaptive RFC It is used when adapt system is communicating with java
33
Authorizations and Security
Profiles (Authorization)
SAP_All – ----------------------------------All authorizations in R3 system
SAP_NEW—-------------------------------All the authorizations objects added in an R3 upgrade for
existing functions
S_A.ADMIN—-----------------------------system administration
S_ABAP_ALL—---------------------------all authorizations for ABAPers
S_BTCH_ADMS_ENQ_ALL—--------background processing
S_BTCH_USER-- ------------------------background processing
S_BTCH_ALL----------------------------- background processing
SAP_BC_USER_ADMIN_AG—------user administration
S_CTS_ADMIN-, S_TRANSPORT ----------TMS
SAP_BC_AUTH_PROFILE_ADMIN_AG—authorization profile administrator
User types
Dialog user—login possible
System user—login not possible, Communicating with in the system
Communication—Login not possible , Communication b/w the system,TMSADM is default
user for communication
Service—Login not possible , reporting purpose
Authorization field: the field on which we are giving an authorization in order to restrict (SU20)
Authorization Object: group of not more than 10 authorization fields (SU21)
S_DEVELOP, S-DATASET ,s-TABLE_DIS ,S_CTS_ADMIN, S_TRANSPORT, S_BTCH_ADM
Authorization Class: group of related authorization objects (SU21)
AAAB , BC_A , BC_C , BC_Z
Authorization: authorization field + activity (SU03)
Activity: is nothing but the action which you perform on the particular authorization field (TACT)
Profile: group of not more than 150 authorizations (SU02)
Role: Role contains profile+T.Codes+reports (PFCG)
Composite role: Group of roles, Based on Position/job (PFCG)
Derived role: derived the role from parent role, based on the Organization level (Company code, Plant,
Division)
Authorization check: SU24, we can analyze the authorization problems and assign the authorization
objects to the T-
34
Code.
Checked : can be add manually in PFCG ,we are not maintaining the values
Checked & maintain: we can be add objects and also maintaining values
ROLE Creation
1. PFCG give the Role name and click on ―create‖ tab, and save
2. in this screen, click on ―menu‖ tab, in this screen we can assign the T-Code,
Reports by clicking
on ―transaction‖ and ―report‖ tab and we should give the target system in
―target system‖ field
and save it
3. After that, click on ―authorizations‖ tab and click on ―change authorization data‖
4. After change authorization data we have to generate the role, it will ask profile
name and save it.
5. Finally, Assign the role to user and click on ―user compare ―for adjusting the user
master records
for this role
User Tables
usr01: user master records (runtime data),·
usr02: logon data,·
usr03: user address data,·
usr04: user master record authorizations, ·
usr05: user SPA/GPA parameter values,·
usr06 and usr14: license data,·
usr08 usr09, and usr30: user menu definition
35