Determining Errors and Troubleshooting

PMI monitors business processes over system landscapes and displays errors in the process flow. But what happens if errors occur when the PMI itself is executed?

Error Determination

·        If errors occur in Process Monitoring itself, Messages for Process Monitoring Exist is displayed on the initial screen (process overview) directly below the process title. Selecting the information icon displays the tab page Error Messages together with the error messages of the self-monitoring of the Process Monitoring. The data comes from the corresponding CCMS Monitor.

If messages are no longer relevant to you, you can confirm them immediately. The symbols in the Current Status column show you whether a message is still open, or whether a message has been completed and can be confirmed. Confirming deletes the errors from the display and confirms the corresponding alerts in the CCMS. You can confirm individual alerts by choosing the trash icon in the alert rows. Choosing Confirm Messagesconfirms all alerts.

·        If you have activated logging, you also find messages in the logs of the application log. For more details on this subject, refer to the section Process Monitor Logging.

Troubleshooting

The following list describes the errors that may occur and how you can correct them:

PMI returns no data

There are multiple reasons for why no more data is delivered into the PMI:

·        The administrator has started Process Monitoring. As described in the section How PMI Works, here the following jobs are started in the background:

Ў        For collecting data in local systems

Ў        For transporting data into the central system

Ў        For assembly

As users often have wide-ranging authorizations, it may be the case that, in transaction SM37, one or all of the periodic jobs were terminated by another user. In such a case, no more data is delivered, meaning that processes can no longer be monitored.

Solution: You can correct this problem by deactivating monitoring and then activating it again. All jobs are then rescheduled in the background.

·        Another difficulty is represented by the partly asynchronous flow of processes. Because processes are distributed across many systems, not everything can run synchronously. There is the Central Monitoring System and various local systems in which actions have to be performed: the agents must be activated, for example. Here it can happen that a single server has to be shut down, meaning that it can no longer be reached.

If the transport identifies that a server is inactive, that is, the destination can no longer be reached, it reports this to self-monitoring. You can see error messages from self-monitoring such as this in the settings on the tab page Error Messages.

The data under 'Settings' is locked

If you are unable to edit any administrative data under Settings because the data is locked, this is because the person who changed the data last did not exit the window by choosing Close window. Using this pushbutton unlocks the data. If this mechanism was not in place, multiple users would be able to edit the data simultaneously.

Solution: You must delete the lock manually by using table SSPIPADET in transaction SM12.

Missing authorization for changing data under 'Further Settings'

To be able to change administrative data under Settings, you must have assigned to you an adjusted copy of the role SAP_BC_BASIS_ADMIN. For more information, see the section Authorizations for Process Monitoring.

 Process Monitoring Display and Administration

.