SAP Library - Find your answers

In the monitoring architecture, you can react automatically to an alert using auto-reaction methods. These methods are automatically started in the case of an alert and by default are executed in the system in which the alert occurs. Almost no assignments are made in the standard SAP system; however, there are several predefined auto-reaction methods in the monitoring architecture that you can assign to any MTE classes.

As of SAP Web Application Server 6.10, you can also define central auto-reaction methods. The auto-reaction methods are not started in the system, in which the alert occurs, but rather in the central monitoring system. In this way, it is possible for reactions to events that occur in monitored components to be performed immediately in a central location.

If problems occur during the execution of auto-reaction methods, it can be useful to check the status of the auto-reaction methods. You can find out the definition and runtime status of an MTE by choosing Display Details (). This method is very time-consuming for obtaining an overview of the auto-reaction methods for the MTEs of an entire monitor. The technical view Status Autoreaction exists as an alternative for this purpose.

In this technical view, you can also manually start the auto-reaction method for any MTE to which an auto-reaction method is assigned. To do this, choose the relevant MTE by double clicking it. This is especially useful during test phases.

Note that when you start an auto-reaction method manually, it runs under your user name and therefore also under your authorizations. As the method runs under the SAPSYS user when it is started automatically, and this user has only very few authorizations, you can assume from a successful test with a manual start that the method will also run without problems during normal operation.

Procedure

To activate the Status Autoreaction technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Status Autoreaction. The alert tree now no longer displays the alert status and reported values, but information about the auto-reaction methods of the MTEs of the monitor.

Result

The view displays the following information for the active monitor about the auto-reaction methods that are assigned to the individual MTEs:

· Assigned auto-reaction method

· Type of the auto-reaction method; depending on the definition of the method, the following types are possible:

· Definition status of the method:

· Runtime status of the method:

· The time specification after the runtime status shows the time since which the method has been in this status.

· The color of the nodes is not passed upward in the alert monitoring tree. Monitoring objects and summary nodes therefore always have the color Green.

Data suppliers deliver values that are displayed in the Alert Monitor. They each belong to the individual system components and create monitoring objects that report values to the monitoring architecture. These values are displayed in the monitor sets.

It can be useful to check the status of the data collection methods if problems occur in the monitoring architecture. You can find out the most important information about the assigned data collection methods on one hand by choosing Properties, if you choose the data collection method in the Methods tab page by double clicking it. On the other hand, you can find out the definition and runtime status of the data collection method of an MTE by choosing Display Details ()

This method is very time-consuming for obtaining an overview of the data collection methods and their status for the MTEs of an entire monitor. The technical view Status Data Collector exists as an alternative for this purpose.

In this technical view, you can also manually start the data collection method for any MTE to which a data collection method is assigned. To do this, choose the relevant MTE by double clicking it. This is useful, for example during test phases or for MTEs for which you require the current value, even if it is not yet time for the next start of the method.

Note that when you start a data collection method manually, it runs under your user name and therefore also under your authorizations. As the method runs under the SAPSYS user when it is started automatically, and this user has only very few authorizations, you can assume from a successful test with a manual start that the method will also run without problems during normal operation.

Procedure

To activate the Status Data Collector technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Status Data Collector. The alert tree now no longer displays the alert status and reported values, but information about the data collection methods of the MTEs of the monitor.

Result

The view displays the following information about the data collection methods that are assigned to the individual MTEs of the monitor:

· Assigned data collection method: If the MTE is assigned an active data supplier, the system will display in the corresponding column, as the active data suppliers are not defined in the monitoring architecture

· Type of the data collection method; depending on the definition of the method, the following types are possible:

· Definition status of the method:

· Runtime status of the method:

The time specification after the runtime status shows the time since which the method has been in this status.

· Frequency of the method call in seconds (Cycle):

The color of the nodes is not passed upward in the alert monitoring tree. Monitoring objects and summary nodes therefore always have the color Green.

Use

The individual monitoring tree elements (MTEs) of the Alert Monitor are assigned methods. These methods determine the data collection of the MTEs (data collection methods) and the possible reactions to an alert in the MTE (auto-reaction and analysis methods). You can find out the assigned methods by selecting an MTE and choosing Properties. This method is very time-consuming for obtaining an overview of the assigned methods for the MTEs of an entire monitor. The technical view Method Allocation exists as an alternative for this purpose. This view displays the method assignments for the MTEs of the entire monitor:

· Assigned data collection method: If the MTE is assigned an active data supplier, the system will display in the corresponding column, as the active data suppliers are not defined in the monitoring architecture

· Assigned auto-reaction method

· Assigned analysis method

· The nodes are always colored green in the technical view Method Allocation; as it contains no alert information.

· Summary nodes or monitoring objects can always be assigned methods; these assignments only take effect for the subordinate monitoring attributes, which can inherit their method assignment from the superordinate nodes.

· If no analysis or auto-reaction method is assigned to the MTE, is displayed in the corresponding column here.

Procedure

To activate the Central Method Allocation technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Method Allocation. The alert tree now no longer displays the alert status and reported values, but information about the methods assigned to the MTEs of the monitor.

Use

MTE classes and attribute groups group nodes of the alert monitoring tree by topic and therefore simplify Customizing, as you no longer need to adjust the properties of all affected monitoring tree elements (MTEs), but rather only of the corresponding MTE class or attribute group. You can find out the assigned MTE class and attribute group by selecting an MTE and choosing Properties. This method is very time-consuming for obtaining an overview of the assigned MTE classes and attribute groups of the MTEs of an entire monitor. The technical view Info on MTE exists as an alternative for this purpose. This view displays the following information for the MTEs of the entire monitor:

· MTE class to which the MTE belongs

· Attribute group to which the MTE belongs (for performance, status, and log attributes)

· Short text that is assigned to the MTE class as help (usually activated using the F1 key)

To additionally display the long help text for an MTE, choose the relevant MTE by double clicking it.

· The nodes are always colored green in the technical view Info on MTE; as it contains no alert information.

· If the corresponding general or specific properties of the MTE are not determined by an MTE class or attribute group, but rather individually for this MTE, no class or group is displayed in this view.

Procedure

To activate the Info on MTE technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Info on MTE. The alert tree now no longer displays the alert status and reported values, but information about the MTEs of the monitor.

he Central Performance History of the monitoring architecture allows you to save performance values of the monitoring architecture long-term, and to output these values in reports to compare the current performance data with its earlier development.

The system only collects values for the MTE classes that you have selected for this purpose. You do this by assigning MTE classes to Collection and Reorganization Schemata. These schemata contain information about how long, and in which resolution, performance values should be collected. To obtain an overview of this type of which data is collected in the Central Performance History, you required the collection and reorganization schemata that are assigned to the individual nodes.

The view displays the following information:

· Assigned collection and reorganization schema

· Resolution of the collected performance values

· Collection method (see Collecting and Reorganizing Performance Values)

· Time zone of the data collection (if explicitly specified)

Procedure

To activate the Central Performance History technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Collect./Reorg.Schema Assignment, or choose Display Assignments of the Central Performance History (). The alert tree now no longer displays the alert status and reported values, but the assigned Collection and Performance Schemata.

Threshold values dictate which reported values generate an alert for the node for performance attributes (see Properties of Performance Attributes). To display these threshold values, select the corresponding node and choose Properties. This method is very time-consuming for obtaining an overview of the threshold values for the MTEs of an entire monitor. The technical view Threshold Values exists as an alternative for this purpose. This view displays the following information for the MTEs of the entire monitor:

· Attribute group to which the MTE belongs

· Threshold values of the MTE for which a yellow and a red alert are generated; also the threshold values at which the alert level is lowered again.

· Unit of the reported performance values

· Comparison value that specifies how the value of the performance attribute is calculated from the reported value, such as the last reported value, the average of the last few minutes (smoothing), or the average of the last full quarter hour/hour (average).

· Information, about whether an alert is to be generated when the value of the performance attribute falls below the threshold value or when the value exceeds the threshold value

To additionally display the long help text for an MTE, choose the relevant MTE by double clicking it.

· The nodes are always colored green in the technical view Threshold Values; as it contains no alert information.

· If the properties of the MTE are not specified by the attribute group, but are defined individually for this MTE, the view displays instead of the attribute group.

Procedure

To activate the Threshold Values technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Threshold Values. The alert tree now no longer displays the alert status and reported values, but the threshold values for the MTEs of the monitor.

There are two ways to do that
1) Turn the audit log on by using SM19 and SM20 and analyze the audit logs.Put filters while setting up these logs so that you can see the specific data.

2) In ST03N / ST03, you can analyze the transactions run by users by selecting the "User Profile" under the "Analysis Views" section.

Note: ST03N keeps limited data

I want to get a list of all transactions used per user in a specific time period. Basically I’m looking for a list of all users logged in SAP and the details of the tcodes they used. Is there any standard report or tcode available to view this info?

EXPERT RESPONSE

There is no standard transaction. The information is available for configurable time periods using transaction ST05N but it is not organized to readily provide a report of users and transactions. Also the information available summarizes a user’s use of a transaction. There will be one entry (with count data) per user per time period. Daily, weekly and monthly summaries can be created and they are stored for configurable durations.
The information is summarized into a cluster table called MONI based on the STAT files that are written in the file system and regularly refreshed. MONI cannot be queried via SE16 etc., but SAP delivers a number of function modules that retrieve data from these tables.

It is also possible to configure audit logging via SM19 and read the log files via SM20. This will provide more detail but it also introduces new file management issues and requires a change to system settings.

To view locked users in sap

1) Call transaction su10
Click on authorization data and scroll down
check the locked users only field as shown in figure and execute (F8).

2) Call transaction sa38 and run the program RSUSR006 . You will get a list of locked users.
3) Goto transaction ewz5 you will get users with locked status
4) Run report EWULKUSR in transaction sa38 to get the list.
5) Call transaction SUIM , goto
a) authorizations > User > User by complex search criteria >List of User Master
Records Locked Due to Incorrect Logon
or
b) user > unsuccessful logons
6) Call transaction S_BCE_68001402

To view locked users in sap

1) Call transaction su10
Click on authorization data and scroll down
check the locked users only field as shown in figure and execute (F8).

2) Call transaction sa38 and run the program RSUSR006 . You will get a list of locked users.
3) Goto transaction ewz5 you will get users with locked status
4) Run report EWULKUSR in transaction sa38 to get the list.
5) Call transaction SUIM , goto
a) authorizations > User > User by complex search criteria >List of User Master
Records Locked Due to Incorrect Logon
or
b) user > unsuccessful logons
6) Call transaction S_BCE_68001402

Goto transaction se11 or se16 and view the table TSTC, the field is CINFO. Enter "A0" as the "HEX01 data element for SYST" starting value and "A9" as the ending value. Instead of doing such cumbersome viewing of table, you can run ABAP report rsauditc to view locked transactions. Use t-code sm01 to lock/unlock the codes