Number of lines of a select query

I want only the number of lines from a result of a select query.
How can i get this?
Greetings Volker

Hi Volkar,
When you extract the data from Database into an internal table, use the DESCRIBE TABLE syntax for fetching the number of lines returned.
Syntax :
DESCRIBE TABLE ITAB lines l_lines.
where l_lines is the no. of lines returned.
Hope this will resolve your query.
Reward all the helpful answers.
Regards
Nagaraj T

Similar Messages

How to get number of rows return in SELECT query

i'm very new in java, i have a question:
- How to get number of rows return in SELECT query?
(i use SQL Server 2000 Driver for JDBC and everything are done, i only want to know problems above)
Thanks.

make the result set scroll insensitve, do rs.last(), get the row num, and call rs.beforeFirst(), then you can process the result set like you currently do.
         String sql = "select * from testing";
         PreparedStatement ps =
          con.prepareStatement(sql,ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
         ResultSet rs = ps.executeQuery();
         rs.last();
         System.out.println("Row count = " + rs.getRow());
         rs.beforeFirst();~Tim
NOTE: Ugly, but does the trick.

Regarding nor of line items selected in per select query..

hi,
i want to display nor of line items selected in per select query for two individual queries which are linkesd by for all entries..
regards..
chetan

Hi,
I dont unserstand the problem you are facing. please paste your SELECT query and then explain the problem. then it will be easy for analysis.
Basically DESCRIBE TABLE itab LINES n. this statement will put the number of lines the internal table contains
//Kothand

Select query in case of Multiple line items

Hi Gurus ,
 I've a doubt in general SQL select query. I want to know , if suppose I've an internal table - itab . I've fetched G/L Account numbers 1st, based on the input selections . Next , I want to loop on those G/L accounts. However, if the G/L account has multiple line items, then I personally use this select query -- >
loop at itab.
select <field> from <table> appending corresponding fields of <itab1> where hkont eq itab-hkont.
endloop.
Now, the execution time for this query is longer than expected. The biggest problem here is, i've to sum up the totals as well. So totaling is an added load. I want to reduce the execution time of this. Kindly suggest me some good method in case u have any.
I've pasted the code which I've written , for u ppl to understand--
SELECT DISTINCT HKONT BELNR
FROM BSIS
 INTO CORRESPONDING FIELDS OF TABLE OTAB
 WHERE HKONT IN S_RACCT
* AND PRCTR IN P_PRCTR
 AND MONAT IN S_POPER
 AND BUKRS EQ P_BUKRS
 AND GJAHR EQ P_GJAHR
 AND PRCTR IN S_PRCTR.
***The code below takes a lot of time to execute.***
LOOP AT OTAB .
SELECT DMBTR HKONT
FROM BSIS APPENDING CORRESPONDING FIELDS OF TABLE CREDITS
 WHERE HKONT EQ OTAB-HKONT
 AND BELNR EQ OTAB-BELNR
 AND MONAT IN S_POPER
 AND BUKRS EQ P_BUKRS
 AND GJAHR EQ P_GJAHR
 AND PRCTR IN S_PRCTR
 AND SHKZG EQ 'H'.
COLLECT CREDITS.
ENDLOOP.

Hi,
First of all try to avoid doing select into corresponding fields. THis would improve the performance of the program.
Try to do a single fetch from the BSIS table . fetch the hkont, belnr, dmbtr fields in to a master internal table. Manipulate and play with the data as required. Don't hit the data base table more than once (unless it is required) . This would improve the performance of your code.
Try to code this way.
types: begin of ty_bsis,
 hkont type hkont,
 belnr type belnr_d,
 dmbtr type dmbtr,
 end of ty_bsis.
data: it_bsis type standard table of ty_bsis,
 wa_bsis type ty_bsis,
select hkont belnr dmbtr
 from bsis
 into table it_bsis
 WHERE HKONT IN S_RACCT
 AND PRCTR IN P_PRCTR
 AND MONAT IN S_POPER
 AND BUKRS EQ P_BUKRS
 AND GJAHR EQ P_GJAHR
 AND PRCTR IN S_PRCTR.
Using the data availabe in the it_bsis, you can manipulate as required.
Hope this would be helpful
Regards
Ramesh Sundaram

Number of Lines limited in InfoPackage Selection?

Hello Experts!
I have 2 InfoPackage in order to load Data from ODS1 into ODS2. Selection is made for customer number - exact criteria is made via Abap Routine in InfoPackage. (InfoPackage 1 has all customers meeting a certain criteria - InfoPackage 2 has all the ranges in between the customer Numvers of InfoPackage 1).
Therefore the load of both InfoPackages should load all data - but the problem is, I only get a small part of the Data. In ODS 1 there are some 2.800.000 entries and in ODS2 the load of the 2 InfoPackages only select about 30.000 entries.
Since the selection criteria in monitoring seem fine - do you have any idea where the problem comes from? Is there a max. number of lines for selection to be made in infoPackage?
Thanks for your help!
Angelika

Hi Angelika,
check out the monitor --> in the request tree check the numbers coming into the update rules an coming out of the update rules, may be you are loosing some records there. The only thing that I know about the size of selections is that you will get a dump if you have to many entries in a select-option table (and having those lines in a infopackage is nothing else).
Another reason might be a missing alpha conversion of the entries in the infopackage.
kind regards
Siggi

CohQL command line Tool select query output in file (unix)

Ho to insert Coherence CohQL command line Tool select query result in file in unix platform. I have tried below query but failed
query.cmd -s -c -l "select * from 'dist-example'" >myOutput.txt
I also tried below query, result is displayed in command line but no file is created in folder.
select * from dist-example >myOutput.txt
I also tried one more query, result is displayed in command line but no file is created in folder.
select * from dist-example >/opt/bin/myOutput.txt

Hi,
In Unix you should use query.sh instead of query.cmd
In your case then the command would be smething like:
query.sh -s -c -l "select * from 'dist-example'" >myOutput.txt
You can also try using '>>' instead of '>' in order to redirect to a text file.
Hope this helps.
-Cris

How to optimize the select query that is executed in a cursor for loop?

Hi Friends,
I have executed the code below and clocked the times for every line of the code using DBMS_PROFILER.
CREATE OR REPLACE PROCEDURE TEST
AS
   p_file_id              NUMBER                                   := 151;
   v_shipper_ind          ah_item.shipper_ind%TYPE;
   v_sales_reserve_ind    ah_item.special_sales_reserve_ind%TYPE;
   v_location_indicator   ah_item.exe_location_ind%TYPE;
   CURSOR activity_c
   IS
      SELECT *
        FROM ah_activity_internal
       WHERE status_id = 30
         AND file_id = p_file_id;
BEGIN
   DBMS_PROFILER.start_profiler ('TEST');
   FOR rec IN activity_c
   LOOP
      SELECT DISTINCT shipper_ind, special_sales_reserve_ind, exe_location_ind
                 INTO v_shipper_ind, v_sales_reserve_ind, v_location_indicator
                 FROM ah_item --464000 rows in this table
                WHERE item_id_edw IN (
                         SELECT item_id_edw
                           FROM ah_item_xref --700000 rows in this table
                          WHERE item_code_cust = rec.item_code_cust
                            AND facility_num IN (
                                   SELECT facility_code
                                     FROM ah_chain_div_facility --17 rows in this table
                                    WHERE chain_id = ah_internal_data_pkg.get_chain_id (p_file_id)
                                      AND div_id = (SELECT div_id
                                                      FROM ah_div --8 rows in this table
                                                     WHERE division = rec.division)));
   END LOOP;
   DBMS_PROFILER.stop_profiler;
EXCEPTION
   WHEN NO_DATA_FOUND
   THEN
      NULL;
   WHEN TOO_MANY_ROWS
   THEN
      NULL;
END TEST;The SELECT query inside the cursor FOR LOOP took 773 seconds.
I have tried using BULK COLLECT instead of cursor for loop but it did not help.
When I took out the select query separately and executed with a sample value then it gave the results in a flash of second.
All the tables have primary key indexes.
Any ideas what can be done to make this code perform better?
Thanks,
Raj.

As suggested I'd try merging the queries into a single SQL. You could also rewrite your IN clauses as JOINs and see if that helps, e.g.
SELECT DISTINCT ai.shipper_ind, ai.special_sales_reserve_ind, ai.exe_location_ind
           INTO v_shipper_ind, v_sales_reserve_ind, v_location_indicator
           FROM ah_item ai, ah_item_xref aix, ah_chain_div_facility acdf, ah_div ad
          WHERE ai.item_id_edw = aix.item_id_edw
            AND aix.item_code_cust = rec.item_code_cust
            AND aix.facility_num = acdf.facility_code
            AND acdf.chain_id = ah_internal_data_pkg.get_chain_id (p_file_id)
            AND acdf.div_id = ad.div_id
            AND ad.division = rec.division;ALSO: You are calling ah_internal_data_pkg.get_chain_id (p_file_id) every time. Why not do it outside the loop and just use a variable in the inner query? That will prevent context switching and improve speed.
Edited by: Dave Hemming on Dec 3, 2008 9:34 AM

Due to MODIF ID, SELECT query in START-OF-SELECTION not getting triggered

Dear SAP Gurus,
I'm stuck with this program, where, my program is not being executed, as in, my SELECT query in my event START-OF-SELECTION is not getting triggered. Since i hav used MODIF ID, for SELECT-OPTIONS, even after putting the entries in select-options...................when i click on the execute button, or press F8, the program still goes into the AT SELECTION-SCREEN OUTPUT event..........but i want it to goto START-OF-SELECTION event where my SELECT query is........what should i do??????????????
Please find the notepad file having the code, n exucse me for any selection-texts absence.
Need help from u in this issue.
Thanks in advance.
REPORT ZPPR_CONVSTAT NO STANDARD PAGE HEADING.
INCLUDE ZPPR_CONVSTAT_TOP.               " data declaration
INCLUDE ZPPR_CONVSTAT_SEL_CRITERIA.      " selection criteria
INCLUDE ZPPR_CONVSTAT_PBO.               " event at selection-screen output
INCLUDE ZPPR_CONVSTAT_START_SELECTION.   " event start-of-selection
INCLUDE ZPPR_CONVSTAT_F_START_OF_SEL.
*& Include           ZPPR_CONVSTAT_TOP
TABLES : VBUK,
          VBUP,
          VBAK,
          VBAP,
          VBEP,
          VBPA,
          TVAK,
          EKUB,
          LIKP,
          LIPS,
          MARA,
          MAKT,
          MARC,
          PLAF,
          AUFK,
          AFKO,
          AFPO,
          AFVC,
          AFVV,
          CRHD,
          PBIM,
          KNA1,
          T134,
          IOHEADER,
          IOITEM.
TYPE-POOLS : slis.
TYPES : BEGIN OF ty_final,
        werks   TYPE vbap-werks, "Plant
        auart   TYPE vbak-auart, "Sales Order Doc. type
        erdat   TYPE vbak-erdat, "Sales Order Creation date
        vbeln   TYPE vbak-vbeln, "Sales Order No.
        posnr   TYPE vbap-posnr, "Sales Order Item No.
        aedat   TYPE vbak-aedat, "Sales Order Change Date
        kwmeng TYPE vbap-kwmeng, "Sales Order qty.
        vdatu   TYPE vbak-vdatu, "Requested Delivery Date
        lfimg   TYPE lips-lfimg, "Sales Order Delivered Qty.
        matnr   TYPE vbap-matnr, "Material ID
        arktx   TYPE vbap-arktx, "Material Description
        strgr   TYPE marc-strgr, "Planning Strategy
        vrkme   TYPE vbap-vrkme, "UOM
        plnum   TYPE plaf-plnum, "Plan Order No.
        gsmng   TYPE plaf-gsmng, "Plan Order Qty.
        auffx   TYPE plaf-auffx, "Plan Order Firming Indicator u2013 Qty.
        stlfx   TYPE plaf-stlfx, "Plan Order Firming Indicator - Component
        erdat2 TYPE aufk-erdat, "Production Order Creation Date
        aufnr   TYPE aufk-aufnr, "Production Order No.
        prdqty TYPE afko-gamng, "Production Order qty.
        pckqty TYPE lips-lfimg, "Packed Delivered Qty.
        psamg   TYPE afpo-psamg, "Allotted scrap
        igmng   TYPE afko-igmng, "Confirmed Yield Qty.
        iasmg   TYPE afko-iasmg, "Confirmed Scrap Qty
        iamng   TYPE afpo-iamng, "Expected Yield
        wemng   TYPE afpo-wemng, "Delivered Qty.
        altscrp TYPE c LENGTH 6, "Allotted Scrap %
        actscrp TYPE c LENGTH 6, "Actual Scrap %
        umrez   TYPE afvv-umrez, "Ups (from Prd. ORD)
        ups     TYPE clobjdat-ausp1, "Ups (from Material Master)
        crtnstl TYPE clobjdat-ausp1, "Carton Style
        ppopr   TYPE clobjdat-ausp1, "Pre-Printing Operation
        brdtyp TYPE clobjdat-ausp1, "Board Type
        lsdim1 TYPE clobjdat-ausp1, "Layout Size u2013 Dim 1
        lsdim2 TYPE clobjdat-ausp1, "Layout Size u2013 Dim 2
        lsgsm   TYPE clobjdat-ausp1, "GSM
        inktyp TYPE clobjdat-ausp1, "Ink Type
        foiltyp TYPE clobjdat-ausp1, "Foiling
        wintyp TYPE clobjdat-ausp1, "Window Type
        lamin   TYPE clobjdat-ausp1, "Lamination
        fsvrnsh TYPE clobjdat-ausp1, "Front Side Varnish
        bsvrnsh TYPE clobjdat-ausp1, "Back Side Varnish
        emboss TYPE clobjdat-ausp1, "Embossing
        punch   TYPE clobjdat-ausp1, "Punching
        paste   TYPE clobjdat-ausp1, "Pasting
        oprno   TYPE afvc-vornr,      "Operation No.
        wrkcntr TYPE crhd-arbpl,      "Work Centre
        oprtxt TYPE afvc-ltxa1,      "Operation Text
        oprqty TYPE afvv-mgvrg,      "Operation qty.
        yield   TYPE afvv-lmnga,      "Yield
        scrap   TYPE afvv-xmnga,      "Scrap
        jobtyp TYPE vbak-augru,      "Job Type
        prordst TYPE bsvx-sttxt,      "Production Order Status
        solinst TYPE vbup-lfsta,      "Sales Order Line Item Status
        sldprty TYPE kna1-name1,      "Sold to Party Name
        shpprty TYPE kna1-name1,      "Ship to Party Name
        shpcity TYPE kna1-ort01,      "Ship to party - City
        END OF ty_final.
TYPES : BEGIN OF ty_vbak,
        auart   TYPE vbak-auart,
        erdat   TYPE vbak-erdat, "Doc creation date
        vbeln   TYPE vbak-vbeln,
        aedat   TYPE vbak-aedat, "Doc change date
        vdatu   TYPE vbak-vdatu, "Requested delivery date
        kunnr   TYPE vbak-kunnr,
        augru   TYPE vbak-augru, "Job Type
        END OF ty_vbak.
TYPES : BEGIN OF ty_vbap,
        vbeln   TYPE vbap-vbeln,
        posnr   TYPE vbap-posnr,
        werks   TYPE vbap-werks,
        matnr   TYPE vbap-matnr,
        arktx   TYPE vbap-arktx,
        kwmeng TYPE vbap-kwmeng,
        vrkme   TYPE vbap-vrkme,
        END OF ty_vbap.
TYPES : BEGIN OF ty_pbim,
        pbdnr TYPE pbim-pbdnr, "Requirements Plan Number
        bdzei TYPE pbim-bdzei, "Independent requirements pointer
        matnr TYPE pbim-matnr,
        werks TYPE pbim-werks,
        END OF ty_pbim.
TYPES : BEGIN OF ty_pbhi,
        bdzei TYPE pbhi-bdzei, "Independent requirements pointer
        pdatu TYPE pbhi-pdatu, "Requirement date
        laeda TYPE pbhi-laeda, "Date of Last Change
        END OF ty_pbhi.
TYPES : BEGIN OF ty_ekko,
        ebeln TYPE ekko-ebeln, "STO doc no
        bsart TYPE ekko-bsart,
        reswk TYPE ekko-reswk, "Supplying plant
        aedat TYPE ekko-aedat, "Doc creation date
        END OF ty_ekko.
TYPES : BEGIN OF ty_ekpo,
        ebeln TYPE ekpo-ebeln,
        ebelp TYPE ekpo-ebelp,
        aedat TYPE ekpo-aedat, "Doc change date
        menge TYPE ekpo-menge,
        meins TYPE ekpo-meins,
        matnr TYPE ekpo-matnr,
        txz01 TYPE ekpo-txz01,
        END OF ty_ekpo.
TYPES : BEGIN OF ty_eket,
        ebeln TYPE eket-ebeln,
        ebelp TYPE eket-ebelp,
        eindt TYPE eket-eindt, "Requested delivery date
        END OF ty_eket.
TYPES : BEGIN OF ty_lips,
        vbeln TYPE lips-vbeln,
        posnr TYPE lips-posnr,
        vgbel TYPE lips-vgbel,
        vgpos TYPE lips-vgpos,
        lfimg TYPE lips-lfimg,
        END OF ty_lips.
TYPES : BEGIN OF ty_plaf,
        plnum TYPE plaf-plnum,
        matnr TYPE plaf-matnr,
        gsmng TYPE plaf-gsmng,
        auffx TYPE plaf-auffx,
        stlfx TYPE plaf-stlfx,
        kdauf TYPE plaf-kdauf,
        kdpos TYPE plaf-kdpos,
        pbdnr TYPE plaf-pbdnr,
        END OF ty_plaf.
TYPES : BEGIN OF ty_aufk,
        aufnr TYPE aufk-aufnr,
        erdat TYPE aufk-erdat,
        objnr TYPE aufk-objnr,
        END OF ty_aufk.
TYPES : BEGIN OF ty_afko,
        aufnr TYPE afko-aufnr,
        gamng TYPE afko-gamng, "Total order quantity
        gasmg TYPE afko-gasmg, "Total scrap quantity in the order
        igmng TYPE afko-igmng, "Confirmed Yield Qty
        iasmg TYPE afko-iasmg, "Confirmed Scrap Qty
        aufpl TYPE afko-aufpl, "Routing number of operations in the order
        END OF ty_afko.
TYPES : BEGIN OF ty_afpo,
        aufnr TYPE afpo-aufnr,
        plnum TYPE afpo-plnum,
        matnr TYPE afpo-matnr,
        pgmng TYPE afpo-pgmng, "Plan Order Qty
        kdauf TYPE afpo-kdauf,
        kdpos TYPE afpo-kdpos,
        psamg TYPE afpo-psamg, "Allotted scrap
        iamng TYPE afpo-iamng, "Expected Yield Variance
        wemng TYPE afpo-wemng, "Delivered Qty
        END OF ty_afpo.
TYPES : BEGIN OF ty_afvc,
        vornr TYPE afvc-vornr,
        aufpl TYPE afvc-aufpl, "Routing number of operations in the order
        aplzl TYPE afvc-aplzl, "General counter for order
        arbid TYPE afvc-arbid, "Object ID of the resource
        ltxa1 TYPE afvc-ltxa1,
        END OF ty_afvc.
TYPES : BEGIN OF ty_afvv,
        aufpl TYPE afvv-aufpl, "Routing number of operations in the order
        aplzl TYPE afvv-aplzl, "General counter for order
        umrez TYPE afvv-umrez,
        mgvrg TYPE afvv-mgvrg,
        lmnga TYPE afvv-lmnga,
        xmnga TYPE afvv-xmnga,
        END OF ty_afvv.
TYPES : BEGIN OF ty_mdvm,
        mdkey TYPE mdvm-mdkey,
        disst TYPE mdkp-disst,
        matnr TYPE mdkp-matnr,
        plwrk TYPE mdkp-plwrk,
        END OF ty_mdvm.
DATA : it_final TYPE STANDARD TABLE OF ty_final,
        it_vbak   TYPE STANDARD TABLE OF ty_vbak,
        it_vbap   TYPE STANDARD TABLE OF ty_vbap,
        it_lips   TYPE STANDARD TABLE OF ty_lips,
        it_pbim   TYPE STANDARD TABLE OF ty_pbim,
        it_pbhi   TYPE STANDARD TABLE OF ty_pbhi,
        it_ekko   TYPE STANDARD TABLE OF ty_ekko,
        it_ekpo   TYPE STANDARD TABLE OF ty_ekpo,
        it_eket   TYPE STANDARD TABLE OF ty_eket,
        it_plaf   TYPE STANDARD TABLE OF ty_plaf,
        it_aufk   TYPE STANDARD TABLE OF ty_aufk,
        it_afko   TYPE STANDARD TABLE OF ty_afko,
        it_afpo   TYPE STANDARD TABLE OF ty_afpo,
        it_afvc   TYPE STANDARD TABLE OF ty_afvc,
        it_afvv   TYPE STANDARD TABLE OF ty_afvv,
        it_mdvm   TYPE STANDARD TABLE OF ty_mdvm.
DATA : wa_final TYPE ty_final,
        wa_vbak   TYPE ty_vbak,
        wa_vbap   TYPE ty_vbap,
        wa_lips   TYPE ty_lips,
        wa_pbim   TYPE ty_pbim,
        wa_pbhi   TYPE ty_pbhi,
        wa_ekko   TYPE ty_ekko,
        wa_ekpo   TYPE ty_ekpo,
        wa_eket   TYPE ty_eket,
        wa_plaf   TYPE ty_plaf,
        wa_aufk   TYPE ty_aufk,
        wa_afko   TYPE ty_afko,
        wa_afpo   TYPE ty_afpo,
        wa_afvc   TYPE ty_afvc,
        wa_afvv   TYPE ty_afvv,
        wa_mdvm   TYPE ty_mdvm.
DATA : it_object TYPE hum_object_t,
        wa_object TYPE hum_object,
        it_item   TYPE hum_hu_item_t,
        wa_item   TYPE vepovb,
        count1(6) TYPE n.
DATA : gv_objek TYPE ausp-objek.       "Put matnr for use in FM u2018CLAF_CLASSIFICATION_OF_OBJECTSu2019
DATA : BEGIN OF it_sclass OCCURS 0.
        INCLUDE STRUCTURE sclass.
DATA : END OF it_sclass.
DATA : BEGIN OF it_clobjdat OCCURS 0.
        INCLUDE STRUCTURE clobjdat.
DATA : END OF it_clobjdat.
*& Include           ZPPR_CONVSTAT_SEL_CRITERIA
SELECTION-SCREEN FOR 'PLANNING STAGE'
SELECTION-SCREEN BEGIN OF BLOCK main WITH FRAME TITLE text-001.
PARAMETERS: mrpntdn RADIOBUTTON GROUP sel                    DEFAULT 'X' user-command flag,
              pldord RADIOBUTTON GROUP sel,
              prdord RADIOBUTTON GROUP sel.
SELECTION-SCREEN END OF BLOCK main.
SELECTION-SCREEN FOR 'SELECTION BY PLANT AND PLANT DATA'
SELECTION-SCREEN BEGIN OF BLOCK plant WITH FRAME TITLE text-002.
PARAMETERS      : p_werks   LIKE ioheader-werks OBLIGATORY DEFAULT '1100' MATCHCODE OBJECT H_T001W.
SELECT-OPTIONS : so_matnr FOR   ioitem-matnr                              MATCHCODE OBJECT MAT1.
PARAMETERS      : so_mtart TYPE t134-mtart     OBLIGATORY DEFAULT 'ZFIN' MATCHCODE OBJECT H_T134.
SELECT-OPTIONS : so_plnum FOR   ioitem-plnum                              MATCHCODE OBJECT plnum MODIF ID pld,
                    so_aufnr FOR   ioheader-aufnr                            MATCHCODE OBJECT orde   MODIF ID prd.
PARAMETERS      : p_prdsta LIKE tj02t-txt04                                                       MODIF ID prd.
SELECTION-SCREEN END OF BLOCK plant.
SELECTION-SCREEN FOR 'SELECTION BY REQUIREMENT TYPE'
SELECTION-SCREEN BEGIN OF BLOCK reqtyp WITH FRAME TITLE text-003.
PARAMETERS      : cb_so     TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                    cb_sto    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                    cb_pir    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag.
SELECTION-SCREEN END OF BLOCK reqtyp.
SELECTION-SCREEN FOR 'SELECTION BY DATE AND REQUIREMENT TYPE NOS'
SELECTION-SCREEN BEGIN OF BLOCK dtreqtypno WITH FRAME TITLE text-004.
SELECT-OPTIONS : so_crtdt FOR vbak-erdat                                                                MODIF ID gen,
                    so_vbeln FOR vbap-vbeln                                  MATCHCODE OBJECT WTY_F4_VBAP MODIF ID rso,
                    so_posnr FOR vbap-posnr                                                                MODIF ID rso,
                    so_ebeln FOR ekub-ebeln                                  MATCHCODE OBJECT MEKKM        MODIF ID rst,
                    so_ebelp FOR ekub-ebelp                                                                MODIF ID rst,
                    so_pbdnr FOR pbim-pbdnr                                                                MODIF ID rpi,
                    so_reqdt FOR vbep-edatu                                                                MODIF ID gen.
SELECTION-SCREEN END OF BLOCK dtreqtypno.
SELECTION-SCREEN FOR 'SELECTION BY OTHER PARAMETERS'
SELECTION-SCREEN BEGIN OF BLOCK othrparam WITH FRAME TITLE text-005.
SELECT-OPTIONS : so_kunnr FOR kna1-kunnr                                   MATCHCODE OBJECT debi   MODIF ID rso,
                    so_auart FOR tvak-auart                                   MATCHCODE OBJECT H_TVAK MODIF ID rso,
                    so_lfsta FOR vbup-lfsta                                                           MODIF ID rso.
SELECTION-SCREEN END OF BLOCK othrparam.
*& Include           ZPPR_CONVSTAT_PBO
*&   Event AT SELECTION-SCREEN OUTPUT
AT SELECTION-SCREEN OUTPUT.
IF mrpntdn = 'X'.
    LOOP AT SCREEN.
      IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSEIF pldord = 'X'.
    LOOP AT SCREEN.
      IF screen-group1 = 'PLD'.
        screen-intensified = 1.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'PRD'.
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSEIF prdord = 'X'.
    LOOP AT SCREEN.
      IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
        screen-intensified = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
IF ( cb_so = ' ' AND cb_sto = ' ' AND cb_pir = ' ' ).
    LOOP AT SCREEN.
      IF ( screen-group1 = 'GEN'
      OR screen-group1 = 'RSO'
      OR screen-group1 = 'RST'
      OR screen-group1 = 'RPI' ).
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
IF cb_so = 'X'.
    LOOP AT SCREEN.
      IF screen-group1 = 'RSO'.
        screen-active = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
    IF cb_sto = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RST'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_pir = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RPI'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ELSEIF cb_sto = 'X'.
    IF cb_so = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RSO'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_pir = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RPI'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ELSEIF cb_pir = 'X'.
    IF cb_so = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RSO'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_sto = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RST'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ENDIF.
*& Include           ZPPR_CONVSTAT_START_SELECTION
*&   Event START-OF-SELECTION
IF mrpntdn = 'X'.
PERFORM start_of_selection_mrpntdn.
ELSEIF pldord = 'X'.
PERFORM start_of_selection_pldord.
ELSEIF prdord = 'X'.
PERFORM start_of_selection_prdord.
ENDIF.
*& Include           ZPPR_CONVSTAT_F_START_OF_SEL
*&      Form START_OF_SELECTION
      Subroutine for MRP NOT DONE
FORM start_of_selection_mrpntdn.
    SELECT mdkey INTO TABLE it_mdvm FROM mdvm
                 WHERE GSAEN = 'X'
                   AND AKKEN = 'X'.
      IF sy-subrc = 0.
        LOOP AT it_mdvm INTO wa_mdvm.
          wa_mdvm-disst = wa_mdvm-mdkey(3).
          wa_mdvm-matnr = wa_mdvm-mdkey+3(18).
          wa_mdvm-plwrk = wa_mdvm-mdkey+21(4).
          MODIFY it_mdvm FROM wa_mdvm INDEX sy-index TRANSPORTING disst matnr plwrk.
        ENDLOOP.
      ENDIF.
ENDFORM.
*&      Form START_OF_SELECTION
      Subroutine for PLAN ORDER CREATED
FORM start_of_selection_pldord.
ENDFORM.
*&      Form START_OF_SELECTION for PRODUCTION ORDER CREATED
      Subroutine for PRODUCTION ORDER CREATED
FORM start_of_selection_prdord.
ENDFORM.

You need to mention START-OF-SELECTION explicitly in your code.
Change your code as below:
*& Event START-OF-SELECTION
START-OF-SELECTION.
IF mrpntdn = 'X'.

Issue in select query

HI All experts, 
i have a program in which i have a select query <pre>
SELECT b~vertrag
 a~anlage
 a~operand
 a~saison
 a~ab
 a~ablfdnr
 a~bis
 a~wert1
FROM ettifn AS a INNER JOIN ever AS b
ON aanlage = banlage
INTO TABLE li_captran PACKAGE SIZE p_pack
WHERE a~anlage IN s_anlage
 AND a~ab <= l_date
 AND a~bis >= l_date
 AND a~operand IN ('ID-CAPLOAD','ID-OBLT')
 AND b~einzdat <= l_date
 AND b~auszdat >= l_date.</pre> 
this query is taking a lot of time in running and we are facing lot of performance related issues
 
kindly guide me how i can break this into som simpler query
 
ettifn has 10 million records
ever has around 5 million records .
 
also please tell me how much data i can store into an internal table
can i store 5 million records in an internal table ??????
is it good in terms of performance of a program if not please tell me what is the better way of doing dat .
 
also tell me how secondry indexes help in improving performance of select query
is it good to maintain number of secondry indexes in a standard table or it decreases performance of a standard table .
 
<pre>
TYPES: BEGIN OF ty_eanlh,
 anlage LIKE eanlh-anlage,
 bis LIKE eanlh-bis,
 tariftyp LIKE eanlh-tariftyp,
 END OF ty_eanlh.
DATA: l_date TYPE datum.
DATA: li_eanlh TYPE HASHED TABLE OF ty_eanlh WITH UNIQUE KEY anlage
 bis
 WITH HEADER LINE.
DATA: li_captran TYPE HASHED TABLE OF ty_captran WITH UNIQUE KEY vertrag
 anlage
 operand
 saison
 ab
 ablfdnr
 WITH HEADER LINE.
DATA: l_tariftyp LIKE eanlh-tariftyp.
l_date = p_date + 6.
l_date = p_date + 5. "As per Terry's Request 1/23/2009
CHECK NOT p_cap IS INITIAL.
Get Operand Values
SELECT b~vertrag
 a~anlage
 a~operand
 a~saison
 a~ab
 a~ablfdnr
 a~bis
 a~wert1
FROM ettifn AS a INNER JOIN ever AS b
ON aanlage = banlage
INTO TABLE li_captran PACKAGE SIZE p_pack
WHERE a~anlage IN s_anlage
 AND a~ab <= l_date
 AND a~bis >= l_date
 AND a~operand IN ('ID-CAPLOAD','ID-OBLT')
 AND b~einzdat <= l_date
 AND b~auszdat >= l_date.
 IF sy-subrc EQ 0 AND NOT li_captran[] IS INITIAL.
 Get Rate Category
 SELECT anlage
 bis
 tariftyp
 FROM eanlh INTO CORRESPONDING FIELDS OF TABLE li_eanlh
 FOR ALL ENTRIES IN li_captran
 WHERE anlage = li_captran-anlage
 AND ab <= l_date
 AND bis >= l_date.
 Get POD ID
 SELECT a~anlage
 a~int_ui
 a~dateto
 a~timeto
 b~ext_ui
 INTO TABLE i_pod
 FROM euiinstln AS a INNER JOIN euitrans AS b
 ON aint_ui = bint_ui
 FOR ALL ENTRIES IN li_captran
 WHERE a~anlage = li_captran-anlage.
 IF sy-subrc EQ 0 AND NOT i_pod[] IS INITIAL.
 SORT i_pod BY anlage.
 SELECT vertrag
 int_ui
 serviceid
 FROM eservice
 INTO TABLE i_servicect
 FOR ALL ENTRIES IN i_pod
 WHERE int_ui = i_pod-int_ui
 AND service_start <= l_date
 AND service_end >= l_date
 AND service = 'ESUP'.
 ENDIF.
 LOOP AT li_captran.
 i_ct-anlage = li_captran-anlage.
 READ TABLE li_eanlh WITH KEY anlage = li_captran-anlage.
 IF sy-subrc EQ 0.
 i_ct-tariftyp = li_eanlh-tariftyp.
 READ TABLE i_rate WITH KEY tariftyp = i_ct-tariftyp.
 IF sy-subrc NE 0.
 CONTINUE.
 ENDIF.
 ELSE.
 i_ct-tariftyp = '0000'.
 ENDIF.
 READ TABLE i_pod WITH KEY anlage = li_captran-anlage.
 IF sy-subrc EQ 0.
 READ TABLE i_servicect WITH KEY int_ui = i_pod-int_ui.
 IF sy-subrc EQ 0.
 i_ct-serviceid = i_servicect-serviceid.
 ENDIF.
 ENDIF.
 IF li_captran-operand = 'ID-CAPLOAD'.
 i_ct-cap = li_captran-wert1.
 ELSEIF li_captran-operand = 'ID-OBLT'.
 i_ct-tran = li_captran-wert1.
 ENDIF.
 COLLECT i_ct.
 CLEAR: li_captran, i_ct.
 ENDLOOP.
 ENDIF.
ENDSELECT.</pre> 
this code is taking a lot of time to execute and decreasing the system performance . 
please guide me how can i increase the performance of this code . 
Thanks in advance 
Edited by: Matt on Oct 11, 2009 9:45 PM

Hi matt ,
no i am not thru bcoz of formatting i just trying to remove it and i just marked it answered so that it will not come in my unanswered because unanswered questions are limited.
also could you please help me in this question .
now how can i change this question to unanswerd .
plz guide me
Thanks in advance

How to calculate the area of a large number of polygons in a single query

Hi forum
Is it possible to calculate the area of a large number of polygons in a single query using a combination of SDO_AGGR_UNION and SDO_AREA? So far, I have tried doing something similar to this:
select sdo_geom.sdo_area((
select sdo_aggr_union ( sdoaggrtype(mg.geoloc, 0.005))
from mapv_gravsted_00182 mg
where mg.dblink = 521 or mg.dblink = 94 or mg.dblink = 38 <many many more....>),
0.0005) calc_area from dualThe table MAPV_GRAVSTED_00182 contains 2 fields - geoloc (SDO_GEOMETRY) and dblink (Id field) needed for querying specific polygons.
As far as I can see, I need to first somehow get a single SDO_GEOMETRY object and use this as input for the SDO_AREA function. But I'm not 100% sure, that I'm doing this the right way. This query is very inefficient, and sometimes fails with strange errors like "No more data to read from socket" when executed from SQL Developer. I even tried with the latest JDBC driver from Oracle without much difference.
Would a better approach be to write some kind of stored procedure, that adds up all the single geometries by adding each call to SDO_AREA on each single geometry object - or what is the best approach?
Any advice would be appreciated.
Thanks in advance,
Jacob

Hi
I am now trying to update all my spatial table with SRID's. To do this, I try to drop the spatial index first to recreate it after the update. But for a lot of tables I can't drop the spatial index. Whenever I try to DROP INDEX <spatial index name>, I get this error - anyone know what this means?
Thanks,
Jacob
Error starting at line 2 in command:
drop index BSSYS.STIER_00182_SX
Error report:
SQL Error: ORA-29856: error occurred in the execution of ODCIINDEXDROP routine
ORA-13249: Error in Spatial index: cannot drop sequence BSSYS.MDRS_1424B$
ORA-13249: Stmt-Execute Failure: DROP SEQUENCE BSSYS.MDRS_1424B$
ORA-29400: data cartridge error
ORA-02289: sequence does not exist
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 27
29856. 00000 - "error occurred in the execution of ODCIINDEXDROP routine"
*Cause: Failed to successfully execute the ODCIIndexDrop routine.
*Action: Check to see if the routine has been coded correctly.
Edit - just found the answer for this in MetaLink note 241003.1. Apparently there is some internal problem when dropping spatial indexes, some objects gets dropped that shouldn't be. Solution is to manually create the sequence it complains it can't drop, then it works... Weird error.

Regarding SELECT query

Dear experts,
Is there a way for the following SELECT query to be improved?
The problem that I'm seeing here is that the same table (l_item_tab) is being queried twice in the SELECT query (due to the "table joins", a and b). How can I improve the data retrieval here? And I also can't change the SELECT query to be out of the loop - ledger is a select-option and multiple values are possible.
* Get Ledger
SELECT * FROM t881 INTO TABLE lt_t881
    WHERE rldnr IN s_rldnr.
LOOP AT lt_t881.
*   Get FI-SL user-defined item table based on ledger
    PERFORM get_sl_item_tab USING lt_t881-rldnr CHANGING l_item_tab.
" L_ITEM_TAB is populated here
*   Get SL line items
    SELECT * APPENDING CORRESPONDING FIELDS OF TABLE gt_glu1
    FROM (l_item_tab) AS a
    WHERE
        rldnr         IN s_rldnr             " Ledger
    AND rbukrs        IN s_bukrs             " Company code
    AND ryyrkeg_wwsub IN s_wwsub             " Subsystem
    AND racct         IN s_racct             " Account no
    AND ryymac        IN s_yymac             " Management area
    AND rtcur         IN s_rtcur             " Trx currency
    AND docnr         IN s_docnr             " Doc. number
    AND docty         IN s_docty             " Doc. type
    AND docct         EQ c_docct_l           " Doc. category (L = Local)
    AND ryear         IN s_ryear             " Fiscal year
    AND budat         IN s_budat             " Posting date
    AND yystodt       IN s_stodt             " Reversal date
    AND yystgrd       IN s_stgrd             " Reversal reason
    AND yyintref      IN s_intref            " Interface ID
    AND NOT exists
      ( SELECT * FROM (l_item_tab) AS b
         WHERE
             b~rldnr    = a~rldnr     AND
             b~docnr    = a~docnr     AND
             b~rbukrs   = a~rbukrs    AND
       ( ( ( b~docct    = c_docct_y
          OR b~docct    = c_docct_x ) AND
             b~refryear = a~ryear )   OR
         ( ( b~docct    = c_docct_u
          OR b~docct    = c_docct_t ) AND
             b~ryear    = a~ryear ) )
ENDLOOP.
Edited by: Rob Burbank on Jun 23, 2010 12:33 PM

>
Siegfried Boes wrote:
> > Will certainly try this out too..
> maybe you should think twice .... The usage of a subselect is that the result set is not transferred to the application server it is only needed
> during the selection.
>
> You should anser the following questions:
> + who wrote the code? you or? I get the impression that you don't know what is intended.
> + SQL Trace, what are the numbers for repeated executions, (go to summary by SQL statement), duration, execution, records
> + how many different tables are accessed, l_item_tab is dynamic
> + what knid of tables are accessed?
>
> Siegfried
Hi Siegfried,
- The codes are currently existing ones and they were not written by me too. I just do know that the first / main SELECT statement in the query is for retrieving FI special ledger line item data records, while the second / sub SELECT statement is to ensure that the line item data records are not already reversed, and not a reversal.
- In the summarized SQL trace of a sample test run: executions = 1, identical executions = 0, duration = 700247324 (almost 100% of the total processing durations), records = 0 (there should be more records returned in an actual production run)
- Only one table, ZZGLV4A (custom) is accessed based on the selection screen variant. ZZGLV4A is an FI special ledger line item table and its data volume: 455 mil. data records. Note: The codes are written for a report that runs in the background, and the selection screen variant is used for the executions too. The table accessed (l_item_tab is ZZGLV4A in this case) depends on the ledger inputted here - only one ledger is specified for the current selection screen variant.
- Table accessed - FI special ledger line item data.
I tried tuning the query a little further by just properly specifying the WHERE fields - only a minimal improvement is observed, an average of about 6% of runtime improvement only (tested via SE30 in the development box for ZZGLV4A but its table volume is 4 mil. data records here only). This obviously works only for the table ZZGLV4A for now, I'm afraid.
Any other ideas on how such subqueries can be improved generally (maybe secondary indexes)? The subquery is certainly re-hitting the same table at least twice.
Thanks for the inputs once again!

Select query resulting in redo?

Hi All,
Does select query results in redo? In what cases this happens?
Regards,
Sphinx

mtefft wrote:
Another possibility is that the SELECT query invokes a PL/SQL function that performs insert, update or delete.
This is a poor practice for a number of reasons but they are out there.
Disagree with that. Proof:
SQL> create table x(y number);
Table created.
SQL> create function f return number as
2 begin
3 insert into x values (2);
4 return 1;
5 end;
6 /
Function created.
SQL> select dummy, f() from dual;
select dummy, f() from dual
ERROR at line 1:
ORA-14551: cannot perform a DML operation inside a query
ORA-06512: at "HR.F", line 3

Select Query taking long time to run second time

Hi All,
I have Oracle 11gR1 in windows server 2008 R2 .
I have some tables with 10 million records . When i run the select query for those tables first time it gives me result in 15 seconds but if i am running the same script second time from the same session I am getting the result in 15 minutes to complete ..
Why it is happening? What may be the solution for this ?
Thanks & Regards,
Vikash jain(Junior DBA)

Hi Mohamed,
I just saw that both the times for the same query execution plan is different ..
here are the details :
First time Second Time
g84m3qqjv2p3q g84m3qqjv2p3q
2733045235 1310485984
So plz tell me how should i force database to use the first execution plan ?
I got this script for forcing the Db to use the same execution plan
accept sql_id -
prompt 'Enter value for sql_id: ' -
default 'X0X0X0X0'
accept plan_hash_value -
prompt 'Enter value for plan_hash_value: ' -
default 'X0X0X0X0'
accept fixed -
prompt 'Enter value for fixed (NO): ' -
default 'NO'
accept enabled -
prompt 'Enter value for enabled (YES): ' -
default 'YES'
accept plan_name -
prompt 'Enter value for plan_name (ID_sqlid_planhashvalue): ' -
default 'X0X0X0X0'
set feedback off
set sqlblanklines on
set serveroutput on
declare
l_plan_name varchar2(40);
l_old_plan_name varchar2(40);
l_sql_handle varchar2(40);
ret binary_integer;
l_sql_id varchar2(13);
l_plan_hash_value number;
l_fixed varchar2(3);
l_enabled varchar2(3);
major_release varchar2(3);
minor_release varchar2(3);
begin
select regexp_replace(version,'\..*'), regexp_substr(version,'[0-9]+',1,2) into major_release, minor_release from v$instance;
minor_release := 2;
l_sql_id := '&&sql_id';
l_plan_hash_value := to_number('&&plan_hash_value');
l_fixed := '&&fixed';
l_enabled := '&&enabled';
ret := dbms_spm.load_plans_from_cursor_cache(
sql_id=>l_sql_id,
plan_hash_value=>l_plan_hash_value,
fixed=>l_fixed,
enabled=>l_enabled);
if minor_release = '1' then
-- 11gR1 has a bug that prevents renaming Baselines
dbms_output.put_line(' ');
dbms_output.put_line('Baseline created.');
dbms_output.put_line(' ');
else
-- This statements looks for Baselines create in the last 4 seconds
select sql_handle, plan_name,
decode('&&plan_name','X0X0X0X0','SQLID_'||'&&sql_id'||'_'||'&&plan_hash_value','&&plan_name')
into l_sql_handle, l_old_plan_name, l_plan_name
from dba_sql_plan_baselines spb
where created > sysdate-(1/24/60/15);
ret := dbms_spm.alter_sql_plan_baseline(
sql_handle=>l_sql_handle,
plan_name=>l_old_plan_name,
attribute_name=>'PLAN_NAME',
attribute_value=>l_plan_name);
dbms_output.put_line(' ');
dbms_output.put_line('Baseline '||upper(l_plan_name)||' created.');
dbms_output.put_line(' ');
end if;
end;
undef sql_id
undef plan_hash_value
undef plan_name
undef fixed
set feedback on
Output:
Enter value for sql_id: g84m3qqjv2p3q
Enter value for plan_hash_value: 2733045235
Enter value for fixed (NO):
Enter value for enabled (YES):
Enter value for plan_name (ID_sqlid_planhashvalue): g84m3qqjv2p3q
old 16: l_sql_id := '&&sql_id';
new 16: l_sql_id := 'g84m3qqjv2p3q';
old 17: l_plan_hash_value := to_number('&&plan_hash_value');
new 17: l_plan_hash_value := to_number('2733045235');
old 18: l_fixed := '&&fixed';
new 18: l_fixed := 'NO';
old 19: l_enabled := '&&enabled';
new 19: l_enabled := 'YES';
old 40: decode('&&plan_name','X0X0X0X0','SQLID_'||'&&sql_id'||'_'||'&&plan_hash_value','&&plan_name')
new 40: decode('g84m3qqjv2p3q','X0X0X0X0','SQLID_'||'g84m3qqjv2p3q'||'_'||'2733045235','g84m3qqjv2p3q')
declare
ERROR at line 1:
ORA-01403: no data found
ORA-06512: at line 39
Kindly help me to resolve the issue ..
Thanks & Regards,
Vikash Jain(Junior DBA)

SELECT query takes too much time! Y?

Plz find my SELECT query below:
select w~mandt
wvbeln wposnr wmeins wmatnr wwerks wnetwr
wkwmeng wvrkme wmatwa wcharg w~pstyv
wposar wprodh wgrkor wantlf wkztlf wlprio
wvstel wroute wumvkz wumvkn wabgru wuntto
wawahr werdat werzet wfixmg wprctr wvpmat
wvpwrk wmvgr1 wmvgr2 wmvgr3 wmvgr4 wmvgr5
wbedae wcuobj w~mtvfp
xetenr xwmeng xbmeng xettyp xwepos xabart
x~edatu
xtddat xmbdat xlddat xwadat xabruf xetart
x~ezeit
into table t_vbap
from vbap as w
inner join vbep as x on xvbeln = wvbeln and
xposnr = wposnr and
xmandt = wmandt
where
( ( werdat > pre_dat ) and ( werdat <= w_date ) ) and
( ( ( erdat > pre_dat and erdat < p_syndt ) or
( erdat = p_syndt and erzet <= p_syntm ) ) ) and
w~matnr in s_matnr and
w~pstyv in s_itmcat and
w~lfrel in s_lfrel and
w~abgru = ' ' and
w~kwmeng > 0 and
w~mtvfp in w_mtvfp and
x~ettyp in w_ettyp and
x~bdart in s_req_tp and
x~plart in s_pln_tp and
x~etart in s_etart and
x~abart in s_abart and
( ( xlifsp in s_lifsp ) or ( xlifsp = ' ' ) ).
The problem: It takes too much time while executing this statement.
Could anybody change this statement and help me out to reduce the DB Access time?
Thx

Ways of Performance Tuning
1. Selection Criteria
2. Select Statements
 Select Queries
 SQL Interface
 Aggregate Functions
 For all Entries
Select Over more than one internal table
Selection Criteria
1. Restrict the data to the selection criteria itself, rather than filtering it out using the ABAP code using CHECK statement.
2. Select with selection list.
SELECT * FROM SBOOK INTO SBOOK_WA.
CHECK: SBOOK_WA-CARRID = 'LH' AND
 SBOOK_WA-CONNID = '0400'.
ENDSELECT.
The above code can be much more optimized by the code written below which avoids CHECK, selects with selection list
SELECT CARRID CONNID FLDATE BOOKID FROM SBOOK INTO TABLE T_SBOOK
WHERE SBOOK_WA-CARRID = 'LH' AND
 SBOOK_WA-CONNID = '0400'.
Select Statements Select Queries
1. Avoid nested selects
SELECT * FROM EKKO INTO EKKO_WA.
SELECT * FROM EKAN INTO EKAN_WA
 WHERE EBELN = EKKO_WA-EBELN.
ENDSELECT.
ENDSELECT.
The above code can be much more optimized by the code written below.
SELECT PF1 PF2 FF3 FF4 INTO TABLE ITAB
 FROM EKKO AS P INNER JOIN EKAN AS F
 ON PEBELN = FEBELN.
Note: A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. One should therefore use nested SELECT loops only if the selection in the outer loop contains very few lines or the outer loop is a SELECT SINGLE statement.
2. Select all the records in a single shot using into table clause of select statement rather than to use Append statements.
SELECT * FROM SBOOK INTO SBOOK_WA.
CHECK: SBOOK_WA-CARRID = 'LH' AND
 SBOOK_WA-CONNID = '0400'.
ENDSELECT.
The above code can be much more optimized by the code written below which avoids CHECK, selects with selection list and puts the data in one shot using into table
SELECT CARRID CONNID FLDATE BOOKID FROM SBOOK INTO TABLE T_SBOOK
WHERE SBOOK_WA-CARRID = 'LH' AND
 SBOOK_WA-CONNID = '0400'.
3. When a base table has multiple indices, the where clause should be in the order of the index, either a primary or a secondary index.
To choose an index, the optimizer checks the field names specified in the where clause and then uses an index that has the same order of the fields. In certain scenarios, it is advisable to check whether a new index can speed up the performance of a program. This will come handy in programs that access data from the finance tables.
4. For testing existence, use Select.. Up to 1 rows statement instead of a Select-Endselect-loop with an Exit.
SELECT * FROM SBOOK INTO SBOOK_WA
UP TO 1 ROWS
WHERE CARRID = 'LH'.
ENDSELECT.
The above code is more optimized as compared to the code mentioned below for testing existence of a record.
SELECT * FROM SBOOK INTO SBOOK_WA
 WHERE CARRID = 'LH'.
EXIT.
ENDSELECT.
5. Use Select Single if all primary key fields are supplied in the Where condition .
If all primary key fields are supplied in the Where conditions you can even use Select Single.
Select Single requires one communication with the database system, whereas Select-Endselect needs two.
Select Statements SQL Interface
1. Use column updates instead of single-row updates
to update your database tables.
SELECT * FROM SFLIGHT INTO SFLIGHT_WA.
SFLIGHT_WA-SEATSOCC =
 SFLIGHT_WA-SEATSOCC - 1.
UPDATE SFLIGHT FROM SFLIGHT_WA.
ENDSELECT.
The above mentioned code can be more optimized by using the following code
UPDATE SFLIGHT
 SET SEATSOCC = SEATSOCC - 1.
2. For all frequently used Select statements, try to use an index.
SELECT * FROM SBOOK CLIENT SPECIFIED INTO SBOOK_WA
WHERE CARRID = 'LH'
 AND CONNID = '0400'.
ENDSELECT.
The above mentioned code can be more optimized by using the following code
SELECT * FROM SBOOK CLIENT SPECIFIED INTO SBOOK_WA
WHERE MANDT IN ( SELECT MANDT FROM T000 )
 AND CARRID = 'LH'
 AND CONNID = '0400'.
ENDSELECT.
3. Using buffered tables improves the performance considerably.
Bypassing the buffer increases the network considerably
SELECT SINGLE * FROM T100 INTO T100_WA
BYPASSING BUFFER
WHERE SPRSL = 'D'
 AND ARBGB = '00'
 AND MSGNR = '999'.
The above mentioned code can be more optimized by using the following code
SELECT SINGLE * FROM T100 INTO T100_WA
WHERE SPRSL = 'D'
 AND ARBGB = '00'
 AND MSGNR = '999'.
Select Statements Aggregate Functions
 If you want to find the maximum, minimum, sum and average value or the count of a database column, use a select list with aggregate functions instead of computing the aggregates yourself.
Some of the Aggregate functions allowed in SAP are MAX, MIN, AVG, SUM, COUNT, COUNT( * )
Consider the following extract.
 Maxno = 0.
 Select * from zflight where airln = LF and cntry = IN.
 Check zflight-fligh > maxno.
 Maxno = zflight-fligh.
 Endselect.
The above mentioned code can be much more optimized by using the following code.
Select max( fligh ) from zflight into maxno where airln = LF and cntry = IN.
Select Statements For All Entries
 The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the length of the WHERE clause.
 The plus
 Large amount of data
 Mixing processing and reading of data
 Fast internal reprocessing of data
 Fast
 The Minus
 Difficult to program/understand
 Memory could be critical (use FREE or PACKAGE size)
Points to be must considered FOR ALL ENTRIES
 Check that data is present in the driver table
 Sorting the driver table
 Removing duplicates from the driver table
Consider the following piece of extract
 Loop at int_cntry.
Select single * from zfligh into int_fligh
where cntry = int_cntry-cntry.
Append int_fligh.
 Endloop.
The above mentioned can be more optimized by using the following code.
Sort int_cntry by cntry.
Delete adjacent duplicates from int_cntry.
If NOT int_cntry[] is INITIAL.
 Select * from zfligh appending table int_fligh
 For all entries in int_cntry
 Where cntry = int_cntry-cntry.
Endif.
Select Statements Select Over more than one Internal table
1. Its better to use a views instead of nested Select statements.
SELECT * FROM DD01L INTO DD01L_WA
WHERE DOMNAME LIKE 'CHAR%'
 AND AS4LOCAL = 'A'.
SELECT SINGLE * FROM DD01T INTO DD01T_WA
 WHERE DOMNAME = DD01L_WA-DOMNAME
 AND AS4LOCAL = 'A'
 AND AS4VERS = DD01L_WA-AS4VERS
 AND DDLANGUAGE = SY-LANGU.
ENDSELECT.
The above code can be more optimized by extracting all the data from view DD01V_WA
SELECT * FROM DD01V INTO DD01V_WA
WHERE DOMNAME LIKE 'CHAR%'
 AND DDLANGUAGE = SY-LANGU.
ENDSELECT
2. To read data from several logically connected tables use a join instead of nested Select statements. Joins are preferred only if all the primary key are available in WHERE clause for the tables that are joined. If the primary keys are not provided in join the Joining of tables itself takes time.
SELECT * FROM EKKO INTO EKKO_WA.
SELECT * FROM EKAN INTO EKAN_WA
 WHERE EBELN = EKKO_WA-EBELN.
ENDSELECT.
ENDSELECT.
The above code can be much more optimized by the code written below.
SELECT PF1 PF2 FF3 FF4 INTO TABLE ITAB
 FROM EKKO AS P INNER JOIN EKAN AS F
 ON PEBELN = FEBELN.
3. Instead of using nested Select loops it is often better to use subqueries.
SELECT * FROM SPFLI
INTO TABLE T_SPFLI
WHERE CITYFROM = 'FRANKFURT'
 AND CITYTO = 'NEW YORK'.
SELECT * FROM SFLIGHT AS F
 INTO SFLIGHT_WA
 FOR ALL ENTRIES IN T_SPFLI
 WHERE SEATSOCC < F~SEATSMAX
 AND CARRID = T_SPFLI-CARRID
 AND CONNID = T_SPFLI-CONNID
 AND FLDATE BETWEEN '19990101' AND '19990331'.
ENDSELECT.
The above mentioned code can be even more optimized by using subqueries instead of for all entries.
SELECT * FROM SFLIGHT AS F INTO SFLIGHT_WA
 WHERE SEATSOCC < F~SEATSMAX
 AND EXISTS ( SELECT * FROM SPFLI
 WHERE CARRID = F~CARRID
 AND CONNID = F~CONNID
 AND CITYFROM = 'FRANKFURT'
 AND CITYTO = 'NEW YORK' )
 AND FLDATE BETWEEN '19990101' AND '19990331'.
ENDSELECT.
1. Table operations should be done using explicit work areas rather than via header lines.
READ TABLE ITAB INTO WA WITH KEY K = 'X BINARY SEARCH.
IS MUCH FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY K = 'X'.
If TAB has n entries, linear search runs in O( n ) time, whereas binary search takes only O( log2( n ) ).
2. Always try to use binary search instead of linear search. But dont forget to sort your internal table before that.
READ TABLE ITAB INTO WA WITH KEY K = 'X'. IS FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY (NAME) = 'X'.
3. A dynamic key access is slower than a static one, since the key specification must be evaluated at runtime.
4. A binary search using secondary index takes considerably less time.
5. LOOP ... WHERE is faster than LOOP/CHECK because LOOP ... WHERE evaluates the specified condition internally.
LOOP AT ITAB INTO WA WHERE K = 'X'.
ENDLOOP.
The above code is much faster than using
LOOP AT ITAB INTO WA.
CHECK WA-K = 'X'.
ENDLOOP.
6. Modifying selected components using MODIFY itab TRANSPORTING f1 f2.. accelerates the task of updating a line of an internal table.
WA-DATE = SY-DATUM.
MODIFY ITAB FROM WA INDEX 1 TRANSPORTING DATE.
The above code is more optimized as compared to
WA-DATE = SY-DATUM.
MODIFY ITAB FROM WA INDEX 1.
7. Accessing the table entries directly in a "LOOP ... ASSIGNING ..." accelerates the task of updating a set of lines of an internal table considerably
Modifying selected components only makes the program faster as compared to Modifying all lines completely.
e.g,
LOOP AT ITAB ASSIGNING <WA>.
I = SY-TABIX MOD 2.
IF I = 0.
 <WA>-FLAG = 'X'.
ENDIF.
ENDLOOP.
The above code works faster as compared to
LOOP AT ITAB INTO WA.
I = SY-TABIX MOD 2.
IF I = 0.
 WA-FLAG = 'X'.
 MODIFY ITAB FROM WA.
ENDIF.
ENDLOOP.
8. If collect semantics is required, it is always better to use to COLLECT rather than READ BINARY and then ADD.
LOOP AT ITAB1 INTO WA1.
READ TABLE ITAB2 INTO WA2 WITH KEY K = WA1-K BINARY SEARCH.
IF SY-SUBRC = 0.
 ADD: WA1-VAL1 TO WA2-VAL1,
 WA1-VAL2 TO WA2-VAL2.
 MODIFY ITAB2 FROM WA2 INDEX SY-TABIX TRANSPORTING VAL1 VAL2.
ELSE.
 INSERT WA1 INTO ITAB2 INDEX SY-TABIX.
ENDIF.
ENDLOOP.
The above code uses BINARY SEARCH for collect semantics. READ BINARY runs in O( log2(n) ) time. The above piece of code can be more optimized by
LOOP AT ITAB1 INTO WA.
COLLECT WA INTO ITAB2.
ENDLOOP.
SORT ITAB2 BY K.
COLLECT, however, uses a hash algorithm and is therefore independent
of the number of entries (i.e. O(1)) .
9. "APPEND LINES OF itab1 TO itab2" accelerates the task of appending a table to another table considerably as compared to LOOP-APPEND-ENDLOOP.
APPEND LINES OF ITAB1 TO ITAB2.
This is more optimized as compared to
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
10. DELETE ADJACENT DUPLICATES accelerates the task of deleting duplicate entries considerably as compared to READ-LOOP-DELETE-ENDLOOP.
DELETE ADJACENT DUPLICATES FROM ITAB COMPARING K.
This is much more optimized as compared to
READ TABLE ITAB INDEX 1 INTO PREV_LINE.
LOOP AT ITAB FROM 2 INTO WA.
IF WA = PREV_LINE.
 DELETE ITAB.
ELSE.
 PREV_LINE = WA.
ENDIF.
ENDLOOP.
11. "DELETE itab FROM ... TO ..." accelerates the task of deleting a sequence of lines considerably as compared to DO -DELETE-ENDDO.
DELETE ITAB FROM 450 TO 550.
This is much more optimized as compared to
DO 101 TIMES.
DELETE ITAB INDEX 450.
ENDDO.
12. Copying internal tables by using ITAB2[ ] = ITAB1[ ] as compared to LOOP-APPEND-ENDLOOP.
ITAB2[] = ITAB1[].
This is much more optimized as compared to
REFRESH ITAB2.
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
13. Specify the sort key as restrictively as possible to run the program faster.
SORT ITAB BY K. makes the program runs faster as compared to SORT ITAB.
Internal Tables contd
Hashed and Sorted tables
1. For single read access hashed tables are more optimized as compared to sorted tables.
2. For partial sequential access sorted tables are more optimized as compared to hashed tables
Hashed And Sorted Tables
Point # 1
Consider the following example where HTAB is a hashed table and STAB is a sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE HTAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
This runs faster for single read access as compared to the following same code for sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE STAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
Point # 2
Similarly for Partial Sequential access the STAB runs faster as compared to HTAB
LOOP AT STAB INTO WA WHERE K = SUBKEY.
ENDLOOP.
This runs faster as compared to
LOOP AT HTAB INTO WA WHERE K = SUBKEY.
ENDLOOP.

Internal table with same variable and one select query

Hi,
I am a new bee here with may be a silly question.
I have a internal table as below.
DATA: BEGIN OF IT_ORDERDETAILS OCCURS 0,
 VBELN LIKE VBAK-VBELN, "Order number
 BSTNK LIKE VBAK-BSTNK, "customer PO
 ERDAT LIKE VBAK-ERDAT, " Order created date
 MATNR LIKE VBAP-MATNR, "Sales order line item
 KWMENG LIKE VBAP-KWMENG, "Quantity
 D_VBELN like likp-vbeln, " delivery no
 POSNR like lips-posnr, " delivery item
 KUNNR LIKE LIKP-KUNNR, "ship quantity
END OF IT_ORDERDETAILS.
Where VBELN field is in VBAK and LIKP table.
VBELN in VBAK table = order #
VBELN in LIKP table is = Delivery #
I want to use join to fetch data in single select query.
Below is the select query
SELECT VBAK~VBELN
 VBAK~BSTNK
 VBAK~ERDAT
 VBAP~MATNR
 VBAP~KWMENG
 likp~vbeln
 lips~posnr
 LIPS~VGBEL
 INTO (IT_ORDERDETAILSvbak, IT_ORDERDETAILSbstnk, IT_ORDERDETAILSerdat, IT_ORDERDETAILSmatnr, IT_ORDERDETAILSkwmeng, IT_ORDERDETAILSd_vbeln,IT_ORDERDETAILSposnr, IT_ORDERDETAILSkunnr)
FROM VBAK left outer JOIN VBAP ON ( VBAKVBELN = VBAPVBELN )
left outer JOIN LIPS ON ( VBAKVBELN = LIPSVGBEL )
join LIKP on ( LIPSVBELN = LIKPVBELN )
WHERE VBAK~ERDAT IN CR_DATE.
I am getting error in the query.
Please suggest.
Thanks,
Rajesh

Hi rajesh.nayakbola,
although this is not quite the right place for this, let me give you some notes:
1. Code should be
formatted as code
by markin it with mouse and use above <> button.
2. Internal tables shoult not be declared using OCCURS clause - this is last century style
3. Internal tables do not need and should not have a header line, they should use TYPES for declaration
4. Data should not be declared using LIKE: If they refer to dictionary TYPES, use TYPE. LIKE is only mandatory for data objects declared in your program, i.e. DATA IT_some_ORDERDETAILS like IT_ORDERDETAILS.
5. If you get an error here, never write "I am getting error" but copy and paste the error message fully.
- The fields in brackets in the INTO clause never have ~ character, there is no IT_ORDERDETAILS~vbak, only IT_ORDERDETAILS-vbeln
It could be something like this:
TYPES:
BEGIN OF TY_ORDERDETAILS,
VBELN TYPE VBAK-VBELN, "Order number
BSTNK TYPE VBAK-BSTNK, "customer PO
ERDAT TYPE VBAK-ERDAT, " Order created date
MATNR TYPE VBAP-MATNR, "Sales order line item
KWMENG TYPE VBAP-KWMENG, "Quantity
D_VBELN TYPE likp-vbeln, " delivery no
POSNR TYPE lips-posnr, " delivery item
KUNNR TYPE LIKP-KUNNR, "ship quantity
END OF TY_ORDERDETAILS.
DATA:
IT_ORDERDETAILS TYPE TABLE OF TY_ORDERDETAILS.
SELECT VBAK~VBELN
VBAK~BSTNK
VBAK~ERDAT
VBAP~MATNR
VBAP~KWMENG
likp~vbeln AS D_VBELN
lips~posnr
LIKP~KUNNR
INTO CORRSPONDING FIELDS OF TABLE IT_ORDERDETAILS
FROM VBAK left outer JOIN VBAP ON ( VBAK~VBELN = VBAP~VBELN )
left outer JOIN LIPS ON ( VBAK~VBELN = LIPS~VGBEL )
join LIKP on ( LIPS~VBELN = LIKP~VBELN )
WHERE VBAK~ERDAT IN CR_DATE.
Regards,
Clemens

Number of lines of a select query

Similar Messages

Maybe you are looking for