Showing results for 
Search instead for 
Did you mean: 

Data Activation in DSO takes a Long time

Former Member
0 Kudos

Hey Guys,

I have a Standard DSO and it has data in the "New Data" Table.

Now, i activate it and Start the activation, the job is scheduled.

Then i click on "Jobs" button to see the status.

But, the job status is yellow for a long time and doesnt turn green!

How to make it faster?

P.S., In my DSO, "SID generation upon activation" option is also not checked.

Thanks in advance !

Accepted Solutions (1)

Accepted Solutions (1)

Active Participant
0 Kudos


Check the following links for optimizing the DSO activation performance.



If the DSO is huge or very old then you can think about doing some maintenance on the change log table of the

DSO. This process basically involves deleting the unwanted or very old data from change log table. So if data is old and you don't expect that to change(very old historic data) you can delete it. Once the change log size is reduced , activation will run pretty fast as checking time of Change log will go down. Usually a retention period of 90 days is good enough but may vary from scenario to scenario and you can also automate this process via process chain. Also you can perform some cleanup in the PSA table table also.

Also it may not be relevant to you now but if you wanted faster access to data then perhaps you can use a Write Optimized DSO. It has only one table which is active Table where in explicitly the activation of DSO is not required.

I hope this information was helpful to you.

Best Regards,

Kush Kashyap

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Shiva,

The first thing is how much data you have in New table(activation queue).

generally DSO activation will happen in child jobs.

When you start DSO activation one main job with name DSOA* will get create. this job will again trigger the child jobs, these are called BIBTCL jobs.

you can always check the job log in SM37.

these child job parameters we can maintain in RSBATCH or RSDSO_SETTINGS.

generally this will be 6, if you think you will get more data and you need more jobs you can increase it. But before you increase it make sure you will have enough background jobs in system.

check below article



Former Member
0 Kudos

Guys.....Thanks for u r answers, which really helped !

Former Member
0 Kudos


Based on your data volume this will take time .... But please check in the settings of DSO whether you have selected 'Set Quality Status Ok Automatically'..




Former Member
0 Kudos

SAP knows this is a big bottleneck. They say that 7.3 is a little better. And that eventually with HANA it will be speedy but until that point it's still going to take a long time. Basically it takes each row from the new table, sees whether it exists in the Active table and then updates the active table if different and enters 2 rows in the change log.

Here are my couple comments.

1) You can play around with Activating in Parallel.

2) Might not possible for you but figuring out some way to do some sort of delta/partial full. (If you're already doing delta then this won't help). Fewer records will help.