HOW TO SAP

How to Implement support packages Execute SPAM. Choose Support Package

January 11, 2008  
How to Implement support packages

  1. Execute SPAM. Choose Support Package > Load Packages > From Front End
    0016-SPAM-SPackage-01

  2. Locate the CAR file and click OPEN
    0016-SPAM-SPackage-02

  3. Select decompress
    0016-SPAM-SPackage-03


  4. In case of you get following message, just press Yes to all
    0016-SPAM-SPackage-04

  5. Click Display/Define button
  6. Click on your component (eg: SAP_BASIS)
  7. Select the highest level and click OK
  8. It will load the SP to the Queue.
  9. Now click Transport (truck) button
  10. Here you choose to start in dialog or backround
  11. Finish and confirm Queue
  12. Done




 Continue Reading

Step by step how to create a batch file to replace saplogin.ini

January 09, 2008  

Step by step how to create a batch file to replace saplogin.ini


Steps:



  1. At times we might need to update items in Sap Logon pad.
    0015-saplogon-batch

  2. The fastest way to do so is to replace the saplogin.ini. (located c:’windows’)
    0015-saplogon-batch-0

  3. Now to backup your original saplogon.ini - just rename it to saplogon.bak.ss

  4. Open saplogon.ini in a notepad. This is how it looks like:
    0015-saplogon-batch-01

  5. Copy paste all the text at the bottom of the screen and paste it into a new notepad. Rename the text file to
    "SAPLOGON-BATCH.BAT"

  6. Open the batch file and replace IP address with your own servers below
    0015-saplogon-batch-03

  7. The above IP address correspond to below system number.
    0015-saplogon-batch-04

  8. Now you can replace your server description accordingly
    0015-saplogon-batch-05

  9. Lastly, replace the system name.
    0015-saplogon-batch-06

  10. Save the "SAPLOGON-BATCH-SAMPL.BAT" on the desktop

  11. Double click the batch file and it will replace your saplogin.ini.

::*********************************************
::* File : Replace existing SAPLOGON.INI
::* Created : 00:43 15/12/2007
::* Version : 1.0
::* Copyright (C) 2007 howtosap.blogspot.com
::*********************************************


@echo Replacing Existing SAPLOGON.INI
@echo 10 precent completed
@echo [Configuration] >= C:’WINDOWS’SAPLOGON.INI
@echo SessManNewKey=4 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [EntryKey] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Router] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 30 precent completed
@echo [Router2] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [RouterChoice] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=0 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Server] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=172.16.6.6 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=172.16.6.8 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=172.16.6.7 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 50 precent completed
@echo [Database] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=01 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=03 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=02 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [System] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=3 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=3 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=3 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Description] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=SAP DEVELOPMENT >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=SAP PRODUCTION >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=SAP QUALITY ASSURANCE >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Address] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [MSSysName] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=DEV >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=PRD >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=QAS >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 70 precent completed
@echo [MSSrvName] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [MSSrvPort] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [SessManKey] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=3 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=2 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [SncName] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [SncChoice] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 90 precent completed
@echo [Codepage] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=1100 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=1100 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=1100 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [CodepageIndex] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Origin] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=USEREDIT >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=USEREDIT >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=USEREDIT >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [LowSpeedConnection] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=0 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Utf8Off] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=0 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [EncodingID] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [ShortcutType] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=0 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [ShortcutString] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [ShortcutTo] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [ShortcutBy] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 100 precent completed!
@echo You may close this window.



Attached Files:

 Continue Reading

Steps by step to query user with certain plants using Business Explorer.

January 03, 2008  

Steps by step to query user with certain plants using Business Explorer.
In organizational level, plant value is actually an object field called "WERKS"


Guide:




  1. Launch Business Explorer
    0010-bussexplorer-001



  2. Select user master data with authorization
    0010-bussexplorer-002



  3. Enter username and execute. Results will be displayed is the excel sheet.
    0010-bussexplorer-003



  4. Right click on a cell > Add Drilldown According to > Field Name
    0010-bussexplorer-004


  5. Now filter again. Right click > Add Drilldown according to > Authoriz. value low
    0010-bussexplorer-005




  6. Keep filtered value
    0010-bussexplorer-006


  7. Congratulation! You have listed only plant company code for the user
    0010-bussexplorer-007
Continue Reading

Find Role inside a Composite role

January 03, 2008  

Step by step to find a role which is used by certain composite role


Guide:



  1. Execute SE16 and enter Table name AGR_AGRS.
    0011-FindRoleinCompositeRol


  2. Enter the role into Child_AGR and execute
    0011-RoleinComposite02

  3. Here, you can see that role "HKTHH1XQNOTA" has a composite role of "HK1THH_KLIENGMU"

    img2
 Continue Reading

Type of processing in SAP - Online and Batch

January 03, 2008  

Type of processing in SAP - Online and Batch



In a SAP R/3 Production environment, business transactions are carried out in the following modes:
-Online Processing
-Batch Processing



Batch Process is a Job, where SAP R/3 reports/Programs are executed in the background as per the scheduled time. Business Process requirements & System Loads are considered for scheduling background Job. A background scheduler is active within the instances of the SAP R/3 System. For Background processing one background work process is assigned to the background Job till the job completes.


Background jobs run in a special type of work process—the background work process—that is different from dialog work processes in two ways:


1. A dialog work process has a run-time limit that prevents users from interactively running especially long reports. By default, the system terminates any dialog work process in a transaction that exceeds 300 seconds. Although the value of the limit can be changed (in the system profile parameter rdisp/max_wprun_time ), that limit is always in effect for dialog work processes. No such limit applies to background work processes.

2. Background work processes allocate memory differently than dialog work processes so that background work processes can become as large as they need to in allocated memory to allow for processing large volumes of data.
Having special work processes for background processing provides an additional dimension for separating background processing and interactive work. Typically, background processing and interactive work on the system is separated by time of day. For example, interactive users have the system during the day; large background jobs have the system by night. But the background work process also lets you separate interactive from background use by server, since background jobs can only run on those servers that offer background work processes.

It is recommended to create one standard user id to run the batch job. Eg: Batch_Adm

 Continue Reading

Step by step to create new job using SM36

January 03, 2008  

Step by step to create new job using SM36Guide:




  1. Execute SM36
    0012-ScheduleJob-01



  2. Enter the Job Name. Click on Step button
    0012-ScheduleJob-02


  3. A step can be:
    - An ABAP program
    - An external command    - An external program

  4. Enter the ABAP program name. Select the Variant. Click on Check and Save button
    *Variant is a predefine set of value which program RSBTCPRIDEL used in our case.

    0012-ScheduleJob-03


  5. A job can be triggered to run:

    -At a predefined date and time
    -At the occurrence of a predefined event


  6. Click on the Start Condition button

    0012-ScheduleJob-04


  7. Background jobs can be prioritized as:

    Class Priority
    Class A High Priority
    Class B Medium Priority
    Class C Low Priority


  8. Click on Date/Time button. Enter the scheduled start date and time.

    0012-ScheduleJob-05


  9. Click on Period Values button. Select the period values. Click on Check and Save button.

    0012-ScheduleJob-06


  10. Click on Check and Save button

    0012-ScheduleJob-07


  11. Click on Save button.

    0012-ScheduleJob-08


  12. The status of the job can be seen at the bottom of the page.

    0012-ScheduleJob-09



 Continue Reading

How to manage jobs from the Job Overview - SM37

January 03, 2008  

How to manage jobs from the Job Overview - SM37


Step:



  1. Execute SM37
    0013-monitorJob-01


  2. To select jobs to display and manage, refine your job selection by filling out each tab as required. Only jobs that meet all of your specification will be selected.



  3. For job selection with more selection criteria, use the flexible job selection interface by choosing the Flexible job selection button in the toolbar.



  4. Note:Any selection criteria you’ve defined here in the Simple Job Selection area will be transferred to the flexible job interface appropriately.



  5. Explanation for each selection field:
    - Jobname: Name of the job as an identifier, which can contain a wildcard (*) to select jobs with related names or by using the wildcard alone
    - Username: Name of the user who designed and planned the job (the wildcard is allowed here as well)
    - Start date: The start condition of the job, which could be a time frame or an event that the job is waiting for. Specifying both will yield jobs whose starting condition is either of the two conditions.
    - ABAP program step: Name of an ABAP program that acts as a step in a job.
    - Status selection: The current status of the job. By default, the SCHEDULED option is not marked. To see the scheduled jobs, you must explicitly check this.
    - Note: Scheduled jobs are those that must explicitly be released before they are eligible to run.



  6. Once execute you will see the below screen
    0013-monitorJob-02



  7. To copy a single existing job, choose Job > Copy.



  8. To reschedule or edit job steps or attributes of a single job, choose Job > Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.



  9. To repeat a single job, choose Job > Repeat Scheduling.



  10. To debug an active job, choose Job > Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode



  11. To review information about a job, choose Job > Job details. Details displayed can include:
    • current job status
    • periodicity, or the repetition interval
    • other jobs linked to the current job, either as previous or subsequent jobs
    • defined job steps
    • spool requests generated by the current job


  12. To cancel a job’s "Released" status, select the job or jobs from the Job Overview list and choose Job à Release -> Scheduled.

  13. To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job > Cancel active job.


  14. To delete a job entirely, select the job or jobs from the Job Overview list and choose Job > Delete. Jobs with the status of Ready or Running cannot be deleted.


  15. To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job > Compare jobs.


  16. To check the status of jobs, select the job or jobs from the Overview Job list and choose Job > Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.


  17. To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and choose Goto > Job log.


  18. To release a job so it can run, select a job from the Job Overview list and choose Goto > Release.

Continue Reading

Type of Standard Jobs in SAP system

January 03, 2008  
What are the type of Standard Jobs in SAP system
’There are a number of housekeeping jobs that must periodically run in a live R/3 installation, for example, to delete outdated jobs or spool objects. Please refer to SNote 16083 – Standard Jobs, reorganization jobs for more details.Below are some examples.
0014-StandardJob01 Continue Reading

User: Creating User in SAP

January 01, 2008  


How to create user in SAP


Steps



  1. Execute SU01

  2. Enter user name and press CREATE (notepad)
    0009-transport-001

  3. Enter necessary details such as Firstname and Lastname
    0009-transport-002

  4. Click on Logon Data Tab and enter password a password eg: enjoysap123
    0009-transport-003

  5. Click Save (floppy disk icon). Now you can informed the user that his/her account has been created.
 Continue Reading

STMS - Steps to perform transport

January 01, 2008  
Consultant & Abapers will request transport from client to client. Once request has been approved, Basis will transport the request using T-CODE STMS


0008-transport-001
1. On the command field, enter STMS. You will see the above screen. Now, click the red color truck on upper left of the screen.

0008-transport-002


2. Double click on the target system. In this case, I am going to transport from Development server to Production server. I’ll double click on PRD.

3. Press refresh once to update the transport list.



0008-transport-003
4. Click on the ‘transport request que (Ctrl-F6) if you see a green colored arrow. Press ok when a window popup.

5. Once completed, click on Import request button (Ctrl-F11)

6. Enter your target client. In my case, its client 800.

0008-transport-004




7. Click on option tab and untick leave transport request in queue for later import. See above picture. Now click ok.


0008-transport-005


8. Click ok to confirm when a new windows pop up.

9. Transport has been completed.
 Continue Reading

News: SAP is still doing great!

January 01, 2008  

From eweek.com

Salaries for SAP specializations increased 15.2 percent in 2006, according to research released in February by Foote Partners, a New Canaan, Conn., IT workforce research firm. Data from the first two quarters of 2007 suggests little abatement of this trend.

“Right now, anybody who is working in the SAP world, either with functional or technical skills, is doing great,” said Jim Lanzalotto, vice president of strategy and marketing for Yoh, a recruiting and outsourcing firm, based in Philadelphia. “The demands are for specialized skills, and if you’ve got to pick the right market to be a specialist in, the world of SAP is hot.”

ERP-related roles accounted for two of the best-paying IT jobs in the second quarter of 2007, according to the second quarter 2007 Yoh Index of Technology Wages, released July 23. SAP technical consultants came in first, with average hourly pay rates of $85.53, and ERP (enterprise resource planning) functional consultants came in eight dollars behind in second place, at $78.40 per hour.

more at http://www.eweek.com/article2/0,1759,2161806,00.asp

 Continue Reading

Deleting Master Data - user claim and vendor list

January 01, 2008  

Enter OBR2 to open deleting master data

If you get the below error this is due to existing data

Open FBL1N to check existing data

If you see this there are data, please reserver the entry

 Continue Reading

Procedure Cache Hit Ratio for database

January 01, 2008  

What is it?
The hit ratio is a mean value that gives a snapshot of a short period of time before the analysis. This value should always be above 95%, even during periods of heavy workload. If the hit ratio is significantly below 95%, the data cache could be too small.


To check the hit ratio:
1. Execute ST04
0007-dbhitratio-001


2. If the hit ratio is below 95%, you will have to increase it.

 Continue Reading

SAP Basis - Daily check list

January 01, 2008  


Basis perform health check daily on the system. Below are the activity most command check list activity.





SAP Logon Connection Test

1. Double click on all below instance to check if you are able to login.
0006-hc-001

2. If login were successful, this means server is alive and has no connectivity issue. A new screen will pop up. See below
00220s

3. Now you are ready to perform the next activity





DB12/DB13 Create and Check backup status for DB2
1. On the command field, key in DB12 and below screen will be displayed. It shows the summary of the backup status.00320d01

2. On command field, enter DB13. This T-code is used to perform backup. You can also check the backup status.


3. In DB13, select a desired cell which you plan to perform your backup. Double click on the cell
img1

4. Choose Full database backup to device

5. Backup mode: Offline

6. Device directory: ‘ d:’backup’ (this is just a folder which your backup could be stored)

7. Below is a sample picture.
0006-backup-001





DB02 Check Database size for DB2


1. Use DB02 to check DB size
2. Database current size (GB) is Total DB size - Free space
0006-hc-002






SM50 Check if instance is running on all servers
1. All work process is either running or waiting and none are stopped except CPIC (interprocess communication)

2. Make sure not all dialog work process are used up, otherwise other user cannot make any transaction.
0006-hc-003

3. Alternatively you can use SMLG to check whether system respond is good or bad.






RZ20 Check filling degree of spool used numbers


1. Click on SAP CCMS Monitor Templates
2. Click on SPOOL System
3. System Wide > Spool > SpoolNumbers > UsedNumebrs
4. If value greater then 80% in spool numbers - will lead to system wait until spool reorganisation is done
0006-hc-004






SM13 Check if update is active


1. Enter SM13 and make sure UPDATE SYSTEM STATUS : Update is active.

2. Make sure client = *, User =* and status = All, Press F8 to execute

3. Click on any entry with error

4. You may have to dig deeper (SM21, ST22, DB02, etc) and work with functional expert to resolve the issue
0006-hc-005






SM12 Check lock entries with long duration


1. Type SM12 in command field
2. Client = *
3. User name = *
4. Click list.
0006-hc-006



Its important to notice all values under the time column show the current time. Jobs with earlier date should be immediately investigated. These locks are problematic because it prevents access or changes to the locked records.






ST22 Check and analyze SAP ABAP short Dumps
An ABAP dump (AKA short dump) is generated when a report or transaction terminates as the result of a serious error. The system records the error in the system log. SM21 and write a snapshot (dump) of the program terminiation to a special table (SNAP). This transaction can also be called from the system log (SM21). ABAP dump is used to analyze and determine why the error occured and take corrective action


(no print screen - currenly my SAP has no Runtime errors)


Once Runtime errors is displayed
1. Double click on the entries
2. A detail analysis on the error will be displayed
3. Dump contains the follow information
- Why program has been terminted
- What caused the program termination
- Where in the program code the termination occured
- What you can do to correct the error
- The values of the relevant system fields when the program terminated
- The calls or events that was active when the program terminated
- Any other programs that are affected






SM21 Check and analyze SAP system log for any critical log entries (hourly)
1. Type SM21 into command field
2. Enter the relevant details and execute
3. Look for unusual entries.
4. Double click on the entries for more information


011sm21


Lastly, a few more userful transaction


1. SM37 - Check and analyze failed background jobs
2. SP01 - Check SPOOL for errors
3. ST06 - CPU & Memory Utilization
4. ST03 - Check for database performance and response time
5. ST11 - Check for core file entries

 Continue Reading
Subscribe to: Posts (Atom)
Designed By: Blogger Templates | Templatelib