How to store output in memory id for performance

[Former Member]

Hi All,

There is a customized report where output is huge and unable to download the output file to PC generated through background job.

Is there any option to store the output file in memory id similar to SAve with ID functionality of SQVI - Query Quick Viewer.

Thanks

Prat

Edited by: prat11 on Jun 16, 2011 5:09 PM

[Former Member]

P,

If the output is that large - I would not consume app server memory to store it. That will impact all users across the enterprise.

Why not save the output to a custom table or even to file on the app server? Then create a foreground program to allow users to read the new dataset (be it a custom table or a file on the server).

[Former Member]

Hi Prat,

You can explore the option of exporting it to DATABASE, instead of memory ID...moreover as you say

unable to download the output file to PC generated through background job

With memory id the data is only available within the session not outside of it.

Go through the below link for more details,

http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3bf8358411d1829f0000e829fbfe/frameset.htm

Regards,

Chen

[Former Member]

Try if you can use ALV extracts. the output will be stored in cluster table and later you can call up the extract and view the output instantaneously. refer function modules REUSE_ALV_EXTRACT*

Regards,

Prabhu

[Former Member]

Hi Prabhu,

Not able to get much info on function modules REUSE_ALV_EXTRACT*. There is one SAP std report BALVEX01 mentioned in many replies but not able to check this as system doesn't have any data.

Can u provide some example.

Thanks

Prat

[Former Member]

Hi Prat,

Run the below reports to generate data that is used by BALVEX01.

SAPBC_DATA_GENERATOR, SFLIGHT_DATA_GEN.

Regards,

Chen

[Former Member]

Hi Prat,

The standard report BALVEX01 has all the steps neccessary for using ALV extracts. may be you can copy the program and use some other table instead of sflight and test it. usage of extracts is quite simple:

1. Include vex01top will give you the selection screen elements needed for extracts

2. REUSE_ALV_EXTRACT_AT_SELSCREEN can be used for validation of the extract fields

3. likewise REUSE_ALV_EXTRACT_AT_F4_P_EX1 is for f4 help on extract fields

4. the major part is REUSE_ALV_EXTRACT_SAVE which saves the data to the extract with the name as mentioned on the selection screen & REUSE_ALV_EXTRACT_LOAD returns the data that is saved in the extract previously.

5. if the user uses the same name for save the old extract data will be over written. but before that system will genrate a warning message.

if you look at the standard report with the brief i think you should be able to get the information you need.

cheers, Prabhu