Ask the BW Expert: Event Chains vs. Subsequent Processing Functionality

  • by Ned Falk, Senior Education Consultant, SAP
  • September 1, 2003
Confusing BW event chains with their subsequent processing functionality is a common mistake. The author explains the differences and shows how SAP has replaced event chains with process chains in BW 3.x.

Dear BW Expert;

Does BW 2.x have a report that lists all event chains with job names, InfoObject names, dependent jobs, and so on from the beginning to end (meaning the full data-load details)?

I think you might have confused “event chains” with “subsequent processing functionality” (what I call chains of events) — a common mistake. Subsequent processing functionality is created by linking the success or failure of a BW administration task with the triggering of an event. You set the event to trigger using the Subsequent Processing button on the leading BW administration task. Another BW administration task is waiting for the trigger, and it executes when it “sees” the triggered event. For example:

Ned Falk

Ned Falk is a senior education consultant at SAP. In prior positions, he implemented many ERP solutions, including SAP R/3. While at SAP, he initially focused on logistics. Now he focuses on SAP HANA, SAP BW (formerly SAP NetWeaver BW), SAP CRM, and the integration of SAP BW and SAP BusinessObjects tools. You can meet him in person when he teaches SAP HANA, SAP BW, or SAP CRM classes from the Atlanta SAP office, or in a virtual training class over the web. If you need an SAP education plan for SAP HANA, SAP BW, BusinessObjects, or SAP CRM, you may contact Ned via email.

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.