How to Improve the Performance of activating DSO data

 

Some system performance bottlenecks may occur during DSO data activation. The following are some practical tips for improving the activation speed:

-If the system table for processing background jobs is too large, the performance of the entire background job will be reduced. DSO data activation is performed through background jobs, which will inevitably reduce the processing speed. Therefore, as the first step, ask the basis technicians to check the background operating system, whether too many unnecessary background jobs are scheduled to occupy too much resources (rsbtcdel2, sm65, and so on are used to clean the background job system. Consult basis technical personnel ).

-Make sure that all DSO-related tables in the database have the latest statistics, so that reading and updating the database can have better performance.

-If your application does not directly generate a report on this DSO, do not select to generate a Sid when activating data.
This will greatly reduce the time required for data activation. Generally, in some background job logs with data activation, we can see that a large amount of time is spent on running the background job bibctl _ * (the program is rsbatch_execute_prozess. Rsbatch_execute_process is used to generate Sid. If you do not directly query the data in this DSO output report, you can remove the "generate Sid (SID generation upon activation)" option in the DSO maintenance interface. You can find this option in the Settings section on the DSO maintenance interface ..

-Adjusting relevant parameters in the transaction code rsodso_settings can help improve activation performance. You can adjust the global parameters that affect all DSO, or the parameters for a specific DSO.

For more information about parameters, see sap note 1118205-rsodso_settings maintain runtime parameter of DSO.

 

Source Document