Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 

Firstly, my sincere thanks to my valuable customer and my supervisor, for trusting me and letting me to experiment on their systems.

Without their encouragement and support, this blog would not have been possible.

IMPORTANT: The methods used here are not supported by SAP. However, they are not very complex to understand and execute.


The BDLS run takes more than 20 hours in our quality systems post system refresh.

Our system details:-

Database size

2 TB

SAP version

ECC 6.0  patch level 21

Database Version


OS Version

RHEL 5.6

No. of Clients to run BDLS

Two (450 & 500)

The objective of this blog is to analyze and find out if there are faster ways to perform BDLS operation, if we cross boundaries of SAP standard methods.

Step - 1

Based on SAP Note. 1547980 we decided to use older version of BDLS program RBDLS2LS as it has capacity to run in parallel.

We were thinking that the program RBDLS2LS itself has some inbuilt capability to run in parallel.

We were expecting it to use some RFC groups like parallel_generators, etc and submit conversion for each table in seperate task/ process like client copy.

Whereas we found out that this is not the case. The RBDLS2LS does not do anything in parallel, neither does it use use any RFC groups not it uses more than one BGD/ DIA processes.

Parallel in this case means that multilpe executions of the report RBDLS2LS is possible. The report do not come back complaining with an error that there is already a running BDLS process like the new BDLS tcode.

Based on the tips from blog , we decided to run multiple jobs.

We increased number of background processes to 26.

Database was put in noarchivelog mode.

No tables were excluded from BDLS.

In client 450 > SE38 > RBDLS2LS > Generated RBDLS450

Again SE38 > RBDLS450 > Filled details as below > Executed in Background

Continued like this for B*, C*,D*...and so on till ...Z* and finally by excluding A* to Z*.

We also started execution on client 500 similarly in parallel.


BDLS completed in 11 hours


We were able to find the jobs & tables taking longer  times.

For examples; Jobs converting tables C*, E*, M*, V* and S* took more times than others.

It was time consuming to schedule 26 jobs per client

Step - 2

Taking help from an ABAPer, we could automate a BDC session to run report RBDLS450 with A*, B*, C*...Z* as inputs to selection screen.

In the next part of this blog we will dive more deeper.

Labels in this area