SAP Library - Find your answers

Purpose

Alerts are assigned methods using the associated monitoring tree elements (MTEs). A method can be a report, a function module, an SAP transaction, or a URL that is to executed as a reaction to an alert. You should differentiate between auto-reaction methods that the system automatically executes as a reaction to an alert (see also Selected Methods of the Alert Monitor, such as an Automatic Alert Notification), and analysis methods that you start manually when analyzing an alert (see Starting Methods).

After you have analyzed an alert and corrected its cause, you no longer need to display the alert in the Alert Monitor: you can complete the alert. This means that it is deleted from the Alert Monitor and saved to an Alert Database. You can display completed alerts from the Alert Database. The Alert Database is also monitored using the Alert Monitor: if the size of the database reaches a defined limit, an alert is triggered. To limit the size of the database, you can reorganize completed alerts.

By default, an alert represents a problem message. You can, however, activate the generation of “green alerts” for selected nodes, that is, an alert of this type for an all-clear or for an explicit message that an action was successful (see Working with All-Clears (Green Alerts)).

See also:

Changing Properties and Method Assignments

Using this monitor, you can monitor the status of background processing in your SAP system both for the entire system and itemized by application servers on which background work processes are configured. For a general introduction to background processing, see Background Processing: Concepts and Functions.

In addition to monitoring background processing in general, you can also monitor selected jobs using the Monitoring Architecture (see Monitoring Jobs with the Alert Monitor).

Features

The monitor contains the following monitoring tree elements (MTEs):

Activities

To start the monitor, follow the procedure below:

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Background Processing monitor from the list by double-clicking it.

Procedure if an Alert Is Triggered

Utilization and SystemWideQueueLength show if there is a serious bottleneck in the capacity of the background processing. The optimal situation is that there is a high utilization of the work processes and a short wait queue length.

Background jobs are usually defined without a target server (Execution target in the Define Job initial screen of transaction SM36). This ensures an optimal distribution of the job workload. Jobs defined in this way therefore do not appear in the ServerSpecificQueueLength, but only in SystemWideQueueLength, meaning that the latter attribute is best for showing capacity problems in background processing.

If a bottleneck exists, it is often useful to divide the existing jobs between more servers. You can do this, for example, by switching dialog work processes to background work processes during the operation mode switch to night operation. Before you increase the number of background work processes, note that it does not make sense to have more than three background work processes for each CPU on a background server, as these work processes will already be fully utilizing the CPU. Set the number of these work processes using the system parameter rdisp/wp_no_btc.

For more information about this topic, see SAP Note 39412 (How many work processes to configure).

An alert for ServerSpecificQueueLength when there is a short SystemWideQueueLengthindicates that the distribution of the jobs is not optimal. You should only specify a target server when it is absolutely necessary that the job is started on this server.

Can someone tell me what the difference between backgroud processing and batch processing is. Also does the access to this function be limited.

I have a requrinment where they want everyone to have access to batch processing and just wanted to know how i should be handling this request.

Please help

Answer:
You have to get clarification from the requester. Most often Batch and background mean the same. There is a SAP useage which means Batch Data Communication ( BDC) that is sometimes refered to as Batch but most often refered to as BDC. Batch anf Background is controlles with S_BTCH_JOB and BDC is S_BDC_MONI. You need clarification fromt he requester.

Answer:
And if the user also has S_BTCH_ADM = Y and S_BTCH_NAM = DDIC (or *), then they can schedule the jobs, release, delete etc (as per S_BTCH_JOB actions permitted), but.. in the name of and with the authorizations of the other user names.

You can check with SUIM reports who can use your user account (for example) without having to know your password.

The myth that one cannot logon with a batch user is therefore true, because you don't need to logon with it...

Cheers,
Bob

Answer:
There is no myth about "loggin on to a Batch id" it does logon to run the batch job it just cannot be used in DIALOG mode. S_BTCH_NAM allows you to run a batch job using that users' access be it DDIC ( which should not have SAP_ALL) or any other id BATCH or DIALOG.

Answer:
There is no myth about "loggin on to a Batch id" it does logon to run the batch job it just cannot be used in DIALOG mode. S_BTCH_NAM allows you to run a batch job using that users' access be it DDIC ( which should not have SAP_ALL) or any other id BATCH or DIALOG.

It does logon, but unlike Communication users, the password is not critical for this login so you can change it. Like Communication users, one does not have to know what the password is... just access to see that someone once did and left it behind in the system. For Communication users one does not need to know the password either, but changing it, would make the access to the user more difficult.

Symptom

Corrective action

1. Choose Applicant activity
® Display.

The Display Applicant Activities screen appears.

2. In the Applicant number field, enter the desired number.
3. Choose Edit
® Execute.
1. If an applicant has several applications, select the one you want, and choose Edit
® Choose application.

The Display Applicant Activities screen appears.



You can display the processing status of an application from the list of all activities for an applicant.

4. You can print out the processing status of the application, or display an individual applicant activity, its notes, or the reference activity of an applicant activity.

Purpose

Prerequisites

Process Flow

Result

The application is ‘in process’. You can continue with the following processes:

Keyword: SAP HR
Title : SAP Payroll - Year-end processing - US

Keyword: SAP HR
Title : Wage Type Processing Basic Concepts

Keyword: SAP HR
Title : Wage Type Processing Basic Concepts – part 2

Keyword: SAP HR
Title : Processing class 71 in Payroll