Hello Sleep,
The parameter for foreground has already been mentioned so I wont dwell on it.
Frankly is not advisable to change profile parameter for a custom report. I have seen custom reports with dumbest pieces of coding which result in time out errors/abap heap memory overflow errors etc. Alternatively some time the data being seletcted is so huge that SAP will give time out dump.
So whole point is that changing value of this parameter makes sense if standard SAP is dumping not for custom reports. I would never change profile parameters for custom reports neither would SAP really advise you that on first go. Even in case of standard SAP you should first review the amount of data that is being selected and try to cut it down. If that is not possible then use background processing. If nothing works go to SAP and check with them why is it behaving in that way. Only as a last resort change your profile parameters.
I would recommend following approaches:
1. First of all get the code reviewed. Make use of SE30 for this. Try to weed out performance bottlenecks. In case of certain tables SAP recommends using function modules instead of direct selects. Check if introducing secondary indexes in the tables involves can help you.
2. Check the amount of data that is being selected in one run. If it is huge try to reduce it and then do foreground processing.
3. However if data volume has to be retained then go for background processing.
I hope this approach will be somewhat useful to you.
Message was edited by:
Ruchit Khushu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.