Re: Wait for event

Hi Vikram,

your assumption that a parallel execution if the report could be a problem is right. Therefor I would create a global class with instance attributes not static attributes. You then instanziate this class with each execution if the report.

As the LUWs won't help you in the cross system scenario you further need a way to differentiate between the events raised by BW upon finishing of the process. Therefor you need to add some parameter to the event which you can check in the method that updates the attribute. You could, for example, create a guid upon instantiation of your class an pass it along with the events as a parameter. On processing of the event you check if the guid of the current process was given or not and only update the attribute if the correct guid is provided.

One additional thing came to my mind when thinking of your requirement. Instead of wating in a report for different Events and continue with the execution after they occurred, you could simply put all the logic in the event handler methods. Then your report only needs to create the event handler class, invoke the first method and wait until completion.

Christian