(SP36) Activation of Data

DSO Request Activation

Activation of request in Data Store object with Writer consists of 3 steps:

1. Pre-Process phase – in this phase, new records from a locked period are selected from the updated table for the currently activated request. Here The Maximum number of locked records that can be updated using NLS Writer, is set by using the settings parameter 'WRITER_ODSO_MAX_RECORDS'. This process uses OutBoard indexes to find the data within the OutBoard archive matching the same key as new data. Afterward, the process moves all needed data from the archive into an active table of the DataStore object. When all records to be activated are found and correctly reloaded, the process will suppress the check for locked data so the activation can start.
2. Standard SAP Activation – Standard activation process used by Data Store Object
3. Post-Process phase – After successful activation of the data, the process will take the locked data from an active table of affected DSO and move this into the archive. There are three possibilities for how the records are handled in this phase:
   1. Update – in case the records already existed and were changed by activation, post-processing will find the existing records in the archive and modify them with new ones from the active table.
   2. Insert – in case these records are new, there is nothing to update and a new package will be created within the archiving requests for these records. There is a restriction for the size of the package in settings, which describes the maximum number of records for the package. In case this size is reached, another package is created for the rest of the data.
   3. Delete – in the case of the BW Delta Process: Update Mode (0RECORDMODE) is set to 'R' or 'D'; records are deleted during the activation process. In the Post-Process phase the keys of the deleted records stored, so the process also deletes the records from the NLS archive. During this phase, an internal table is used as a buffering table for storing the updated packages that should be moved back to the archive. If the number of updated packages, stored in the internal table, reaches the maximum number of packages (parameter 'WRITER_MAX_BUFFERED_PACKAGES'), the packages are stored in a generated database table. This table is then deleted after the data is successfully updated in the archive.

Note: If an issue with authorization occurs, you'll be informed about it in the displayed message. We recommend checking transactions SM37 and SLG1, where will be further information about how to solve the problem. One of the known issues is the case of a loaded request, that couldn't be activated.

DSO Request Deletion

Follows a similar process to DSO Request Activation. However, it differs during the pre-processing phase because the locked records are selected from the ChangeLog table.
SPO with DSO activation
On the HANA database, do not process activation in parallel, but rather do it sequentially to preserve data consistency!
Reloading of archived Data
When the Writer moves archived data in an InfoCube and activated data in DataStore Object into the NLS archive, this data will be read or reloaded. SAP information generated from the moving of data, like the number of packages, the number of records in package and request, etc. are rebuilt. So in general the reloading of archiving requests is the same with or without Writer, as the data is available. The user just needs to go to the archiving tab of InfoProvider in transaction RSA1 and then reload requests.
Writer has automatic reload functionality, too. At the beginning of a DTP load to cube / DSO activation, empty archiving requests are reloaded.