Avoid the SID Generation Error While Activating Data in a DSO

You might run into one of these error messages while activating data in a DataStore object (DSO) either manually or from a process chain:
 “Activation of M records from DataStore object terminated”
 “Resource error. No batch process available. Process terminated”
 “Time limit exceeded. No return of the split processes”
When you create a DSO, the system sets a system ID of SIDs Generation upon Activation by default. It is a check box option in the edit mode settings of the DSO. If this option is checked, the system checks the SID values for all of the characteristics in the DSO. If a SID value for the particular characteristic doesn’t exist, then the system generates the SIDs. So the SIDs Generation upon Activation option helps to improve the performance of the query as the system doesn’t have to generate SIDs at query runtime.



The general understanding is that the error messages in above Figure during activation of a DSO are due to the SIDs Generation upon Activation setting. However, we will show that the error messages are not due to this setting, but rather to incorrect parameterization of the processes to activate requests. This means that several background processes were running simultaneously (i.e., activation of requests in DSO and SID creation), resulting in the termination of the request. If a process chain is used for activation of a DSO, all the above processes still run simultaneously in the background. You can use transaction RZ04 to check how many background processes are available in the system at the time of load.



You can change the runtime parameters for this affected DSO by going to transaction RSODSO_SETTINGS. Note that transaction RSCUSTA2 is obsolete in SAP NetWeaver BI 7.0. In the RSODSO_SETTINGS screen select the DSO in question, Click on the Change button to change the runtime parameter. On the Maintenance of Runtime Param. screen click on the Change Process Params. button under Parameter for Activation as the issue right now is an activation error.

Alternatively, you can get to this screen from the context menu of the DSO by selecting Manage, which is the activation request that failed. Click on the Activate button just as you would to activate a request that is loaded to the activation queue. The Activate Data in DSO … window pops up. Click on the Activate in Parallel button. A pop-up window displays the process type ODSACTIVAT.

Maximum Wait Time for Process is set to 300 seconds by default, but you can increase it to a higher value if you think the system workload will be high. If you choose Dialog process as an option. then SAP recommends that the wait time in SAP NetWeaver BI should be three times higher than in R/3 (SAP Note 1118205). SAP Note 192658 also recommends that you set the maximum runtime for the work process as 3,600 seconds. After you click on the Change Process Params. button, you see the settings window.


Enter the Number of Processes. Under Parallel Processing, select Dialog. Select parallel generators in Server Group for Parallel Dialog Processing and then click on the save icon. You can re-initiate the failed activation again and the data should be activated now without any issues.


After the successful activation of data in the DSO, you can revert back to the normal settings for the DSO if necessary to avoid having too many dialog processes. If the activation of data in the DSO is done through process chains (transaction RSPC), you can access the settings. If many DSOs are failing in activation and the above parameters have to be changed for all of these DSOs, then SAP recommends updating the table RSBATCHPARALLEL directly. However, one should have security access to change the data in the tables directly and the steps we describe are easier to perform for individual DSOs.