Short Dump to extending internal table memory

Hi All,
I have an internal table with 10 million records . While appending records to this internal table iam getting dump as "No storage space available for extending the internal table." .I declared internal table with "OCCURS 0 "How can i avoid this dump ?

Hi,
The problem seems to be related to overflow of the internal table allocation size which will be set by BASIS people. Like if the internal table size restricted to say 1024KB and if we are trying to push data more than this it will throw such error.
Please try to split them into more smaller but several internal tables. Also try to restrict the number of records selected, if they are not really required to be selected.
Regards,
Ferry Lianto

Similar Messages

Increase internal table memory

Dear Techis,
How to increase size of internal table. while executing it gettin in DUMP.
I checked wid basis consultanat the Heap memory is more than sufficient, but still my report is not gettin executed its showin dump .
Will anybody pls tell me is it possible to increase size of internal table as of now i am using "Occurs 0" if i use "occurs 100" is dis help in any way??
Pls Suggest
Regards
Santosh

Hi Shree,
The Dump is
Line width: 1700
Number of lines: 106904
Allocated lines: 106904
New no. of requested lines: 8 (in 1 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
The Dump is given Below
You attempted to extend an internal table, but the required space was
not available.
The internal table "\PROGRAM=ZFIGLN0002\DATA=IT_LINEITEM[]" 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: 197
Number of rows: 43248
Allocated rows: 43248
Newly requested rows: 64 (in 1 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server TCPRDSAP_TCP_00 on host TCPRDSAP (wp 4)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1881
The error reported by the operating system is:
Error number..... " "
Error text....... " "
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 1508832
Extended memory (EM)........... 383623632
Assigned memory (HEAP)......... 369003312
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... " "
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" " "
"ZFIGLN0002" or "ZFIGLN0002"
"POPULATE_SUMMARY_INFO"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
                    Above is the error in showing in Dump Analysisi
i Checked heap memory parameter thru basis consultant and its more as compared to dis

Where I can check the internal table memory that have the system?

Hi
I have some jobs that cancel with this error: No storage space available for extending an internal table.
Where I can check the amount of space memory that have the system and if I can resolve this problem if I put a commit work or something like that?
The dump stop when I make a import:
IMPORT TIMES DHIST3 SUM3 FROM DATABASE MONI(DB) ID MONIKEY.
Thanks for the help!

hi,
goto:
sm04 - goto- memory
A.
Message was edited by:
Andreas Mann

Internal table Memory Issue Exception TSV_TNEW_PAGE_ALLOC_FAILED

Hi experts,
I am working on a conversiojn programme. This programme is dealing with 4 input files.
Each of these files is having more than 50,000 records. I am reading the corresponding application server files to fill
the internal tables related to these files.
The files are being read properly and internal tables are being filled.
However when i try to assign any of these 4 internal tables to other temproray internal tables in programme(requirement)
i get a dump TSV_TNEW_PAGE_ALLOC_FAILED.
The dump is related to memory issue.
I think The memory available in the programme at this point is not sufficient for table assignment.
Please suggest any alternatives where i can save any memory .
Changig of basis setting is not an option.
Regards,
Abhishek Kokate

Hi Kiran,
I am not agree with you , I am agree with Hermann.
While writting file you restrict the record max 5,000 to 10,000 records and process don't store the mutch data into internal table.
After every used refresh the internal table, Declare table where necessary.
But you can try to avoid the copy cost.
Rgds
Ravi Lanjewar

Short dump while accessing the table

There is a report ppioa0000, when executing the report it is going for short dump, error analysis showing that
<b>when accessing the attributes of dictionary table IOSOPER meaningless values are found.</b>
and ABAP run time error showing that DDIC_FIELD_ACCESS_ERROR
suggest me,
thanks and regards
krishna

The database is damaged, links between SAP dictionary and actual database seems to be broken. Try to use SE14 to adjust database.
Regards

Error while extending internal table

Hi,
We have a data load going on from one ODS to another, this is a daily load but for but last few days data load is failing saying
"Runtime Error: TSV_TNEW_PAGE_ALLOC_FAILED - You attempted to extend an internal table, but the required space was not available. "
What all measures can be taken to make this load happen regularly?
Regards,
Kironmoy Banerjee.

Hi ,
Please check below threads.
http://forumsa.sdn.sap.com/click.jspa?searchID=32822064&messageID=4660903
http://forumsa.sdn.sap.com/click.jspa?searchID=32822064&messageID=6806983
http://forumsa.sdn.sap.com/click.jspa?searchID=32822064&messageID=6794034
http://forumsa.sdn.sap.com/click.jspa?searchID=32822064&messageID=5618979
http://forumsa.sdn.sap.com/click.jspa?searchID=32822064&messageID=8059962
http://forumsa.sdn.sap.com/click.jspa?searchID=32822064&messageID=6678629
http://forumsa.sdn.sap.com/click.jspa?searchID=32822064&messageID=5989583
Hope it helps.
Thanks & Regards,
Ramnaresh.P.

Internal Table Memory Allocation

Hello all,
I could understand the difference between Internal Table with occurs 0 and internal table with type declaration...
correct me if i am wrong, occurs 0 declaration occupies 8kb memory and header line 256 bytes...
But what i could not get is...
Where can i view this internal table runtime memory usage?? Should i have to check that in some transaction???
If that is the case, what transaction i should look at?? Can i view this in debugging mode??? I tried GOTO -> STATUS DISPLAY -> MEMORY USE and i have tried even SETTINGS -> MEMORY MONITORING ->MEMORY DISPLAY ON...Nothing worked..
when i go for GOTO -> STATUS DISPLAY -> MEMORY USE in debugging
memory allocated seems to be same for Internal table with occur 0 and Internal table with type declaration
I have searched a lot about this in SDN....But could not come to a conclusion......
I don't have authorisation here for DBG_MEMORY_DIFFTOOL or S_MEMORY_INSPECTOR unfortunately.....
Waiting for your replies....

Hi Jagannathan,
You can view this on Debugger(ECC6.0) onwards.
To find out how much memory internal tables occupy, choose Goto --> Display Condition --> Memory Usage.
Choose Change Settings to display a window, in which you can choose the Internal Tables button.
Hope this will assists you for your quest.
Regards,
-Syed.

Short Dump while acessing external tables using DB Connect

Hello SDN'rs,
I am getting Short dump (below) when i am trying to look into the table contents using DB Connect.
Please let me know how to resolve this problem. Is there any OSS Note on this??
External Database is Oracle; i can look into other tables.
ShrtText
Syntax error in program "GP_CREATE_STRUCTURE_DBCON_026 "
|What happened?                                                                                |
|    Error in ABAP application program.                                                            |
|                                                                                |
|    The current ABAP program "CL_RS_STRUC===================CP" had to be                         |
|     terminated because one of the                                                                |
|    statements could not be executed.                                                             |
|                                                                                |
|    This is probably due to an error in the ABAP program.                                         |
|                                                                                |
|    In program "GP_CREATE_STRUCTURE_DBCON_026 ", the following syntax error                       |
|     occurred                                                                                |
|    in the Include "GP_CREATE_STRUCTURE_DBCON_026 " in line 5:                                    |
|    "Type "D" can only have the length specification "8" or no length speci"                      |
|    "fication at all."                                                                            |
|    " "                                                                                |
|    " "                                                                                |
|                                                                                |
|    Author and last person to change the Include are:                                             |
|    Author "XYZ "                                                                            |
|    Last changed by "XYZ
|Error analysis                                                                                |
|    In program "GP_CREATE_STRUCTURE_DBCON_026 ", the following syntax error                       |
|     occurred:                                                                                |
|    "Type "D" can only have the length specification "8" or no length speci"                      |
|    "fication at all."                                                                            |
|    " "                                                                                |
|    " "                                                                                |
Trigger Location of Runtime Error                                                                 |
|    Program                                 CL_RS_STRUC===================CP                      |
|    Include                                 CL_RS_STRUC===================CM002                   |
|    Row                                     108                                                   |
|    Module type                             (METHOD)                                              |
|    Module Name                             CREATE
Thanks,
Faizee B

When i tried today for the same table i am getting the shortdump description(below), I have noticed that the number have changed from 026 to 055, any thoughts why it happen and how it can be resolved?
In program "GP_CREATE_STRUCTURE_DBCON_055 ", the following syntax error
occurred in the Include "GP_CREATE_STRUCTURE_DBCON_055 " in line 5:
    "Type "D" can only have the length specification "8" or no length specification at all."
Thanks,
Faizee B

Internal table memory

Hi,
Can any one say how to identify,how much memory is associated with the internal table which we are using in our prog.

Hi Prince
occurs 0, the memory allocation is done by system,
in case of occurs 100 memory of 100 records allocated initially ,then if records exceeds then system ll allocate memory,
memory allocation here is known as extent and depend upon basis administrator...
You can use the above addition to reserve memory space for <n> table lines when you declare the table object.
When this initial area is full, the system makes twice as much extra space available up to a limit of 8KB. Further memory areas of 12KB each are then allocated.
You can usually leave it to the system to work out the initial memory requirement. The first time you fill the table, little memory is used. The space occupied, depending on the line width, is 16 <= <n> <= 100.
It only makes sense to specify a concrete value of <n> if you can specify a precise number of table entries when you create the table and need to allocate exactly that amount of memory (exception: Appending table lines to ranked lists). This can be particularly important for deep-structured internal tables where the inner table only has a few entries (less than 5, for example).
To avoid excessive requests for memory, large values of <n> are treated as follows: The largest possible value of <n> is 8KB divided by the length of the line. If you specify a larger value of <n>, the system calculates a new value so that n times the line width is around 12KB."
OCCURS 0 is betten than OCCURS 100 because
OCCURS 100.
if you use occurs 100, the ABAP memory will allocate for 100 records memory location, some time you have only 20 records at that time the remaining 80 records memory space will waste.
REAL TIME EXAMPLE: BUS
In bus total seat is 57, some time only 20 people only will come at that time also bus should go so remaining seats will waste.
OCCURS 0:
OCCURS 0, the memory is not allocated previously, that is optimistic.if you have 20 records the memory will take for only 20 records.
1. when can we use occurs0?
When declaring internal tables,
whose expected number of records we are not sure,
or we are not bothered.
Its normally better to use occurs 0,
rather than occur 10 , 100 , 90 etc.
2. if we use occurs 0 how will the memory be allocated?
a. if we use 0, 10 , or any other figure,
there is no restriction on the expansion of the internal table.
the 0, 10, etc is just a indicative figure for expected number of records.
b. When using 0,
8 KB - the internal table will be expanded in bunches of 8 KB.
Reward if helpful.
Thanks

Dump In Dynamic Internal Table

REPORT ZDYNAMIC_INTERNAL_TABLE.
TYPE-POOLS : abap.
FIELD-SYMBOLS: <fs_table> TYPE STANDARD TABLE,
               <fs_wa>,
               <fs_field>.
DATA: it_table TYPE REF TO data,
      it_line TYPE REF TO data,
      xfc TYPE LVC_S_FCAT,
      ifc TYPE lvc_t_fcat.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS: p_table(30) TYPE c DEFAULT 'T001'.
SELECTION-SCREEN END OF BLOCK b1.
START-OF-SELECTION.
PERFORM get_structure.
PERFORM create_dynamic_itab.
PERFORM get_data.
PERFORM write_out.
*&      Form get_structure
      text
FORM get_structure.
DATA : idetails TYPE abap_compdescr_tab,
         xdetails TYPE abap_compdescr.
DATA : ref_table_des TYPE REF TO cl_abap_structdescr.
Get the structure of the table.
ref_table_des ?=
      cl_abap_typedescr=>describe_by_name( p_table ).
idetails[] = ref_table_des->components[].
LOOP AT idetails INTO xdetails.
    CLEAR xfc.
    xfc-fieldname = xdetails-name .
    xfc-datatype = xdetails-type_kind.
    xfc-inttype = xdetails-type_kind.
    xfc-intlen = xdetails-length.
    xfc-decimals = xdetails-decimals.
    APPEND xfc TO ifc.
   WA_XFC-FIELDNAME = P_NAME.
   WA_XFC-DATATYPE = 'C'.
   WA_XFC-INTTYPE = 'C'.
   WA_XFC-INTLEN = P_LEN.
   WA_XFC-DECIMALS = 0.
   APPEND WA_XFC TO IST_IFC.
ENDLOOP.
ENDFORM.                    "get_structure
*&      Form create_dynamic_itab
      text
FORM create_dynamic_itab.
Create dynamic internal table and assign to FS
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = ifc
    IMPORTING
      ep_table        = it_table.
ASSIGN it_table->* TO <fs_table>.
Create dynamic work area and assign to FS
CREATE DATA it_line LIKE LINE OF <fs_table>.
ASSIGN it_line->* TO <fs_wa>.
ENDFORM.                    "create_dynamic_itab
*&      Form get_data
      text
FORM get_data.
Select Data from table.
SELECT * INTO CORRESPONDING FIELDS OF TABLE <fs_table>
             FROM (p_table).
ENDFORM.                    "get_data
*&      Form write_out
      text
FORM write_out.
Print data from table.
*call function 'reuse_alv_grid_display'.
*pass <fs_table> as internal table to the function **
BREAK-POINT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
      EXPORTING
        I_CALLBACK_PROGRAM       = SY-REPID
        IT_FIELDCAT              = ifc[]
       IT_SORT                  = IST_SORT_SUBTOTAL[]
       IT_EVENTS                = IST_EVENT[]
       IS_LAYOUT                = WA_LAYOUT
        I_CALLBACK_PF_STATUS_SET = 'PF_STATUS'
        I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
        I_SAVE                   = 'X'
      TABLES
        T_OUTTAB                 = <fs_table>.
ENDFORM.                    "write_out
It was tried to transfer the internal table "IFC" to the formal parameter
"IT_FIELDCAT". In doing so, a type conflict occurred between the formal.
here how can i resolve it.
thanks ,
rajan.

Try like following
TYPE-POOLS : abap,SLIS.
FIELD-SYMBOLS: <TABLE> TYPE STANDARD TABLE.
DATA: it_table TYPE REF TO data,
      it_line TYPE REF TO data,
      xfc      TYPE LVC_S_FCAT,
      ifc      TYPE LVC_T_FCAT.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS: p_table(30) TYPE c DEFAULT 'T001'.
SELECTION-SCREEN END OF BLOCK b1.
START-OF-SELECTION.
PERFORM get_structure.
PERFORM create_dynamic_itab.
PERFORM get_data.
PERFORM write_out.
FORM get_structure.
DATA : idetails TYPE abap_compdescr_tab,
            xdetails TYPE abap_compdescr.
DATA : ref_table_des TYPE REF TO cl_abap_structdescr.
* Get the structure of the table.
ref_table_des ?= cl_abap_typedescr=>describe_by_name( p_table ).
idetails[]     = ref_table_des->components[].
LOOP AT idetails INTO xdetails.
   CLEAR xfc.
   xfc-fieldname = xdetails-name .
   xfc-datatype = xdetails-type_kind.
   xfc-inttype   = xdetails-type_kind.
   xfc-intlen    = xdetails-length.
   xfc-decimals = xdetails-decimals.
   APPEND xfc TO ifc.
ENDLOOP.
ENDFORM. "get_structure
FORM create_dynamic_itab.
* Create dynamic internal table and assign to FS
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = ifc
    IMPORTING
      ep_table = it_table.
ASSIGN it_table->* TO <TABLE>.
* Create dynamic work area and assign to FS
* CREATE DATA it_line LIKE LINE OF .
* ASSIGN it_line->* TO .
ENDFORM. "create_dynamic_itab
FORM get_data.
* Select Data from table.
SELECT * INTO CORRESPONDING FIELDS OF TABLE <TABLE> FROM (p_table).
ENDFORM.
"get_data
FORM write_out.
*REPLACE FM REUSE_ALV_GRID_DISPLAY WITH REUSE_ALV_GRID_DISPLAY_LVC
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY_LVC'
   EXPORTING
     I_CALLBACK_PROGRAM = SY-REPID
     IT_FIELDCAT_LVC        = ifc[]
     I_CALLBACK_PF_STATUS_SET = 'PF_STATUS'
     I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
     I_SAVE = 'X'
TABLES
     T_OUTTAB = <TABLE>.
ENDFORM.

Short Dump TSV_TNEW_PAGE_ALLOC_FAILED while using shared memory objects

Hi Gurus,
We are using shared memory objects to stor some data which we will be reading later. I have implemented the interfce IF_SHM_BUILD_INSTANCE in root class and using its method BUILD for automatic area structuring.
Today our developments moved from dev system to quality system, and while writing the data into the shared memory using the methods ATTACH_FOR_WRITE and DETACH_COMMIT in one report. We started getting the run time error TSV_TNEW_PAGE_ALLOC_FAILED.This is raised when the method DETACH_COMMIT is called to commit the changes in the shared memory.
Everyhting works fine before DETACH_COMMIT. I know that it is happening since the program ran out of extended memory, but I am not sure why it is happening at DETACH_COMMIT call. If excessive memory is being used in the program, this run time error should have been raised while calling the ATTACH_FOR_WRITE method or while filling the root class attributes. I am not sure why it is happening at DETACH_COMMIT method.
Many Thanks in advance.
Thanks,
Raveesh

Hi raveesh,
as Naimesh suggested: Probably system parameter for shared memory area is too small. Compare the system parameters in devel and QA, check what other shared memory areas are used.
Regarding your question, why it does not fail at ATTACH_FOR_WRITE but then on DETACH_COMMIT:
Probably ATTACH_FOR_WRITE will set an exclusive write lock on the shared memory data, then write to some kind of 'rollback' memory and DETACH_COMMIT will really put the data into shared memory area and release the lock. The 'rollback' memory is in the LUW's work memory which is much bigger as the usual shared memory size.
This is my assumption - don't know who can verify or reject it.
Regards,
Clemens

ABAP Program Short Dump in BW

I have created a dynamic program which would read any table name as input parameter and print the contents. Its working if I use a small table(3 fields) and the same program is throwing short dump if pass a big table.
Shortdump
"SAPSQL_SELECT_TAB_TOO_SMALL" C
"ZBW_DYNAMIC_ITAB1" or "ZBW_DYNAMIC_ITAB1"
"START-OF-SELECTION"
Error in the line below
   61
   62 * Select Data from table.
>>>>> select * into table <dyn_table>
   64            from (p_table).
   65
Program
*& Report ZBW_DYNAMIC_ITAB1
REPORT ZBW_DYNAMIC_ITAB1.
type-pools: slis.
field-symbols: <dyn_table> type standard table,
               <dyn_wa>,
               <dyn_field>.
data: alv_fldcat type slis_t_fieldcat_alv,
      it_fldcat type lvc_t_fcat.
type-pools : abap.
data : it_details type abap_compdescr_tab,
       wa_details type abap_compdescr.
data : ref_descr type ref to cl_abap_structdescr.
data: new_table type ref to data,
      new_line type ref to data,
      wa_it_fldcat type lvc_s_fcat.
selection-screen begin of block b1 with frame title text .
parameters: p_table(30) type c.
selection-screen end of block b1.
Get the structure of the table.
ref_descr ?= cl_abap_typedescr=>describe_by_name( p_table ).
it_details[] = ref_descr->components[].
loop at it_details into wa_details.
clear wa_it_fldcat.
wa_it_fldcat-fieldname = wa_details-name .
wa_it_fldcat-datatype = wa_details-type_kind.
wa_it_fldcat-intlen = wa_details-length.
wa_it_fldcat-decimals = wa_details-decimals.
append wa_it_fldcat to it_fldcat .
endloop.
Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
             exporting
                it_fieldcatalog = it_fldcat
             importing
                ep_table        = new_table.
assign new_table->* to <dyn_table>.
Create dynamic work area and assign to FS
create data new_line like line of <dyn_table>.
assign new_line->* to <dyn_wa>.
Select Data from table.
select * from (p_table) into table <dyn_table>
Write out data from table.
loop at <dyn_table> into <dyn_wa>.
do.
    assign component sy-index of structure <dyn_wa> to <dyn_field>.
    if sy-subrc <> 0.
      exit.
    endif.
    if sy-index = 1.
      write:/ <dyn_field>.
    else.
      write: <dyn_field>.
    endif.
enddo.
endloop.

Hi,
The dynamic table that is generated is not converting the exact output length in case of packed numbers.
Foe eg : If there is an packed field of length 7 , the dynamic table is converting it to Char 7 , but the actual output length of Pack 7 is 15.Hence it is giving short dump saying that Internal Table length is not sufficient.
Probably it might have worked for smaller tables for you because you might not have used Packed field in there.
Regards,
Vijay.

Short dump -No more storage space available for extending an internal table

Hi All,
While running one program I get the short dump saying
"No more storage space available for extending an internal table "IT_862".
Error Analysis given in the dump log :
The internal table "IT_862" could not be enlarged further.
To extend the internal table, 14656 bytes of storage space was
needed, but none was available. At this point, the table "IT_862" has
8528862 entries.
Source Code Extract :
003360     loop at t_line.
003370       clear t_output.
003380
003390   *   Increment Line counter
003400       add 1 to l_line_cnt.
003410
003420       t_output-object = t_stxh-tdobject.
003430       t_output-id     = t_stxh-tdid.
003440       t_output-spras = t_stxh-tdspras.
003450       t_output-name   = t_stxh-tdname.
003460       t_output-line   = l_line_cnt.
003470       t_output-format = t_line-tdformat.
003480       t_output-text   = t_line-tdline.
     *>       append toutput.   " ERROR POINT*
Can you please suggest what can be the possible solution for the above error.
Thanks in advance.
Sanjeet

Hi
Check out this thread:
Re: No storage space available for extending the internal table
Make sure you are not having an infinite loop.
Hope this helps
Regards,
Jayanthi.K

Short dump-internal table size issue

Hi,
I get the following message in the short dump analysis for a report.
No storage space available for extending table "IT_920".
You attempted to extend an internal table, but the required space was not available.
Error Analysis:
The internal table "IT_920" could not be enlarged further.
To extend the internal table, 9696 bytes of storage space was
needed, but none was available. At this point, the table "IT_920" has
1008240 entries.
Its an old report and I saw the internal table declaration using the "OCCURS" clause in the internal table declaration.
begin of itab occurs 100.
end of itab.
I tried the option of changing to "OCCURS 0", still issue persists.
Any help would be highly appretiated
CM

Hello CMV,
This is basic problem with SAP internal tables. For every internal table memory is alocated ( Max..256K)...once you cross the memory size/limit of the internal table it resuls in short dump.
Only way to overcome this problem is handle limited number of records at a time..
Please refer following sample code which will help you to avoid short dump while processing large number of records....
SORT TAB_RESULT.
DESCRIBE TABLE TAB_RESULT LINES W_RECORDS.
W_LOW      = 1.
W_UP       = 1000.
*Spliting the records from tab_result1 by pakage of 1000 at a time
*to avoid short dump in case of more records
WHILE W_LOW <= W_RECORDS.
    R_PKUNWE-SIGN = 'I'.
    R_PKUNWE-OPTION = 'EQ'.
    R_WERKS-SIGN = 'I'.
    R_WERKS-OPTION = 'EQ'.
    LOOP AT TAB_RESULT FROM W_LOW TO W_UP.
      MOVE TAB_RESULT-PKUNWE TO R_PKUNWE-LOW.
      MOVE TAB_RESULT-WERKS TO R_WERKS-LOW.
      APPEND R_PKUNWE.
      APPEND R_WERKS.
    ENDLOOP.
*fetch sold to party
     SELECT KUNNR NAME1
       FROM KNA1
       APPENDING CORRESPONDING FIELDS OF TABLE TAB_KNA1
       WHERE KUNNR IN R_PKUNWE.
*fetch plant
SELECT WERKS NAME1
         FROM T001W
         APPENDING CORRESPONDING FIELDS OF TABLE TAB_T001W
         WHERE WERKS IN R_WERKS.
   REFRESH: R_PKUNWE,
            R_WERKS.
    W_LOW = W_LOW + 1000.
    W_UP = W_UP + 1000.
ENDWHILE.
Hope this will help you to solve problem.
Cheers,
Nilesh

Dump -- No more storage space available for extending an internal table

In Our system we are getting this dump
No more storage space available for extending an internal table
and because of it no user is able to login into the system.
We have Some classes in the system and we have defined shared memories to all classes according to regions.
So for a particular class means users of a region are not able to logon to systems and we are getting these dumps in the system.
So please suggest first how to clear the shared memory & how to conclude what activity in system made the shared memory full.
Regards,
Shivam Mittal

My OS is HP-UNIX..
And we do not access on OS level,So please suggest the way to clear it from SAP level.
In dump it is also mentioned:
The internal table "\AREA=<Name>\INSTANCE=$DEFAULT_INSTANCE$\VER
SID=2\OBJ={O:1.2*\CLASS=<CLASS>\DATA=GT_BUFFER[1]-DATA" 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: "\AREA=<Name>\INST=$DEFAULT_INSTANCE$\CLNT=100"
Row width: 156
Number of rows: 0
Allocated rows: 63
Newly requested rows: 1216 (in 19 blocks)
Please also suggest what is the internel table name that is causing the issue.
Regards,
Shivam Mittal

Short Dump to extending internal table memory

Similar Messages

Maybe you are looking for