Facing Problem during Data Load using BEx connector
I'm Facing problem while loading data from SAP BW using BEx connector when there are more than 500000 Rows.
There is no problem while loading the Query which has less than 500000 Rows but the problem occurs when row number exceeds 500000.
In order to limit the data during loading I'm loading data based on filtering Particular feilds like Month,Place,ProgramName this method is working fine for all Except one Month, Place, ProgramName combination of filter which means that particular combination of filter itself having more than 700000 records.
So I want to reduce the number of Records to be loaded / fetched from SAP BW through BEx connector.
Can Anybody please help in this scenario to limit the Number of Records or Any Alternate solution for this problem.
Yes, this is the best way (that I know of). There are some settings in BW itself where you can increase the 500000 limit, but that would be decision for your SAP basis team (and is you're already at 700000 cells then you risk hitting the new limit soon enough).
Look at looping through days in your query, rather than months. And if you can, try an incremental load (load only the records since your last load).
These should all increase speed and reliability of the loads.
But the things there is not only one place there are more than 15 places and 15 program and 12 months each which means 15 * 15 * 12 = 2700 iterations and If I apply for day wise filtering means It will complex the loading. Already it is taking 10 + hours. So I don't want to increase the loading time by filtering by Date.
That's why I asked is there is any SAP BW query to LIMIT the data load like LOAD only first 400000 records and then loading other set.
Like In SQL we use query for limiting
If you have any alternate solution means please let me know that would be more helpful.
I'm Already doing this only and I'm looking for alternate solution for Loading data from SAP BW other than BEx connector.
Like I'm trying in Composite Provider to load data it is much faster than BEx but QlikSense is not displaying the same Composite Provider Queries in All environments like those Composite providers are visible in EBA,PBA but it is not visible in QBA.