Reading BSAK dump

[Former Member]

Dear Experts,

The following select gives me a Dump.

I was selecting from bseg before,it gave me a dump.
Then I decided to select the same fields from BSAK.For a while it worked,Now its giving me the dump again.

SELECT bsak~belnr bsak~lifnr bsak~rebzg bsak~zfbdt bsak~zterm bsak~wrbtr bsak~shkzg bsak~buzei
   INTO CORRESPONDING FIELDS OF TABLE gt_spsppo FROM bsak WHERE
                                   bsak~lifnr IN so_kred
                                   AND bsak~bukrs = p_bukrs                                  
                                   AND bsak~augbl NE ''.

How should I modify this call.

Thanks
K

[Former Member]

Dear Experts,

The following select gives me a Dump.

I was selecting from bseg before,it gave me a dump.
Then I decided to select the same fields from BSAK.For a while it worked,Now its giving me the dump again.

SELECT bsak~belnr bsak~lifnr bsak~rebzg bsak~zfbdt bsak~zterm bsak~wrbtr bsak~shkzg bsak~buzei
   INTO CORRESPONDING FIELDS OF TABLE gt_spsppo FROM bsak WHERE
                                   bsak~lifnr IN so_kred
                                   AND bsak~bukrs = p_bukrs                                  
                                   AND bsak~augbl NE ''.

How should I modify this call.

Thanks
K

[ThomasZloch]

What is the title of the short dump, and please paste the section "error analysis".

Thomas

[Former Member]

TSV_TNEW_PAGE_ALLOC_FAILED

Error analysis                                                                           

    The internal table "\PROGRAM= ZUKV_PSP\DATA=GT_SPSPPO" 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: 242                                                                       

    Number of rows: 15494448                                                             

    Allocated rows: 15494448                                                             

    Newly requested rows: 64 (in 1 blocks)                                              

[Former Member]

Found the reason.This select was going through an endless loop.