Dump in BAPI while fetching data

Former Member — Wed, 21 Jul 2010 04:19:11 GMT

Hi all,

I m getting a short dump (: ' No more storage space available for extending an internal table.') in my vendor trial balance report . The place of short dump is the BAPI which im using to fetch opening balance i.e BAPI_AP_ACC_GETKEYDATEBALANCE.

Please find below the screen shot of the dump.

Kindl suggest the possible solutions.

Short text

No more storage space available for extending an internal table.

What happened?

You attempted to extend an internal table, but the required space was

not available.

Error analysis

The internal table "\FUNCTION-POOL=3008\DATA=XLINEITEMS[]" could not be further

extended. To enable

error handling, the table had to be delete before this log was written.

As a result, the table is displayed further down or, if you branch to

the ABAP Debugger, with 0 rows.

At the time of the termination, the following data was determined for

the relevant internal table:

Memory location: "Session memory"

Row width: 2122

Number of rows: 2757476

Allocated rows: 2757476

Newly requested rows: 4 (in 1 blocks)

How to correct the error

The amount of storage space (in bytes) filled at termination time was:

Roll area...................... 6216720

Extended memory (EM)........... 4005681840

Assigned memory (HEAP)......... 1998959040

Short area..................... " "

Paging area.................... 24576

Maximum address space.......... 18446743890435787967

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"TSV_TNEW_PAGE_ALLOC_FAILED" " "

"SAPL3008" or "L3008U05"

"BAPI_AP_ACC_GETKEYDATEBALANCE"

Information on where terminated

Termination occurred in the ABAP program "SAPL3008" - in

"BAPI_AP_ACC_GETKEYDATEBALANCE".

The main program was "ZIBFI_VEND_TB_H1 ".

In the source code you have the termination point in line 48

of the (Include) program "L3008U05".

The program "SAPL3008" was started as a background job.

Job Name....... "ZIBFI_VEND_TB_H1"

Job Initiator.. 108735

Job Number..... 11490500

Line number:

44 PERFORM READ_KONTO USING VENDOR

45 COMPANYCODE RETURN.

46 CHECK RETURN IS INITIAL.

>>>>> SELECT * FROM BSIK APPENDING CORRESPONDING FIELDS OF TABLE XLINEITEMS

49 WHERE BUDAT <= KEYDATE

50 AND BUKRS EQ COMPANYCODE

51 AND LIFNR EQ VENDOR

52 AND BSTAT IN BSTAT.

Re: Dump in BAPI while fetching data

Former Member — Wed, 21 Jul 2010 09:21:26 GMT

Only 2 ways for this:

a) reduce the no of records

b) ask your basis team to increase the session memory

Regards,

Nikhil

Re: Dump in BAPI while fetching data

Former Member — Wed, 21 Jul 2010 12:03:13 GMT

hi,

thanx alot.

we already tried these two options.

with less records its working fine. But my client does not want to retrict the selection.

Harshita Saxena

Re: Dump in BAPI while fetching data

HermannGahm — Wed, 21 Jul 2010 15:05:53 GMT

> we already tried these two options.

> with less records its working fine. But my client does not want to retrict the selection.

then you have to allow for more memory (increase the quotas)

topic Re: Dump in BAPI while fetching data in Application Development and Automation Discussions

Dump in BAPI while fetching data

Re: Dump in BAPI while fetching data

Re: Dump in BAPI while fetching data

Re: Dump in BAPI while fetching data