Use Event-Oriented Reporting to Automatically Send Information or Trigger an Action

  • by Deepankar Maitra, Senior Manager, Accenture
  • September 15, 2002
Use these techniques to automatically send alerts or perform tasks such as listing projects that exceeded budget.

Most R/3 standard reports are time-based. They show you the status of a financial object over time — the revenue variance from budget at the end of May, or the cumulative indirect expenses up to the end of June, for example. In some cases, however, event-oriented reporting is a more useful option, particularly for monitoring and controlling cost and assuring smooth performance by a business model.

Potential event-reporting requirements for a business might be:

  • List all materials that were received late or by their due date.
  • List all projects that exceeded budget.
  • List all activities that did not complete by their early finish date.

Although the requirements are simple, the translation to the SAP world can be complex. For example, how do you determine that an activity is not finished by its due date? Would you check the forecast hours, if actual hours are confirmed after the early finish date, the percentage of work completed, or all of the above?

Deepankar Maitra

Deepankar Maitra has more than 25 years of consulting experience specializing in SAP-based solutions for human resources, supply chain, and reporting in multi-national companies around the world. He has successfully directed large implementation projects as solution architect, delivery manager, global lead, and country lead. His expertise lies in pragmatic harmonization of data and synthesis of processes using tools that improve process execution through quantum leaps in productivity.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.