Skip to Content

Now we understand the structure of the Auditing DB we can start to use the data. SAP Business Objects supplies a sample universe and some sample reports based on this universe. We won’t be using these samples as they were designed to answer specific questions and so are over complex for this discussion.

 

With the knowledge we have of the schema we can quickly build a universe. I have attached an example universe. Using this we can build some queries to understand the audit data. This isn’t a blog on either universe design, or report building techniques, so there will be nothing too complex covered, only a couple of simple examples in this post. If you want to use the universe you will need to ensure that it is connected to your audit DB and that you have refreshed the structure to ensure it is mapping correctly to your tables.

Click here for the sample universe.

Using this universe you should be able to quickly see how the data is structured and the events are generated. A simple query for example can list all the logons to the system.

Simple Query 1

A little formatting will give us the events and their details.

Simple report

Another example will return my top users based on the number of times they have logged into my system.

 

Simple Query 2

 

Simple report 2 

 

You should be able to use this universe to understand the audit data and to produce some useful reports. Suggestions for enhancements or feedback are always welcome.

To report this post you need to login first.

2 Comments

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

  1. Alexander Schuchman
    Is there much of a resource utilization created by enabling the auditing functionality?
    We currently have this disabled in our production system and I’m curious to know if I should expect any performance impact to my user community be enabling this addition event writing to the DB.
    -alex
    (0) 
    1. Adrian Westmoreland Post author
      Alexander,

      This is a difficult question to give a good answer to. There will be a performance impact as the CMS will have to process the audit data from the auditees and submit it to the audit database. Will this have any (noticeable) impact on your production deployment? That depends on many factors such as how many auditing events your are capturing, how ‘busy’ you system is and how close to maximum utilization your system is. Generally there should not be a significant impact.
      I will be posting some tips on auditing performance in a future post.

      (0) 

Leave a Reply