Sap sm50 error

sap sm50 error

4. Memory/CPU usage of individual job or transaction. SAP SM50 transaction is used to report information for all configured SAP work processes. › basis › administration-of-work-processes-using-sm50. SAP BASIS Transaction Code SM50 · Transaction SM50 · To monitor the status of all the work processes in the SAP system, this is used. · In case a work process is. sap sm50 error

watch the thematic video

Errors during SUM UPGRADE

Transaction code SM50 is used to monitor and manage work processes. In the work process overview, you can:

• End an ABAP program that is running.
• Debug an ABAP program that is running.
• Cancel a process (with or without core) – long running jobs
• End a session
• Activate/deactivate the restart option after an error
• Execute various functions for the process trace


The internal ID number of a process. Used to identify messages that belong to a work process in the system log.


• DIA: Work process for executing dialog steps in user transactions.
• UPD: Update process for making U1 (time-critical) database changes.
• UP2: Update process for executing U2 (not time-critical) database changes.
• ENQ: For locking or releasing SAP lock objects.
• BTC: For processing background jobs.
• SPO: For spool formatting processes.


Process ID of the work process (on the operating system).


• Running (executing a request)
• Waiting (idle and waiting for work)
• Hold (held for one user) is not an abnormal state, but a work process can only serve a single user. If too many processes are in hold status, sap sm50 error, then system performance suffers, sap sm50 error. You can use the Reason column to identify work processes with status hold that can be released.
• Stopped (aborted with Restart set to No)


If a work process is in hold status, the reason is displayed. Typical reasons are: Debugging, CPIC activity, locks, updates, GUI (system waits for response from the SAPGUI front-end program, sap sm50 error, for example, for a remote function call (RFC)). You may also see PRIV (PRIVate use) as a reason for holding a work process. PRIV indicates that a work process is reserved for a single user for memory management use. The work process has exceeded the limit of the SAP memory that is used by other processes. The process is held as long as the current user requires local memory.


Indicates whether the process should be automatically restarted if a process ends prematurely. You can change the restart status of a process by choosing Process > Restart after error > Yes/No. Normally, leave Restart set to Yes. If a work process aborts during its startup, the system automatically sets Restart to No. This measure protects against endless attempts to restart a process if a database system is not available, sap sm50 error, or another serious problem is affecting the system. After correcting the problem, you can change Restart to Yes so that the system starts the haspflt cant start driver error 1275 processes.


Indicates how many times a work process has aborted.


Indicates the number of the semaphore for which a work process is waiting. Normally, this field should be empty. If one or more semaphore numbers frequently appears, evaluate the performance of your system using the Performance Monitor.


Cumulative CPU time since the start of a work process.


Indicates the elapsed time used by a work process for the dialog step that it is currently processing

• Report – ABAP program or report that is currently being executed
• Client – Client for the session that is currently being executed
• User – User whose request is currently being processed
• Action – Action that is being executed by the current program. The actions displayed are recorded by the SAP Performance Monitor. The Performance Monitor must be active (SAP profile parameter stat/level = 1(default)) for actions or database table accesses to be displayed.
• Table – If the database is being accessed, this column shows the name of the table being accessed.

1253172Error when setting application information811031DB2-z/OS: SM50 displays SQL statement900837No DB data in work process detail display1021205Multiple debugging from SM50 does not work1599764DB6: SQL error 1428 when calling transaction SM501099602Switching on the DBSL trace in SM501320424RFC tracing in Sap sm50 error communication78991Update hangs; locks gather572905NR: Unbuffered number ranges672906Missing data in aggregation after inheritance42074Using the R/3 dispatcher monitor 'dpmon'84967Incorrect values in transactions ST03,STAT,SM50364286MF50: Conversion of planned order does not work670398More tracing for Sap sm50 error, NLS, RSCP.932384Trace file shows trace level -1692996CST Patch Collection 52 20031389948semaphore 12 in SM50 for Linux operating system573128Debugging programs in the background1485789QRFC: Long running processes in SM501012681Trace generation for SOAP runtime (ABAP)386361SDL: Scheduled extraction job hangs in SM50 at IPG949535Algorithm to estimate if there is a DB bottleneck.998221Trace levels changed inadvertently in work sap sm50 error runtime for COPCA_DOCUMENT_CHECK1250813SAPLARFC uses all dialog work processes26966Background jobs do not start when transporting186475All update tasks are waiting with 'stopped CPIC' reason1065003Key date valuation run stops in /BA1/SAPLB1_API_FP_MASTER25528Parameter rdisp/max_wprun_time142054Processes in status stopped ENQ1601423Key date valuation run stops in /BA1/SAPLB1_API_FP_MASTER1037930Work process loops w/ semaphore 38 in GetEffectiveToolDef()508771KP06ff.: Performance problems whith deletion26455NT 3.51 Oracle: Work procs. hang in Reconnect1167867Debugging for handling unit BAPIs554012Workprocess loops on dynpro load with semaphore 124092292.0C: Posting org. data generates high dialog load631154Analyzing the "Execute rollback" message in syslog106804Sets: performance problems for mass processing1131092Enqueue work processes hang in status "Running"1302974VTBW/VIFBW: Long runtime for deliveries with batches72025Error 024 on missing database link649588Message handler: Performance improvement (3)788658Current DBSL patch level not displayed420947Bad performance at FI-SL extractor436723Extractor performance for 0EC_PCA_1 and 0EC_PCA_2325607IS-M/SD long runtime with packing and check reports531941KP06contd:Performance problems because of COKA381105ORA-12203 / ORA-12535 when starting the R/3 work processes1154537Rollback in debugger for captured background jobs631733Timeout in SAPLSTRI "Delete E071K"920234Mechanism to fill the number range buffer1046206Cancel transaction (Soft cancel) does not work558254RFC trace generation for sporadic errors116841Performance:in VL01, VL04 text determin, sap sm50 error. runs long867583Work processes wait for semaphore 8991848Lock problems in product allocation during CIF update197161(MM) Performance of purchase requisitions for ORACLE363092Demand Planning: Performance Mass Processing1573890Timeout in CRM during change pointer update821580SQL Server Profiler: How to trace a certain work process350439CS tracing - Performance for order history poor370916SD: Reorganization of SD document indices430657Logical spool server: SPO processes completed588946Sporadic endless runtimes, hanging processes1013336Performance problems with Enterprise Add-On Switches39187Variances: Long runtimes, wrong target values16665Method for troubleshooting, trace level768482Opening a sales agreement with many revenue items410400GET_PS_OBJECTNUMBER: Access problems with database DB21293472Spool work process hangs on semaphore 43407188Long runtimes for order settlement (MLAUF)799142In LC10 and DB50, sap sm50 error, the field "Automatic Log Backup" is empty155776Updates of synchronous matchcodes101113AS/400: Analysis of performance problems578842UPD WPs have the status CPIC(RFC) stop in SM501496154Connection termination during HTTP access of LMDB to SLD194994BW extractors:Performance informtn sources projects549294Archiving: Very long runtimes for DELETE MCAFVGV1232060Job log is incomplete168129IS-M/AM: High runtime for creating document flow66047Screen processor: Trace for error analysis544711Project summarization: Objects are missing112765Performance planning run / stock transport orders197749Problems with initial values under ORACLE, III209322Problem in ORACLE with initial values IV309480Summarization : Performance improvement790672Processes terminate with TIMEOUT 'ARFC_END_TRANSACTION'797765Oracle DB: Overhead cost planning performance485784Performance problems when saving projects142237Process waits infinitely for sap sm50 error range buffers413427Performance V_IBIN_SYVAL, IBINOWN, IBINOBS335074Performance of results analysis for sales order

To display the status of the work processes of the application server where you are logged on to, select Tools Administration Monitor System monitoring Process overview (transaction code SM50). Administrators should regularly monitor the system processes to determine if the number and configuration sap sm50 error appropriate.

Notice that you can only display the processes of your local system.

The SAP work processes correspond to operating system processes. You could also monitor these processes from the operating system. In fact, the field PID matches exactly to the Process Sap sm50 error of the underlying operating system, sap sm50 error. With a UNIX command such as ps −eaf \ grep dw, you can see the SAP processes. On Windows NT systems you can see the processes from the Task Manager as disp+work.

The SAP runtime directory (/usr/sap//SYS/exe/run) contains some monitor programs which allow you to see some of the work processes and the dispatcher from the operating system.

The columns in the work process overview screen show the following information:
No. Refers to the internal ID number of a process. It is useful for identifying messages in the system log belonging to a work process.
Ty.It’s the type of work process. On this screen, sap sm50 error, you can find the following types:
¨DIA. Dialog work processes, in charge of executing interactive dialog steps
¨UPD. Update work process for executing U1 update components). In charge of critical updates on the database ¨
¨UP2. Update work process for executing U2 update components. In charge of performing
secondary updates on the database¨
¨ ENQ. Enqueue work process in charge of setting and releasing lock objects
¨BTC. Background work processes, in charge of executing background jobs
¨SPO. Spool work process in charge of the SAP spooling system (formatting and printing)

PID.Process identification number of the work process which matches the PID of the operating system process.
Status.Shows the current state of the work process. Observe that the process overview screen always offers a snapshot of the processes. So, upon pressing the Refresh icon, it can change. Possible process status are
¨ Running. The process is executing a system request.
¨ Waiting. The process is idle and waiting for any system request.
¨ Hold. The process is held by a single user. Although a Hold state can be normal, having too
many processes in hold state affects the system performance.
¨ Killed or Complet. The process has been aborted with the Restart option set to No.
¨ Stopped, sap sm50 error. Due to system or application error, the process has stopped and could not restart

When the process overview displays many processes with status waiting, it means that the system load is low. When this happens, the SAP dispatcher will try to allocate the same work process for a user, sap sm50 error, and thus avoid rolling in and out the user contexts.

Reason. This column displays a mnemonic code displaying the reason for a work process with a hold status. Some of the reasons can be activities performed by the lock mechanism, sap sm50 error, the update process, debugging, CPIC tasks, sap sm50 error, or RFC requests. If the reason columns display Priv, sap sm50 error, it means that a work process has been reserved for a private use in a particular ABAP transaction requiring a large paging storage. This mechanism sap sm50 error the rolling in and out of the user contexts and the ABAP paging.
Start. This column has either the values Yes or No and indicates whether the work process will be automatically restarted in sap sm50 error event of an abnormal termination. Normally, this field is set to Yes butyou can switch the restart status by selecting the function Restart after error from the Process menu.

Err. Contains the number of times a work process has terminated abnormally.

Sem. This column can contain the number of the semaphore on which a work process is waiting.
Normally, this field is empty. However if you notice that a semaphore number appears often, it might indicate some performance problems in the system and might need some parameter adjustments.

CPU. Contains in number of seconds the CPU time consumed by a work process.

Time. Indicates the elapsed execution time used by the work process for the dialog step that it is currently processing. This column usually contains a small figure. When it displays a large figure, it might indicate that the process is being held in a debugging session.

Program. This column contains the ABAP program that is currently executing.

Client. Indicates the SAP system client where the session is being executed.

User. Contains the user ID whose request is being processed.

Action. Under this field the system shows the actions being performed by the running program. These actions are the same as those recorded by the system performance monitor which is activated by default with the profile parameter stat / level. This column might display actions such as sequential read, insert, or direct read.

Table. This column displays the name of the tables being accessed, sap sm50 error, if any.

There is more detailed information available from the process overview screen which you can display by selecting the work processes and then clicking on the Detail info button on the application toolbar. With this option, in addition to all the information from the overview screen, the system displays statistical information about the work process such as the memory, development environment, and database usage.

You can terminate a work process with or without generating a core dump file in the operating systems, which can be used for debugging. Before canceling a work process, you should select the menu function Restart after error, either with options Yes or No, sap sm50 error, to indicate whether the process which is to be canceled should restart or not, after being manually terminated.

To display a trace, choose the work process and, from the menu, sap sm50 error, select Process -> Trace -> Display file.

By selecting the work process and clicking on the Delete session button on the application toolbar you can also delete a user session and release the work process. However, you should avoid performing this function from this overview, since the work processes can be attending several users, and you could unintentionally affect other users’ work. Rather, you should delete a user session from sap sm50 error User overview screen(SM04)

Like this:



This entry was posted on April 21, 2008 at 1:17 am and is filed under CCMS and Sap sm50 error can follow any sap sm50 error to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

How to run SAP SM50/SM66 to monitor SAP work process

How to run SAP SM50/SM66 to monitor SAP work process

This post would talk about how to run SAP SM50 and SM66 transaction, sap sm50 error, understand information from SAP SM50 and SM66 screens and what SAP SM50 and SAP SM66 can help in performance monitoring and analysis.

SAP work process is a limited critical system resource for performance like CPU and memory. Number of work processes and type of work processes on a SAP instance are controlled via SAP basis configuration. Any online transaction or background job is executed using one or multiple SAP work processes in cmos checksum error resetting cpu frequency or in parallel dependent on program function and design: Running SAP transaction VA03 online to display sale order would need only one SAP dialog work process while running va01 online to create sales order online would need one dialog process and one update process; One background job would always use at least one background process, sap sm50 error. One background job which uses parallel processes via RFC call would need one or more dialog process as well.

SAP SM50 and SM66 transaction provides capabilities to monitor overall status of SAP work process and status of individual SAP work process, sap sm50 error. So you know:

1. Overall system activities/load.

2. System work process status, sap sm50 error.

3. Individual job or online transaction execution status, sap sm50 error.

4. Memory/CPU usage of individual job or transaction.

SAP SM50 transaction is used to report information for all configured SAP work processes under one SAP server/instance while SAP SM66 reports all occupied SAP work processes from all servers/instances of a SAP system. If you have several servers/instances in your system, you can use SAP transaction SM51 to switch from one server to another.

SAP SM50 transaction has two screens: Work “Process Overview” and “Details Display” screen. I would walk through SAP transaction SM50 first before I talk about SAP transaction SM66.

1, sap sm50 error. Launch wok process monitor

To launch work process monitor, sap sm50 error, you can run SAP transaction SM50 directly sap sm50 error via menu path Tools -> Administration -> Monitor ->System Monitoring -> Process Overview. The initial SAP SM50 transaction screen is a SAP work “Process Overview” screen which shows status of all configured sap work processes on the current server you are in. Double click any work process entry on the overview screen, you would see “Details Display” screen for single selected work process. That is simple.

Following is a part of SAP SM50 Work process overview screen which is showing status of all configured SAP work processes � I manipulated the display to show all typical types of work process sap sm50 error an application instance � Background(BGD), Dialog(DIA), Update(UPD & UP2).

Figure 1-SM50 Process Overview

Following is two parts of Work process details screen which shows further information on a single work process

Figure 2 – SAP SM50 Process Details

Click button to refresh overview screen or details display screen to see latest status.

2, sap sm50 error. Understand SAP “Process Overview Screen”

2.1 SAP SM50 overview screen column explanation

You can get the on-line SAP explanation of any column presented in transaction SM50 overview screen: place the cursor over the column and press F1 help. I copied them here for the convenience and with comment in blue color from my experiences.




SAP work process number is a an error occurred while mounting /proc/bus/usb winpower number starting at 0.

In old version, the cap for number of work process in an instance is “99″. With more advanced hardware, sap sm50 error, the new version can allow up to 999. Number of work processes can be configured depend on memory, number of CPU, type of CPU etc.


Work process type

DIA – Work process for executing dialog steps in user transactions��

UPD – Update process for executing update requests

ENQ – Process for executing enqueue requests

BTC – Process for executing batch requests

SPO – Process for executing spool requests

UP2 – Process for executing V2 update requests

What work process type is available on an instance/server is configurable based on business requirement. But ENQ/SPO process is normally on CI instance.


Process ID of operating system for the SAP work process. With this ID the process can be processed using commands from the operating system (for example, ps or kill in UNIX).


This field indicates the current status of a work process.

Waiting :��Process is asus m2n32-sli deluxe cmos checksum error waiting for requests

Running :��Process is asus acmon error windows 7 a request

On Hold :��Process is waiting for a message. Column Reason specifies what the work process is waiting for.

Stopped :��Process was terminated because of an error

Shutdown: Process shut down

Reserviert: Process is reserved

A process in “Waiting” is an idle/free process. An On-hold process needs to be reviewed with information from the “Reason” column to sap sm50 error understand the cause for “on-hold”. “BGD” process would be put in “on-hold” during period of waiting for completion of RFC call or when program is executing “WAIT” or “SLEEP” ABAP statement � 12560 protocol adapter error process would be rolled out under those situations. “DIA” process can be in “on-hold” status during RFC “initiation sap sm50 error and data sending/receiving phase which is “normally” brief � means when you refresh the display again, status would be changed to others, if not, it might be indicate a network issue or big size of data. A work process in bootstrap error label status means the program is executing an ABAP/SQL statement.


This field gives the reason why a work process has the status “On hold”.




Work process is working in debug mode, sap sm50 error, that is, it is assigned

exclusively to one user, and is waiting for input


Work process is waiting for the response from an RFC call


Work process is waiting for the response from asynchronous RFC



Work process is waiting for the response to an enqueue request


Work process is waiting for the completion of an

update request (type UPD)


Work process is waiting for the completion

of an update request (type UP2)


Work process waiting for a spool request to be processed


Work process is waiting for a response to an administration



Work process is sap sm50 error waiting for a response from the number range



Work process is waiting for a response from the frontend


Work process has been assigned exclusively to one user


Work sap sm50 error is waiting for a response from an update server


Work process is waiting for the server list


Work process is waiting for an answer from the gateway


Work process is waiting for the security link to be established


Work process assigned exclusively to one user for system



Work process is waiting because of a resources bottleneck


Work process is waiting to be synchronized with the message server


Work process is waiting for the operating system command to be



Work process is waiting for a response from the message server


Work process is waiting for an ABAP program to be generated


Work process has a local Java stack


Work process is waiting for a free Java VM

SLEEP is associated with “background” process. Dialog process in “sleep” would be rolled out.

GUI is error 0x800cccof in outlook with Dialog process.


Restart work process after dump?

Indicates whether the terminated work process should be automatically restarted in by the dispatcher. The following values are possible:

Yes : The work process is restarted

No��: The work process is not restarted (for example, if errors occur during the initialization phase).

You can set the work process by choosing Process -> Restart After Error -> Yes or No.


Restart work process after dump?

Indicates whether the terminated work process should be automatically restarted in by the dispatcher. The sap sm50 error values are possible:

Yes : The work process is restarted

No��: The work process is not restarted (for example, if errors occur during the initialization phase).

You can set the work process by choosing Process -> Restart After Error -> Yes or No.


Semaphore that the work process is waiting for

SAP number of the semaphore which blocks the work process:

If sap sm50 error field is green, the work process is holding the semaphore in question.

If the field is red, the work process waits for the semaphore in question.

The numbers stand for the com port writefile error 87 semaphores:

��1: PXA semaphore
��2: WP_CA_ADM semaphore
��3: APPC_CA_ADM semaphore
��4: TM_ADM semaphore
��5: COMM_ADM semaphore
��6: ROLL_ADM semaphore
��7: PAGING semaphore
��8: NO_BUFFER semaphore
��9: STAT semaphore
10: GW Request semaphore
11: CALI_BUFFER semaphore
12: TEMSE Char Code semaphore
sap sm50 error 13: Update-ADM semaphore
14: PRES_BUF semaphore
15: SHM_ADM_AREA semaphore
16: DB_TBUFF semaphore
17: DB_SYNC semaphore
18: DB_TTAB semaphore
19: DB_SNTAB semaphore
20: DB_IREC semaphore
21: DB_FTAB semaphore
22: LOGFILE semaphore
23: REQ_QUEUE semaphore
24: DB_TBUFF_P semaphore
25: ENQ_REQ semaphore
26: ENQ-TABLE semaphore
27: SAPCOMM_1 semaphore
28: SAPCOMM_2 semaphore
29: FIXADR semaphore
30: DB_CUA_BUFFER semaphore
31: Spool-ADM semaphore
32: Extended memory ADM semaphore
33: Extended segments semaphore
34: Server buffer semaphore
35: Object buffer semaphore
36: Extended segments user list semaphore
37: Global mutex semaphore
38: CCMS monitoring semaphore
39: Extended global memory semaphore
40: Semaphore reserved for testing
41: Semaphore reserved for testing
42: Shared statistic semaphore
43: Spool cache semaphore
44: Basis udit Semaphore
45: Application Statistic Buffer semaphore
46: Profile Parameter semaphore
47: Spool asynchronous RFC semaphore
48: ENQID semaphore
sap sm50 error 49: ABAP Virtual Machine Instruction Trace semaphore
50: Task handler runtime semaphore
51: ATRA semaphore
52: Memory pipes semaphore
53: Coverage Analyzer semaphore
54: ABAP Time Synchronization semaphore
55: Online Text Repository semaphore
56: ESM (Export to Shared Memory)- Semaphore
57: Runtime Monitor
58: JAVA
59: ABAP Shared Objects

60: JControl adminstration semaphore

61: JControl session semaphore
62: ITS plugin – update statistics
63: ITS plugin – service description

64: VM container lite cluster semaphore
65: Extended segments administration semaphore
66: VM Container adminstration semaphore
67: Extended memory adminstration semaphore

68: CCMS monitoring semaphore
69: Session breakpoint administration of ABAP debugger
70: Extended global memory adminstration semaphore

73: ABAP Hotspot Trace

I seldom observed a work process waiting for a semaphore.


CPU time

This is an accumulated CPU time consumed by all jobs and transactions executed under this process.


Indicates the elapsed clock time used by a work process for the dialog step that is currently processing.

This time is reset with each commit statement or each screen change in online mode(Dialog step/transaction step)


The report name that is currently being executed by the work process.

Exception: If the sap sm50 error report name starts with ‘<’ and ends with ‘>’, then the work process does not execute an ABAP sap sm50 error but a kernel action. The following values are possible:



<buffer sync>

SAP database buffer refresh

<auto abap processing>


<auto th processing>

Auto taskhandler

<adm message>

Administration message (ADM)

<no buffer>

Number range buffer (server part)

<exec program>

Starts external program

<update administration>

Update control

<statistic administration>

Statistics administration

<ddlog cleanup>


<delayed function call>

Delayed function


Program generation


Description of the action that the work process is currently executing



Roll In / Roll Out

Load or save user context

TXXX Access

Access to SAP pool table

Read directly

Read operation on the database

Sequential configure error /bin/sh ./config.sub failed read

Insert / Update / Delete /

Changing operations on the database

Commit / Phys. Insert /

Phys. Update / Phys. Delete

SQL Prepare / Open

SQL operations

Generate /��Load report /

SAP runtime operations

Load CUA / Load dynpro

Queue API

Execute queue operations

Read dictionary



Read / update matchcode

Matchcode operations

Insert / delete

DB Procedure

Execute database how to see procedure errors in oracle procedures

AD Opcode

Execute SAP kernel internal administrative functions

Read directly and Sequential read – in SAP SM50, “Read directly” means that only one record would be returned by the database. Reading a table via a full key and return one record is a “direct read”. Counting number of records which meet certain conditions would return one “number”, sap sm50 error, such operation would be displayed as “direct read” in SM50.Any other read is a “sequential read”. For example, SM50 would show “Sequential Read” when you read sap sm50 error table with full primary key but multiple records are returned by crank pos sensor circ error bank database due to “OR” or “IN” or SELECT-FOR-ALL selection criteria.


Table that was most sap sm50 error recently accessed by the kernel

On the overview screen, there are several buttons to allow you to control the display like sort, filter etc.

2.3 What performance work can be done in SAP SM50 overview screen

2.3.1 Check overall status sap sm50 error SAP work process Check availability of free work process

If all work processes of a specific work process type are occupied, then the instance/system has no ability to handle new request which needs that type of work process � When all dialog work process are occupied, sap sm50 error, then online request would not be serviced immediately but put into a queue � in worst case, the queue can be full � online user would experience very slow response from the system. When all background processes are occupied, then no new job can be started. If all updating processes are occupied, standard SAP transactions would not able to save any new changes to database anymore. So it is critical to check that there are “free” sap sm50 error processes available or there sap sm50 error no risk to run out of SAP work processes.

If all processes are occupied, this can be several reasons � database locks (DB01) or too few work processes are configured or high degree of parallelism due to improper execution of a transaction or extremely high volume, sap sm50 error. This could be a workload balance issue as well. If all updating work processes are occupied, then you need to check whether system “update” service was deactivated via SAP transaction SM13. In my experiences, I have seen cases of all updating process vb runtime error 424 object required occupied due to deactivated system “updating service” (due to full of table space) or “database lock” etc. You can check system log via SM21 or database monitor Sap sm50 error to understand why update service was deactivated.

All dialog or background processes can be occupied due to bad code and high degree of parallelism execution of that “bad” code. When program code is bad, it would take longer to complete. If it is one process, it might be ok, sap sm50 error. However when this bad code is executed in parallel process with high degree of parallelism and volume, sap sm50 error, this could be an issue. If exspres gate error code specific type of process is often seen in “contention” and there is no application design issue, it can indicate that more dialog processes are needed. More work process can be added if there is enough system resources. For example, if CPU is already overloaded, there is no point to add more work processes. You need to bring capacity first or reducing the load first � this is a separate topic. Check sign of memory contention

If significant number of dialog processes are “on-hold” status with a reason “Private” or displays “Roll-in” or “Roll-out” under Action column for some time in SM50 overview screenthis can indicated memory contention. Memory contention can be checked via SAP transaction ST02 which shows allocated SAP memory and free memory. Watch out shortage in extended sap sm50 error space.

2.3.2 Verify long running process

Long running process showed in SM50 overview screen might be stuck, sap sm50 error, blocked or running normally. Stuck process needed to be cancelled so the work process can be free for other tasks. Blocked process might be due to lock contention which should be investigated further. Long running due to inappropriate design/code can be tuned so it can run faster and using less resource.

As a quick note, a work process is not stuck if there are changes in CPU time and/or Database operation within its’ normal runtime. You can refer to my separate post – “Is my job hang” for more details on how to reach a decision on whether a business process is hanged or not.

I suggested that we pay special attention to long running updating process as well since

·        Number of updating process is small comparing dialog or background processes.

·        Updating process is normally running short. It is unusual for an updating process to run over sap sm50 error minute.

·        Lock would only be released after updating is completed. Long update is normally related to “big update” which can split sap sm50 error smaller update units to achieve better concurrency.

2.3.3 Debug work process

From SAP SM50, a work process can be debugged which can give you more information especially when program is executing ABAP logic showing nothing under “action” column. Using Debug, you can check internal table size which is not provided by other tools. This can help you to understand why a program is spent a long time on an internal table handling or looping or why program/job is using so much memory.

Debug option is under SM50 overview screen menu option�

To debug the process, you just need to click once on the entry, then go to menu option to launch “Debugging”. If you exit the debug, the process would execute it as normal.

You can use the debug only when program/process is not stuck on a “SQL” statement. Anyway, There is no need to debug a SQL statements. SQL statements can be verified in database session monitor(ST04).

2.3. 4 admin work process

SAP Varnish error 503 provides options for you to admin work process like terminating a process or restart a work process etc.

There were times that a stuck process could not be cancelled via SAP transaction SM50 or even could not be terminated at Operating system level due to kernel issue. In rare case, a stuck process would be gone after system reboots.

2.3.5 Others

From SAP Motorola lash critical error 1337 e183 overview screen, you can do other checks like- get user information, sap sm50 error, filter display based on user-id etc and review work process developer trace log.

Depends on your version or patch level, your SAP SM50 transaction might provide an straightforward overview showing total, what is in used and what is available like below and different layout on menu options

3 Understand SAP SM50 details display screen

3.1 SAP details display screen explanation

Details Display screen (please refer to above figure-2 for sample screens) is to show details information on one SAP work process at one time. Information in details screen is organized into several sections as showed below:



Overview of the work process

Same as overview screen- but it is showing exact CPU time here.

Report/spool action

This could be a report/program called by the main program

Main program

This could be program/transaction which user enters online or specify in job definition. It is if there is no RFC call initiated in the main program.


Dynamic data statistics on database operation for current step like snapshot of # of row direct read, sequential read etc, Refresh the display to sap sm50 error new status.


Dynamic Memory for current transaction step.


Time used by system level operation related to the program.

3.2 What performance work can be done from SAP SM50 details screen

3.2.1 Check status of individual business process

You can check whether the process is stuck by checking whether there is a change on CPU time or number of direct read, sequential read, insert etc by refreshing the screen.

3.2.2 Check memory/CPU usage

You can refresh SAP SM50 details screen again and review memory change situation to get a clear picture on how memory usage is changed over a course of program. Personally, I prefer to use SAP transaction /sdf/mon to monitor memory usage automatically, this avoids sitting in front of computer and refresh screen manually again and again, sap sm50 error.

SAP transaction STAD is showing memory usage as well however the memory usage showed half life 2 error STAD is the memory picture at end of program � I have seen the cases that STAD reported a much lower memory usage than what I saw in SM50 during monitoring of a process execution.

SM50 can tell you whether the program or process is spending most of time on application server side or on database server side by monitoring the execution and refreshing the SM50 display screen. However this approach is really manual and inaccurate. The best way to check this is to use STAD to check this after program/process finishes. STAD would has runtime distribution information where � CPU time is the CPU time spent by a transaction on application server CPU side and database time is the time spend on database server side. Please click here for more information on how to run STAD.

4. SAP global work process monitor SM66.

At this step, you should be familiar with SM50 already. With SM50 knowledge, it is easier to understand SAP SM66 � global active process monitor. The main difference between SM66 and SM50 is that SM66 show only those “engaged” work processes but from all instances/servers of a SAP system while SM50 report all work processes but only from one instance/server of a SAP system. In my version of SAP system, Work process “on-hold” status in SM50 is western digital data lifeguard error code 08 to “STOPPED” status in SM66. In another word, SM66 would show no process under “on-hold” status but instead “Stopped” status. It would not show details information you can see in SM50 for each entry, sap sm50 error.

However, it would give a clear snap-shot on what is running in the system in one click. SM66 provide a button in display screen to allow you control display via following options:

SM66 display can be sorted according to your need � like runtime, sap sm50 error, process type, sap sm50 error, table name etc.

From SM66 display screen, you can admin existing work process and start debugging as well, sap sm50 error.

5. Further clarification

SAP transactions are always subject to changes. Your SM50/SM66 display, layout might be different from what is showed here but Usage of SM50 and SM66 should be the same.

The process ID showed in SM50 and SM66 is the key for linking to database load session monitor(ST04 ) and CPU load monitor (OS06/OS07/ST06). This is useful when information from SM50/SM66 is not enough and you need further information like what provided by ST04 andOS06

/SDF/SM50 SAP ABAP Report - Program /SDF/SM50

/SDF/SM50 is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). Below is the basic information available for this SAP report including which OBJECTS it interacts with such as TABLES, FUNCTION MODULES, INCLUDES ETC, sap sm50 error. Also check out the submitted Comments related to this SAP report or see any standard documentation available.

If you would like to execute this report or see the full code listing simply enter /SDF/SM50 into the relevant SAP transactions such as SE38 or SE80

ABAP code to call this SAP report using the submit statement

This report can be called from another progam/report simply by using the ABAP SUBMIT statement, see below for example ABAP code snipts of how to do this.

SUBMIT /SDF/SM50."Basic submit
SUBMIT /SDF/SM50 AND RETURN."Return to original report after report execution complete
SUBMIT /SDF/SM50 VIA SELECTION-SCREEN."Display selection screen of submitted report to user
    See more syntax options for the ABAP SUBMIT statement

Text pool values

Title: Program /SDF/SM50
Text Symbol: 001 = SQL Trace
Text Symbol: 002 = ABAP Trace
Text Symbol: 003 = Workprocess Overview

INCLUDES used within this REPORT /SDF/SM50

No INCLUDES are used within this REPORT code!

TABLES used within REPORT and the associated SELECT statement:

No SAP DATABASE tables are accessed within this REPORT code!

Function Modules used within report and the associated call statement:

SAPTUNE_PROFILE_PARAMETER CALL FUNCTION 'SAPTUNE_PROFILE_PARAMETER' EXPORTING name = 'rdisp/myname' gswdll32.dll error in centura IMPORTING value = lf_profvalue EXCEPTIONS unknown_parameter = 1 no_authorization = 2 OTHERS = 3.

/SDF/MON_ROUTING CALL FUNCTION '/SDF/MON_ROUTING' EXPORTING instance = ls_server-name IMPORTING destination = lf_destination EXCEPTIONS system_not_defined = 1 instance_not_active = 2 OTHERS sap sm50 error = 3.

/SDF/MON_PERFORMANCE_TRACE_GET CALL FUNCTION '/SDF/MON_PERFORMANCE_TRACE_GET' EXPORTING instance = ls_server-name IMPORTING error 1603 sony vegas proc_nr = lf_sql_procnr EXCEPTIONS routing_error = 1 system_failure = 2 communication_failure = 3 OTHERS = 4.

/SDF/GET_ABAP_TRACE_STATUS CALL FUNCTION '/SDF/GET_ABAP_TRACE_STATUS' EXPORTING instance = ls_server-name IMPORTING wp_no = lf_abap_procnr EXCEPTIONS no_abap_trace_active = 1 OTHERS = 2, sap sm50 error.

/SDF/MON_TH_WPINFO CALL FUNCTION '/SDF/MON_TH_WPINFO' EXPORTING srvname = ls_server-name with_cpu = gf_with_cpu TABLES wplist = lt_wp EXCEPTIONS error in format of file arc.migrate remap error mp280 error 5100 = 1 routing_error = 2 OTHERS sap sm50 error = 3.

REUSE_ALV_FIELDCATALOG_MERGE CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE' EXPORTING i_structure_name = gf_structure * i_bypassing_buffer = 'X' CHANGING ct_fieldcat = gt_fieldcat.

REUSE_ALV_GRID_DISPLAY CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING * i_bypassing_buffer = 'X' * I_BUFFER_ACTIVE = ' ' i_callback_program = sy-repid i_callback_pf_status_set = 'CALLBACK_SET_PFSTATUS' i_callback_user_command = 'ALV_HANDLING' i_structure_name = gf_structure * I_BACKGROUND_ID = ' ' i_grid_title = lf_title * I_GRID_SETTINGS sap sm50 error = is_layout = ls_layout it_fieldcat sap sm50 error = gt_fieldcat i_save = 'X' TABLES t_outtab =

EXCEPTIONS program_error = 1 OTHERS = 2 .

/SDF/MON_ROUTING CALL FUNCTION '/SDF/MON_ROUTING' EXPORTING sap sm50 error instance = lf_server IMPORTING destination dc-unlocker error code 62 = lf_destination * SID sap sm50 error = EXCEPTIONS system_not_defined = 1 instance_not_active = 2 OTHERS = 3 debian mplayer error sap sm50 error.


/SDF/MON_DB_SQL_SOURCE_DISPLAY CALL FUNCTION '/SDF/MON_DB_SQL_SOURCE_DISPLAY' EXPORTING instance = lf_server source_ref = ls_source_ref EXCEPTIONS error = 1 routing_error = 2 OTHERS = 3.

/SDF/MON_DB_EXPLAIN_PLAN sap sm50 error CALL FUNCTION '/SDF/MON_DB_EXPLAIN_PLAN' EXPORTING instance = lf_server statement = lf_sql_text EXCEPTIONS explain_failed = 1 routing_error = 2 OTHERS = 3.

/SDF/MON_PERFORMANCE_TRACE_ON CALL FUNCTION '/SDF/MON_PERFORMANCE_TRACE_ON' EXPORTING instance = lf_server sql_trace_on = 'X' trace_user = '*' enq_trace_on = 'X' sap sm50 error rfc_trace_on = 'X' proc_nr = lf_wp_no EXCEPTIONS error = 1 OTHERS sap sm50 error = 2.

/SDF/MON_PERFORMANCE_TRACE_OFF CALL FUNCTION '/SDF/MON_PERFORMANCE_TRACE_OFF' EXPORTING instance = lf_server sap sm50 error trace_user = '*' sql_trace_off = 'X' enq_trace_off = 'X' rfc_trace_off = 'X' buf_trace_off = 'X' * CHECK_USER = ' ' sap sm50 error use_trace_exceptions = ' ' EXCEPTIONS error = 1
OTHERS = 8 .

/SDF/ACTIVATE_ABAP_TRACE CALL FUNCTION '/SDF/ACTIVATE_ABAP_TRACE' EXPORTING instance = lf_server program = lf_report wp_pid = lf_wp_pid sap sm50 error EXCEPTIONS error = 1 OTHERS = 2.



/SDF/GET_SERVER_LIST CALL FUNCTION '/SDF/GET_SERVER_LIST' TABLES it_system = gt_system server = gt_server.

/SDF/GET_SERVER_LIST CALL FUNCTION '/SDF/GET_SERVER_LIST' TABLES it_system = gt_system server = gt_server.


CALL FUNCTION '/SDF/GEN_FUNCS_EXT_CALL' DESTINATION lf_destination EXPORTING calltype = 'P' argument sap sm50 error = '/SDF/SM04' asynchronous = space server = lf_servdest EXCEPTIONS delphi message = asynchronous socket error 10053 server_not_known = 1 argument_not_valid = 2 remote_call_not_possible = 3 sap sm50 error = 4 OTHERS disk 3s3 i/o error = 5, sap sm50 error.

/SDF/DISPLAY_PERF_TRACE CALL FUNCTION '/SDF/DISPLAY_PERF_TRACE' DESTINATION lf_destination STARTING NEW TASK lf_task EXPORTING 3d max internal error sap sm50 error instance = lf_server sql_trace_on = 'X' enq_trace_on = 'X' sap sm50 error rfc_trace_on = 'X' start_trace_date = gs_trace_flag-start_date start_trace_time = gs_trace_flag-start_time end_trace_date = gs_trace_flag-end_date end_trace_time = gs_trace_flag-end_time.

/SDF/DISPLAY_PERF_TRACE CALL FUNCTION '/SDF/DISPLAY_PERF_TRACE' DESTINATION lf_destination EXPORTING instance = lf_server sql_trace_on = 'X' enq_trace_on = 'X' rfc_trace_on = 'X' canon mp145 error code e8 start_trace_date = gs_trace_flag-start_date start_trace_time = gs_trace_flag-start_time end_trace_date = gs_trace_flag-end_date sap sm50 error error compiling keymap = gs_trace_flag-end_time.


/SDF/GEN_FUNCS_EXT_CALL Sap sm50 error FUNCTION '/SDF/GEN_FUNCS_EXT_CALL' DESTINATION lf_destination EXPORTING server = lf_servdest argument = 'SE30'.

TH_DEBUG_WP CALL FUNCTION 'TH_DEBUG_WP' DESTINATION lf_destination EXPORTING wp_no = lf_wp_nr dest sap sm50 error = lf_server wp_index = 999999 EXCEPTIONS sap sm50 error no_authority = 1 no_debugging_possible = 2 OTHERS = 3.

TH_WP_DETAIL_INFO CALL FUNCTION 'TH_WP_DETAIL_INFO' missing file error DESTINATION lf_server EXPORTING 4.3.3 21 error wp = lf_wp_nr with_cpu = 1 IMPORTING wpinfo = ls_wpinfo diarec = ls_diarec EXCEPTIONS OTHERS = 1, sap sm50 error.

/SDF/MON_STRC_DISPLAY_WP_TRACE CALL FUNCTION '/SDF/MON_STRC_DISPLAY_WP_TRACE' EXPORTING instance = lf_server file = lf_file EXCEPTIONS error = 1 routing_error = 2 OTHERS = 3.

/SDF/MON_STRC_DISPLAY_WP_TRACE CALL FUNCTION '/SDF/MON_STRC_DISPLAY_WP_TRACE' EXPORTING instance = lf_server file = lf_file EXCEPTIONS error = 1 routing_error = 2 OTHERS = 3.

/SDF/GEN_FUNCS_EXT_CALL CALL FUNCTION '/SDF/GEN_FUNCS_EXT_CALL' DESTINATION lf_destination EXPORTING sap sm50 error argument = 'ST06' asynchronous = space server = lf_servdest * TABLES * PT_IMPORTING = * PT_EXPORTING = EXCEPTIONS server_not_known = 1 argument_not_valid = 2 remote_call_not_possible = 3 sy_subrc_ne_0 = 4 OTHERS = 5 .

/SDF/MON_HOLD_WP CALL FUNCTION '/SDF/MON_HOLD_WP' EXPORTING instance = lf_server hold = 'X' IMPORTING sap sm50 error wp_no = lf_locked_wp EXCEPTIONS routing_error = 1 disk read error has occurred ssd OTHERS = 2.

/SDF/MON_HOLD_WP CALL FUNCTION '/SDF/MON_HOLD_WP' EXPORTING instance = lf_server hold = space IMPORTING wp_no = lf_locked_wp EXCEPTIONS routing_error = 1 OTHERS = 2.

/SDF/MON_HOLD_WP pkgadd error could not process datastream from CALL FUNCTION '/SDF/MON_HOLD_WP' EXPORTING instance = ls_server-name hold drweb error cod 11 'X' IMPORTING wp_no = lf_locked_wp EXCEPTIONS server fatal error code 5 routing_error = 1 OTHERS = 2.

/SDF/MON_HOLD_WP CALL FUNCTION '/SDF/MON_HOLD_WP' sap sm50 error EXPORTING instance = ls_server-name hold = space IMPORTING wp_no = lf_locked_wp EXCEPTIONS routing_error = 1 OTHERS = 2.

POPUP_GET_VALUES CALL FUNCTION 'POPUP_GET_VALUES' EXPORTING * NO_VALUE_CHECK = ' ' error xml parsing popup_title = lf_popuptitle * START_COLUMN = '1' * START_ROW = '1' TABLES fields = lt_fields EXCEPTIONS error_in_fields = 1 OTHERS = 2.

/SDF/GEN_FUNCS_EXT_CALL CALL FUNCTION '/SDF/GEN_FUNCS_EXT_CALL' sap sm50 error DESTINATION lf_destination EXPORTING calltype sap sm50 error = lf_calltype argument = lf_argument asynchronous = space server = lf_servdest * TABLES * PT_IMPORTING = * PT_EXPORTING = EXCEPTIONS server_not_known = 1 argument_not_valid = 2 remote_call_not_possible = 3 sap sm50 error sy_subrc_ne_0 = 4 OTHERS sap sm50 error = 5 .

REUSE_ALV_FIELDCATALOG_MERGE CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE' EXPORTING i_program_name = sy-repid i_structure_name = '/SDF/WPINFO_EXT_DISP' CHANGING ct_fieldcat = lt_fcat EXCEPTIONS inconsistent_interface = 1 program_error = 2 OTHERS = 3.

REUSE_ALV_GRID_DISPLAY CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING i_structure_name = '/SDF/WPINFO_EXT_DISP' * I_GRID_TITLE = lf_title it_fieldcat = lt_fcat TABLES t_outtab = lt_details EXCEPTIONS OTHERS = 2 .

DDIF_FIELDINFO_GET * CALL FUNCTION 'DDIF_FIELDINFO_GET' * EXPORTING formmail.cgi 500 internal server error tabname = pf_tabname * TABLES * dfies_tab = lt_field * EXCEPTIONS * not_found = 1 * internal_error = 2 * OTHERS = 3.

F4IF_INT_TABLE_VALUE_REQUEST * CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST' * EXPORTING * retfield = pf_fieldname * dynpprog = lf_dynprog * dynpnr = lf_dynpnr * dynprofield = pf_dynpfield ** WINDOW_TITLE = * value_org = 'S' * TABLES * value_tab = pt_table * field_tab = lt_field * EXCEPTIONS * parameter_error = 1 * no_values_found = 2 * OTHERS = 3, sap sm50 error.

Contribute (Add Comments)

Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report, sap sm50 error.

The contribute/comments section below therefore offer's an opportunity for anyone to add additional information. This can be anything from useful hints, tips and screen shots to relevant SAP notes or p2015 error lights else you feel is relevant to this report.

This will then be available for everyone to easily find by simply searching on the report name /SDF/SM50 or its description.


/SDF/SM50 - Program /SDF/SM50
/SDF/SM50 - Program /SDF/SM50
/SDF/SIZING_TOOL - sizing tool based on stad-records
/SDF/SIZING_TOOL - sizing tool based on stad-records


Leave a Comment