Stopping Run-Away or “Bad” Work Processes

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM50.

3. On the Process Overview screen, find the process which must be

stopped. Place a √ in the □ to the left of the process number

to be stopped by pressing Space. On the top-most menu bar,

click the Process → Cancel without core.

4. Click the blue arrow circle picture-icon to refresh the Process

Overview screen until the stopped process has cleared from the

display.

5. You may now leave the SM50 transaction.

If this does not kill the process, you can go to transaction SM04 and kill the user’s session. If this does not kill the process, you can log on to the server, open a Task Manager session, and End the Process. If this does not kill the session, there is an executable in the RUN directory on the server called sapntkill.exe. Run it providing the process ID number. If none of the above work, you have no choice but to “bounce” the SAP instance and/or possibly the serve.

There are five types of work process in sap

Dialog Work process: The Dialog work process fulfill all requests for the execution of dialog steps triggered by an active user. The dialog work process are not used for request which take long time and which use more cpu. Every dispatcher requires at least two dialog work processes. The dialog work process default time is 300 secs. If the dialog work process does not respond in this time, it will be terminated. Also dialog work process are multiplexed to handle large no of user request. Learn more about multiplexing here . You can set the maximum response time of dialog work process from transaction rz11 & set the parameter rdisp/max_wprun_time to time you need. The no of dialog work process can be changed by changing the parameter rdisp/wp_no_dia.

Background Work process: The background work processes execute programs that run without user interaction. At least two background work processes are required per SAP system. More than one background work processes can be configured per dispatcher. Usually the background work process are used for carrying jobs that take long time to finish, like client copy, client transport etc.., Then no of background work process can be changed by changing the parameter rdisp/wp_no_btc . There are two types of background work process. They are A type and B type. A type background work process are used for mission critical jobs. Background jobs of priority a have high priority than B type back ground jobs.

Update Work Process: Update work processes execute update requests. You need at least one update work process per SAP system and you can have more than one per dispatcher. The profile parameter rdisp/wp_no_vb is used to control the no of update work process and rdisp/wp_no_vb2 for not of update work process of type v2. There are two types of update work process. They are v1 and v2. v1 update jobs have higher priority than v2 jobs. v1 jobs are used for critical jobs. There must be at least one V1 update work process in the SAP System. However there can be more than than one.V2 modules describe less critical secondary changes. These are pure statistical updates, for example, such as result calculations.

Spool work process: The Spool work process pass sequential data flows on to printers. Every SAP system requires at least one Spool work process. However, there can be more than one per dispatcher. The parameter to set the no of spool work process is rdisp/wp_no_spo.

Enqueue Work Process:The Enqueue work process administers the lock table in the shared memory. The lock table contains the logical database locks of the ABAP stack. Only one enqueue work process is needed for each SAP system. This is present on the central instance. You can determine or find an central instance by looking the the various work process present in it. For example, only the central instance contains enqueue and message work process. rdisp/wp_no_enq. It is not dynamically switchable.



You can see an overview of all work processes in the application server by calling transaction sm50.

IF you want to find out the optimum no of work processes there are two ways
1) Goto transaction sm50 and click CPU as shown in figure

or press ctrl+shift+f6 . You will see the cpu total times of the work processes . If you have WPs whose CPU time is very less (Say less than 0:20), you can decrease the number of WPS of that type . If the CPU time of certain type of work process is high, you may decide to increase their no.

2) Another method is to go for transaction Al12 then click all servers as shown


Then you will see the total no of requests for each work process. If all the dialog work process have large no of requests then you can add additional dia wps. If you have less dia wps with less requests , then you can decrease the no of dia wps.
This method is useful in deciding which operation mode to be used at a particular time.

Windows:

Go to Windows Task manager and you can see the processes listed. All the disp+work.exe processes are SAP work processes.

Right-click Start bar and click Task Manager to invoke it.


Unix:

The following Process Status command can be used to know the work processes status.

ps -ef | grep SAP

Also, irrespective or the operating system we can use dpmon.exe executable, which is located in the Kernel (usr\sap\\sys\exe\run) directory.

The DPMON.EXE program can be used to adminster the work processes from the operating system. It is located in the Exe -> Run directory. It is equivalent to SM50 transaction.


This will be very useful, when you have issues at SAP Level, and cant use SM50 to terminate any processes.

SAP RFC Programming - FREE DOWNLOAD

Report Painter in sap - FREE DOWNLOAD

Ebook : SAP Business workflow getting started - FREE DOWNLOAD

SAP ABAP Idoc Interface - FREE DOWNLOAD

SAP ABAP Dictionary - FREE DOWNLOAD

Instalacao e Post NW04 WAS ABAP HPUX Oracle - Free Download

Business Process Management - Build your own workflow from Scratch - FREE DOWNLOAD

Java and BAPI technology for EP - FREE DOWNLOAD

Performance Tuning for SAP R/3 - FREE DOWNLOAD

Managing SAP for Optimum Performance and Avaliability - FREE DOWNLOAD

SAP WorkFlow FREE DOWNLOAD

1. Start the workload monitor by calling transaction ST03N.
2. Choose the
user mode that you require.
3. Choose Load History and Distribution (or Load Distribution in the Administrator user mode) and then Users per Instance.

Pushbutton	Meaning
Choose instance	Outputs all users, the number of dialog steps executed by them and the response times on the selected instance
Instances per user or User per instances	Switches between two views (the pushbutton displays the view to which you can change, not the active one): Instances per User: For each user, the system displays all instances that the user has logged on to during the selected time period. User per instances For each instance, the system displays the number of users that were logged on during the selected time period.
Period-, Period+	Change the displayed period of time by one unit of the selected period
Filter...	Restricts the users to those with response time or number of dialog steps above a threshold value of your choice (only available in the Instances per User view)
By days, By weeks, By months	Period for the output lines

The workload monitor is a one-screen transaction that has as few additional menus as possible. This makes operation significantly easier and more intuitive.
Integration
The workload monitor transaction ST03N replaced the old ST03 transaction.
Features

Activities
The individual screen elements of the workload monitor mean the following:
User Mode
After starting the workload monitor, you should first choose a user mode. Through this, you gain access to precisely the functions and time periods that are relevant for the selected role.
Functions
In the Functions subscreen, choose a symbol by double clicking it:

Function	Meaning
Workload	Here you can define the instance and the time period that you want to define, in accordance with the user mode.
Detailed analysis	These functions read the workload directly from the statistics files of the individual instances.
Business transaction analysis	Here, you can perform a very precise analysis of individual transaction down to the level of individual steps.
Last minutes’ load	Here you can analyze the workload data that has not yet been written to the MONI performance database.
Load history and distribution Load history Instance Comparison Users per Instance	Here (unlike in the workload monitor), you cannot display the workload for a particular instance and a particular time period, instead you can compare the workload for instances or time periods. A comparison of the most important data allows you to directly compare the instances.
Collector & Perf. Database	Here you can determine, among other things, which values the statistics collector determines, and how often, and for how long they should be retained in the performance database.

Analysis Views
An analysis view displays a particular aspect of the workload. In the analysis views subscreen, choose the view that you want to analyze by double clicking it.




Only those Analysis Views are shown that:

• Are active in the selected user mode
• Exist for the data

Output Area
The output area uses an ALV Grid Control, with which you can greatly tailor the selected view to your requirements. For most load parameters, the workload monitor displays more data fields than are required for your analysis. You therefore have a considerable amount of help in the output area to obtain the data that is relevant for you:

• The data for most analysis views is grouped in tab pages by various topic areas
• To obtain an overview of which data fields exist for an analysis view, choose the All Data tab page.

• Using the
standard functions of the ALV Grid Control, you can:

• Show and hide columns
• Sort lines by the contents of a column
• Set and delete filters
• Perform summations
• Export tables in a file type of your choice
• Display tables as graphics
• Save sort orders, filters, and selected columns as your layout

Edit Views
Choose one of the following pushbuttons in the Edit Views screen area:

Pushbutton	Meaning
Save View	Saves the current view as your initial screen for the workload monitor (see also Saving User-Specific Views).
Previous View or Next View	Moves one view forward or backward in the view history
Full Screen: Show/Hide Tree	Shows or hides the Functions and Analysis Views sections in the left-hand part of the screen.

Purpose
The workload monitor (transaction ST03N) is intended for use by EarlyWatch and GoingLive teams. The workload monitor was reworked as part of the EnjoySAP initiative, so that the Workload Overview is now simpler and more intuitive.
You use the workload monitor to analyze statistical data from the SAP kernel. When analyzing the performance of a system, you should normally start by analyzing the workload overview. For example, you can display the totals for all instances and the compare the performances of individual instances over specific periods of time. You can quickly determine the source of possible performance problems using the large number of analysis views and the determined data.
You can use the workload monitor to display the:

• Number of configured instances for each SAP R/3 System
• Number of users working on the different instances
• Distribution of response times
• Distribution of workload by transaction steps, transactions, packages, subapplications, and applications
• Transactions with the highest response time and database time
• Memory usage for each transaction or each user per dialog step
• Workload through RFC, listed by transactions, function modules and destinations
• Number and volume of spool requests
• Statistics about response time distributeion, with or without the GUI time
• Optional: Table accesses
• Workload and transactions used listed by users, payroll number, and client
• Workload generated by requests from external systems

For all of this data:

• You can display the data for a particular instance (not only the one to which your logged on) or optionally totalled for all instances.
• Depending on your user mode, you can choose the time period for which you want to display the data between day, week and month (or determine the length of time yourself using the
Last Minutes’ Load function).
• For most analysis views, you can display all or only certain task types.

Integration
The workload monitor completely replaces the old ST03 transaction.
Features
The workload monitor has an interface that is divided into two parts. Use the tree structures on the left of the screen to make the following settings:

• Select the
user mode
• Select the time period for which you want to display the workload
• Select various functions and analysis views (which data you want to display).

The system then displays the result on the right of the screen in a standardized ALV Grid Control. With it, you can :

• 
  
Adjust the Layout of the Data Output
• Find the information you want using sort and filter functions
• Save user-specific views
• Display statistics graphically

In SAP Basis 4.6C, the workload monitor was extended so that it now also includes GUI times, Frontend network times and the RFC time.

You can display the workload overview for all task types (Dialog, Background, RFC, ALE and Update) or for one particular task type. The system displays the following data:

Information	Explanation
Average CPU Time	Average time that a workprocess uses the CPU; during a dialog step, the CPU of the application server is used for processing (loading, generating, processing database requests, ABAP processing, and so on). The CPU time is determined by the operating system. At the end of a transaction step, the SAP work process queries the CPU time from the operating system. The CPU time is therefore not an additive component of the response time, unlike wait time, roll in time, load time and database time.
Average Response Time	Average time between the time at which a dialog process sends a request to a dispatcher work process, and the time at which the dialog is completed and the data is transferred to the presentation layer. The response time does not include the time for transferring the data from the SAP frontend to the application server. For networks with bad performance, a more subjective response time can therefore emerge. The transfer time is included in the GUI time and the Frontend network time.
Average Wait Time	The average time an unprocessed dialog step waits in the dispatcher queue for a free work process. Under normal circumstances, the dispatcher work process should pass a dialog step immediately after receiving the request from the dialog step. In this situation, the average wait time should be only a few milliseconds. If the application server of the entire system is under a heavy load, this can lead to traffic jams in the dispatcher wait queue.
Average Load and Generation Time	Average time required to load and generate objects such as ABAP source code and screen information from the database.
DB Calls	Number of parsed accesses to the database
DB Access	Number of logical ABAP accesses to data in the database; these accesses are made through the SAP database interface and are parsed into individual database calls. The ratio of database calls to database accesses is important. If the access to information in a table is buffered in the SAP buffer, no database calls to the database server are required. The ratio of Calls/Accesses therefore gives an indication about the efficiency of the table buffering. A good ratio would be 1:10.
GUI Time	Response time between the dispatcher and the Gui during the roundtrips (roundtrips are communication steps between the SAP system and the frontend during a transaction step).
Roll Ins	Number of rolled in user contexts
Roll Outs	Number of rolled-out user contexts
Roll In Time	Processing time for the rolling in of user contexts
Roll Out Time	Processing time for the rolling out of user contexts
Roll Wait Time	Wait time in the roll area When synchronous RFCs are called, the work process performs a roll out and waits for the end of the RFC in the roll area. The RFC server programs can wait for other RFCs to be sent to them in the roll area.
Average Time per Logical Database Call	Average response time for all commands sent to the database system (in milliseconds). The time depends on the CPU capacity of the database server, the network, buffering, and on the input/output capabilities of the database server. The access times for buffered tables are far faster and are not considered here.

Background information
The response time is usually split into wait time plus execution time. The SAP response time is made up of the following components:
Response Time = Wait Time + Execution Time
where: Execution Time =
Generation time during the run
+ Load time for programs, screens and the graphical interface
+ Roll times for rolling in the work data
+ ABAP processing time
+ Database time
+ Enqueue time for logical SAP lock processes
+ CPIC/RFC time
+ Roll wait time (excluding Task types RFC/CPIC/ALE)
The CPU time is not an additive component of the response time, but the total of the individual components of the utilized CPU time. The CPU time is therefore an additional, independent piece of information about the response time.

Free Download SAP XI Overview PPT


XI Overview PPT

Free Download SAP XI System Content Copy material


XI System Content Copy

Free Download SAP XI Assign Interface Mapping to Interface Determination

Free Download SAP XI Create Interface Mapping


XI - Create Interface Mapping

Free Download SAP XI Create Message Mapping


XI - Create Message Mapping

Free Download SAP XI Create namespace

Free Download SAP XI Create Software Component

Free Download SAP XI Import SW

Download SAP XI Logon To IB Design

Free Download XI Tuning Guide

As in ADK-based archiving, the authorization to carry out various archiving object programs is checked by the authorization object S_ARCHIVE.

To display resources from archive administration an additional application-specific check is performed, with the help of a Business Add-In (BAdI).

This website/blog uses third-party advertising companies to serve ads when visiting this site. These third parties may collect and use information (but not your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, you can visit Google's Advertising and Privacy page.

If you wish to opt out of Advertising companies tracking and tailoring advertisements to your surfing patterns you may do so at Network Advertising Initiative.

Google uses the Doubleclick DART cookie to serve ads across it's Adsense network and you can get further information regarding the DART cookie at Doubleclick as well as opt out options at Google's Privacy Center.

Privacy:
I respect your privacy and I am committed to safeguarding your privacy while online at this site www.saphelpdata.blogspot.com. The following discloses how I gather and disseminate information for this Blog.

RSS Feeds and Email Updates

If a user wishes to subscribe to my RSS Feeds or Email Updates (powered by Feedburner), I ask for contact information such as name and email address. Users may opt-out of these communications at any time. Your personal information will never be sold or given to a third party. (You will never be spammed by me - ever)

Log Files and Stats

Like most blogging platforms I use log files, in this case Statcounter. This stores information such as internet protocol (IP) addresses, browser type, internet service provider (ISP), referring, exit and visited pages, platform used, date/time stamp, track user’s movement in the whole, and gather broad demographic information for aggregate use. IP addresses etc. are not linked to personally identifiable information.

Cookies

A cookie is a piece of data stored on the user’s computer tied to information about the user. This blog doesn't use cookies. However, some of my business partners use cookies on this site (for example - advertisers). I can't access or control these cookies once the advertisers have set them.

Links

This Blog contains links to other sites. Please be aware that I am not responsible for the privacy practices of these other sites. I suggest my users to be aware of this when they leave this blog and to read the privacy statements of each and every site that collects personally identifiable information. This privacy statement applies solely to information collected by this Blog.

Advertisers

I use outside ad companies to display ads on this blog. These ads may contain cookies and are collected by the advertising companies and I do not have access to this information. I work with Google Adsense. Please check the advertisers websites for respective privacy policies.

Contact Information

If you have any questions or concerns please contact me at saphelpdata[at the rate of]gmail[dot]com.


@ 2009 All Information About SAP - The articles are copyrighted to Krishna K and can only be reproduced given the author's permission.

All product names are trademarks of their respective companies.Every effort is made to ensure content integrity. Use information on this site at your own risk. Information furnished in the blog is collected from various sites. This blog does not host any files on its server. Please report any broken links in comment.

The Blog www.saphelpdata.blogspot.com no way affiliated with SAP AG.