Alternative for Open , Fetch cursor command

Question

Hi Experts,
I am populating data from glpca table using Open Cursor statement with hold as shown below:
  OPEN CURSOR WITH HOLD cur1 FOR
Select data from the purchase order header table.
  SELECT runit rprctr sprctr                               
         racct rfarea hsl msl kostl aufnr ps_psp_pnr
          FROM glpca
         WHERE docnr  IN s_docnr
           AND rbukrs =  p_rbukrs
           AND rprctr IN s_rprctr
           AND sprctr IN s_sprctr                          
           AND rfarea IN s_rfarea
           AND budat  IN s_budat
           AND kostl  IN s_kostl
           AND aufnr  IN s_aufnr.
Now when i try to Fetch the cursor even restricting it with PACKAGE SIZE command ( value 998), my program get struck over here for 20-30 mins or more den that & session gets out for the user at client end coz of large data. I checked the value of cursor , it was around 670-700 approx.
The query is shown below:
DO.
fetch rows from cursor depending on package size
    FETCH NEXT CURSOR cur1 INTO TABLE t_glpca
       PACKAGE SIZE p_size.
    IF sy-subrc NE 0.
      CLOSE CURSOR cur1.
      EXIT.
    ENDIF.
The program get struck at above fetch next cursor command.
Kindly suggest me some other way to handle or populate the data or any alternative for Cursor command.
Thanks for your consideration.
Regards
Mudit

Answer 1

Siegfried Boes  wrote:
> there is a reason why OPEN CURSOR WITH HOLD is usually used.
>
> Siegfried
Sorry for hijacking this thread and asking here. I am here in the forums on daily basis just reading and learning.
This got me curious and I googled and read SAP tutorial about cursors:
http://help.sap.com/saphelp_nw70/helpdata/en/fc/eb3b23358411d1829f0000e829fbfe/content.htm
also read an answer from Thomas after searching forum:
The combination with OPEN CURSOR ... WITH HOLD allows package processing of tasks that require a database commit inside the loop. A normal SELECT loop without holding the cursor would be interrupted by a commit -> short dump.
MY TWO QUESTIONs
1. In SAP tutorial it states that
"WITH HOLD addition in the OPEN CURSOR statement allows you to prevent a cursor from being closed when a database commit occurs in Native SQL"
If I don't specify any commit statements in my abap code and user cursor without the addition with hold.
Can a commit be executed anyway and I get an unwanted commit and thus an unwanted close of my cursor?
Or do they mean that "if you specify commit in native sql"?
2. Thomas says a normal select loop without the cursor holding would be interrupted. Interrupted by who? Again, it seems like there is an "unwanted" commit here? Again, can there be any commits and unwanted interrupts if I dont specify it somewhere in my code?
regards
Baran
Edited by: Baran Sölen on Feb 25, 2009 11:39 AM