ABAP RUNTIME ERROR WHILE RUNNING BSEG REPORTS

[Former Member]

hi Exports

I've developed one report using bseg (G/L Account Balance) report but following error occured while giving some G/L account no. bbos those GL account contains lot of records in bseg? how can i fine tuning the report both system and program side?

help me

What happened?

The current program had to be terminated because of an

error when installing the R/3 System.

The program had already requested 474181200 bytes from the operating

system with 'malloc' when the operating system reported after a

further memory request that there was no more memory space

available.

What can you do?

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Set the system profile parameters

- abap/heap_area_dia

- abap/heap_area_nondia

to a maximum of 474181200. Then reduce the value by 10.000.000 to be on the

safe side.

Then restart the SAP System.

[Former Member]

Hi,

Try to make a first selection in BKPF reducing the Nb of occurence using BUKRS( Company Code) GJAHR( fiscal year ) and if u can BLART ( doc type ).

Use the result in the BSEG selection using a "For all entries" statement. It should reduce the execution time and resources !

Regards,

Erwan

[Former Member]

hi,

You can fetching excess records so it is oing for a dump.

Regards,

Sailaja.

[andreas_mann3]

Hi,

-if you only want to display balances use table glt0.

-for accounts with open item administr. use tables bsas/bsis

-for other accounts use bkpf (fill key and index-fields bukrs , gjahr, blart, budat) and than bseg with bkpf-

bukrs, belnr and gjahr.

A.

[Former Member]

Hi,

use bkpf-bukrs = bseg-bukrs

bkpf-belnr = bseg-belnr

bkpf-gjahr = bseg-gjahr.

dump is due to excess recors in internal table.

Regards

amole