Select-endselect

WHY WE DONOT USE SELECT-ENDSELECT. IF I WILL USE SELECT-END SELECT STATEMENT IN REPORT. I KNOW PEEFORMANCE OF THE REPORT WILL BE SLOW. COULD U PLESE TELL ME THE OTHER REASON

hi,
look in online-docu for:
select (fields) from dbtable into itab
where ....
or if you search a single item:
select single field from dbtable into hfield
where .... (complete primary key)
Andreas

Similar Messages

Diff b/w select endselect and select into table............

what is the difference b/w
Select
Endselect
and select into table....
Akshitha..

Hi,
When ever u want to append data into the workarea then use select ... endselect. When u r appending data into the internal table then use select. Also when u use select single then also use only select.
Eg: Using only Select
data : begin of itab occurs 0,
lifnr like lfa1-lifnr,
end of itab.
select single lifnr from lfa1 into itab.
data itab like lfa1 occurs 0 with header line.
select * from lfa1 into table itab.
Eg: Using Select .. endselect.
data : itab like lfa1 occurs 0,
wa like lfa1.
select * from lfa1 into wa.
append wa to itab.
endselect.
Regards

What happen if i use controll break statement in between select & endselect

Hi all,
what happen if i use controll break statement in between select & endselect ?
Thanks in Advance
KR

Hi for reference u can go through this code example
data:
fs_tab like sflight.
data:
   t_tab like standard table of fs_tab.
   select * from sflight into table t_tab.
   loop at t_tab into fs_tab.
     write: / fs_tab-carrid.
   endloop.
   refresh t_tab.
   clear fs_tab.
   select * from sflight into fs_tab.
     at new fs_tab-carrid.
       append fs_tab to t_tab.
     endat.
   endselect.

Report on smartform.Replace select endselect with something to efficient it

To make a smartform report efficient by removing all occurs & modify internal table statements.
What i have been given to do is to select all data from respective tables put them into one internal table & then finally making tab2 or tab3 in the report to be the final table.I am not sure which among these two i can make final table.
THE CODE is:
REPORT zgr_note.
TABLES : mseg, "Document Segment : Material
         prps, "WBS element master data
         proj, "Project Definition
         mkpf, "Header : Material Document
         lfa1, "Vendor Master
         makt, "Material Description
         aufk, "Order Master Data
         afvc. "Operation within an order
DATA : fname LIKE rs38l-name. "Name of Function Module
DATA: lf_fm_name            TYPE rs38l_fnam.
DATA: ls_control_param      TYPE ssfctrlop.
DATA: ls_composer_param     TYPE ssfcompop.
DATA: ls_recipient          TYPE swotobjid.
DATA: ls_sender             TYPE swotobjid.
DATA: lf_formname           TYPE tdsfname.
DATA: ls_addr_key           LIKE addr_key.
DATA: ls_dlv_land           LIKE vbrk-land1.
DATA: ls_job_info           TYPE ssfcrescl.
DATA: ls_otpt_opt           TYPE ssfcompop.
DATA: retcode TYPE sy-subrc.
DATA: cntr TYPE i VALUE 0.
DATA: cntr1 TYPE i .
DATA: number TYPE SSFCRESCL-SPOOLIDS. " OCCURS 0 WITH HEADER LINE.
DATA: TSP01 type TABLE OF TSP01_SP0R.
DATA : BEGIN OF itab OCCURS 0.
        INCLUDE STRUCTURE mseg.
DATA : post1 LIKE proj-post1,           "Project Definition
       pspnr LIKE proj-pspnr,           "WBS element
       maktx LIKE makt-maktx,           "Material Description
       name1 LIKE lfa1-name1,           "Name of the supplier
       budat LIKE mkpf-budat,           "Posting date
       bldat LIKE mkpf-bldat,           "Document date
       cpudt LIKE mkpf-cpudt,           "Date on which account document was entered
       psphi LIKE prps-psphi,           "Current number of project
       post2 LIKE prps-post1,           "WBS Definition
       xblnr LIKE mkpf-xblnr,           "Reference number( in this case challan number)
       bktxt LIKE mkpf-bktxt,           "Header text
       ort01 LIKE lfa1-ort01,           "vendor city
       ktext LIKE aufk-ktext,           "network description
       ltxa1 LIKE afvc-ltxa1.           "operation short text
DATA : END OF itab.
DATA : BEGIN OF jtab OCCURS 0.
        INCLUDE STRUCTURE itab.
DATA : END OF jtab.
DATA : itab1 LIKE itab OCCURS 0
      WITH HEADER LINE.
DATA :itab2 LIKE itab OCCURS 0
      WITH HEADER LINE.
DATA: itab3 LIKE itab OCCURS 0 WITH HEADER LINE.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text_001.
SELECT-OPTIONS : gr_num FOR mseg-mblnr . "no INTERVALS.
PARAMETERS : gr_note LIKE itemset-xopsel RADIOBUTTON GROUP rad1.
SELECTION-SCREEN SKIP.
SELECT-OPTIONS : mat_num FOR mseg-mblnr . "no INTERVALS.
PARAMETERS : mat_slip LIKE itemset-xopsel RADIOBUTTON GROUP rad1.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN SKIP.
CASE 'X'.
WHEN gr_note.
    PERFORM gr_display.
WHEN mat_slip.
    PERFORM mat_display.
ENDCASE.
FORM gr_display .
*break developer1.
SELECT mblnr mjahr matnr werks lgort lifnr menge meins
         erfmg bpmng ebeln ps_psp_pnr zeile lsmng erfme
FROM mseg
INTO CORRESPONDING FIELDS OF TABLE itab
   WHERE mblnr IN gr_num.
LOOP AT itab.
    SELECT pspnr psphi post1 INTO CORRESPONDING FIELDS OF itab1
      FROM prps WHERE pspnr = itab-ps_psp_pnr.
      itab-psphi = itab1-psphi.
      itab-pspnr = itab1-pspnr.
      itab-post2 = itab1-post1.
      MODIFY itab TRANSPORTING psphi pspnr post2.
    ENDSELECT.
    SELECT post1 FROM proj INTO CORRESPONDING FIELDS OF itab2
    WHERE pspnr = itab-psphi.
      itab-post1 = itab2-post1.
      MODIFY itab TRANSPORTING post1.
    ENDSELECT.
    REFRESH itab2.
    SELECT maktx FROM makt INTO CORRESPONDING FIELDS OF itab2
      WHERE matnr = itab-matnr.
      itab-maktx = itab2-maktx.
      MODIFY itab TRANSPORTING maktx.
    ENDSELECT.
    REFRESH itab2.
    SELECT name1 ort01 FROM lfa1 INTO CORRESPONDING FIELDS OF itab2
      WHERE lifnr = itab-lifnr.
      itab-name1 = itab2-name1.
      itab-ort01 = itab2-ort01.
      MODIFY itab TRANSPORTING name1 ort01.
    ENDSELECT.
    REFRESH itab2.
    SELECT budat bldat cpudt xblnr bktxt FROM mkpf
      INTO CORRESPONDING FIELDS OF itab2
      WHERE mblnr = itab-mblnr.
      itab-budat = itab2-budat.
      itab-bldat = itab2-bldat.
      itab-cpudt = itab2-cpudt.
      itab-xblnr = itab2-xblnr.
      itab-bktxt = itab2-bktxt.
      MODIFY itab TRANSPORTING budat bldat cpudt xblnr bktxt.
    ENDSELECT.
ENDLOOP.
LOOP AT itab .
    ON CHANGE OF itab-mblnr.
      itab3-mblnr = itab-mblnr.
      itab3-post1 = itab-post1.
      itab3-post2 = itab-post2.
      itab3-name1 = itab-name1.
      itab3-ort01 = itab-ort01.
      itab3-bldat = itab-bldat.
      APPEND itab3.
      CLEAR itab3.
    ENDON.
ENDLOOP.
jtab-mblnr = itab-mblnr.
jtab-xblnr = itab-xblnr.
jtab-budat = itab-budat.
jtab-bktxt = itab-bktxt.
jtab-lsmng = itab-lsmng.
jtab-erfmg = itab-erfmg.
jtab-erfme = itab-erfme.
jtab-matnr = itab-matnr.
jtab-maktx = itab-maktx.
jtab-zeile = itab-zeile.
APPEND jtab.
LOOP AT itab3.
    CLEAR: itab2,itab2[].
    LOOP AT itab WHERE mblnr = itab3-mblnr.
      MOVE-CORRESPONDING itab TO itab2.
      APPEND itab2.
      CLEAR itab2.
    ENDLOOP.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        formname                 = 'ZMM_GOODS_RECEIPT1'
VARIANT                  = ' '
DIRECT_CALL              = ' '
     IMPORTING
       fm_name                  = fname
EXCEPTIONS
NO_FORM                  = 1
NO_FUNCTION_MODULE       = 2
OTHERS                   = 3
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
*break developer1.
PERFORM print_parameters.
    CALL FUNCTION fname
      EXPORTING
       control_parameters         = ls_control_param
       output_options             = ls_otpt_opt
       user_settings              = 'X'
       gr_mseg_hdr                = itab3
IMPORTING
DOCUMENT_OUTPUT_INFO       =
JOB_OUTPUT_INFO            =
JOB_OUTPUT_OPTIONS         =
      TABLES
        gr_mseg                    = itab2
     EXCEPTIONS
       formatting_error           = 1
       internal_error             = 2
       send_error                 = 3
       user_canceled              = 4
       OTHERS                     = 5
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDLOOP.
ENDFORM.                    " GR_DISPLAY
FORM mat_display .
SELECT mblnr mjahr matnr werks lgort lifnr menge meins
         erfmg bpmng ebeln ps_psp_pnr zeile lsmng erfme
         mat_pspnr nplnr aufpl aplzl
FROM mseg
INTO CORRESPONDING FIELDS OF TABLE itab
   WHERE mblnr IN mat_num.
LOOP AT itab.
    SELECT ltxa1 FROM afvc INTO CORRESPONDING FIELDS OF itab1
      WHERE aufpl = itab-aufpl AND aplzl = itab-aplzl.
      itab-ltxa1 = itab1-ltxa1.
      MODIFY itab TRANSPORTING ltxa1.
    ENDSELECT.
    REFRESH itab1.
    SELECT ktext FROM aufk INTO CORRESPONDING FIELDS OF itab1
      WHERE aufnr = itab-nplnr.
      itab-ktext = itab1-ktext.
      MODIFY itab TRANSPORTING ktext.
    ENDSELECT.
    REFRESH itab1.
    SELECT pspnr psphi post1 INTO CORRESPONDING FIELDS OF itab1
      FROM prps WHERE pspnr = itab-mat_pspnr.
      itab-psphi = itab1-psphi.
      itab-pspnr = itab1-pspnr.
      itab-post2 = itab1-post1.
      MODIFY itab TRANSPORTING psphi pspnr post2.
    ENDSELECT.
    SELECT post1 FROM proj INTO CORRESPONDING FIELDS OF itab2
    WHERE pspnr = itab-psphi.
      itab-post1 = itab2-post1.
      MODIFY itab TRANSPORTING post1.
    ENDSELECT.
    REFRESH itab2.
    SELECT maktx FROM makt INTO CORRESPONDING FIELDS OF itab2
      WHERE matnr = itab-matnr.
      itab-maktx = itab2-maktx.
      MODIFY itab TRANSPORTING maktx.
    ENDSELECT.
    REFRESH itab2.
    SELECT name1 ort01 FROM lfa1 INTO CORRESPONDING FIELDS OF itab2
      WHERE lifnr = itab-lifnr.
      itab-name1 = itab2-name1.
      itab-ort01 = itab2-ort01.
      MODIFY itab TRANSPORTING name1 ort01.
    ENDSELECT.
    REFRESH itab2.
    SELECT budat bldat cpudt xblnr bktxt FROM mkpf
      INTO CORRESPONDING FIELDS OF itab2
      WHERE mblnr = itab-mblnr.
      itab-budat = itab2-budat.
      itab-bldat = itab2-bldat.
      itab-cpudt = itab2-cpudt.
      itab-xblnr = itab2-xblnr.
      itab-bktxt = itab2-bktxt.
     break developer1.
      MODIFY itab TRANSPORTING budat bldat cpudt xblnr bktxt.
    ENDSELECT.
ENDLOOP.
LOOP AT itab.
    ON CHANGE OF itab-mblnr.
      itab3-mblnr = itab-mblnr.
      itab3-budat = itab-budat.
      itab3-bldat = itab-bldat.
      itab3-post1 = itab-post1.
      itab3-ktext = itab-ktext.
      APPEND itab3.
      CLEAR itab3.
    ENDON.
ENDLOOP.
LOOP AT itab3.
    CLEAR: itab2, itab2[].
    LOOP AT itab WHERE mblnr EQ itab3-mblnr.
      MOVE-CORRESPONDING itab TO itab2.
      APPEND itab2.
      CLEAR itab2.
    ENDLOOP.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        formname                 = 'ZMM_MAT_ISSUE_SLIP'
VARIANT                  = ' '
DIRECT_CALL              = ' '
     IMPORTING
       fm_name                  = fname
EXCEPTIONS
NO_FORM                  = 1
NO_FUNCTION_MODULE       = 2
OTHERS                   = 3
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ls_control_param-no_dialog = 'X'.
*ls_control_param-preview = 'X'.
*ls_control_param-getotf = 'X'.
   ls_otpt_opt-tdnoprev = 'X'.
    ls_otpt_opt-tdnewid = ''.
    ls_otpt_opt-tdimmed = 'X'.
    ls_otpt_opt-tddest = 'LP01'.
    CALL FUNCTION fname
      EXPORTING
    ARCHIVE_INDEX              =
    ARCHIVE_INDEX_TAB          =
    ARCHIVE_PARAMETERS         =
       control_parameters         = ls_control_param
    MAIL_APPL_OBJ              =
    MAIL_RECIPIENT             =
    MAIL_SENDER                =
       output_options             = ls_otpt_opt
       user_settings              = 'X'
        mat_slip_hdr               = itab3
   IMPORTING
    DOCUMENT_OUTPUT_INFO       =
     JOB_OUTPUT_INFO            = ls_job_info
    JOB_OUTPUT_OPTIONS         =
      TABLES
        mat_slip                   = itab2
EXCEPTIONS
    FORMATTING_ERROR           = 1
    INTERNAL_ERROR             = 2
    SEND_ERROR                 = 3
    USER_CANCELED              = 4
    OTHERS                     = 5
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDLOOP.
ENDFORM.

Hi saswat mohanty ,
Welcome to SDN. Ya your program takes lot of time to give the output becauase of more select endselects in a loop.
You are hitting as many times as the records in the ITAB.
Instead use "for all entries"   clause for fetching the complete data from a table atonce.
Example: your itab is there.
Select * from xyz
   into table itab2
   for all entries in itab
where field1 eq itab-field1
    and field2 eq itab-field2.
After fetching the data you can populate the final table by looping through ITAB and itab2.
This is best procedure to reduce the load on database.
Implement this in your program to improve performance.
REWARD POINTS IF USEFUL.
Venkat.

Improve performance on statement select endselect retrieval on tables

Hi Experts,
Good day!
May I ask some help regarding a custom program on how to improve the retrieval on tables using select endselect.
    SELECT atinn INTO v_abv_classification
    UP TO 1 ROWS FROM cabn WHERE atnam = c_abv.
    ENDSELECT.
    CHECK sy-subrc = 0.
    CLEAR ausp.
    SELECT clint INTO kssk-clint
      FROM kssk
      WHERE objek EQ l_matnr
        AND mafid EQ c_o
        AND klart EQ c_001.
      SELECT imerk klart INTO (ksml-imerk, ksml-klart)
        FROM ksml
        WHERE clint EQ kssk-clint
          AND imerk = v_abv_classification.
        SELECT atwrt INTO ausp-atwrt
          FROM ausp
          WHERE objek EQ l_matnr
            AND atinn EQ ksml-imerk
            AND mafid EQ c_o
            AND klart EQ ksml-klart.
        ENDSELECT.
        EXIT.
      ENDSELECT.
      EXIT.
    ENDSELECT.
Answer's will be a great help.
~God Bless,
Lourd

eidting is half of the solution:
SELECT atinn
             INTO v_abv_classification
             FROM cabn
            WHERE atnam = c_abv
            UP TO 1 ROWS
ENDSELECT.
CHECK sy-subrc = 0.
CLEAR ausp.
SELECT clint
              INTO kssk-clint
              FROM kssk
              WHERE objek EQ l_matnr
              AND mafid EQ c_o
              AND klart EQ c_001.
SELECT imerk klart
              INTO (ksml-imerk, ksml-klart)
              FROM ksml
              WHERE clint EQ kssk-clint
              AND imerk = v_abv_classification.
SELECT atwrt
              INTO ausp-atwrt
              FROM ausp
              WHERE objek EQ l_matnr
              AND atinn EQ ksml-imerk
              AND mafid EQ c_o
             AND klart EQ ksml-klart.
ENDSELECT.
EXIT.
ENDSELECT.
EXIT.
ENDSELECT.
I do not really understand the logic of the nesting, because the handling of the result is missing. Which SELECT can find several records? Or are these only SELECT UP TO 1 ROWS not nested but in a sequence?
Siegfried

Report on Smartform..To make it efficient by removing SELECT ,ENDSELECT

To make a smartform report efficient by removing all occurs & modify internal table statements.
What i have been given to do is to select all data from respective tables put them into one internal table & then finally making tab2 or tab3 in the report to be the final table.I am not sure which among these two i can make final table.
THE CODE is:
REPORT zgr_note.
TABLES : mseg, "Document Segment : Material
         prps, "WBS element master data
         proj, "Project Definition
         mkpf, "Header : Material Document
         lfa1, "Vendor Master
         makt, "Material Description
         aufk, "Order Master Data
         afvc. "Operation within an order
DATA : fname LIKE rs38l-name. "Name of Function Module
DATA: lf_fm_name            TYPE rs38l_fnam.
DATA: ls_control_param      TYPE ssfctrlop.
DATA: ls_composer_param     TYPE ssfcompop.
DATA: ls_recipient          TYPE swotobjid.
DATA: ls_sender             TYPE swotobjid.
DATA: lf_formname           TYPE tdsfname.
DATA: ls_addr_key           LIKE addr_key.
DATA: ls_dlv_land           LIKE vbrk-land1.
DATA: ls_job_info           TYPE ssfcrescl.
DATA: ls_otpt_opt           TYPE ssfcompop.
DATA: retcode TYPE sy-subrc.
DATA: cntr TYPE i VALUE 0.
DATA: cntr1 TYPE i .
DATA: number TYPE SSFCRESCL-SPOOLIDS. " OCCURS 0 WITH HEADER LINE.
DATA: TSP01 type TABLE OF TSP01_SP0R.
DATA : BEGIN OF itab OCCURS 0.
        INCLUDE STRUCTURE mseg.
DATA : post1 LIKE proj-post1,           "Project Definition
       pspnr LIKE proj-pspnr,           "WBS element
       maktx LIKE makt-maktx,           "Material Description
       name1 LIKE lfa1-name1,           "Name of the supplier
       budat LIKE mkpf-budat,           "Posting date
       bldat LIKE mkpf-bldat,           "Document date
       cpudt LIKE mkpf-cpudt,           "Date on which account document was entered
       psphi LIKE prps-psphi,           "Current number of project
       post2 LIKE prps-post1,           "WBS Definition
       xblnr LIKE mkpf-xblnr,           "Reference number( in this case challan number)
       bktxt LIKE mkpf-bktxt,           "Header text
       ort01 LIKE lfa1-ort01,           "vendor city
       ktext LIKE aufk-ktext,           "network description
       ltxa1 LIKE afvc-ltxa1.           "operation short text
DATA : END OF itab.
DATA : BEGIN OF jtab OCCURS 0.
        INCLUDE STRUCTURE itab.
DATA : END OF jtab.
DATA : itab1 LIKE itab OCCURS 0
      WITH HEADER LINE.
DATA :itab2 LIKE itab OCCURS 0
      WITH HEADER LINE.
DATA: itab3 LIKE itab OCCURS 0 WITH HEADER LINE.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text_001.
SELECT-OPTIONS : gr_num FOR mseg-mblnr . "no INTERVALS.
PARAMETERS : gr_note LIKE itemset-xopsel RADIOBUTTON GROUP rad1.
SELECTION-SCREEN SKIP.
SELECT-OPTIONS : mat_num FOR mseg-mblnr . "no INTERVALS.
PARAMETERS : mat_slip LIKE itemset-xopsel RADIOBUTTON GROUP rad1.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN SKIP.
CASE 'X'.
WHEN gr_note.
    PERFORM gr_display.
WHEN mat_slip.
    PERFORM mat_display.
ENDCASE.
FORM gr_display .
*break developer1.
SELECT mblnr mjahr matnr werks lgort lifnr menge meins
         erfmg bpmng ebeln ps_psp_pnr zeile lsmng erfme
FROM mseg
INTO CORRESPONDING FIELDS OF TABLE itab
   WHERE mblnr IN gr_num.
LOOP AT itab.
    SELECT pspnr psphi post1 INTO CORRESPONDING FIELDS OF itab1
      FROM prps WHERE pspnr = itab-ps_psp_pnr.
      itab-psphi = itab1-psphi.
      itab-pspnr = itab1-pspnr.
      itab-post2 = itab1-post1.
      MODIFY itab TRANSPORTING psphi pspnr post2.
    ENDSELECT.
    SELECT post1 FROM proj INTO CORRESPONDING FIELDS OF itab2
    WHERE pspnr = itab-psphi.
      itab-post1 = itab2-post1.
      MODIFY itab TRANSPORTING post1.
    ENDSELECT.
    REFRESH itab2.
    SELECT maktx FROM makt INTO CORRESPONDING FIELDS OF itab2
      WHERE matnr = itab-matnr.
      itab-maktx = itab2-maktx.
      MODIFY itab TRANSPORTING maktx.
    ENDSELECT.
    REFRESH itab2.
    SELECT name1 ort01 FROM lfa1 INTO CORRESPONDING FIELDS OF itab2
      WHERE lifnr = itab-lifnr.
      itab-name1 = itab2-name1.
      itab-ort01 = itab2-ort01.
      MODIFY itab TRANSPORTING name1 ort01.
    ENDSELECT.
    REFRESH itab2.
    SELECT budat bldat cpudt xblnr bktxt FROM mkpf
      INTO CORRESPONDING FIELDS OF itab2
      WHERE mblnr = itab-mblnr.
      itab-budat = itab2-budat.
      itab-bldat = itab2-bldat.
      itab-cpudt = itab2-cpudt.
      itab-xblnr = itab2-xblnr.
      itab-bktxt = itab2-bktxt.
      MODIFY itab TRANSPORTING budat bldat cpudt xblnr bktxt.
    ENDSELECT.
ENDLOOP.
LOOP AT itab .
    ON CHANGE OF itab-mblnr.
      itab3-mblnr = itab-mblnr.
      itab3-post1 = itab-post1.
      itab3-post2 = itab-post2.
      itab3-name1 = itab-name1.
      itab3-ort01 = itab-ort01.
      itab3-bldat = itab-bldat.
      APPEND itab3.
      CLEAR itab3.
    ENDON.
ENDLOOP.
jtab-mblnr = itab-mblnr.
jtab-xblnr = itab-xblnr.
jtab-budat = itab-budat.
jtab-bktxt = itab-bktxt.
jtab-lsmng = itab-lsmng.
jtab-erfmg = itab-erfmg.
jtab-erfme = itab-erfme.
jtab-matnr = itab-matnr.
jtab-maktx = itab-maktx.
jtab-zeile = itab-zeile.
APPEND jtab.
LOOP AT itab3.
    CLEAR: itab2,itab2[].
    LOOP AT itab WHERE mblnr = itab3-mblnr.
      MOVE-CORRESPONDING itab TO itab2.
      APPEND itab2.
      CLEAR itab2.
    ENDLOOP.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        formname                 = 'ZMM_GOODS_RECEIPT1'
VARIANT                  = ' '
DIRECT_CALL              = ' '
     IMPORTING
       fm_name                  = fname
EXCEPTIONS
NO_FORM                  = 1
NO_FUNCTION_MODULE       = 2
OTHERS                   = 3
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
*break developer1.
PERFORM print_parameters.
    CALL FUNCTION fname
      EXPORTING
       control_parameters         = ls_control_param
       output_options             = ls_otpt_opt
       user_settings              = 'X'
       gr_mseg_hdr                = itab3
IMPORTING
DOCUMENT_OUTPUT_INFO       =
JOB_OUTPUT_INFO            =
JOB_OUTPUT_OPTIONS         =
      TABLES
        gr_mseg                    = itab2
     EXCEPTIONS
       formatting_error           = 1
       internal_error             = 2
       send_error                 = 3
       user_canceled              = 4
       OTHERS                     = 5
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDLOOP.
ENDFORM.                    " GR_DISPLAY
FORM mat_display .
SELECT mblnr mjahr matnr werks lgort lifnr menge meins
         erfmg bpmng ebeln ps_psp_pnr zeile lsmng erfme
         mat_pspnr nplnr aufpl aplzl
FROM mseg
INTO CORRESPONDING FIELDS OF TABLE itab
   WHERE mblnr IN mat_num.
LOOP AT itab.
    SELECT ltxa1 FROM afvc INTO CORRESPONDING FIELDS OF itab1
      WHERE aufpl = itab-aufpl AND aplzl = itab-aplzl.
      itab-ltxa1 = itab1-ltxa1.
      MODIFY itab TRANSPORTING ltxa1.
    ENDSELECT.
    REFRESH itab1.
    SELECT ktext FROM aufk INTO CORRESPONDING FIELDS OF itab1
      WHERE aufnr = itab-nplnr.
      itab-ktext = itab1-ktext.
      MODIFY itab TRANSPORTING ktext.
    ENDSELECT.
    REFRESH itab1.
    SELECT pspnr psphi post1 INTO CORRESPONDING FIELDS OF itab1
      FROM prps WHERE pspnr = itab-mat_pspnr.
      itab-psphi = itab1-psphi.
      itab-pspnr = itab1-pspnr.
      itab-post2 = itab1-post1.
      MODIFY itab TRANSPORTING psphi pspnr post2.
    ENDSELECT.
    SELECT post1 FROM proj INTO CORRESPONDING FIELDS OF itab2
    WHERE pspnr = itab-psphi.
      itab-post1 = itab2-post1.
      MODIFY itab TRANSPORTING post1.
    ENDSELECT.
    REFRESH itab2.
    SELECT maktx FROM makt INTO CORRESPONDING FIELDS OF itab2
      WHERE matnr = itab-matnr.
      itab-maktx = itab2-maktx.
      MODIFY itab TRANSPORTING maktx.
    ENDSELECT.
    REFRESH itab2.
    SELECT name1 ort01 FROM lfa1 INTO CORRESPONDING FIELDS OF itab2
      WHERE lifnr = itab-lifnr.
      itab-name1 = itab2-name1.
      itab-ort01 = itab2-ort01.
      MODIFY itab TRANSPORTING name1 ort01.
    ENDSELECT.
    REFRESH itab2.
    SELECT budat bldat cpudt xblnr bktxt FROM mkpf
      INTO CORRESPONDING FIELDS OF itab2
      WHERE mblnr = itab-mblnr.
      itab-budat = itab2-budat.
      itab-bldat = itab2-bldat.
      itab-cpudt = itab2-cpudt.
      itab-xblnr = itab2-xblnr.
      itab-bktxt = itab2-bktxt.
     break developer1.
      MODIFY itab TRANSPORTING budat bldat cpudt xblnr bktxt.
    ENDSELECT.
ENDLOOP.
LOOP AT itab.
    ON CHANGE OF itab-mblnr.
      itab3-mblnr = itab-mblnr.
      itab3-budat = itab-budat.
      itab3-bldat = itab-bldat.
      itab3-post1 = itab-post1.
      itab3-ktext = itab-ktext.
      APPEND itab3.
      CLEAR itab3.
    ENDON.
ENDLOOP.
LOOP AT itab3.
    CLEAR: itab2, itab2[].
    LOOP AT itab WHERE mblnr EQ itab3-mblnr.
      MOVE-CORRESPONDING itab TO itab2.
      APPEND itab2.
      CLEAR itab2.
    ENDLOOP.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        formname                 = 'ZMM_MAT_ISSUE_SLIP'
VARIANT                  = ' '
DIRECT_CALL              = ' '
     IMPORTING
       fm_name                  = fname
EXCEPTIONS
NO_FORM                  = 1
NO_FUNCTION_MODULE       = 2
OTHERS                   = 3
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ls_control_param-no_dialog = 'X'.
*ls_control_param-preview = 'X'.
*ls_control_param-getotf = 'X'.
   ls_otpt_opt-tdnoprev = 'X'.
    ls_otpt_opt-tdnewid = ''.
    ls_otpt_opt-tdimmed = 'X'.
    ls_otpt_opt-tddest = 'LP01'.
    CALL FUNCTION fname
      EXPORTING
    ARCHIVE_INDEX              =
    ARCHIVE_INDEX_TAB          =
    ARCHIVE_PARAMETERS         =
       control_parameters         = ls_control_param
    MAIL_APPL_OBJ              =
    MAIL_RECIPIENT             =
    MAIL_SENDER                =
       output_options             = ls_otpt_opt
       user_settings              = 'X'
        mat_slip_hdr               = itab3
   IMPORTING
    DOCUMENT_OUTPUT_INFO       =
     JOB_OUTPUT_INFO            = ls_job_info
    JOB_OUTPUT_OPTIONS         =
      TABLES
        mat_slip                   = itab2
EXCEPTIONS
    FORMATTING_ERROR           = 1
    INTERNAL_ERROR             = 2
    SEND_ERROR                 = 3
    USER_CANCELED              = 4
    OTHERS                     = 5
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDLOOP.
ENDFORM.

Hello Saswat,
There are a couple of criteria to make a SmartForm report efficient, i.e. to achieve a better performance:
- provide the best possible interface to the temporary FM (fname). When you do so, SmartForm itself has not to perform so much programming stuff by itself.
- The Driver program (zgr_note) has to be designed and coded well. What mean the performance of the Driver has to be optimized. In your case there should be a couple of performance improvements:
-- adjust your program declaration to the new ABAP syntax, i.e. don't use OCCURS clauses and do not use HEADER LINE. Instead, implement TYPES and use them. Here is an example:
TYPES: BEGIN OF ty_itab.
             INCLUDE STRUCTURE mseg.
TYPES: post1 LIKE proj-post1, "Project Definition
             pspnr LIKE proj-pspnr, "WBS element
             maktx LIKE makt-maktx, "Material Description
             name1 LIKE lfa1-name1, "Name of the supplier
             budat LIKE mkpf-budat, "Posting date
             bldat LIKE mkpf-bldat, "Document date
             cpudt LIKE mkpf-cpudt, "Date on which account document was entered
             psphi LIKE prps-psphi, "Current number of project
             post2 LIKE prps-post1, "WBS Definition
             xblnr LIKE mkpf-xblnr, "Reference number( in this case challan number)
             bktxt LIKE mkpf-bktxt, "Header text
             ort01 LIKE lfa1-ort01, "vendor city
             ktext LIKE aufk-ktext, "network description
             ltxa1 LIKE afvc-ltxa1, "operation short text
             END OF ty_itab.
* Declare your internal tables and the corresponding working structures
DATA: itab1 type standard table of ty_itab,
           itab2 type standard table of ty_itab,
           itab3 type standard table of ty_itab,
           jtab type standard table of ty_itab,
          wa_itab1 type ty_itab,
          wa_itab2 type ty_itab,
          wa_itab3 type ty_itab,
          wa_jtab   type ty_itab.
-- Don't use
LOOP at itab.
SELECT ...... WHERE pspnr = itab-ps_psp_pnr.
ENDSELECT.
SELECT * ...
ENDSELECT
SELECT * .....
ENDSELECT
ENDLOOP.
Instead try to populate itab, itab1, itab2 each in ONE select statement using FOR ALL ENTRIES clause. After that you have to perform the LOOP runs using LOOP at itab INTO wa_itab. The more redundant SELECTs, the slower the program! When you perform a LOOP run, let say over itab1 and you need a corresponding record from table itab2 the use READ <itab> with key.
One additional, very important hint: Using internal tables w/o header line the CLEAR statement has another functionality than with HEADER LINE
CLEAR with HEADER LINE clears the HEADER line only
CLEAR w/o HEADER LINE clears the entire table. CLEAR does the same as REFRESH.
Another performance improvement is (when itab contains a lot of records) using FIELD-SYMBOLS.
A simple example is
FIELD-SYMBOLS: <fs> type itab.
LOOP at itab assigning <fs>.
wa_itab3-post1 = <fs>-post1.
wa_itab3-post2 = <fs>-post2.
APPEND wa_itab3 to itab.
ENDLOOP.
In this case no data values have to be transfered to a working field. The values are taken directly from the current line of the internal table.
-- For better readability disign some events like START-OF-SELECTION, END-OF-SELECTION, INITIALIZATION and others.
Try to gather all in SmartForms needed fields and pop them into table itab3.
I hope this helps improving zgr_note's efficiency.
Good luck,
Heinz

How to determine package size dynamically for select - endselect statement in ABAP

Hi All,
I was using select- edselect with package size but i have hard coding the package size. Can any one tell me the the process to determine dynamic package size so that i can use in parallel processing.

Hi,
If you are looking to determine or set the value of package size dynamically then use below code for reference.
DATA: itab TYPE TABLE OF spfli,
       wa like LINE OF itab,
       n    TYPE i.
n = 10.
SELECT carrid connid
FROM   spfli
INTO   CORRESPONDING FIELDS OF TABLE itab
PACKAGE SIZE n.
   LOOP AT itab INTO wa.
     WRITE: / wa-carrid, wa-connid.
   ENDLOOP.
ENDSELECT.
If you are concerned about the performance then either use SELECT with OPEN CURSOR and CLOSE CURSOR.
Let me know if it helped?
Regards,
Zuber

ERROR while debugging a SELECT..ENDSELECT

Hello All,
We get an error while we go into the select..endselect loop during debugging. Because of this if we try to do some research on existing program with Select-endselect..it fails in the second pass of this loop.
This problem was not there earlier, but after we upgraded from 4.6 to 4.7 this problem is bugging us..every day. Does any one have a clue why ?
Thanks!!
Regards,
Vishal

Hi,
debugging a SELECT...ENDSELECT statements brings to a LUW commit work if no other work processes are available for debug.
See OSS notes 675, 2104.
From OSS note 675 **********************************
Cause and prerequisites
Chain of causes:
      1. There is a statement in one of the Select loops, that leads to a database Commit (or Rollback).
      2. A database Commit causes the database to lose the cursor.
      3. The system cannot automatically continue within Select loop after loss of cursor.
Following statements lead to a database Commit:
    * All statements that cause a change of screen (CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT, I/W-Message)
    * BREAK-POINT/ Debugging
      . if no debug process free
      . always after regeneration (in order to release generation lock).
    * WAIT Here a work process is released and a Commit is executed.
    * COMMIT WORK/ROLLBACK WORK
From OSS note 2104 **********************************
Solution
The "COMMITWORK" message appears in the ABAP debugger when programs
orscreensrequireregeneration,or when not enough free capacity
is available inthesystem (or else the debugger blocks a system
process).
Normallyonly one work process is released for debugging. This
isgenerally insufficient ina developmentsystem, as processes
can be blocked for other reasonstoo(background processing,
CPI-C connections,andso on).
The number of work processes made available for debugging can
be configured using the profileparameter
                  rdisp/wpdbug_max_no
Forexample:
                rdisp/wpdbug_max_no = 10
setsthe maximum number of work processes made available for
debuggingto 10. It may be necessary to generally increase the
numberofwork processesatthis time (parameter rdisp/wp_no_dia).
In all other known cases, an error in the application program is
involved.
Regards, Manuel

What is the use of additon in up to 1 rows in SELECT statement

Hi All,
         What is the use of up to 1 rows in select statement.
for example
SELECT kostl
      FROM pa0001
      INTO y_lv_kostl UP TO 1 ROWS
      WHERE pernr EQ pernr
      AND endda GE sy-datum.
    ENDSELECT.
I'm unable to get in wat situations we hav to add up to 1 rows
please help me out...
Thanks,
santosh.

Hi,
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Regards,
Bhaskar

Problem while selecting BELNR from BSEG

Hi Experts,
I have a report performance problem while fetching BELNR from BSEG table.
I have to print latest BELNR from BSEG where BUZID = M but at the time of execution of report, It is taking too much time (More that hour and sometimes it gets hanged).
I have also gone through the comments provided by experts for previous problems asked in this forum e.g. BSEG is a cluster table that is why data retrieval takes long time etc.
Can any one has any other idea or suggestion or any other way to solve this problem
Regards,
Neeraj

Hi,
1) Try to create an index on BUZID field
2) Don't use SELECT/ENDSELECT statement. Instead of that extract all the concerned entries from BSEG into an internal table :
select belnr from bseg appending table itab where buzid = 'M'.
then do this :
sort itab by belnr.
describe itab lines n.
read table itab index n.
Please reward if helpful.
Regards,
Nicolas.

Error: Invalid interruption of a database selection

Hi,
When i execute the below code, the output is displayed without any problem.
<b>tables lfa1.
select * from lfa1 order by lifnr.
write / lfa1-lifnr.
endselect.</b>
But however when i debug this piece of code, i get an error as below.
ShrtText - Invalid interruption of a database selection
Runtime Errors - DBIF_RSQL_INVALID_CURSOR
Exceptn - CX_SY_OPEN_SQL_DB
Can anybody help me with the reason for the occurence of this problem.

Hi Vijay,
Just go through the following link:
Re: DBIF_RSQL_INVALID_CURSOR dump during debugging
As Sooness pointed out, SELECT-ENDSELECT dumps only the first time. Try re-executing it and it will work fine.
Meanwhile, it is always better to use INTO TABLE OF instead of SELECT-ENDSELECT, as this minimizes database hits.
Regards
Anil Madhavan

DBIF_RSQL_INVALID_CURSOR: Invalid interruption of a database selection.

I have created an external program that extracts a very large table from SAP 7.0 through RFC using the NetWeaver SDK APIs. This program repeatedly calls an RFC-enabled function written in ABAP. On the first
call the function does "OPEN CURSOR WITH HOLD" and a "FETCH". On each subsequent call the function does a "FETCH". The cursor is declared as "STATICS".
When I run the program I am getting the following error:
DBIF_RSQL_INVALID_CURSOR: Invalid interruption of a database selection.
This error manifests itself in two ways.
1) When time interval between RfcInvoke() calls is about 0.5 sec., it takes 30 sec. to 90 sec. for the error to come out.
2) When time interval between RfcInvoke() calls is about 0.2 sec. or lower, it takes 8 min. to 17 min. for the error to come out, but sometimes the program completes successfully in 25 min.
1) What is causing this error?
2) If it has something to do with SAP configuration, how it be modified to extract this particular table.
3) Is it possible in general to extract a table of any size (on the magnitude of gigabytes) using such an approach, that is, a "pull".
4) If the answer is negative, what approach do you think is appropriate.
Any help will be appreciated.

Hi Andrew Coleman ,
This error sounds like problem is in the way you are calling the RFC Function module (n -number of times). Looks like during the subsequent calls the Select / ENDSELECT is failing need to check that logic.
Thanks,
Greetson

Regarding performance issue in SELECT - need suggestions

Moderator message - use a more informative subject in future - having two or more posts with the same subject isn't helpful
Hi All could you plese send me the alternative code for this select quesy:
form read_data_from_GIPD.
select * from zbacks_gipd
    where failf = '2'
      and recno in recno.
    clear tab.
    clear result_total. "reset the record counter
    tab-werks = zbacks_gipd-WERKS.         "plant
    tab-aufnr = zbacks_gipd-AUFNR.         "production order no.
    tab-matnr = zbacks_gipd-MATNR.         "material
    tab-erdat = zbacks_gipd-BUDAT.         "transaction date
    tab-recno = zbacks_gipd-recno.
    TAB-MENGE = zbacks_gipd-menge.         "qty
    TAB-USAFL = zbacks_gipd-usafl.         "usage/consumption ind.
*          TAB-EXPCD            "Expenses code
    TAB-SAKNR = zbacks_gipd-saknr.         "G/L account number
    TAB-IDNUM = zbacks_gipd-idnum.         "BACKS identification no.
    TAB-KUNNR = zbacks_gipd-kunnr.         "Customer Number
    TAB-USACD = zbacks_gipd-usacd.         "usage code
    TAB-ORDCD = zbacks_gipd-ordcd.         "order code
    TAB-LOSTY = zbacks_gipd-losty.         "loss type
    TAB-COTAX = zbacks_gipd-cotax.         "consumption tax
    TAB-MWSKZ = zbacks_gipd-mwskz.         "tax code
    tab-runum = zbacks_gipd-runum.         "running number
    tab-failf = zbacks_gipd-failf.     "failure flag
    tab-msgnr = zbacks_gipd-failf.     "failure flag
    tab-matdoc = zbacks_gipd-docm1.    "material doc
* BEGIN OF SR#20293 WITH DEVK955638
*    tab-msgtx = 'Repost 2nd step'.
    tab-msgtx = 'Repost 2nd step'(057).
*   END OF SR#20293 WITH DEVK955638
*    tab-erdat_raw = tab-erdat. "keep the MM/DD/YYYY format
*    CONCATENATE TAB-ERDAT+6(4) TAB-ERDAT+0(2) TAB-ERDAT+3(2)
*           INTO TAB-ERDAT.
     concatenate tab-erdat+4(2) '/'
                 tab-erdat+6(2) '/'
                 tab-erdat+0(4)
               into tab-erdat_raw.
*Process only a particular set of usage indicator first
    if tab-usafl = p_usafl.
      APPEND TAB.
      result_total = result_total + 1. "Increase the record counter
    endif.
endselect.
* BEGIN OF SR#20293 WITH DEVK955638
* write: / 'Re-processing records for usage indicator', p_usafl.
write: / 'Re-processing records for usage indicator'(056), p_usafl.
* END OF SR#20293 WITH DEVK955638
endform.
Note : how can i avoid the select endselect statement , here he move data from database table to internal table .
Edited by: Julius Bussche on Jan 19, 2009 1:52 PM
Please use code tags
Edited by: Matt on Jan 19, 2009 4:46 PM

Hi,
     Declare an Internal table with zbacks_gipd type,
     Move the records into that table based on conditions,
     Then loop that internal table, and fill tab internal table.
form read_data_from_GIPD.
Types : begin of ty_zbacks_gipd.
             include structure zbacks_gipd.
Types : end of ty_zbacks_gipd.
Data : it_zbacks_gipd type table of ty_zbacks_gipd,
             wa_zbacks_gipd type ty_zbacks_gipd.
select * from zbacks_gipd into table it_zbacks_gipd
       where failf = '2'
      and recno in recno.
loop at it_zbacks_gipd into wa_zbacks_gipd.
clear tab.
    clear result_total. "reset the record counter
    tab-werks = wa_zbacks_gipd-WERKS.         "plant
    tab-aufnr = wa_zbacks_gipd-AUFNR.         "production order no.
    tab-matnr = wa_zbacks_gipd-MATNR.         "material
    tab-erdat = wa_zbacks_gipd-BUDAT.         "transaction date
    tab-recno = wa_zbacks_gipd-recno.
    TAB-MENGE = wa_zbacks_gipd-menge.         "qty
    TAB-USAFL = wa_zbacks_gipd-usafl.         "usage/consumption ind.
*          TAB-EXPCD            "Expenses code
    TAB-SAKNR = wa_zbacks_gipd-saknr.         "G/L account number
    TAB-IDNUM = wa_zbacks_gipd-idnum.         "BACKS identification no.
    TAB-KUNNR = wa_zbacks_gipd-kunnr.         "Customer Number
    TAB-USACD = wa_zbacks_gipd-usacd.         "usage code
    TAB-ORDCD = wa_zbacks_gipd-ordcd.         "order code
    TAB-LOSTY = wa_zbacks_gipd-losty.         "loss type
    TAB-COTAX = wa_zbacks_gipd-cotax.         "consumption tax
    TAB-MWSKZ = wa_zbacks_gipd-mwskz.         "tax code
    tab-runum = wa_zbacks_gipd-runum.         "running number
    tab-failf = wa_zbacks_gipd-failf.     "failure flag
    tab-msgnr = wa_zbacks_gipd-failf.     "failure flag
    tab-matdoc = wa_zbacks_gipd-docm1.    "material doc
* BEGIN OF SR#20293 WITH DEVK955638
*    tab-msgtx = 'Repost 2nd step'.
    tab-msgtx = 'Repost 2nd step'(057).
*   END OF SR#20293 WITH DEVK955638
*    tab-erdat_raw = tab-erdat. "keep the MM/DD/YYYY format
*    CONCATENATE TAB-ERDAT+6(4) TAB-ERDAT+0(2) TAB-ERDAT+3(2)
*           INTO TAB-ERDAT.
     concatenate tab-erdat+4(2) '/'
                 tab-erdat+6(2) '/'
                 tab-erdat+0(4)
               into tab-erdat_raw.
*Process only a particular set of usage indicator first
    if tab-usafl = p_usafl.
      APPEND TAB.
      result_total = result_total + 1. "Increase the record counter
    endif.
endloop.
endform.
Regards
Bala Krishna
Edited by: Bala Krishna on Jan 19, 2009 6:48 PM

Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query

Hi All,
There is a Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query in a report painter.
This query is working fine when executed in 4.7 system where as it is running for more time in ECC6.0.
Select query is on the table COSP.
SELECT (FIELD_LIST)
        INTO CORRESPONDING FIELDS OF TABLE I_COSP PACKAGE SIZE 1000
        FROM COSP CLIENT SPECIFIED
        WHERE GJAHR IN SELR_GJAHR
          AND KSTAR IN SELR_KSTAR
          AND LEDNR EQ '00'
          AND OBJNR IN SELR_OBJNR
          AND PERBL IN SELR_PERBL
          AND VERSN IN SELR_VERSN
          AND WRTTP IN SELR_WRTTP
          AND MANDT IN MANDTTAB
        GROUP BY (GROUP_LIST).
   LOOP AT I_COSP      .
     COSP                           = I_COSP      .
     PERFORM PCOSP       USING I_COSP-_COUNTER.
     CLEAR: $RWTAB, COSP                          .
     CLEAR CCR1S                         .
   ENDLOOP.
ENDSELECT.
I have checked with the table indexes, they were same as in 4.7 system.
What can be the reson for the difference in execution time. How can this be reduced without adjusting the select query.
Thanks in advance for the responses.
Regards,
Dedeepya.

Hi,
ohhhhh....... lots of problems in select query......this is not the way you should write it.
Some generic comments:
1. never use SELECT
                   endselect.
   SELECT
into table
   for all entries in table
where.
   use perform statment after this selection.
2. Do not use into corresponding fields. use exact structure type.
3. use proper sequence of fields in the where condition so that it helps table go according to indexes.
    e.g in your case
          sequence should be
LEDNR
OBJNR
GJAHR
WRTTP
VERSN
KSTAR
HRKFT
VRGNG
VBUND
PARGB
BEKNZ
TWAER
PERBL
sequence should be same as defined in table.
Always keep select query as simple as possible and perform all other calculations etc. afterwords.
I hope it helps.
Regards,
Pranaya

Query in select statment

Hi ,
what is the difference between,select single and
select upto one row .
In a select statment .
Thanks ,
shankar.

According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not
using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key,
it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key
supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s)
you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the
second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional
level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause
If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that
are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns
the first record of the result set.
Mainly: to check if entries exist.
You can refer to the below link..
http://www.sap-img.com/abap/difference-between-select-single-and-select-upto-one-rows.htm

Select-endselect

Similar Messages

Maybe you are looking for