Subsequent Processing 

Use

With particular BW processes, you can trigger an event using subsequent processing following the successful or incorrect work down of an event.  The following processes are supported:

·        Load data

·        Compressing data

·        Aggregating data

·        Deleting requests

·        Reconstructing InfoCubes

·        Structuring statistics for an InfoCube

·        Structuring an index for an InfoCube

·        Deleting indexes

·        Selective deletion of data

·        Activation of ODS data

You can start subsequent processes on the basis of this kind of event. After the event has been activated, background controlling starts all processes that are waiting for this event. Use the Selections pushbutton in the maintenance dialogs in the supported processes to determine whether a (successor) process should react to an event that was determined in the subsequent processing of a predecessor process.

Prerequisites

You must have already created the events that you want to use for controlling processes using Tools → CCMS → Jobs → Maintain event.

Functions

In the subsequent processing for a process, you determine whether an event is triggered following this process. Here you determine which successful or unsuccessful event is to be triggered if the process has been completed successfully or incorrectly. You can schedule processes that are to be triggered dependent on a completed process in the background in the current maintenance dialog, waiting for such an event.

Besides triggering an event, you also have an additional option in the scheduler for subsequent processing. A user exit in the form of a Business Add-In is also available to you. You fill it with user coding.

Note when loading into an ODS object and for the subsequent, event-controlled update:

If you switched on the automatic activation in the ODS maintenance or administration, the monitor status for the request remains yellow after the load was successfully completed. Nevertheless, the subsequent processing for the InfoPackage is started, because the loading process is successfully completed.

If you want to update the data from the ODS object and want to trigger this using an event, use the Subsequent Processing when activating data in the ODS. In the InfoProvider tree for the ODS object, choose the context menu entry Activate ODS Object Data. From the following screen, choose Subsequent Processing. In the following screen, specify the event that needs to be executed after the activation process. This procedure is required, since the data has to actively exist for updating in the ODS object.

You can find additional information under Update ODS Object.

In BW 3.0, automatic process control has been enhanced and improved significantly with the concept of process chains.  Process control using post-processing events and event collectors is not functionally enhanced but it is still supported. We recommend that you only use process chains for schedules of connected processes that must be re-defined.