Skip to main content

How To Monitor Your Background Jobs With CCMS In SAP Systems


The Limitations Of This CCMS Monitoring Solution

I mentioned monitoring several jobs, but there are limits to the solution I’m going to show you. My own experiments have showed that trying to monitor more than 100 jobs is not a good idea I will not work very well. You see, the major problem is that the Internal Dispatcher has toloop through many tasks including the job monitoring task within a 5 minute time period. So as long as your list of jobs is not too long and the loop can be achieved with the 5 minute time limit this solution should work just fine.

Initial Configuration

First of all, we need to select a job to be monitored and I’m not talking about a single report. Pick a real batch job; one that may contain several reports.
For this example I will first call the transaction SE16 (You may know this one, don’t you?), and in the table name field, just type ALBTCMON. See screen below:
SE16 Data Browser - Table ALBTCMON
Next, press the “F5” key, or click on the Create Entries button. The system will pop up a warning informing you the table you are trying to add entries to is a Cross Client table:
:
SAP Cross Client Warning
This is completely normal, nothing to be scared of. Press the green tick button to confirm and proceed. You will then be presented with the following screen (Or something similar as mine already has entries filled in).
SAP Table View For Batch Monitoring
Click the New Entries Button and the following screen will appear:
SAP New Entries Table View For Batch Monitoring
I won’t go through the whole list of possible parameters as a full list of possible entries would require a full article in itself. But I will mention the 3 main ones:
  • System Group: This option allows you to group your alerts by system name by adding a system group entry.
  • Job Name: Enter the name of the job that we want to monitor. Please take note that you can use a pattern here (Wild cards etc…) and if many jobs are to be monitored with similar names it’s much more efficient to use a pattern. It can also allow you to exceed the 100 jobs limit!
  • MTE class: This is the monitoring class which to be created and associated with your alerts. If you are to assign an auto reaction method to your alerts I would strongly recommend you to use this to group your jobs per functional areas.
Once you have entered you records, press the save button. You will be prompted for a transport number to enable you to transport you configuration into another system if required. However, from past experience I have noticed this type of activity is usually done directly in the desired system as many job names can change between development, quality assurance and production environments.
Anyway, now we are ready to go to the next step.

Job Monitoring Activation

Here I will activate what is called the data collection method associated to the job monitoring function. By default, it’s deactivated.
Go to the transaction RZ21, select Method Definitions and choose Display Overview. You will a screen like this:
Transaction RZ21 - Monitoring Properties and Methods
Select the method CCMS_BATCH_MONITORING and choose Edit Data.
As shown in the screen below, switch to the edit mode and then activate the function Execute method immediately after monitoring segment start.
CCMS Batch Job Monitoring Methods
Save your entry and you’re all done….well almost. Here, you have two options, to really activate it, either you restart your system, or you switch your monitoring system to the warm up mode…that’s up to you.
In order to check, that everything is ok, just go to the transaction RZ20 and everything will be visible in the All Monitoring Contexts monitor of the SAP CCMS Technical Expert Monitors monitor set, as displayed in the screenshot below:
RZ20_AllMonContext
By expanding the nodes, you will notice there different monitoring points available:
  • Status
  • Log of Current Job
  • Runtime
  • Delay
  • Delay + Runtime
Those are the possible alerts for your newly monitored jobs. They should cover most of your needs regarding the monitoring of your jobs.

Conclusion

As we saw, it’s quite simple to put in place a simple monitoring system for your jobs, failures won’t be left unnoticed. We didn’t cover the automatic delivery of an email in this article, but this is something which can be done quite easily for somebody who knows how to assign an auto reaction method to the MTE we just created.

Comments

Post a Comment

Popular posts from this blog

Step by Step guide on BADI with Filter implementation

Step 1 à Before implementing filter objects to a BADI. We need to deactivate all the implementation for that BADI. Go to SE18 (BADI definition) and from there navigate to all BADI implementation to view all the active implementations for that BADI Select the BADI implementations listed on the screen and deactivate the implementation. Once done, return back to the initial screen of SE18 and proceed with next step. Step 2 à go to SE18 – BADI Definition screen and change the existing BADI definition that we created in the earlier tutorial.   Select the FILTER –DEPENDENT check box under the TYPE section. This will open up the FILTER TYPE field for inputs. And do an F1 on the FILTER TYPE field. Click on the F4 on the FILTER TYPE field name and enter some search criteria to find a relevant data element. And click on the continue button   Select the data element from the list to set up your filter and hit enter. Click on the save butto...
1 comment
Read more

Create Data Source in SAP

Data Sources are extraction structure. Data Sources are used to extract data from various source system. In the below steps, we will see how to create a data source using a SAP table VBAK. 1) Execute transaction RSO2 2) Enter data source name to be created 3) Press Create 4) Enter description of the data source 5) Enter the name of table or view on which data source has to be created. Data Source can also be created using a View, Info set or a Function Module. 6) Save the data source 7) Execute RSO2 again and click Change 8) Select VBELN field as selection 9) Save the Data Source 11) To check whether data is getting extracted, execute transaction RSA3 12) Enter the name of data source as shown below and press 'Extraction' 13) An information message will appear stating no. of records fetched 14) Additional button 'Display list' will appear, press button 15) Select one of the data packet and double click to get records fetched 16) Data Source is ready to be used!
4 comments
Read more

Introduction to SAP Hierarchies

Definition A hierarchy is a method of displaying a characteristic structured and groupedaccording to individual evaluation criteria.A BW hierarchy has the following properties: Hierarchies are created for basic characteristics (characteristics containing master data).The characteristic 0COSTCENTER is an example. Hierarchies are stored in master data tables. They are also similar to master data, and can therefore be used and modified in all InfoCubes. You can define several hierarchies for a single characteristic. A hierarchy can have a maximum of 98 levels. You can load hierarchies from the R/3 system, or from a flat file. You can also create andchange hierarchies manually in the BW system. Use: Hierarchies are used in two main ways: 1. Firstly, the structured display of characteristic values (tree display) in a presentation hierarchy. 2.Secondly, selecting a defined quantity of characteristic values as a selection of hierarchy nodes. Structure A hierarchy consists of nodes. A node can...
Post a Comment
Read more