Entering content frame

Background documentation Questions and Answers Locate the document in its SAP Library structure

What are the benefits of loading requests in parallel?

Several requests can be updated more quickly in the DataStore object.

Can requests be loaded and activated independently of one another?

Yes. You need to create a process chain that starts the activation process once the loading process is complete. See also Structure linkIncluding DataStore Objects in Process Chains.

Are there a maximum number of records that can be activated simultaneously?

No.

Can the loading method that is used to load the data into the DataStore object be changed from a full update to a delta update?

No. Once a full update has been used to load data into the DataStore object, you are no longer able to change the loading method for this particular DataSource/source system combination. One exception to this is updating a DataStore object to another (not yet filled) DataStore object if InfoProviders already exist that have been supplied with deltas from the DataStore object. In this case you can run a full upload, which is handled like an init, into the empty DataStore object and then load deltas on top of that. For more information, see the last section of Structure linkUpdating DataStore Object Data.

Why is it, that after several data loads, the change log is larger than the table of active data?

The change log grows in proportion to the table of active data, because before and after-images of each new request are stored there. See also the Structure linkExample of Updating Data to a DataStore Object and the description of the Structure linkDelta Process

Can data be deleted from the change log once the data has been activated?

If a delta initialization for updates to connected InfoProviders is available, requests have to be posted first before the corresponding data can be deleted from the change log. In the administration screen for the DataStore object, you use the Structure linkdelete change log data  function. You can schedule this process to run periodically.

However, you cannot immediately delete the data that you just activated, because you can only specify Older Than 1 Day as the most recent deletion selection.

Are locks set when you delete data from the DataStore object to prevent data being written simultaneously?

See Structure linkFunctional Constraints of Processes.

When is it useful to delete data from the DataStore object?

There are three options available for deleting data from the DataStore object: by request, selectively, and from the change log. In order to determine the best option, read the Structure linkdetailed description for deleting data from DataStore objects.

What do you use the DataStore Object for direct update for?

To load data quickly (without using the extraction and load processes in the BI system). See DataStore Object for Direct Update.

 

Leaving content frame