Skip to Content
Technical Articles

Use Event based schedules in BOBJ

Introduction:

There are reports which are scheduled based on  time (triggered at a particular time)  . The issue with such  time based reports  is that , if the underlying tables are not refreshed or still loading, the reports that are generated will have incomplete data. In such instances, the report has to be refreshed again to view the complete data.

Also if the tables are refreshed earlier than the report schedule timings , users will have to wait till the report is triggered and refreshed.

 

Sample scenario:
Table load Finish time  Report scheduled time Remarks
    6:35 PM    6:00 PM Report will have incomplete data and needs to be retriggered again
    5:30 PM    6:00 PM Users need to wait till the report is triggered at 6:00PM though , table load is completed at 5:30 PM

 

To resolve the above issues, we need to create File based event schedules instead of time based schedules. File-based events wait for a particular file (the trigger) to appear before the event occurs.

Before scheduling a report that waits for a file-based event to occur, you must first create the file-based event in the Events management area of the CMC. Then, you can schedule the Report and select this event.

File-based events are monitored by the Event Server. When the file that you specify appears, the Event Server triggers the event. CMC then releases any schedule requests that depend on the event

 

Step By Step Implementation:

  1. Create a Trigger file at the database server (Oracle, SQL server etc.) which will be generated on completion of the Table load.
  2. This trigger file needs to be configured to be sent to the Business Objects Server at a particular location .for example, C:\<folder>\<FileName>, or /home/<folder>/<FileName>).

 

In Business Objects CMC tool, create an File based Event

  1. Navigate to the Events management area of CMC.
  2. Open the System Events folder.
  3. Click Manage > New> New Event
  4. Under Type list, select File.
  5. Provide a name for the event in the Event Name box.
  6. Provide  description in the Description box.
  7. Under the Server list, select the event server that will look for the specified file
  8. Enter a file name in the Filename box.
    Enter the absolute path to the file that the event server should look for (for example, C:\<folder>\<FileName>, or /home/<folder>/<FileName>). The directory should be on a local drive.
  9. To enable alerting for the event, select Alerting Enabled, and enter a message in the Alert Message box.
    When the event is triggered, this message will be included in the alert notification that is sent.
  10. Click OK.

After the Event is created , you can view them under Events section in CMC.

Date modified defines the time at which the Trigger file was received at BO.

In the report schedule, select the respective File Event that the report needs to be depend on .

 

After the schedule is created, the report will be triggered after the file based event is updated based on the trigger file sent to BO server from DB server and the remaining schedule conditions are met.

 

Conclusion

With above steps, you should be able to optimize the scheduling of Reports by saving time and avoid the manual effort of rescheduling.

 

Reference:

https://help.sap.com/viewer/2710d05c6f7f452baddb4ca72b72fdc2/4.2.5/en-US/46f385b76e041014910aba7db0e91070.html

 

4 Comments
You must be Logged on to comment or reply to a post.
  • Some additional information about file events:

    1. The event looks for a specific file in a specific location.
    2. The file must be deleted at some point because the event triggers when the file appears after having been absent for at least one cycle of the Event Server.
    3. The event DOES NOT look at:
      1. Timestamp on the file.
      2. Contents of the file.

    My clients who use file events usually do one of two things to make this work:

    1. Run a .bat file on a Windows schedule to delete all of the event files at midnight or another specified time.

    OR

    2. Have steps in the ETL process to delete one or more event files at the beginning of the process and re-create it/them at the end of the ETL process.

    -Dell