Applied performance tuning conditions, but no result..!

Question

Hi,
Requirement:
1. Display data from tables like BSEG, BKPF, CSKS etc..,
2. Amount of data , which needs to be display is very huze.
3. Changing of requirement will be happen, only if we agree ABAP can not increase performance more than this.
Result:
1. Bad Performance, perticulerly at BSEG.
2. Some times falling into Memory Over flow issue. Because of number of records pulling from tables are very high.
What I did:
1. I used for all entreis methid.
2. Used availble Indexs in where conditions.
3. Using Clear and Refresh statement where ever neccassary.
4. Applied all performance related options , as of my knowledge.
5. There are syntax, exended check, code inspector errors or warings.
I know this is because of huze data, but as a developer how can reduce the runtime..still...?
---How can solve this problem...?
Is there any way to modify my program acrchitecture to get result...!
Thanks,
Naveen Inuganti.

Answer 1

Hello Naveen,
As i could see from your question, you have tried most of the basic fine tuning methods to improve the performance of the program.
There might still be some things like using binary search's with proper sort criterias, fine tuning a loop processing etc. But that could be suggested only looking at the designed program.
My recommendation is to first recheck the design of the program, verify if any loop processings or search criterias can be fine tuned and make changes accordingly.
If the run time still does not improve, try splitting the selction criteria logically inside the program (as customer might not agree to change the requirement). Once the individual "split" selection data is processed, you can collect all the data for common processings.
For memory issues, use FREE and REFRESH statements to delete all the data which is not required. Sometimes, we keep the internal tables with huge data to be used in later processings. My suggestion is to delete such data once your first steps of processing is completed and select the data again when it is required. We can check if "SELECT..ENDSELECT" can be used which again depends on case to case.
If this is report which displays data based on some criteria from time to time, depending on the various selction criterion being used, you can al alternative solution:
1) Create a database view and each time the program runs and reports the data, store it also in this database view. The view and design of the data base will depend on how the requirement is and teh complexity of the data being shown.
2) Next time when the program runs, only the delta data can be processed from actual database table (BKPF, BSEG, CSKS etc) and teh rest of the data can be fetched from previous processed data.
This might be helpful particularly if the report is working on timestamps.
If it still does not work, due to huge data, the only resort is to run the program in background.
Regards,
Pavan Kolli