Skip to Content

Monitoring SAP CPS by Redwood jobs with SAP Solution Manager

For the monitoring of SAP CPS by Redwood jobs with SAP Solution Manager there are two options:

Push Monitoring

Push Monitoring allows monitoring of all kinds of jobs, e.g. XBP, JXBP, Business Objects jobs, Job Chains, system jobs, … with the Business Process Monitoring Infrastructure.

For Push Monitoring to work you have to schedule the CPS job from a Job Documentation in Solution Manage with the CPS parameter “Status Notification” (i.e. Callbacks) checked.

The technical reason is that only if the job was scheduled (or modified) from a Job Documentation the CPS jobs gets linked to the Job Documentation (not only the ID of the Job Documentation but also other information like SMSY system name).

In order to be able to schedule CPS jobs from a Job Documentation you have to setup the Business Automation Enabler (BAE) in SAP Solution Manager (see SAP note 1265635 or IMG (transaction SPRO) in SolMan).

If the job was scheduled with flag “status notifications” checked you can continue to activate Job Monitoring with parameter “Source is SAP CPS” (i.e. Callbacks) checked.

You can activate/deactivate a logging of the communication between SAP Solution Manager and SAP CPS by setting parameter CPSCALLBACKMON to value ‘X’/space in table AGS_JOB_CONFIG.

The logging information is stored in tables AGSDBG_CPSCBACK1 (directly after getting called from SAP CPS) and AGSDBG_CPSCBACK2 (after reading additional information from SAP CPS).

Once you see data in table AGSDBG_CPSCBACK1 but not in table
AGSDBG_CPSCBACK2 it can be assumed that you have to assign the BAE
authorization in SAP CPS also to the user that performs the callback (in SAP CPS M33 and higher this is SPA Inbound connector user and for lower releases it is the XBP user) to Solution Manager.

Information about use of Callbacks in Push Monitoring:

In order push job data into SAP Solution Manager SAP CPS has to logon to SolMan. For the logon SAP CPS uses the very same user as for job scheduling: The XBP
user specified on the SAP System object in SAP CPS [Note: there is a
dedicated SAP Inbound Connector object in SAP CPS M33 or higher].

The CPSCOMM user is typically used by SAP CPS to call SAP Solution Manager and Solution Manager also uses user CPSCOMM to call SAP CPS for additional information (in the same callback from SAP CPS).

Let’s make an example what happens SAP CPS calls SolMan with user CPSCOMM:

The Push information is logged in table AGSDBG_CPSCBACK1. However Solution Manager needs additional information about the job (in addition to data provided by the SAP CPS callback). SAP Solution Manager now also calls SAP CPS via the BAE interface with user CPSCOMM to get more data. The extended data set information is logged in table AGSDBG_CPSCBACK2. If user CPSCOMM a) does not exist in SAP CPS or b) user CPSCOMM has not authorization for BAE in SAP CPS the call from Solution Manager to SAP CPS will fail and Job Monitoring is not possible.

How to test user CPSCOMM?

Change user CPSCOMM from Communication to Dialog user. Logon with user CPSCOMM to Solution Manager. Execute test program RSEXTSDL_TEST with transaction SA38 and see if you can read out the systems, queues or even the parameters of a job.

Note that can you access the test program from transaction EXTSDL as well.

If communication with SAP CPS is working and you see all the SAP systems, queues and jobs relevant for monitoring make user  CPSCOMM a communication user again and setup Push Monitoring for an ABAP Job Definitions first and check if you get all the data in the logging tables and if you get alerts.


Pull Monitoring

Pull Monitoring relies on the data collector infrastructure of the Business Process Monitoring (BPMon) and allows monitoring of ABAP jobs in a SAP system.

To setup Pull Monitoring you don’t have to use a Job Documentation instead you can just setup Job Monitoring as ususal, i.e. as always in the BPMon setup session.

In case you want to use Pull Monitoring together with a Job Documentation you first should document the job parameters (SAP job name, report, variant) and the job schedule with a standard SAPAbapRun job definition.
Afterwards you can activate the Business Process Monitoring but make sure that parameter “Source is SAP CPS” (i.e. Callbacks) is unchecked.


Difference between Push/Pull monitoring: Example for Job Chains

Using Push Monitoring CPS will push the status of the Job Chain to SolMan. Consequences:

  • You would get alerts or receive notifications in case the Job Chain has status “Error” (Cancellation Alert).
  • You are not able to monitor a single job of the chain with push monitoring.

With Pull Monitoring you can monitoring all individual ABAP jobs of a job chain. You will get an alert if the ABAP job fails even if the Job Chain continues (or retries) with alternate processing.


Combining Push and Pull Monitoring (for Job Chains):

  • Setup Pull Monitoring to monitor all relevant SAPR3 Job Definitions of the Job Chain
  • Setup Push Monitoring for the Job Chain itself
You must be Logged on to comment or reply to a post.
  • You mentioned that Solution Manager can be used to monitor Business Objects jobs. I’d be interested to read about that. Perhaps a topic for a future blog. 🙂 We have jobs for BO Enterprise and BO Data Servics.


  • Can i setup alerting wherein i can get alert if job is not triggered when it is scheduled to start at certain time and not starting even after 3-4 hours? push or pull,anything, appreciate if i get some pointers..

  • Hi Vaibhav,

    When you configure Job Monitoring, you can use Start Delay within the Alert Configuration area.

    You can also click on the Quick help on the Right-top-corner to read what each one does