Skip to Content

One of the most annoying activities in SAP BI/BW systems is connected with Process Chains Monitoring: how much time do you spend each day to check if everything has gone fine? Typically, every morning, somebody has to control all Process Chains executions occurred during night. And what about if the system itself called you to say: “hey guy, something didn’t work with the Process Chain XYZ” with an e-mail? That’s why we say “start Passive Monitoring”.

There are two main ways to gather the result: the first one is to use transaction RSPCM – “Monitor Daily process Chain” to put the relevant Process Chains under control. If a Process Chain will fail you will be alerted with a message (e.g. via e-mail): how many times did you use it? To tell the truth, in my experience, introducing this transaction is like discovering the wheel!

There’s another solution, even simpler, that provides answers to other questions as: “how can I be sure that the Process Chain has completed successfully?”.
You must simply define two messages at the end of the Process Chain:

 

  1. Successful termination
  2. Bad termination

I think the traffic light colour is clear to everybody …
When I open up my PC one of these two messages has to be in the Inbox folder: either the first or the second. If none of these is there I get worried about … Consider also the benefit of informing, at the same, automatically, the information consumer that data are ready and updated, your End-User!

I know there are other solutions, as creating an ALERTs, but sometimes such innovations seems to be too expensive in terms of learning. In most cases who cares of CCMS doesn’t know what has to be done in case of bad termination.

According to me KISS principle (Keep It Simple and Small), sometimes can really help. “Passive Monitoring” can be a starting point to introduce further Monitoring options, is cheap (requires only SCOT configuration) and gets in touch with you with your e-mail address: I think that most of you will check you e-mail accounts even more than ten times a day!

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Witalij Rudnicki
    Hi Gianfranco,

    You raised an importnat topic – Process Chains are in the heartbeat of the BW and while there are some features available (like you described) I think there is much more SAP can do for us to make both development and monitoring a much easier task.

    Regards,
    -Vitaliy

    (0) 
  2. Dirk Herzog
    You’ve mentioned a great point. At one of our customers each morning starts with about twenty messages in the inbox saying “Process chain name – successful/with errors”. I’m still figuring out how you can send a message if a special chain hasn’t finished at let’s say 6 a.m. I’m sure that it is quite easy with the new process chain types introduced with NW 7.0 BI. Just need to find the time to do it.

    Best regards
    Dirk

    (0) 
  3. Yann-Rudolf Michel
    Hi,
    big point. When I first discovered the RSPCM I could hardly understand thst this transation was not worth  a word in the courses I took.
    Meanwhile, my first look in the morning is the RSPCM besides the check of the error e-mails.
    Cheers,
    Yann
    (0) 
  4. Ian Worley
    We took this monitoring a step further at my previous company, with an ABAP job checking a table for certain process chain statuses at a set time each morning and then emailing the results.  It meant that just looking at the one email was easier on the eye.

    I seem to remember the function RSPC_API_CHAIN_GET_STATUS being involved.

    (0) 

Leave a Reply