Difference between SM50 and SM66

[former_member343107]

Dear all,

I heard that SM50 view the work process inan instance's scope and SM66 view them in a system's scope. But I always see there're much more processes displayed in SM50 than SM66. Can anybody explain why some processes don't appear in SM66 even if SM66 has a bigger scope?

Thanks + Best Regards

Jerome

null

[Former Member · Accepted solution]

Hi

<b>SM50</b>

SM50 is t-code for process overview. It shows the status of type of work process and their satatus. By double clicking on the row of respective process we can see the details about the kind of programs it is running and SQL statements, database activities and extended memory allocation while the process is running.Basically we use this transaction code to display work processes, To check the Update StatusProcess, Analysis SQL Locks .you can 'kill' the running process with core or without core in SM50.

<b>SM66</b>

The T-CODE SM66 is “Global servers work area”. That means it is having all the servers running with in an organization/company etc. When you again double click on any one of the server at that time is shows SM50 of that particular server. SM50 is local server work area and SM66 is global work area.You can see the how work process is encaged ie status the process running,waiting...

As a note, unless you are a BAIS person and know what you are doing, you shouldn't use SM 50 in PROD. Developers and Support shuld only use SM66. Here, you can display same infomration as SM50, but you cannot accidentally kill any process. In SM66, you can also see Multiple Server Detials in same screen unlike SM50.

Also, Support People should kill loads using SM37 only, SM50 should be used with care

Rewrad suiatble points

[former_member343107 · Accepted solution]

Hi All,

Thanks a lot for the explanation!

Best Regards

Jerome

[Former Member · Accepted solution]

Hi Jerome,

Goto SM66 click on Select Process

status: select the check box for waiting

you can see more workprocess

by default Waiting check box is not selected

Thanks & Reg,

Kishore

[former_member343107 · Accepted solution]

Thanks for this information!

Best Regards

Jerome

[Former Member]

Hi

SM50 Work Process Overview

SM66 System Wide Work Process Overview

SM50--Display and Control Work Processes

Use

Work processes do the majority of the processing of the SAP System. They execute dialog steps in user transactions, updates, lock administration, etc.

You can also find the term Work Process in the glossary.

You can display the current status of the work processes on the application server where you are logged on by choosing Monitor ® System monitoring ® Process overview or Transaction sm50 You must refresh the display to get updated information. The information on this screen is described in the following section.

The Process overview is intended primarily for information-gathering. For example, you can monitor processes to determine if the number of work processes in your system is adequate, to gather information for trouble-shooting, or for tuning.

Integration

By choosing Monitor - System monitoring - Servers, this displays the overview of the SAP application servers. Here, you can further display the work process overview for a particular server in the SAP System by clicking on the desired server name.

If system load is low and you are displaying the Process overview, you notice that your requests seem to be processed in only one work process. The dispatcher is trying to use one work process for as many dialog steps for one user as possible. This avoids having to reload the roll area for the user

SM66--Global Work Process Overview

Purpose

You can quickly investigate the potential cause of a system performance problem by checking the work process load. You can use the global work process overview to:

Monitor the work process load on all active instances across the system

Identify locks in the database (lock waits).

Using the Global Work Process Overview screen, you can see at a glance:

The status of each application server

The reason why it is not running

Whether it has been restarted

The CPU and request run time

The user who has logged on and the client that they logged on to

The report that is running

This should clear your doubt. If you need any more clarification you are welcome.

Regards

Sumit Jain

**Reward with points if useful

[Former Member]

HI Jerome,

SM66 --> It displayes only the ACTIVE process in the system ( On ALL Servers)

SM50 --> It displays all Work process (ACTIVE and INACTIVE) of one particular server.

SM51 --> It displays all servers and on selection of any particular server it shows all the ACTIVE and INACTIVE work proceesses

Hope it helps.

Br,

Sri

Award points for helpful answers