SYSTEM_NO_ROLL while exporting report to excel sheet

[Former Member]

Dear Experts,

1. In our Production system, 7.01 version, we are gettign the dump SYSTEM_NO_ROLL with the details:
2. Unable to fulfil request for 1464 bytes of memory space.
3. Termination occurred in the ABAP program "CL_SALV_BS_TT_RESULT_TABLE====CP" -  in "GET_CELL_VALUE".
4. The main program was "ZAR_REVENUE_OPEN_CLOSE_ALL ".
5. The dump occurs for only a particular user .
6. The report is generated with 80,000 line items successfully.But while exporting to excel sheet, it ends up with the dump.
7. For other users it seems to be working fine with different company codes.

Please help...

Regards

Imaan

Message was edited by: imaan shaikh

Message was edited by: imaan shaikh

[Former Member]

This message was moderated.

[Former Member]

we got the same issue in our BW system.....

System was dumping out when we were exporting the report in excel sheet for one year data.

Although it works fine for 6 months data.

Workaround:

Export the report in .csv format and then change it to .xlsx format.

Rajesh

[Former Member]

You are selecting too much data, try reducing the number of rows.

Cheers Michael

[Former Member]

Thank you all of the responses...

Problem is resolved.

The user was trying to extract 1 month data, but on checking the variant, it had 3 months selection criteria !!

Imaan

[former_member4224]

Hi..

usually you have to increase the roll area.

note  353579    SYSTEM_NO_ROLL

Clébio

[Former Member]

Hi,

Please check the limitations of 32 or 64 bit which ever you server is on.

Increase the roll_area, roll_extension, extended meory for dialog  and run the task again...

Thanks,

Subhash.G

[Former Member]

Hi Clebio....

Please be noted: it's happening with one particula SAP ID only.

If we execute this report with selection criteria on another SAP ID, it gets success..

user using latest MS-Excel version10 in his PC...

[Former Member]

Hi subhash

Please be noted: it's happening with one particula SAP ID only.

If we execute this report with selection criteria on another SAP ID, it gets success..

user using latest MS-Excel version10 in his PC...

[Former Member]

Hi,

The memory settings are global to all users , check does the user is going to particluar server where config is low , run the task on the server where the memory config is good .

If possible try to change the user output options to ABAP  and rerun the task.

Inform user to test from other system , just to check if evrything is fine with Excel macros  & security settings in  his Ms-access.

Thanks,

Subhash.G

[Former Member]

Hi,

Use STAD when you have had memory-related short dumps such as SYSTEM_NO_ROLL or TSV_TNEW_PAGE_ALLOC_FAILED or when you have observed Dialog work processes in PRIV status. The statistic records in the time immediately preceding these events may show which programs were consuming too much storage.

It's important to remember that memory problems almost never appear during development or integration testing. Also, ABAP is inherently resistant to memory leaks, since most transactions and requests run discretely and finish fast, so that their resources are quickly freed.

Regards,

Venkata S Pagolu.