Select query in routing(operation,sequence)

Hello frds,
i am into change routing BDC actually i want a select query .....for like existing of operation for a particular sequence in routing....
if i will found operation for particular sequence i will run the bdc code lese i will exit...any one can help me...
just provide me a query....to check existnece of operation for a particular sequence......ASAP...

Why on earth would you want to keep the queries separate? As Tom Kyte would say, databases are born to join!
Providing emp_id has an index on it (and it should, assuming it's the table's primary key!) your "complex" (or, what I would call simple*), it'll most likely be faster than doing it separately. You've not got the context switches for one thing.
If you want to see what the optimizer does with your query, you should run a trace on the query. An explain plan would give you an idea of what it's going to do, too.
In general, doing something like this procedurally is going to almost certainly be worse than doing it in SQL (and by worse, I mean slower).
* I'd hate to see what you'd call some of the monster queries I work with, if you think that query is complex!

Similar Messages

Splitting complex SQL select query in to independent sequence of small queries.

=====================
Problem Description
=====================
Consider I have the following table structures with approx no. of records in each.
Employee Table
emp_id:
name :
dept_id:
#Approx no. of rows in the table: 1 million
Department Table
dept_id:
dept_name:
#Approx no. of rows in the table: 1 Hundred
=====================
Target Result: is to get the employee name who's id is '100' and the department name he belongs to.
=====================
=====================
Ideal Query : Consider it as COMPLEX QUERY
=====================
select emp.name,dept.name
from     employee emp, department dept
where
     emp.dept_id = dept.dept_id
     and
     emp.emp_id = '100';
=====================
Optimized Independent Queries : Consider it as SIMPLE QUERIES
=====================
Now i want to split the above query in to two independent queries.
Query #1
select emp.name
from     employee emp
where emp.id = '100';
:: Returns one row as emp.id is unique.
Query #2
select dept.dept_id, dept.name
from department dept
:: Returns 100 rows as there are only 100 rows.
=====================
Need Your Suggestions Here
=====================
If you compare the COMPLEX QUERY against SIMPLE QUERIES, i prefer to use SIMPLE QUERIES, get the results
and compare department id against two results programmatically and then get the final result. I know the database
query engines will do similar query optimization like dividing COMPLEX QUERY to SIMPLE QUERIES and run them
in some specific order to get results faster.
Now is it possible to get the exact sub queries which the database query engine (ANY database query engine) generates
out of complex select query? I mean i don't want to do the splitting manually but i still need those sub-queries.
Can any one help me out please?

Why on earth would you want to keep the queries separate? As Tom Kyte would say, databases are born to join!
Providing emp_id has an index on it (and it should, assuming it's the table's primary key!) your "complex" (or, what I would call simple*), it'll most likely be faster than doing it separately. You've not got the context switches for one thing.
If you want to see what the optimizer does with your query, you should run a trace on the query. An explain plan would give you an idea of what it's going to do, too.
In general, doing something like this procedurally is going to almost certainly be worse than doing it in SQL (and by worse, I mean slower).
* I'd hate to see what you'd call some of the monster queries I work with, if you think that query is complex!

Select Query using AND operation

Hello,
I am developing RFC which will retrieve some records from SAP HR module table.
Input will be one structure (INPUT_TABLE) containing 4 fields. User may enter values for any fields, and my requirement is to perform a AND operation on those entered fields only. Currently i am writing query as follows :
SELECT DISTINCT apernr aVORNA aNACHN acname a~gbdat FROM
              PA0002 as a INTO CORRESPONDING FIELDS OF TABLE Z_PD_TABLE
                                            WHERE apernr = INPUT_TABLE-pernr AND aVNAMC = INPUT_TABLE-VORNA AND aNCHMC = INPUT_TABLE-NACHN AND agbdat = INPUT_TABLE-GBDAT .
If only 2 values are entered by user out of 4 , it will perform AND operation by taking other values as blank or 000000. I want to skip these AND operation on fields which are not entered by user.
Please help for writing query.
Thanks in advance,
Prashant

Hi,
Create dynamic where condition based upon user input.
Try like this....
IF NOT INPUT_TABLE-pernr IS INITIAL.
      CLEAR : lv_pernr_condition.
      CONCATENATE 'PERNR' ' = ' '''' INPUT_TABLE-pernr '''' INTO
      lv_pernr_condition.
ENDIF.
IF NOT INPUT_TABLE-vnamc IS INITIAL.
      CLEAR : lv_vnamc_condition.
      CONCATENATE 'VNAMC' ' = ' '''' INPUT_TABLE-vnamc '''' INTO
      lv_vnamc_condition.
ENDIF.
IF NOT INPUT_TABLE-vorna IS INITIAL.
      CLEAR : lv_vorna_condition.
      CONCATENATE 'VORNA' ' = ' '''' INPUT_TABLE-vorna '''' INTO
      lv_vorna_condition.
ENDIF.
IF NOT INPUT_TABLE-nchmc IS INITIAL.
      CLEAR : lv_nchmc_condition.
      CONCATENATE 'NCHMC' ' = ' '''' INPUT_TABLE-nchmc '''' INTO
      lv_nchmc_condition.
ENDIF.
IF NOT INPUT_TABLE-gbdat IS INITIAL.
      CLEAR : lv_gbdat_condition.
      CONCATENATE 'GBDAT' ' = ' '''' INPUT_TABLE-gbdat '''' INTO
      lv_gbdat_condition.
ENDIF.
IF NOT lv_pernr_condition IS INITIAL.
      CONCATENATE lv_pernr_condition lv_condition
      INTO lv_condition SEPARATED BY space.
ENDIF.
IF NOT lv_vnamc_condition IS INITIAL.
      IF lv_condition IS INITIAL.
        CONCATENATE lv_vnamc_condition lv_condition
            INTO lv_condition SEPARATED BY space.
      ELSE.
        CONCATENATE lv_condition 'AND' lv_vnamc_condition
            INTO lv_condition SEPARATED BY space.
      ENDIF.
ENDIF.
IF NOT lv_vorna_condition IS INITIAL.
      IF lv_condition IS INITIAL.
        CONCATENATE lv_vorna_condition lv_condition
            INTO lv_condition SEPARATED BY space.
      ELSE.
        CONCATENATE lv_condition 'AND' lv_vorna_condition
            INTO lv_condition SEPARATED BY space.
      ENDIF.
ENDIF.
IF NOT lv_nchmc_condition IS INITIAL.
      IF lv_condition IS INITIAL.
        CONCATENATE lv_nchmc_condition lv_condition
            INTO lv_condition SEPARATED BY space.
      ELSE.
        CONCATENATE lv_condition 'AND' lv_nchmc_condition
            INTO lv_condition SEPARATED BY space.
      ENDIF.
ENDIF.
IF NOT lv_gbdat_condition IS INITIAL.
      IF lv_condition IS INITIAL.
        CONCATENATE lv_gbdat_condition lv_condition
            INTO lv_condition SEPARATED BY space.
      ELSE.
        CONCATENATE lv_condition 'AND' lv_gbdat_condition
            INTO lv_condition SEPARATED BY space.
      ENDIF.
ENDIF.
SELECT DISTINCT pernr VORNA NACHN cname gbdat FROM
PA0002 INTO CORRESPONDING FIELDS OF TABLE Z_PD_TABLE
WHERE lv_condition .   " Dynamic where condition
Hope it will helps

Like with select query

Hi,
I have a query something like ...
Select ....
where
b.prodname like 'SHAFT GEAR%' or b.prodname like '%FRONT GEAR%' or b.prodname like '%BREAK 4K%'
and
b.prodname like
(select company name from companyms
where <some comdition>
order by 3,6
I am stucking at :
b.prodname like
(select company name from companyms
where <some comdition>
i.e. how do I give select query with like operator.
In above query I want b.prodname like above and those company name for which I am giving condition. Company names are stored in other table and I want to select and use them with like operator.
Thanks.

create table stock
prodname varchar2(50)
insert into stock values ('MICRO FRONT PANEL');
insert into stock values ('ZEBRA FRONT SHAFT');
insert into stock values ('KOBRA SHAFT GEAR');
insert into stock values ('T RUBBER TUBES');
insert into stock values ('MICRO TUBES PANELS');
insert into stock values ('HEFT SHAFT GEAR');
SELECT * FROM STOCK;
PRODNAME
MICRO FRONT PANEL
ZEBRA FRONT SHAFT
KOBRA SHAFT GEAR
T RUBBER TUBES
MICRO TUBES PANELS
HEFT SHAFT GEAR
6 rows selected.
create table companyms
company_name varchar2(50)
insert into companyms values ('MICRO');
insert into companyms values ('CHOPRA');
insert into companyms values ('H.P.');
insert into companyms values ('T');
insert into companyms values ('BEST BROTHERS');
insert into companyms values ('FIVE STAR');
SELECT * FROM COMPANYMS;
COMPANY_NAME
MICRO
CHOPRA
H.P.
T
BEST BROTHERS
FIVE STAR
6 rows selected.
Actually I have little big query which have inner join with couple of more tables and suppose query returned me to select those rows who have SHAFT GEAR or FRONT GEAR or BREAK 4K of MICRO or ZEBRO or ABC company.
So, I have query like :
select ...
.... some inner join...
.... some outer join
.... some union
SOME MORE WHERE CLAUSES ... ETC. ETC...
where b.prodname (b means stock table) like 'SHAFT GEAR%' or 'FRONT PANEL%'
FOR MICRO or ZEBRA or ABC company.

Query in Select query operation

Please excuse me for posting this again.
I'm stuck up with this for 3 days. Lenghty post pls do read and help me.
How is the select query going to be changed in the SAP so that the original database behind it understands it. I want to know the operation of IN operation in where clause where in we can use ranges.
I'm asking this because I'm facing a problem using Native SQL.
Query is like this:
EXEC SQl.
OPEN C1 for
SELECT field1 from table@domain where field2 IN :ABAP_VAR.
ENDEXEC.
EXEC SQL.
FETCH C1 NEXT INTO :VAR1 , :VAR2
ENDEXEC.
Oracle usually recognises this statement IN ( '2222' , '3658' , '6895' )
But here this field that is build dynamically like this is not recognising them as seperate fileds but instead it is taking them as a single string and not selecting anything.
But if a single value is passed it is fetching the data into the cursor. And the code is working fine.
Any help in this is highly appreciable.

"if a in r_range" is is effectively: does the value held in 'a' comply with the values held in range 'r_range'. Ranges can hold NE, patterns etc so this can get quite complex.
You can see that it is very different from the SQL type IN.
If your range hold several values you could unstrip it into a string varaible so that it ended up having a value something like: ( '2222' , '3658' , '6895' ). Not sure if you need the '(' but it would be something like this:
eg,
assuming your range is simple and only holds 'I' and 'EQ' values:
data v_string type string.
loop at r_range.
concatenate v_string '@''' r_range-low '''@' into v_string.
endloop.
REPLACE
ALL OCCURRENCES OF '@'
IN v_string
WITH ' '.
Then you can use:
SELECT field1 from table@domain where field2 IN :v_string.

Sequence selection in Rate Routing

hi,
In Normal Routing in sequence overview - extras - new entries we can find the option of creating a Parallel or Alt sequence, but in Rate routing there is no way to select the type of Sequence. It by default shows Parallel sequence.
Pl. let me know the step by step proceduer to create a Alternate sequence in Rate routing.
regards

Dear Rishi,
We cant create any alternative sequence for a rate routing.This is one of the difference between routing and rate routing.
Rate routing supports only standard and parallel sequence.
If alternative sequence is present in a routing,then at the time of order creation the system gives a pop to select for alternative
sequence or to skip it and proceed.
For this under OPL8,for plant order type combination the field sequence exchange should be having value 2 - manual selection.
Creating production version or sequence in my understanding depends on the business requirement.
Check and revert
Regards
S Mangalraj

Need to select all equipments (PRT) for a plan (routing) operation (PLPO)

hi,
I need to select all assigned equipments (PRT) for a plan (routing) operation (PLPO).
Can anybody tell me the database table relation or is there a function module or a BAPI or something like this !?
Thanks
Olaf
Edited by: Olaf Krüger on Feb 20, 2008 12:03 PM: BADI to BAPI

I suppose you have every PLPO needed (else look at function module WOSTS_TASKLIST_READ_FROM_DB)
Then read
PLMZ Allocation of bill of material items to operations
STPO BOM item
SELECT * FROM plmz INTO TABLE t_plmz
    FOR ALL ENTRIES IN t_plpo
    WHERE plnty = t_plpo-plnty
      AND plnnr = t_plpo-plnnr
      AND plnkn = t_plpo-plnkn.
SELECT * FROM stpo INTO TABLE t_stpo
    FOR ALL ENTRIES IN t_plmz
    WHERE stlty = t_plmz-stlty
      AND stlnr = t_plmz-stlnr
      AND stlkn = t_plmz-stlkn.
Regards

How to use string operation in where clause of select query

Hello All,
I just want to know how can i write a restriction in select query saying retrive data only begins with name "DE*".
Explaination: If my table has records and names starts with character then i want to write a query to fetch all the records in which names starts with DE*.
Thanks in advance for your quick reply...
Dev.

Hi
In the where clause you need to write like
WHERE NAME LIKE 'DE%'
Regards
Sudheer

Select query not working with like & and operator

Hi,
The below is the select query which is used to select only the failed rollup jobs from DB table ( background jobs ) the status 'A' which means only the failed roll up jobs.
select jobname status from v_op into table zjob_rollup where jobname like '%ROLLUP%'
                                                         or jobname like 'BI_AGGR%'
                                                         and status like 'A'.
Right now my internal tables is picking the job name other than status A also.
Can you please help.
Note: Ps consider the performance of select query also.
Thanks,
Siva

Hi,
select jobname status
     from v_op
     into table zjob_rollup
     where ( jobname like '%ROLLUP%' or jobname like 'BI_AGGR%' )
                  and status = 'A'.

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'.

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.

Regarding to perform in select query

could any tell the select query in this piece of code would affect the performance of the programe
DATA: BEGIN OF OUTREC,
      BANKS LIKE BNKA-BANKS,
      BANKL LIKE BNKA-BANKL,
      BANKA LIKE BNKA-BANKA,
      PROVZ LIKE BNKA-PROVZ,   "Region (State, Province, County)
      BRNCH LIKE BNKA-BRNCH,
      STRAS LIKE BNKA-STRAS,
      ORT01 LIKE BNKA-ORT01,
      SWIFT LIKE BNKA-SWIFT,
END OF OUTREC.
OPEN DATASET P_OUTPUT FOR OUTPUT IN TEXT MODE.
IF SY-SUBRC NE 0. EXIT. ENDIF.
SELECT * FROM BNKA
         WHERE BANKS EQ P_BANKS
         AND   LOEVM NE 'X'
         AND   XPGRO NE 'X'
         ORDER BY BANKS BANKL.
PERFORM TRANSFER_DATA.
ENDSELECT.
CLOSE DATASET P_OUTPUT.
*&      Transfer the data to the output file
FORM TRANSFER_DATA.
OUTREC-BANKS = BNKA-BANKS.
OUTREC-BANKL = BNKA-BANKL.
OUTREC-BANKA = BNKA-BANKA.
OUTREC-PROVZ = BNKA-PROVZ.
OUTREC-BRNCH = BNKA-BRNCH.
OUTREC-STRAS = BNKA-STRAS.
OUTREC-ORT01 = BNKA-ORT01.
OUTREC-SWIFT = BNKA-SWIFT.
TRANSFER OUTREC TO P_OUTPUT.
ENDFORM.                               " READ_IN_DATA

Hi
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.
Points # 1/2
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
2.     Select all the records in a single shot using into table clause of select statement rather than to use Append statements.
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.
4.     For testing existence , use Select.. Up to 1 rows statement instead of a Select-Endselect-loop with an Exit.
5.     Use Select Single if all primary key fields are supplied in the Where condition .
Point # 1
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.
Point # 2
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'.
Point # 3
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.
Point # 4
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.
Point # 5
If all primary key fields are supplied in the Where condition you can even use Select Single.
Select Single requires one communication with the database system, whereas Select-Endselect needs two.
Select Statements           contd.. SQL Interface
1.     Use column updates instead of single-row updates
to update your database tables.
2.     For all frequently used Select statements, try to use an index.
3.     Using buffered tables improves the performance considerably.
Point # 1
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.
Point # 2
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.
Point # 3
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       contd           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    contdFor 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    contd Select Over more than one Internal table
1.     Its better to use a views instead of nested Select statements.
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.
3.     Instead of using nested Select loops it is often better to use subqueries.
Point # 1
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
Point # 2
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.
Point # 3
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.
2.     Always try to use binary search instead of linear search. But dont forget to sort your internal table before that.
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.
6.     Modifying selected components using MODIFY itab TRANSPORTING f1 f2.. accelerates the task of updating a line of an internal table.
Point # 2
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 ) ).
Point # 3
READ TABLE ITAB INTO WA WITH KEY K = 'X'. IS FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY (NAME) = 'X'.
Point # 5
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.
Point # 6
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
8.    If collect semantics is required, it is always better to use to COLLECT rather than READ BINARY and then ADD.
9.    "APPEND LINES OF itab1 TO itab2" accelerates the task of appending a table to another table considerably as compared to LOOP-APPEND-ENDLOOP.
10.   DELETE ADJACENT DUPLICATES accelerates the task of deleting duplicate entries considerably as compared to READ-LOOP-DELETE-ENDLOOP.
11.   "DELETE itab FROM ... TO ..." accelerates the task of deleting a sequence of lines considerably as compared to DO -DELETE-ENDDO.
Point # 7
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.
Point # 8
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)) .
Point # 9
APPEND LINES OF ITAB1 TO ITAB2.
This is more optimized as compared to
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
Point # 10
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.
Point # 11
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.
13.   Specify the sort key as restrictively as possible to run the program faster.
Point # 12
ITAB2[] = ITAB1[].
This is much more optimized as compared to
REFRESH ITAB2.
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
Point # 13
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.

Operation sequence

Hi, my operation sequence is mix of std and parellel, how to maintain the same thru ca01? when i click on sequence, always std is appearing and it is grade out, not changable. how to select diffenrt seq like parallel or alternative>?

Dear Yadav,
Plz refer this link
[Routing;
Regards
kumar

Unplanned Inspection Characteristics in Routing - Operation

Hi experts,
What is the use of the function Unplanned Inspection Characteristics in Routing - Operation ? Its normally grayed off.
I am aware of the same in RR of the Inspection Lot.
Thanx
George

Hello Jomy,
Ok so you were asking the same for Production order. You wrote routing operation and my mind stuck there since I read it. I was searching for it. You make good exercised to me. LOL!!!
Anyways, in the production or process order the unplanned MIC does the same task of job what it used to de in QE51N or any other RR work sheet. And you can assign the Unplanned MIC to Pro. Order itself to the relevant operation. Let it be gray there, you just follow the steps to attach an unplanned MIC to Operation in the Order, and the same will be reflated to RR screen also.
- Select the operation line item.
- Now follow the path,,, Operation->Function for phase / for operation->Unplanned Inspection characteristics.
- Now it will lead you to the same screen for unplanned characteristic as you can have in other RR work lists.
Pls revert if there is any query.
Regards,
Shyamal

Oracle SQL Select query takes long time than expected.

Hi,
I am facing a problem in SQL select query statement. There is a long time taken in select query from the Database.
The query is as follows.
select /*+rule */ f1.id,f1.fdn,p1.attr_name,p1.attr_value from fdnmappingtable f1,parametertable p1 where p1.id = f1.id and ((f1.object_type ='ne_sub_type.780' )) and ( (f1.id in(select id from fdnmappingtable where fdn like '0=#1#/14=#S0058-3#/17=#S0058-3#/18=#1#/780=#5#%')))order by f1.id asc
This query is taking more than 4 seconds to get the results in a system where the DB is running for more than 1 month.
The same query is taking very few milliseconds (50-100ms) in a system where the DB is freshly installed and the data in the tables are same in both the systems.
Kindly advice what is going wrong??
Regards,
Purushotham

SQL> @/alcatel/omc1/data/query.sql
2 ;
9 rows selected.
Execution Plan
Plan hash value: 3745571015
| Id | Operation | Name |
| 0 | SELECT STATEMENT | |
| 1 | SORT ORDER BY | |
| 2 | NESTED LOOPS | |
| 3 | NESTED LOOPS | |
| 4 | TABLE ACCESS FULL | PARAMETERTABLE |
|* 5 | TABLE ACCESS BY INDEX ROWID| FDNMAPPINGTABLE |
|* 6 | INDEX UNIQUE SCAN | PRIMARY_KY_FDNMAPPINGTABLE |
|* 7 | TABLE ACCESS BY INDEX ROWID | FDNMAPPINGTABLE |
|* 8 | INDEX UNIQUE SCAN | PRIMARY_KY_FDNMAPPINGTABLE |
Predicate Information (identified by operation id):
5 - filter("F1"."OBJECT_TYPE"='ne_sub_type.780')
6 - access("P1"."ID"="F1"."ID")
7 - filter("FDN" LIKE '0=#1#/14=#S0058-3#/17=#S0058-3#/18=#1#/780=#5#
8 - access("F1"."ID"="ID")
Note
- rule based optimizer used (consider using cbo)
Statistics
0 recursive calls
0 db block gets
0 consistent gets
0 physical reads
0 redo size
0 bytes sent via SQL*Net to client
0 bytes received via SQL*Net from client
0 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
9 rows processed
SQL>

Select query in routing(operation,sequence)

Similar Messages

Maybe you are looking for