Activation of Data in DataStore Objects 

Use

Upon activation, data is written from the activation queue to the table of active data.

Features

The SIDs are determined before the process of activating the data starts. The process of activating the data only begins after the SIDs have been determined.

If the activation process terminates while the SIDs are being determined, the data remains inactive and stays in the activation queue.

When the data is activated, it is written directly to the table for active data, where it is made available for reporting purposes. Requests are then sorted by the key of the DataStore object/ the request ID/ the data package ID/ the data record number. This ensures that the data is updated in the correct request sequence in the table for active data. During an activation session, packages (from several PSA requests) are created that can be activated in parallel. There cannot be more than one activation session running at any one time. Instead, when one activation sessions ends, the next one in the sequence must be triggered. This is, however, only relevant when data is activated automatically. When you activate data manually, the pushbutton that you use to trigger the process disappears from the toolbar and is available again only after the current activation run is completed.

The following options are available:

·        Do not compress requests into a single request when activation takes place.

If you set this indicator, when the activation is complete a request is displayed in the change log for each of the requests that have been loaded. This means you can delete requests again on an individual basis in order to return to a previous status of the DataStore object. However, when you update into a further data target, all requests that are active but have not yet been updated are combined into one single request.

If you want to update requests into connected InfoProviders on an individual basis, you have to update requests immediately after you have activated them. You can do this using process chains.

If you do not set this indicator all the requests activated in this process are compressed into one change log request. Only this request can be rolled back in its entirety from the DataStore object.

·        Process requests in series in a batch process during activation:

If you set this indicator, the data is activated in series in an extracting background process. Otherwise, the data is activated in parallel in separate dialog processes.

If an activation process is canceled, you are also unable to activate any subsequent requests. You have to keep repeating the activation process that was canceled until it is completed successfully.

Activities

From the context menu choose DataStore Object ® Activate DataStore Object Data or click on the  Activate DataStore Data icon on the Requests tab in the administration screen. The inactive requests are displayed so that you can activate them. Only requests that have been activated can be updated in additional data targets.