Checking workprocess status

Checking failed updates

User administration
Review workload stats& review buffer stats.
Analysis & Solving R/3 errors using ABAP dumps & system logs
Scheduling background jobs, monitoring background jobs & review for cancelled jobs.
Moving current TMS & moving TR
Creation of clients & performed client copies and defined logical system
Creation of parameters using profile parameters.
Performed kernel upgradation
Oracle Upgradation from 9i to 10g
SAP R/3 Competency Upgradation.

Task: Check that all application servers are up

TCode: SM51, SM66 SAP Serves
Procedure: Check that all servers are up
Task: Check workprocesses (started from SM51)
TCode: SM50 Process Overview
Procedure: All work processes are with running or waiting status.
Task: Look for any failed updates (Update terminates)
Tcode: SM13 Update records
Procedure: Set date 1 year ago, Enter * in the user ID & set to All updates
Check for lines with Err.
Task: Check system log
TCode: SM21 System log
Procedure: Set time & date to before last log review. Check for errors, warnings, security,
messages, abends, database problems, another different agent.
Task: Review for cancelled jobs
TCode: SM37 Select background jobs
Procedure: Enter * in the user ID, verify that all critical jobs were successful.
Task: Check for old locks
TCode: SM12 Lock entry list
Procedure: Enter * for the user ID, check for entries for prior days
Task: Check for users on the system
TCode: SM04/AL08, users
Procedure: Review for unknown or different user ID and terminal this task should be
done several times a day.
Task: Review & resolve dumps
TCode: ST22 ABAP dump analysis
Procedure: Look for an excessive number of dumps. Look for dumps of an unusual
nature

Task: Review workload stats

TCode: ST03 Workload analysis of <SID>
Procedure: Expertmode>>Last week>>analysis view>>transaction profile>>standard
Task: Review buffer statistics
TCode: ST02 Tune summery
Procedure: Look for swaps
Task: Check that daily backups executed with out errors
TCode: DB12 Backup logs Overview
Procedure: Check the database backup, database backup runtime, check o/s level backup,
o/s backup run time
Task: Applying support packs
TCode: SPAM Support packs
Procedure: Download the patches for service marketplace. Run tcode SPAM on 000
client select the patch from load option in Application server. Select the patch that has to
be uploaded. Decompress of the patches ATT and PAT will de done automatically. Once
Done. Select the patch in import queue .once selected import the patch. Once completed
confirm the queue .repeat this procedure...
Task: Background jobs are a means of running reports without having to wait for the
report to finish. Background jobs can be scheduled to run immediately or at specific
times or the day or night. Background jobs can be scheduled to run automatically on a
periodic basis (eg daily, weekly, monthly etc). A background job can consist of one or
more reports. Each report is run in sequence.
Tcode: SM36 Background job scheduling
Procedure: A selection variant must be be created for any report run as a background job
in order to supply the report with the required selection criteria.
To create a background job you will need to know the ABAP program name. This can be
found by running the report and using System>Status to view the Program field. For
example the ABAP program name for the Cost Centre Line Item Report (transaction
KSB1) is RKAEP000.
DYNPRO_FAILED_CONVERSION
A Conversion error occurred while this data was converted. The table contains the data
which has range more than what the SAP screen can handle.
CALL_C_FUNCTION_NO_AUTHORITY
ABAP dump occurs, if there is an issue with the authorization
CNTL_ERRO, RAISE_EXCEPTION
This are bugs cause by earlier version of the SAPGUI. Apply the SAPGUIs latest front
end patch
LOAD_PROGRAM_LOST
This is also a message if client independent transports are being done while users are
working
PXA_NO_FREE_SPACE
You can increase or decrease the PXA in the SAP profile parameter abap/buffersize.
PXA_NO_SHARED_MEMORY
Run sappfpar check pf=<profile name>. This will tell us the errors before starting the
instance or while it is running.

ROLL_BACK_IN_POSTING
This is generated due to update terminations in FI.
RFC_SYS_EXCEPTION
System exception raised, connection closed.
TIME_OUT
isp/max_wprun_time Process exceeding the dialogue workprocess run time.
CALL FUNCTION_SIGNON_INCOMPL
An Application calls a function module that is not existing, check the calling program.
CONVT_NO_NUMBER
It seems the value 00000Bex is transferred to a numeric variable. The system cant
convert it to a number so the dump is raised conversion error.
LOAD_PROGRAM_NOT_FOUND
The error appears to be in a user program. I suggest you to talk to the developer who
created this program.
Transport control program cancelled with error code 0232
The transport has been released, when transport it the following message An error
occurred when executing tp command. And when I check the transport log, it shows that
the transport was cancelled.
On domain controller
>>go to /nSTMS>>Overview>>Systems
>>Click client then select SAP systems>>update configurations(cntl+F2)
>>Extras>>Generate RFC destinations
>>Repeat this for controller instance itself.
For domain clients
>>goto /nSTMS>>Overview>>Systems>>Client its instance, then SAP system
>>Update configuration>>Extras>>Generate RFC destinations
>>After this done, test your RFC connections

How to find a old request

>>SE03>>Request/task>>find request
My server become slow, when more users logon?
>>Check SAP response time is acceptable, to have look at o/s response time, look at
CPU, memory, swap, disk & LAN response time. Try to look at buffer quality; ST02 if
many fields are red, investigate each fields dependant parameters, shared pool cache hit
ratio should be>96%.
List of inactive users
>>SA38>>RSUSR200 (run report)
Find the frequently used programs or transactions
>>Detail analysis button>>Under global>>One recent period then select
day/week/month>>transaction profile button.
If the transports not getting imported
>>Need to RDD* jobs
Upgrade
>>Additional h/w requirements, project duration, business down time, reasons for
upgrade

Defaults
ST02
Program buffer hit ratios, screen buffer hit ratios, calendar buffer hot ratios, program
buffer swaps, screen buffer swaps, calendar buffer swaps, swap memory usage & hit
ratio.
ST03
Response time of users, response time of instance, average response time of workprocess,
average dialogue steps, average CPU time, average wait time, average load time.
Average response time should be in between 500 to 1500 ms for dialogue.
CPU time should be upto 500ms
Time per database request should be upto 10ms
Roll in time should be 10s and roll out time 40s for good performance.
ST04: Databse performance
Quality databuffer should be 90 to 100% for good performance means memory should be
more
Get ratio & Pin ratio should be 99 to 100
Allocate fault rate should be 0 to 0.5%.
Upgrade: In response to todays competitive business pressures, companies now need to
be innovative and adoptable to changing ways of doing business, collaborating more
closely with customers & suppliers to stream line the value chain. At the same time
organizations are seeking greater efficiency from their core processes, through
standardization, automation & internal integration. These operational drivers must be
achieved while at the same time maintaining stability and reducing total cost of
ownership. MySAPERP and versions SAP new dimensional products have evolved to
meet these changing requirements.
Support Package Manager: Phases
1. PROLOGUE
This phase checks whether you are authorized to import Support Packages.
2. CHECK_REQUIREMENTS
This phase checks various requirements for importing a Support Package, for example,
whether the transport control program tp can log on to your system.
3. DISASSEMBLE
This phase unpacks files from the appropriate EPS parcels and saves them to the transport
directory.
4. ADD_TO_BUFFER
This phase places the queue in the transport buffer of your system.
5. MODIFY_BUFFER
This phase prepares the transport buffer for correct processing of the following import
phases.
6. TEST_IMPORT
This phase performs a test import for the queue with the transport control program tp. The
system checks whether there are objects that are in open repairs and that are overwritten
during the import, or whether other conditions prevent the import of an object.
7. IMPORT_OBJECT_LIST
This phase imports the object lists for the Support Packages in the queue into the system.
8. OBJECTS_LOCKED_?

This phase checks whether there are objects that are overwritten by the import, and that
are still in unreleased requests.
9. ADDON_CONFLICTS_?
This phase checks whether there are conflicts between objects in the queue and any
installed add-ons.
10. SCHEDULE_RDDIMPDP
This phase schedules the transport daemon (program RDDIMPDP).
Import 1 Module
11. CREATE_VERS_BEFORE
This phase generates versions of the objects that are contained in the Support Packages in
the queue (if this option is set).
12. SPDD_SPAU_CHECK
In this phase, the system checks if a modification adjustment is necessary (transactions
SPDD/SPAU).
13. DDIC_IMPORT
This phase imports all ABAP Dictionary objects in the queue.
14. AUTO_MOD_SPDD
This phase checks whether all modifications to ABAP Dictionary objects can be adjusted
automatically.
15. RUN_SPDD_?
In this phase, you are asked to adjust your modifications to the ABAP Dictionary objects by
calling transaction SPDD.
16. LOCK_EU (only for import mode downtime-minimized)
This phase locks the development environment.
17. INACTIVE_IMPORT (only for import mode downtime-minimized)
This phase imports program code and program texts in an inactive state.
18. DDIC_ACTIVATION
This phase activates the imported ABAP Dictionary objects.
Import 2 Module
19. IMPORT_PROPER
This phase imports all the Repository objects and table entries if they were not already
imported in the INACTIVE_IMPORT phase. This is preceded by actions such as table
conversion and activation of the name tabs.
20. PREPARE_XPRA
This phase prepares the execution of the XPRAs and after-import methods.
21. UNLOCK_EU (only for import mode downtime-minimized)
This phase unlocks the development environment.
22. AUTO_MOD_SPAU
This phase checks whether modifications can be adjusted automatically.
23. XPRA_EXECUTION
This phase executes the XPRAs and after-import methods.
24. ABAP_GENERATION
This phase generates the runtime objects for the imported Repository objects (ABAP
source texts and screens).
Clean Up Module
25. RUN_SPAU_?
This phase prompts you to adjust your modifications to Repository objects by calling
transaction SPAU.
26. CLEAR_OLD_REPORTS (only for import mode downtime-minimized)

This phase deletes the obsolete versions of program code and program texts in the
database.
27. EPILOGUE
This phase completes the import. Among other things, it checks whether the queue has
been processed completely.
Standard Background jobs
SAP_REORG_JOBS>>RSBTCDEL=Daily
Delete old background jobs
SAP_REORG_SPOOL>>RSPO0041=Daily
Delete old spool requests
SAP_REORG_BATCHINPUT>>RSBDCREO=Daily
Delete batch input sessions
SAP_REORG_ABAPDUMPS>>RSSNAPDL=Daily
Delete old dumps
SAP_REORG_JOBSTATISTIC>>RSBPCTDE=Monthly Delete job stats for jobs not running
since the specified date
SAP_REORG_UPDATERECORDS>>RSM13002>>Daily
Delete old completed records
SAP_COLLECTOR_FOR_JOBSTATISTIC>>RSBPCOL=Daily Generate runtime statistics for
background jobs.
SAP_COLLECTOR_FOR_PERFORMANCE>>RSCOLL00=Hourly
Collect system
performance statistics

STMS Configuration
>>Logon to client 000 user ID: administrative user (other than DDIC)
>>put Tcode SE06 in the command field
>>Click standard installation and click post installation (Yes)
>>Put a Tcode STMS in the command field and give a description then save it
>>Click system overview push button, click extras option from the menu and distribute
& activate configuration (Yes)
>>Back STMS main screen and click the transport routes from the push button
>>Click configuration button from the menu
>>Click distribute & activate from configuration menu
>>Now your SAP system is activate in domain controller.
Now Logon to QAS, client 000, user administrative user
>>put Tcode SE06 in the command field
>>Click standard installation and click post installation(Yes)
>>Put Tcode STMS in the command field
>>Click other configuration push button in the bottom appear screen
>>Give information about development system
>>Save it>>Ok
Now QAS is waiting for include in domain controller
>>Logon to development system
>>Click system overview push button
>>Click SAP system from the menu
>>Select the QAS systems
>>Click approve button from SAP system menu
Now QAS is member system of domain controller (DEV system)