Bind variables improve the performence of query??

Hi,
Bind variables improve the performence of program or SQL Query.
Select empno,ename,sal from emp where empno=:eno;
select sal into :vno from emp;
According to these queries i am asking performence of bind variables to learn more from you.
Regards,
Venkat.
Edited by: Venkata2 on Sep 16, 2008 6:40 PM

Karthick_Arp wrote:
any variable inside a stored procedure is a bind variable.
using bind variables can help you avoid hard parse. which leads to performance improvement.
Well, you mentioned pros and I will mention cons. Since bind variable value is not known until execution time optimizer can not select best plan. So Oracle introduced bind variable peeking where plan is deferred until first execution. With bind variable peeking optimizer costructs plan using bind variable values at the first execution. However, if first execution has "not typical" bind variable values we end up with sub-optimal plan.
SY.
P.S. Please do not consider my reply as "we should not use bind variables".

Similar Messages

How to use bind variables in the following query

CREATE OR REPLACE PROCEDURE MMDB.test IS
sel_qtn VARCHAR2 (10);
CURSOR PT_QUANTITY IS select * from mmdb.product_tree WHERE QUANTITY_CHECK ='E'
AND run_id = 100
a PT_QUANTITY%ROWTYPE;
BEGIN
FOR i IN PT_QUANTITY
loop
sel_qtn := i.quanttity-1;
While sel_qtn>=1
loop
insert into mmdb.product_tree (BILLING_ACCOUNT_NO ,S_CODE) values (i.BILLING_ACCOUNT_NO ,i.S_CODE||'E');
sel_qtn :=sel_qtn -1;
End loop;
commit;
end;

Don't duplicate threads: How to use bind variables in the following query

Hi very urgent How to improve the performence of the program

Hi all please tell me how to improve the performence of this program......
REPORT z03_gil010 NO STANDARD PAGE HEADING LINE-SIZE 130.
                             INCLUDE                                 *
INCLUDE: z00_bci010.                   " Gestion des anomalies.
                      Déclaration des données                        *
                   Tables de la bases de données                     *
TABLES:
        ekpo,        " Poste document d'achat.
        lfa1,        " Base fournisseurs (généralités).
        marc,        " Données division de l'article.
        z03_bw_cmp1,
        eord,        "Répertoire des sources appro. Achats
        eina,        "Fiche infos-achats - données générales
        t024,        "Groupes d'acheteurs
        tvarv.                                              "FAE17345+
                   Déclaration des données internes                  *
Déclaration de la table interne qui permet de recuperer les mois.
DATA: BEGIN OF itb_months OCCURS 12.
        INCLUDE STRUCTURE t247.
DATA: END OF itb_months.
Table pour récupération d'infos sur les divisions
DATA: BEGIN OF itb_t001w OCCURS 0,
        werks LIKE t001w-werks,
        fabkl LIKE t001w-fabkl," Clé du calendrier d'entreprise
      END OF itb_t001w.
Déclaration de la table interne contenant les infos sur l'adresse du
fournisseur.
DATA: BEGIN OF itb_adresse OCCURS 0,
        lifnr LIKE lfa1-lifnr,           " Numéro de compte fournisseur.
        name1 LIKE lfa1-name1,                              " Nom 1.
        name2 LIKE lfa1-name2,                              " Nom 2.
        name3 LIKE lfa1-name3,                              " Nom 3.
        name4 LIKE lfa1-name4,                              " Nom 4.
        stras LIKE lfa1-stras,           " N° de rue et nom de la rue.
        pstlz LIKE lfa1-pstlz,           " Code postal.
        ort01 LIKE lfa1-ort01,           " Localité.
        pfach LIKE lfa1-pfach,           " Boîte postale.
        pstl2 LIKE lfa1-pstl2,           " Code de la boîte postale.
        land1 LIKE lfa1-land1,           " Clé de pays.
        landx LIKE t005t-landx,          " Pays.
        spras LIKE lfa1-spras,           " Code langue
END OF itb_adresse.
Déclaration d'une table interne pour les informations sur les
prévisions de commande.
DATA: BEGIN OF itb_prev_cde OCCURS 0,
        werks LIKE marc-werks,            " Division
        idnlf LIKE eina-idnlf,            " ADDsde ref article frn
        lifnr LIKE eord-lifnr,            " N° fournisseur.
        ekgrp LIKE marc-ekgrp,            " Groupe d'acheteurs
        dispo LIKE marc-dispo,            " Code gestionnaire MRP
        matnr LIKE eord-matnr,            " Article.
        maktx LIKE makt-maktx,            " Désignation article.
        bstmi LIKE marc-bstmi,            " Quantité de commande.
        men00 LIKE plaf-gsmng,            " Quantité du mois en cours M.
        men01 LIKE plaf-gsmng,            " Quantité pour le mois M+1.
        men02 LIKE plaf-gsmng,            " Quantité pour le mois M+2.
        men03 LIKE plaf-gsmng,            " Quantité pour le mois M+3.
        men04 LIKE plaf-gsmng,            " Quantité pour le mois M+4.
        men05 LIKE plaf-gsmng,            " Quantité pour le mois M+5.
        men06 LIKE plaf-gsmng.            " Quantité pour le mois M+6.
DATA: END OF itb_prev_cde.
Structure de travail pour les commandes convernant les PFC
DATA str_pca_pfc LIKE itb_prev_cde.
*add sde
DATA str_eord_pfc LIKE itb_prev_cde.
Structure de travail pour les prévisons PFC
DATA str_prev_pfc LIKE itb_prev_cde.
Déclaration d'une table interne pour les informations sur le
portefeuille des commandes d'achat.
DATA: BEGIN OF itb_pca OCCURS 0,
        werks LIKE ekpo-werks,    " Division
        idnlf LIKE eina-idnlf,     " ADDsde ref article frn
        lifnr LIKE eord-lifnr,    " N° fournisseur.
        ekgrp LIKE marc-ekgrp,    " Groupe d'acheteurs
        dispo LIKE marc-dispo,    " Code gestionnaire MRP
        matnr LIKE eord-matnr,    " Article.
        maktx LIKE makt-maktx,    " Désignation article.
        ebeln LIKE ekes-ebeln,    " Numéro du document d'achat.
        ebelp LIKE ekes-ebelp,    " Numéro de poste du document d'achat.
        slfdt LIKE eket-slfdt,    " Date de livraison statistique
        eindt LIKE ekes-eindt,    " Date de livraison indiquée dans la
                                  " confirmation de la cde.
        menge LIKE ekes-menge,    " Quantité indiquée dans la confirma-
                                  " tion de la commande.
        attdu LIKE eket-wemng,    " Portefeuille fournisseur.
        netpr LIKE ekpo-brtwr,    " Prix net du document d'achat dans
                                  " la devise du document.
        rtard TYPE i,             " Retard en jours ouvres.
        wemng LIKE eket-wemng,    " Quantité de l'entrée de marchandise.
        bldat LIKE mkpf-bldat,    " Date inscrite sur la pièce/sur le
                                  " document.
        qtran LIKE ekes-menge,    " Quantité en transit.
        dtran LIKE ekes-eindt.    " Date du dernier avis de transit.
DATA: END OF itb_pca.
DATA: w_i TYPE i,                "Compteur
      w_i_char(1) TYPE c,        "Texte pour récupérer compteur
      w_nm_zone(20) TYPE c,      "Nom zone pour assign au field-symbols
      w_nb_j TYPE i,             "Nb de jours ouvrés jusqu'à fin mois
      w_nb_j_tot TYPE i.         "Nb de jours ouvrés du mois
FIELD-SYMBOLS:       TYPE ANY.
Déclaration d'une table contenant les fiches info achat.
DATA: BEGIN OF itb_eina OCCURS 0,
        matnr LIKE eina-matnr,
        lifnr LIKE eina-lifnr,
        idfnl LIKE eina-idnlf.
DATA: END OF itb_eina.
Déclaration d'une table contenant les infos groupe acheteur.
*DATA: BEGIN OF itb_t024 OCCURS 0,
       ekgrp LIKE t024-ekgrp,
       eknam LIKE t024-eknam,
       ektel LIKE t024-ektel,
       telfx LIKE t024-telfx.
*DATA: END OF itb_t024.
Déclaration d'une table pour le transfert du fichier.
DATA: BEGIN OF itb_transfert OCCURS 0,
        col00(8),                 "division
        col00bis(20),             "Reference article
        col01(18),                "No article
        col02(45),                "libelle article
        col021(17),               "Groupe acheteur
        col022(13),               "gestionnaire
        col03(17),                "qte commandée ou No de commande
        col04(13),                "Mois 1 ou No poste cde
        col05(20),                "Mois 2 ou délai initial
        col06(33),                "Mois 3 ou délai négocié
        col07(13),                "Mois 4 ou qté cdée
        col08(13),                "Mois 5 ou qté attendue
        col09(13),                "Mois 6 ou Montant attendu
        col10(13),                "Mois 7 ou retard
        col11(13),                "qte partielle livree
        col12(13),                "date livraison partielle
        col13(13),                "qté en transit
        col14(13).                "date
DATA: END OF itb_transfert.
Déclaration d'une table contenant la liste des fournisseurs.
DATA: BEGIN OF itb_lifnr OCCURS 0,
        werks LIKE marc-werks,
        idfnl LIKE eina-idnlf,
        lifnr LIKE eord-lifnr,
        ekgrp LIKE marc-ekgrp,
        spras LIKE lfa1-spras,
        eknam LIKE t024-eknam,
        ektel LIKE t024-ektel,
        telfx LIKE t024-telfx.
DATA: END OF itb_lifnr.
Déclaration d'une structure pour la selection dans la table MSEG.
DATA : BEGIN OF itb_mseg OCCURS 0,
         mblnr LIKE mseg-mblnr,
         mjahr LIKE mseg-mjahr,
         ebeln LIKE mseg-ebeln,
         ebelp LIKE mseg-ebelp,
       END OF itb_mseg.
déclaration d'une structure pour la selection dans EKPO.
DATA : BEGIN OF itb_ekpo OCCURS 0,
         lifnr LIKE ekko-lifnr,
         ebeln LIKE ekpo-ebeln,
         ebelp LIKE ekpo-ebelp,
         menge LIKE ekpo-menge,
         bpumz LIKE ekpo-bpumz,
         bpumn LIKE ekpo-bpumn,
         matnr LIKE ekpo-matnr,
         werks LIKE ekpo-werks,
         netpr LIKE ekpo-netpr,
         peinh LIKE ekpo-peinh, "Base de prix FAE17345+
         ekgrp LIKE ekko-ekgrp,   "AFT++
         dispo LIKE marc-dispo,   "AFT++
       END OF itb_ekpo.
déclaration d'une structure pour la selection dans EKPO.
DATA : BEGIN OF itb_ekko OCCURS 0,
         ebeln LIKE ekko-ebeln,
         lifnr LIKE ekko-lifnr,
         spras LIKE ekko-spras,
       END OF itb_ekko.
déclaration d'une structure pour la selection dans EKES.
DATA : BEGIN OF itb_ekes OCCURS 0,
         ebeln LIKE eket-ebeln,
         ebelp LIKE eket-ebelp,
         ebtyp LIKE ekes-ebtyp,
         eindt LIKE ekes-eindt,
         menge LIKE ekes-menge,
         dabmg LIKE ekes-dabmg,
         etens LIKE ekes-etens,
       END OF itb_ekes.
déclaration d'une structure pour la selection dans EKET
DATA : BEGIN OF itb_eket OCCURS 0,
         ebeln LIKE eket-ebeln,
         ebelp LIKE eket-ebelp,
         menge LIKE eket-menge,
         wemng LIKE eket-wemng,
         eindt LIKE eket-eindt,
         slfdt LIKE eket-slfdt,
       END OF itb_eket.
déclaration d'une structure pour la selection dans MKPF.
DATA : BEGIN OF itb_mkpf OCCURS 0,
         mblnr LIKE mkpf-mblnr,
         mjahr LIKE mkpf-mjahr,
         bldat LIKE mkpf-bldat,
       END OF itb_mkpf.
Déclaration d'une structure pour la sélection dans EORD.
DATA : BEGIN OF itb_eord OCCURS 0,
         matnr LIKE eord-matnr,
         werks LIKE eord-werks,
         lifnr LIKE eord-lifnr,
         ekgrp LIKE marc-ekgrp,
         dispo LIKE marc-dispo,                             "DE3K924352
         disls LIKE marc-disls,
         bstfe LIKE marc-bstfe,
         bstrf LIKE marc-bstrf,
         bstmi LIKE marc-bstmi,
         bstma LIKE marc-bstma,
       END OF itb_eord.
DATA : BEGIN OF itb_eordw OCCURS 0.
        INCLUDE STRUCTURE itb_eord.
DATA : END OF itb_eordw.
Déclaration d'une structure pour la sélection dans MAKT.
DATA : BEGIN OF itb_makt OCCURS 0,
         matnr LIKE makt-matnr,
         spras LIKE makt-spras,
         maktx LIKE makt-maktx,
       END OF itb_makt.
Déclaration d'une structure pour la sélection dans EBAN.
DATA : BEGIN OF itb_eban OCCURS 0,
         matnr LIKE eban-matnr,
         werks LIKE eban-werks,
         flief LIKE eban-flief,
         lfdat LIKE eban-lfdat,
         menge LIKE eban-menge,
         bsmng LIKE eban-bsmng,
         webaz LIKE eban-webaz,
         ekgrp LIKE eban-ekgrp,
         ebeln LIKE eban-ebeln,
         banfn LIKE eban-banfn,
         bnfpo LIKE eban-bnfpo, "DB3K900702+
       END OF itb_eban.
Déclaration d'une structure pour la sélection dans PLAF.
DATA : BEGIN OF itb_plaf OCCURS 0,
         plnum LIKE plaf-plnum, "DB3K900702+
         matnr LIKE plaf-matnr,
         plwrk LIKE plaf-plwrk,
         flief LIKE plaf-flief,
         pedtr LIKE plaf-pedtr,
         gsmng LIKE plaf-gsmng,
         webaz LIKE plaf-webaz,
       END OF itb_plaf.
Déclaration d'une structure pour la sélection dans MARC.
DATA : BEGIN OF itb_marc OCCURS 0,
         matnr LIKE marc-matnr,
         werks LIKE marc-werks,
         disls LIKE marc-disls,
         bstrf LIKE marc-bstrf,
         bstmi LIKE marc-bstmi,
         bstma LIKE marc-bstma,
         bstfe LIKE marc-bstfe,
         ekgrp LIKE marc-ekgrp,
         dispo LIKE marc-dispo,
       END OF itb_marc.
DATA : BEGIN OF itb_marc_eord OCCURS 0,
          matnr LIKE marc-matnr,
          werks LIKE marc-werks,
          strgr LIKE marc-strgr,   "groupe de stratégie planif
       END OF itb_marc_eord.
DATA : BEGIN OF itb_z03_bw_cmp1 OCCURS 0,
         matnr LIKE z03_bw_cmp1-matnr,
         werks LIKE z03_bw_cmp1-werks,
         pdatu LIKE z03_bw_cmp1-pdatu,
         plnmg LIKE z03_bw_cmp1-plnmg,
       END OF itb_z03_bw_cmp1.
Begin change BNI <DE3K937051>
DATA : BEGIN OF itb_z03_bw_cmp2 OCCURS 0,
         matnr LIKE z03_bw_cmp2-matnr,
         werks LIKE z03_bw_cmp2-werks,
         pdatu LIKE z03_bw_cmp2-pdatu,
         plnmg LIKE z03_bw_cmp2-plnmg,
       END OF itb_z03_bw_cmp2.
*End change BNI
DATA : BEGIN OF str_index1,
         matnr LIKE eord-matnr,
         werks LIKE eord-werks,
      END OF str_index1.
DATA : BEGIN OF str_index2,
         matnr LIKE eord-matnr,
         werks LIKE eord-werks,
      END OF str_index2.
DATA : BEGIN OF str_index3_eord,
         matnr LIKE eord-matnr,
         werks LIKE eord-werks,
      END OF str_index3_eord.
DATA : BEGIN OF str_index4,
         matnr LIKE eord-matnr,
         werks LIKE eord-werks,
      END OF str_index4.
DATA : BEGIN OF str_index5,
         matnr LIKE eord-matnr,
         werks LIKE eord-werks,
END OF str_index5.
DATA : BEGIN OF str_index6,
         matnr LIKE eord-matnr,
         werks LIKE eord-werks,
END OF str_index6.
DATA : BEGIN OF str_index7,
         matnr LIKE eord-matnr,
         werks LIKE eord-werks,
END OF str_index7.
Déclaration des variables de debut et de fin de mois.
DATA: w_debut_mois    LIKE sy-datum,
      w_debut_periode LIKE sy-datum,
      w_fin_mois      LIKE sy-datum,
      w_fin_periode   LIKE sy-datum.
Déclaration des variables pour les dates.
DATA: w_date0 LIKE sy-datum,
      w_date1 LIKE sy-datum,
      w_date2 LIKE sy-datum,
      w_date3 LIKE sy-datum,
      w_date4 LIKE sy-datum,
      w_date5 LIKE sy-datum,
      w_date6 LIKE sy-datum,
      w_datejour LIKE sy-datum,                             "FAE15269
      w_dat_da LIKE eban-lfdat,
      w_dat_op LIKE plaf-pedtr,
      w_mois0 LIKE t247-ltx,
      w_mois1 LIKE t247-ltx,
      w_mois2 LIKE t247-ltx,
      w_mois3 LIKE t247-ltx,
      w_mois4 LIKE t247-ltx,
      w_mois5 LIKE t247-ltx,
      w_mois6 LIKE t247-ltx,
      w_lendemain LIKE sy-datum.                            "FAE17345+
Temoin d'un AR dans la commande d'achat.
DATA: w_temoin_ar.
Numéro de la confirmation de la commande
DATA : w_etens LIKE ekes-etens.
Déclaration des variables pour le nom des fichiers.
DATA: w_nom_fichier LIKE rlgrap-filename,
      w_fichier LIKE rlgrap-filename,
      w_racine LIKE rlgrap-filename,
      w_file LIKE rlgrap-filename.
Déclaration d'une table interne pour le transfert.
DATA: BEGIN OF itb_trans OCCURS 0,
        w_ligne(320).
DATA: END OF itb_trans.
Déclaration d'une variable pour rechercher les enregistrements vides.
DATA: w_compteur     TYPE i,
      w_compteur1    TYPE i,
      w_compteur2    TYPE i,
      w_retard       TYPE i,          " Retard en jours ouvres.
      w_trouve_pfc   TYPE c, "addsde
      w_trouve_pfs   TYPE c, "+DE3K937051
      w_trouve       TYPE c.
*Index pour les LOOP
DATA : w_index_ekpo LIKE sy-tabix,
       w_index_ekes LIKE sy-tabix,
       w_index_eket LIKE sy-tabix,
       w_index_mseg LIKE sy-tabix,
       w_index_eban LIKE sy-tabix,
       w_index_plaf LIKE sy-tabix,
       w_index_pca LIKE sy-tabix,
       w_index_z03_bw_cmp1 LIKE sy-tabix,
       w_index_z03_bw_cmp2 LIKE sy-tabix."+DE3K937051
RANGES : r_type_pfs   FOR marc-strgr.
*fichier sur serveur +EDR231003
DATA : w_chemin LIKE filename-fileintern, "nom du fichier
       w_date_fichier(12) TYPE c,          "Date format DD_MM_AA
       w_csv(307) TYPE c.                  "ligne du fichier format CSV
CONSTANTS: k_imputation_m LIKE eban-knttp VALUE 'M'.        "FAE19001+
                 Description de l écran de sélection                 *
                     Paramètres "UTILISATION"                        *
Ouverture d'un block de sélection pour le(s) fournisseur(s).
SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME TITLE text-bl1.
Sélection division(s)
SELECT-OPTIONS: s_werks FOR ekpo-werks.
Sélection fournisseur(s).
SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr OBLIGATORY.
Sélection du Groupe d'acheteur
*SELECT-OPTIONS: s_ekgrp FOR marc-ekgrp.   "-FAE26446
*SELECT-OPTIONS: s_dispo FOR marc-dispo.   "-FAE26446
SELECTION-SCREEN END OF BLOCK block1.
FAE 26446 : ajout
SELECTION-SCREEN BEGIN OF BLOCK block3 WITH FRAME TITLE text-bl3.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETER p_ekgrp RADIOBUTTON GROUP g3.
SELECTION-SCREEN COMMENT 5(24) text-001 FOR FIELD p_ekgrp.
SELECT-OPTIONS: s_ekgrp FOR marc-ekgrp.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETER p_dispo RADIOBUTTON GROUP g3.
SELECTION-SCREEN COMMENT 5(24) text-002 FOR FIELD p_dispo.
SELECT-OPTIONS: s_dispo FOR marc-dispo.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK block3.
FAE 26446 : fin ajout
                       Paramètres "SYSTEME"                          *
Saut de 2 lignes.
SELECTION-SCREEN: SKIP 2.
Ouverture d'un block de sélection pour l'adresse physique du fichier.
SELECTION-SCREEN BEGIN OF BLOCK block2 WITH FRAME TITLE text-bl2.
PARAMETERS: p_pc       RADIOBUTTON GROUP rad1 DEFAULT 'X', "+EDR231003
            p_fic_pc LIKE rlgrap-filename.                  "+EDR231003
SELECTION-SCREEN SKIP.                                      "+EDR231003
PARAMETERS     : p_serve   RADIOBUTTON GROUP rad1,          "+EDR231003
                 p_fic_se LIKE filename-fileintern          "+EDR231003
                          DEFAULT 'Z03_PREV_COMMANDES'.     "+EDR231003
SELECTION-SCREEN END OF BLOCK block2.
                       Logique de traitement                         *
                          INITIALIZATION                             *
INITIALIZATION.
Date du jour
MOVE sy-datum TO w_datejour.                              "FAE15269
Gestion des anomalies.
MOVE text-lb1 TO w_lb_traitement.
PERFORM f930_init USING sy-cprog '30'.
Fin de la gestions des anomalies.
Récuperation des mois dans la table interne 'ITB_MONTHS'.
CALL FUNCTION 'MONTH_NAMES_GET'
       EXPORTING
            language              = sy-langu
       TABLES
            month_names           = itb_months
       EXCEPTIONS
            month_names_not_found = 1
            OTHERS                = 2.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Récupération des differentes periodes.
PERFORM f100_recuperation_date TABLES itb_months.
Récupération du debut du mois.
CONCATENATE sy-datlo(6) '01' INTO w_debut_mois.
MOVE: w_debut_mois TO w_debut_periode.
Récupération du dernier jour du mois.
CALL FUNCTION 'LAST_DAY_OF_MONTHS'
       EXPORTING
            day_in            = sy-datlo
       IMPORTING
            last_day_of_month = w_fin_mois
       EXCEPTIONS
            day_in_no_date    = 1
            OTHERS            = 2.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
          WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
                          TOP-OF-PAGE                                *
TOP-OF-PAGE.
CALL FUNCTION 'Z_00_BC_TOP_OF_PAGE'
       EXPORTING
            p_linsz   = k_ligne
            p_pagno   = sy-pagno
            p_prog    = sy-cprog
            p_projet = k_projet
            p_societe = k_societe
            p_sujet   = sy-title.
                          END-OF-PAGE                                *
END-OF-PAGE.
                        AT SELECTION-SCREEN                          *
FAE 26446 : ajout
AT SELECTION-SCREEN ON BLOCK block3.
IF NOT ( s_ekgrp IS INITIAL )
AND NOT ( s_dispo IS INITIAL ).
    MESSAGE e394(z03_mm).
ENDIF.
IF p_ekgrp = 'X'.
    IF s_ekgrp IS INITIAL.
      MESSAGE e395(z03_mm).
    ENDIF.
ELSE.
    IF s_dispo IS INITIAL.
      MESSAGE e396(z03_mm).
    ENDIF.
ENDIF.
fae26446 fin ajout
AT SELECTION-SCREEN ON BLOCK block2.
IF p_pc = 'X'.
    IF p_fic_pc IS INITIAL.
*Attention, il n'y a aucune adresse de sauvegarde pour le(s) fichier(s)
      MESSAGE e021(z03_mm).
    ENDIF.
ELSE.
    IF p_fic_se IS INITIAL.
*Attention, il n'y a aucune adresse de sauvegarde pour le(s) fichier(s)
      MESSAGE e021(z03_mm).
    ENDIF.
ENDIF.
Création du matchcode pour la selection du fichier local.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fic_pc.
CALL FUNCTION 'WS_FILENAME_GET'
       EXPORTING
            def_filename     = p_fic_pc
            def_path         = 'C:'
            mask             = text-ma1
            mode             = 'S'
            title            = text-sel
       IMPORTING
            filename         = p_fic_pc
       EXCEPTIONS
            inv_winsys       = 1
            no_batch         = 2
            selection_cancel = 3
            selection_error = 4
            OTHERS           = 5.
IF sy-subrc NE 0 AND sy-subrc NE 3.
    MESSAGE e032(z03_mm).
ENDIF.
                        START-OF-SELECTION                           *
START-OF-SELECTION.
PERFORM select_donnees.
=================================================
Liste des ARTICLES impactés pour les prévisions *
=================================================
===================================
PORTEFEUILLE DE COMMANDES D'ACHAT *
===================================
Construction itb_pca à partir de EKKO/EKPO.
w_index_ekpo = 1.
w_index_ekes = 1.
w_index_eket = 1.
w_index_mseg = 1.
SORT itb_ekko BY ebeln.           "-FAE26446
SORT itb_ekpo BY ebeln ebelp.
SORT itb_makt BY matnr spras.
SORT itb_eket BY ebeln ebelp.
SORT itb_ekes BY ebeln ebelp.
SORT itb_mseg BY ebeln ebelp.
SORT itb_mkpf BY mblnr mjahr.
SORT itb_marc BY matnr werks.                             "+FAE26446
FAE 26446 remplacement
LOOP AT itb_ekko.
   LOOP AT itb_ekpo.
           FROM w_index_ekpo.
     IF itb_ekko-ebeln = itb_ekpo-ebeln.
LOOP AT itb_ekpo.
    READ TABLE itb_marc WITH KEY
       matnr = itb_ekpo-matnr
       werks = itb_ekpo-werks BINARY SEARCH.
    CHECK sy-subrc = 0.
FAE 26446 fin remplacement
    itb_pca-ebeln = itb_ekpo-ebeln.
    itb_pca-ebelp = itb_ekpo-ebelp.
itb_pca-lifnr = itb_ekko-lifnr.   "-FAE26446
    itb_pca-lifnr = itb_ekpo-lifnr.                         "+FAE26446
    itb_pca-ekgrp = itb_ekpo-ekgrp.                         "+FAE26446
    itb_pca-dispo = itb_ekpo-dispo.                         "+FAE26446
    itb_pca-matnr = itb_ekpo-matnr.
    itb_pca-werks = itb_ekpo-werks.
Recherche du libellé article
    READ TABLE itb_makt
               WITH KEY matnr = itb_ekpo-matnr
                        spras = text-fra
               BINARY SEARCH.
    IF sy-subrc = 0.
      itb_pca-maktx = itb_makt-maktx.
    ELSE.
      READ TABLE itb_makt
                WITH KEY matnr = itb_ekpo-matnr
                         spras = text-ang
                BINARY SEARCH.
      IF sy-subrc = 0.
        itb_pca-maktx = itb_makt-maktx.
      ENDIF.
    ENDIF.
    IF NOT itb_ekpo-bpumn IS INITIAL.
      itb_pca-menge = itb_ekpo-menge * itb_ekpo-bpumz /
                                       itb_ekpo-bpumn.
    ENDIF.
Sélect° ds la table EKES des dates de livraisons et des qtés
en transit
    CLEAR w_temoin_ar.
    CLEAR w_etens.
    LOOP AT itb_ekes
            FROM w_index_ekes.
      IF itb_ekes-ebeln = itb_ekpo-ebeln
      AND itb_ekes-ebelp = itb_ekpo-ebelp.
        IF itb_ekes-ebtyp = text-arn.
          itb_pca-eindt = itb_ekes-eindt.
          w_temoin_ar = 'X'.
        ELSE.
        Si c'est une qté en transit alors on recupere
        la quantité et la date.
          IF itb_ekes-dabmg < itb_ekes-menge.
            itb_pca-qtran = itb_pca-qtran + itb_ekes-menge -
                            itb_ekes-dabmg.
          ENDIF.
          IF itb_ekes-etens > w_etens.
            w_etens = itb_ekes-etens.
            itb_pca-dtran = itb_ekes-eindt.
          ENDIF.
        ENDIF.
      ELSEIF itb_ekes-ebeln > itb_ekpo-ebeln
      OR ( itb_ekes-ebeln = itb_ekpo-ebeln
      AND itb_ekes-ebelp > itb_ekpo-ebelp ).
        w_index_ekes = sy-tabix.
        EXIT.
      ENDIF.
    ENDLOOP.
S'il n'y a pas d'AR alors récupérat° de la date livraison dans EKET.
    LOOP AT itb_eket
            FROM w_index_eket.
      IF itb_eket-ebeln = itb_ekpo-ebeln
      AND itb_eket-ebelp = itb_ekpo-ebelp.
        IF w_temoin_ar IS INITIAL.
          itb_pca-eindt = itb_eket-eindt.
        ENDIF.
        itb_pca-slfdt = itb_eket-slfdt.
      Calcul du portefeuille fournisseur à partir de la
      qté commandée et la qté reçue
        itb_pca-attdu = itb_pca-attdu + itb_eket-menge -
                        itb_eket-wemng.
      Calcul du montant du poste
        itb_pca-netpr = itb_ekpo-netpr * itb_pca-attdu.
        IF itb_ekpo-peinh NE 0.
          itb_pca-netpr = itb_pca-netpr / itb_ekpo-peinh.
        ENDIF.
      Calcul quantité réceptionnée.
        itb_pca-wemng = itb_pca-wemng + itb_eket-wemng.
      Calcul du retard en nombre de jours calendaires
      Le calcul du retard ne doit pas prendre en compte
      le jour de livraison
        ADD 1 TO itb_eket-eindt.
        IF NOT itb_pca-attdu IS INITIAL
        AND    itb_eket-eindt LT sy-datum.
        Calcul du retard en nombre de jours ouvrés
          CLEAR w_retard.
          CALL FUNCTION 'Z_00_BC_WORKDAYS_PER_PERIOD'
               EXPORTING
                    date_deb = itb_eket-eindt
                    date_fin = sy-datum
               IMPORTING
                    jours    = w_retard.
          itb_pca-rtard = itb_pca-rtard + w_retard .
        ENDIF.
      ELSEIF itb_eket-ebeln > itb_ekpo-ebeln
      OR (   itb_eket-ebeln = itb_ekpo-ebeln
      AND    itb_eket-ebelp > itb_ekpo-ebelp ).
        w_index_eket = sy-tabix.
        EXIT.
      ENDIF.
    ENDLOOP.
Recherche de la derniere date de livraison.
    LOOP AT itb_mseg
            FROM w_index_mseg.
      IF itb_mseg-ebeln = itb_ekpo-ebeln
      AND itb_mseg-ebelp = itb_ekpo-ebelp.
        READ TABLE itb_mkpf
                   WITH KEY mblnr = itb_mseg-mblnr
                            mjahr = itb_mseg-mjahr
                   BINARY SEARCH.
        IF sy-subrc = 0.
          IF itb_mkpf-bldat > itb_pca-bldat.
            itb_pca-bldat = itb_mkpf-bldat.
          ENDIF.
        ENDIF.
      ELSEIF itb_mseg-ebeln > itb_ekpo-ebeln
      OR (   itb_mseg-ebeln = itb_ekpo-ebeln
      AND    itb_mseg-ebelp > itb_ekpo-ebelp ).
        w_index_mseg = sy-tabix.
        EXIT.
      ENDIF.
    ENDLOOP.
    APPEND itb_pca.
    CLEAR itb_pca.
FAE26446 suppression parag. suivant
     ELSEIF itb_ekpo-ebeln > itb_ekko-ebeln.
       w_index_ekpo = sy-tabix.
       EXIT.
     ENDIF.
   ENDLOOP.
Fin FAE26446
ENDLOOP.
=========================
PREVISIONS DE COMMANDES *
=========================
SORT itb_eord        BY matnr werks lifnr ekgrp.
SORT itb_eban        BY matnr werks flief ekgrp.
SORT itb_plaf        BY matnr plwrk flief.
SORT itb_z03_bw_cmp1 BY matnr werks.
SORT itb_z03_bw_cmp2 BY matnr werks."+DE3K937051
SORT itb_pca         BY matnr werks lifnr.
w_index_eban = 1.
w_index_plaf = 1.
w_index_z03_bw_cmp1 = 1.
w_index_pca = 1.
w_index_z03_bw_cmp2 = 1."+DE3K937051
Remplissage de la table des prévisions de commande.
LOOP AT itb_eord.
    CLEAR: str_prev_pfc,
           w_trouve.
    MOVE-CORRESPONDING itb_eord TO str_index1.
    MOVE-CORRESPONDING itb_eord TO str_index3_eord.
    MOVE-CORRESPONDING itb_eord TO itb_prev_cde.
Recherche dans table division/article (MARC) afin de déterminer si
article PFS (prod fabriqué à stock) ou PFC (Prod fabriqué sur cde)
    AT NEW werks.
      READ TABLE itb_marc_eord
                 WITH KEY matnr = itb_eord-matnr
                          werks = itb_eord-werks
                 BINARY SEARCH.
      IF sy-subrc NE 0.
        CLEAR itb_marc_eord.
      ENDIF.
    ENDAT.
a - Prévisions pour les PFS : DA + OP *
*Calcul des quantités de commande.
    IF itb_eord-disls = text-tl1.
      itb_prev_cde-bstmi = itb_eord-bstfe.
    ELSEIF itb_eord-disls = text-tl2
    OR     itb_eord-disls = text-tl3.
      IF itb_eord-bstrf NE 0
      AND itb_eord-bstmi = 0
      AND itb_eord-bstma = 0.
        itb_prev_cde-bstmi = itb_eord-bstrf.
      ELSEIF itb_eord-bstrf NE 0
      AND    itb_eord-bstmi NE 0.
        itb_prev_cde-bstmi = itb_eord-bstmi.
      ELSEIF itb_eord-bstrf = itb_eord-bstma
      AND    itb_eord-bstrf NE 0
      AND    itb_eord-bstmi = 0.
        itb_prev_cde-bstmi = itb_eord-bstma.
      ENDIF.
    ENDIF.
si article PFS (Prod fabriqué à stock) recherche des
demandes d'achat ou ordres planfiés
    IF itb_marc_eord-strgr IN r_type_pfs.
Récupérat° calendrier de la division pour calcul correct lors de
l'ajout de eban-webaz ou plaf-webaz jours ouvrés
      CLEAR w_trouve_pfs ."+DE3K937051
      READ TABLE itb_t001w
                 WITH KEY werks = itb_eord-werks
                 BINARY SEARCH.
      IF sy-subrc = 0.
        LOOP AT itb_eban
                FROM w_index_eban.
          MOVE-CORRESPONDING itb_eban TO str_index2.
          IF str_index1 = str_index2.
            w_trouve_pfs = 'X'."+DE3K937051
          si qte commandées pour la DA < quantité de la DA
            IF itb_eban-bsmng < itb_eban-menge.
            ajout de quantité de la DA - qte commandée pour la DA
              PERFORM affect_da.
            ENDIF.
          ELSEIF str_index2 > str_index1.
            w_index_eban = sy-tabix.
            EXIT.
          ENDIF.
        ENDLOOP.
      ENDIF.
    ajout des quantité des OP (ordres planifiés)
      LOOP AT itb_plaf
              FROM w_index_plaf.
        MOVE-CORRESPONDING itb_plaf TO str_index4.
        str_index4-werks = itb_plaf-plwrk.
      str_index4-lifnr = itb_plaf-flief.
        IF str_index4 = str_index3_eord.
        Ajout de webaz jours ouvrés à pedtr
          CALL FUNCTION 'Z_03_MM_ADD_TO_FACTORYDATE'
               EXPORTING
                    i_date        = itb_plaf-pedtr
                    i_calendar_id = itb_t001w-fabkl
                    i_nb_days     = itb_plaf-webaz
               IMPORTING
                    o_date        = w_dat_op
               EXCEPTIONS
                    conv_error    = 1
                    OTHERS        = 2.
          IF sy-subrc
   If forecasts found in Z03_BW_CMP2 for the article
   IF w_trouve_pfs = 'X'."-DE3K937602
Recalculation prev month M in fct of Nb of wrought days of the month
    IF NOT itb_prev_cde-men00 IS INITIAL.
   one does not hold any more account of the day in progress
      w_lendemain = w_date0 + 1.
      CLEAR:w_nb_j,w_nb_j_tot.         "DE3K938206+
      CALL FUNCTION 'Z_00_BC_WORKDAYS_PER_PERIOD'
           EXPORTING
                date_deb = w_lendemain
                date_fin = w_fin_mois
           IMPORTING
                jours    = w_nb_j.
      CALL FUNCTION 'Z_00_BC_WORKDAYS_PER_MONTH'
           EXPORTING
                date = w_lendemain
           IMPORTING
                jours = w_nb_j_tot.
      itb_prev_cde-men00 = itb_prev_cde-men00 * w_nb_j / w_nb_j_tot
*CLA DE3K925301 FAE27197
*to round has the higher entirety
    itb_prev_cde-men00 = ceil( itb_prev_cde-men00 ). "DE3K938206-
    ENDIF.
   ENDIF."-DE3K937602
*End change BNI
b - Prévisions pour les PFC (Z03_BW_CMP1 puis rééquilibrage) *
Recherche des previsions dans Z03_BW_CMP1
si article PFC (Prod fabriqué sur cde) recherche des prévisions
    IF NOT itb_marc_eord-strgr IN r_type_pfs.
      CLEAR str_prev_pfc.
      MOVE-CORRESPONDING itb_eord TO str_prev_pfc.
      CLEAR w_trouve_pfc .
      LOOP AT itb_z03_bw_cmp1
              FROM w_index_z03_bw_cmp1.
        MOVE-CORRESPONDING itb_z03_bw_cmp1 TO str_index7.
        MOVE-CORRESPONDING itb_eord TO str_index6.
        IF str_index6 = str_index7.
      si on trouve des prévisions dans z03_bw_cmp1 pour la source
      d'appro eord alors c'est un article PFC
          w_trouve_pfc = 'X'.
          CASE itb_z03_bw_cmp1-pdatu+0(6).
            WHEN w_date0+0(6).
              str_prev_pfc-men00 = itb_z03_bw_cmp1-plnmg.
            WHEN w_date1+0(6).
              str_prev_pfc-men01 = itb_z03_bw_cmp1-plnmg.
            WHEN w_date2+0(6).
              str_prev_pfc-men02 = itb_z03_bw_cmp1-plnmg.
            WHEN w_date3+0(6).
              str_prev_pfc-men03 = itb_z03_bw_cmp1-plnmg.
            WHEN w_date4+0(6).
              str_prev_pfc-men04 = itb_z03_bw_cmp1-plnmg.
            WHEN w_date5+0(6).
              str_prev_pfc-men05 = itb_z03_bw_cmp1-plnmg.
            WHEN w_date6+0(6).
              str_prev_pfc-men06 = itb_z03_bw_cmp1-plnmg.
            WHEN OTHERS.
          ENDCASE.
        ELSEIF str_index7 > str_index6.
          w_index_z03_bw_cmp1 = sy-tabix.
          EXIT.
        ENDIF.
      ENDLOOP.
*Begin change BNI
    Si des prévisions trouvées dans Z03_BW_CMP1 pour l'article
      IF w_trouve_pfc = 'X'.
      Recalcul prev mois M en fct du nb de jours ouvrés du mois
        IF NOT str_prev_pfc-men00 IS INITIAL.
        on ne tient plus compte du jour en cours
          w_lendemain = w_date0 + 1.
          CLEAR:w_nb_j,w_nb_j_tot.               "DE3K938206+
          CALL FUNCTION 'Z_00_BC_WORKDAYS_PER_PERIOD'
               EXPORTING
                    date_deb = w_lendemain
                    date_fin = w_fin_mois
               IMPORTING
                    jours    = w_nb_j.
          CALL FUNCTION 'Z_00_BC_WORKDAYS_PER_MONTH'
               EXPORTING
                    date = w_lendemain
               IMPORTING
                    jours = w_nb_j_tot.
          str_prev_pfc-men00 = str_prev_pfc-men00 * w_nb_j / w_nb_j_tot.
*CLA DE3K925301 FAE27197
*arrondir a l'entier supèrieur
          str_prev_pfc-men00 = ceil( str_prev_pfc-men00 ).
        ENDIF.
      Equilibrage PFC : commande/prévision du mois
      Recherche COMMANDES cumulées pour M à M+6
        CLEAR str_pca_pfc.
        LOOP AT itb_pca
                FROM w_index_pca.
          MOVE-CORRESPONDING itb_pca TO str_index5.
          IF str_index5 = str_index3_eord.
            IF NOT itb_pca-menge IS INITIAL.
              CASE itb_pca-eindt+0(6).
                WHEN w_date0+0(6).
                  IF itb_pca-eindt >= w_date0.
                  str_pca_pfc-men00 = str_pca_pfc-men00 + itb_pca-menge.
                  ENDIF.
                WHEN w_date1+0(6).
                  str_pca_pfc-men01 = str_pca_pfc-men01 + itb_pca-menge.
                WHEN w_date2+0(6).
                  str_pca_pfc-men02 = str_pca_pfc-men02 + itb_pca-menge.
                WHEN w_date3+0(6).
                  str_pca_pfc-men03 = str_pca_pfc-men03 + itb_pca-menge.
                WHEN w_date4+0(6).
                  str_pca_pfc-men04 = str_pca_pfc-men04 + itb_pca-menge.
                WHEN w_date5+0(6).
                  str_pca_pfc-men05 = str_pca_pfc-men05 + itb_pca-menge.
                WHEN w_date6+0(6).
                  str_pca_pfc-men06 = str_pca_pfc-men06 + itb_pca-menge.
              ENDCASE.
            ENDIF."NOT itb_pca-menge IS INITIAL
          ELSEIF str_index5 > str_index3_eord.
            w_index_pca = sy-tabix.
            EXIT.
          ENDIF.
        ENDLOOP."itb_pca
*. Equilibrer commande / prévision des mois : diminuer la quantité de
prévision de chaque mois par le portefeuille de commande client du
mois*. Si ce solde est négatif alors lui donner la valeur 0.
        w_i = 0.
      Ajustement commandes/prévisions pour les mois M à M+6
        WHILE w_i .
        Pour un mois, SI Prévisions > Commandes en cours
          IF .
          Prévisions = Prévisions - Commandes en cours
             = 0.
          ENDIF.
        On passe au mois suivant
          w_i = w_i + 1.
        ENDWHILE.
        MOVE str_prev_pfc-men00 TO itb_prev_cde-men00.
        MOVE str_prev_pfc-men01 TO itb_prev_cde-men01.
        MOVE str_prev_pfc-men02 TO itb_prev_cde-men02.
        MOVE str_prev_pfc-men03 TO itb_prev_cde-men03.
        MOVE str_prev_pfc-men04 TO itb_prev_cde-men04.
        MOVE str_prev_pfc-men05 TO itb_prev_cde-men05.
        MOVE str_prev_pfc-men06 TO itb_prev_cde-men06.

Hi
You check in SM50 by executing the programing, You will come to know which select is taking more time and accordingly you modify that select.
You can do SQL trace and Run time analysis and analyse and see.
check this and use
1) Dont use nested select statements
2) If possible use for all entries in addition
3) In the where addition make sure you give all the primary key
4) Use Index for the selection criteria.
5) You can also use inner joins
6) You can try to put the data from the first select statement into an Itab and then in order to select the data from the second table use for all entries in.
7) Use the runtime analysis SE30 and SQL Trace (ST05) to identify the performance and also to identify where the load is heavy, so that you can change the code accordingly
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d0db4c9-0e01-0010-b68f-9b1408d5f234
ABAP performance depends upon various factors and in devicded in three parts:
1. Database
2. ABAP
3. System
Run Any program using SE30 (performance analys) to improve performance refer to tips and trics section of SE30, Always remember that ABAP perfirmance is improved when there is least load on Database.
u can get an interactive grap in SE30 regarding this with a file.
also if u find runtime of parts of codes then use :
Switch on RTA Dynamically within ABAP Code
*To turn runtim analysis on within ABAP code insert the following code
SET RUN TIME ANALYZER ON.
*To turn runtim analysis off within ABAP code insert the following code
SET RUN TIME ANALYZER OFF.
Always check the driver internal tables is not empty, while using FOR ALL ENTRIES
Avoid for all entries in JOINS
Try to avoid joins and use FOR ALL ENTRIES.
Try to restrict the joins to 1 level only ie only for tables
Avoid using Select *.
Avoid having multiple Selects from the same table in the same object.
Try to minimize the number of variables to save memory.
The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)
Avoid creation of index as far as possible
Avoid operators like <>, > , < & like % in where clause conditions
Avoid select/select single statements in loops.
Try to use 'binary search' in READ internal table. Ensure table is sorted before using BINARY SEARCH.
Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)
Avoid using ORDER BY in selects
Avoid Nested Selects
Avoid Nested Loops of Internal Tables
Try to use FIELD SYMBOLS.
Try to avoid into Corresponding Fields of
Avoid using Select Distinct, Use DELETE ADJACENT
Check the following Links
Re: performance tuning
Re: Performance tuning of program
http://www.sapgenie.com/abap/performance.htm
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
check the below link
http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm
See the following link if it's any help:
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
Check also http://service.sap.com/performance
and
books like
http://www.sap-press.com/product.cfm?account=&product=H951
http://www.sap-press.com/product.cfm?account=&product=H973
http://www.sap-img.com/abap/more-than-100-abap-interview-faqs.htm
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
Performance tuning for Data Selection Statement
http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm
Debugger
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
Run Time Analyser
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm
SQL trace
http://help.sap.com/saphelp_47x200/helpdata/en/d1/801f7c454211d189710000e8322d00/content.htm
CATT - Computer Aided Testing Too
http://help.sap.com/saphelp_47x200/helpdata/en/b3/410b37233f7c6fe10000009b38f936/frameset.htm
Test Workbench
http://help.sap.com/saphelp_47x200/helpdata/en/a8/157235d0fa8742e10000009b38f889/frameset.htm
Coverage Analyser
http://help.sap.com/saphelp_47x200/helpdata/en/c7/af9a79061a11d4b3d4080009b43351/content.htm
Runtime Monitor
http://help.sap.com/saphelp_47x200/helpdata/en/b5/fa121cc15911d5993d00508b6b8b11/content.htm
Memory Inspector
http://help.sap.com/saphelp_47x200/helpdata/en/a2/e5fc84cc87964cb2c29f584152d74e/content.htm
ECATT - Extended Computer Aided testing tool.
http://help.sap.com/saphelp_47x200/helpdata/en/20/e81c3b84e65e7be10000000a11402f/frameset.htm
Just refer to these links...
performance
Performance
Performance Guide
performance issues...
Performance Tuning
Performance issues
performance tuning
performance tuning
You can go to the transaction SE30 to have the runtime analysis of your program.Also try the transaction SCI , which is SAP Code Inspector.
1 Always check the driver internal tables is not empty, while using FOR ALL ENTRIES
2 Avoid for all entries in JOINS
3 Try to avoid joins and use FOR ALL ENTRIES.
4 Try to restrict the joins to 1 level only ie only for 2 tables
5 Avoid using Select *.
6 Avoid having multiple Selects from the same table in the same object.
7 Try to minimize the number of variables to save memory.
8 The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)
9 Avoid creation of index as far as possible
10 Avoid operators like <>, > , < & like % in where clause conditions
11 Avoid select/select single statements in loops.
12 Try to use 'binary search' in READ internal table. Ensure table is sorted before using BINARY SEARCH.
13 Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)
14 Avoid using ORDER BY in selects
15 Avoid Nested Selects
16 Avoid Nested Loops of Internal Tables
17 Try to use FIELD SYMBOLS.
18 Try to avoid into Corresponding Fields of
19 Avoid using Select Distinct, Use DELETE ADJACENT.
Regards
Anji

Bind Variables and Shared Component Report Query

I have a query in a region report which I have replicated to a shared component report query.
Both queries reference page items as bind variables in the where clause.
The report region on screen shows the correct results but the report query shows "no data". This is the case when running "Test Query" and "Download XML data" from the shared component report query definition. If I hardcode the variable names I get rows returned, If I use bind variables - and specify the values for these variables I get no data. THe XML file contains the tags for each bind variable I have specified but has no data between the tags. I have Ticked the box to include application and session state but it appears that the bind variables are not being used.
When I use my report query in the application (URL tied to a button) I get the same problem, the binds are not being passed to the report query.
Can someone please clarify if this is a bug or not? And if not, how can I get it to work.
I am using Apex 4.0.2
Thanks
Kathryn

Hi
To confirm, yes I selected the bind variables. I used these in the report layout, but the xml file has them as empty i.e.
<P0_START_DATE><P0_START_DATE/> with nothing in between.
IN the Test Query section, if I put real values in the boxes for the bind variables, I get no data found. If I hardcode the values into the query, I get the data.
I've repeated the create report query many times and have created a report layout in RTF. I can use the layout with my region - in the print attributes and the layout works with the query but I need to create a PDF using 2 queries - ROWSET1 and ROWSET2. I can generate the XML but the values in the rows are all empty. When I use the layout with a report query instead of the region, I get no data even though I have used the same sql and have selected the bind variables. I was using variables from page items on page zero but have also tried using page items on the current page, the result is the same.
I need to use a report query and a report layout as I need data from 2 queries in the PDF.
I looked at your demo - what happens if you add a second sql query to the report query - is there any chance I can look at the back end (developer access?)
Thanks for your input
Kathryn

Using Bind Variables in Parameter Form's Query

I want to use bind variables in the query of Parameter form. But
it does not allows. What is the other way out. The structure of
my Parameter form is as under:
State:
Customer:
Now I want that I want to list only those customer in the
Customer LOV which belongs to the selected state.
Thanks.
Muhammad Nadeem

Can we just link to an oracle form using a url still as we can with reports? I've built a report that requires the user to select from a dynamic list as well, and I know how to do this through forms, but can I simply call the form from a webpage?

Need suggestion to improve the performence of the report execution

Hi all,
I have to improve the performence of the report . I am executing the report in foreground. First time it is giving after running 6 mins . If i execute again It is giving the output.
I am using innner join between EKKO and EKPO. When I see the report in debugging, this is the select talking long time to execute then it is giving dump.
what all the things i need to take care .
Please suggest any advicess to over the issue.
Thanks,
Ajay

in sap tip-tricks:
Nested Select statements
Runtime: 4,641 microseconds
SELECT * FROM SPFLI INTO SPFLI_WA.
SELECT * FROM SFLIGHT INTO SFLIGHT_WA
      WHERE CARRID = SPFLI_WA-CARRID
        AND CONNID = SPFLI_WA-CONNID.
ENDSELECT.
ENDSELECT.
Select with join
Runtime: 5,080 microseconds
SELECT * INTO WA
    FROM SPFLI AS P INNER JOIN SFLIGHT AS F
      ON P~CARRID = F~CARRID AND
         P~CONNID = F~CONNID.
ENDSELECT

How to use bind variable in the query to avoid hard parsing

Hi,
I have a query which is using literals
strquery:='SELECT SUMTOTAL FROM tab1 WHERE BATCHNO = '''
      || gBNo
      || ''' AND A_ID = '''
      || g_id
      || ''' AND L_ID = '''
      || g_LId
      || ''' AND S_Code = ''C_3'' ';
execute immediate strquery;I have been asked to use a bind variable to avoid hard parsing.
How do i do it?
Edited by: user8731258 on Jul 27, 2012 5:07 AM
Edited by: user8731258 on Jul 27, 2012 5:08 AM

You dont need Dynamic SQL. Your Table and Column Name are static in that query. Just use Static SQL
SELECT SUMTOTAL
INTO lSumTotal
FROM tab1
WHERE BATCHNO = gBatchNo
   AND ATM_ID = gAtm_id
   AND LOAD_ID = gLoadId
   AND STEP_CODE = 'C_3';

Use of Bind Variable in the Query of view object giving null pointer excep

I am using this code in the backing bean of my page to set the value of the bind variable 'cmdID' in the view object.
String AM = "model.UnixCommandsAppMod";
String CF = "UnixCommandsAppModLocal";
ApplicationModule am = Configuration.createRootApplicationModule(AM, CF);
ViewObject vo = am.findViewObject("Command_options_view");
vo.setNamedWhereClauseParam("cmdID", 1);
vo.executeQuery();
On the fifth line it is giving NullPointer exception.
I am not being able to figure out the reason.

User,
a). Don't keep posting new questions in the same thread. It really does decrease the usability of the forum. Now, if someone searches for "INFO: ADF Faces is running with time-stamp checking enabled," they will find a post about null pointer exception in a bind variable and think, "oh, that doesn't apply to me." If your question is answered, mark the answer as correct. New questions go into a new thread. Kind of funny that the thread I pointed you to with the answer to your question also has this same admonishment.. ;)
b). I'll relent and answer your new question. Ignore that INFO message. It is not an error. It will ALWAYS ALWAYS appear when you run your application in the embedded OC4J with JDeveloper. Had you searched the forum for "INFO: ADF Faces is running with time-stamp checking enabled" you would find that the first hit (among some others) has this same answer
John

Use of bind variables with the oracle db - to improve library cache perform

Dear Friends,
We are using oracle 9.0.1.1.1 db server - the performance of the db was pathetic and upon investigation it was revealed that the library cache was over loaded with sql hard parses generated by not using bind variables. We are using vb as a front end with oracle and our connection object in vb is created using ole db for oracle provided by oracle (installed from oracle client custom - programmer option).
I would appreciate if any body can tell how can we use bind variables in vb to connect to oracle such that the hard parses can be changed into soft parses.
Your effort to bring some peace in my life is worth comendable and I would be very obliged for your time and help.
Thanks a lot.
Bye
Take care.
qj

Generally, you would use bind variables by changing statements that are written like this
select * from emp where empno=6678 and ename='Jones'
so that they're written like
select * from emp where empno=? and ename=?
How you then bind these question marks to the particular values you want depends on the API you're using (ADO? OLE DB directly?, etc). If you have a support contract, there are plenty of examples for any API on metalink.oracle.com
Justin

Using bind variables in the model view for master detail

Hi all,
I have a master-detail views setup on the following two queries.
In the first query below - I use two bind variables to collect the start and end date.
you have to add (and :startDate = :startDate and :endDate = :endDate) or you will get errors - bind not defined in sql
I then use the viewQueryCriteria to collect the data on a search panel - so far so good. (Make the bind variables required) along with the other criteria.
The bind variables are displayed in the search panel and the data is entered correctly.
The query executes and all is happy.
VIEWOBJECT1
SELECT DepositAccounts.COA_ID,
... ChartOfAccounts.ACCOUNT_CODE || ' ' || ChartOfAccounts.ACCOUNT_TITLE as description
FROM DEPOSIT_ACCOUNTS DepositAccounts, DEPOSIT_ACCOUNT_DETAILS DepositAccountDetails, CHART_OF_ACCOUNTS ChartOfAccounts
WHERE DepositAccounts.ID = DepositAccountDetails.DEP_ACC_ID
and ChartOfAccounts.id = DepositAccountDetails.COA_ID
and :startDate = :startDate and :endDate = :endDate
Now I add the summation of a value (AMOUNT) to the view object (java - create view impl) to the VOViewRowImpl
and everything works - the value is shown in the transient attribute formatted and looking nice.
VIEWOBJECT2
SELECT PostingBatchAccounts.AMOUNT,
FROM POSTING_BATCH_ACCOUNTS PostingBatchAccounts, POSTING_BATCHES PostingBatches
where PostingBatchAccounts.PB_ID = PostingBatches.ID
and PostingBatches.SOURCE_DATE between :startDate and :endDate
Now I need to add the start date and end date to the child query - before the view executes (or the summation is calculated).
The attributes are in the where clause (PostingBatches.SOURCE_DATE between :startDate and :endDate) in VIEWOBJECT2 which is the child.
I need the child records and the summation to work with the date restrictions.
I would assume you could get access to the child view in the VOViewImpl file and set the bind variables there.
Everything I find is based on the JSF - not the model layer - this should be fairly easy (and common). can anyone give me a hand on this?

Hi all,
I have a master-detail views setup on the following two queries.
In the first query below - I use two bind variables to collect the start and end date.
you have to add (and :startDate = :startDate and :endDate = :endDate) or you will get errors - bind not defined in sql
I then use the viewQueryCriteria to collect the data on a search panel - so far so good. (Make the bind variables required) along with the other criteria.
The bind variables are displayed in the search panel and the data is entered correctly.
The query executes and all is happy.
VIEWOBJECT1
SELECT DepositAccounts.COA_ID,
... ChartOfAccounts.ACCOUNT_CODE || ' ' || ChartOfAccounts.ACCOUNT_TITLE as description
FROM DEPOSIT_ACCOUNTS DepositAccounts, DEPOSIT_ACCOUNT_DETAILS DepositAccountDetails, CHART_OF_ACCOUNTS ChartOfAccounts
WHERE DepositAccounts.ID = DepositAccountDetails.DEP_ACC_ID
and ChartOfAccounts.id = DepositAccountDetails.COA_ID
and :startDate = :startDate and :endDate = :endDate
Now I add the summation of a value (AMOUNT) to the view object (java - create view impl) to the VOViewRowImpl
and everything works - the value is shown in the transient attribute formatted and looking nice.
VIEWOBJECT2
SELECT PostingBatchAccounts.AMOUNT,
FROM POSTING_BATCH_ACCOUNTS PostingBatchAccounts, POSTING_BATCHES PostingBatches
where PostingBatchAccounts.PB_ID = PostingBatches.ID
and PostingBatches.SOURCE_DATE between :startDate and :endDate
Now I need to add the start date and end date to the child query - before the view executes (or the summation is calculated).
The attributes are in the where clause (PostingBatches.SOURCE_DATE between :startDate and :endDate) in VIEWOBJECT2 which is the child.
I need the child records and the summation to work with the date restrictions.
I would assume you could get access to the child view in the VOViewImpl file and set the bind variables there.
Everything I find is based on the JSF - not the model layer - this should be fairly easy (and common). can anyone give me a hand on this?

Using a Bind Variable in the FROM part of a SQL Statement?

Hello Everyone,
I have a problem, I am trying to run an SQL statement. However I need the FROM part of the SQL statement to be a bind variable. This is because the end user will need to select between 2 database views.
I have tried this:
select CON_ID from :P23_DB_NAME where CON_LEGACY_ID=:P23_CONLEG_NO
I had no luck. The error i got was,
"+Query cannot be parsed within the Builder. If you believe your query is
syntactically correct, check the ''generic columns'' checkbox below the
region source to proceed without parsing.
ORA-00903: invalid table name+"
Which makes sence, but now I am a bit stuck.
Does anyone have any ideas as to get around this problem?
Thanks in Advance.
-N.S.N.O.

The example I gave you is quite simple. You need to take some time to study it to see where you need be carefull what you put where. Now, your example of course doesn't work becaues you have several errors. This will work for you:
DECLARE
   x   VARCHAR2 (4000);
BEGIN
   x := x || 'SELECT CON_ID FROM ';
   x := x || :p23_db_name;
   x := x || ' WHERE CON_LEGACY_ID = ' || :p23_conleg_no;
   RETURN (x);
END;Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
-------------------------------------------------------------------

How can i improve a performence of query

How can i improve performence of query which not having the where clause for a table

whenever the query have the where clause then only it can use the indexes
otherwise how it can use the index eventhough we create the index of that table columns.

How do I use bind variables for the SQL statements having IN clause

SELECT id, name FROM t
WHERE id in (10,20,30)
As the IN list will have 'n' number of values, I am not able to specify fixed number of bind
variables like
SELECT id, name FROM t
WHERE id in (?,?,?....)

452051 wrote:
I am not able to specify fixed number of bind variablesYou could use collection:
SQL> create or replace force
2    type NumList
3      as
4        table of number
5 /
SQL> select ename from emp where deptno member of NumList(10)
2 /
ENAME
CLARK
KING
MILLER
SQL> select ename from emp where deptno member of NumList(10,20,30)
2 /
ENAME
SMITH
ALLEN
WARD
JONES
MARTIN
BLAKE
CLARK
SCOTT
KING
TURNER
ADAMS
ENAME
JAMES
FORD
MILLER
14 rows selected.
SQL> This way you have one bind variable - collection.
SY.

How to set a bind variable across the pages in a report

I want to create a portal report where data will come from a table for a date range for a week.
For e.g select event_date,last_name, event_name
from RESOURCES
where event_date between trunc(to_date(:curr_date,'DD-MON-RRRR'))
and trunc(to_date(:curr_date,'DD-MON-RRRR')+ 7)
The :curr_date is defined as a bind variable whose default value is sysdate.
Now, when we run the report for the first time, it takes the :curr_date as
sysdate and prints the report.
I have two buttons in the report output like "previous week" and "next week".
If someone presses previous week, the same report should run with curr_date
as sysdate-7 and if someone presses next week, the report should run with
curr_date as sysdate +7 and also the :curr_date sets to sysdate - 7 or sysdate + 7
depending on the button pressed.
Problem:
How do I set the value of curr_date if someone presses any of
previous week/next week.
null

Best to state your JDev version, and technology stack (eg. ADF BC) when posting.
I can think of 2 approaches.
1) Create a parent VO based on SELECT :bindVar FROM dual, then create links between your other VOs and the parent
2) Create a AM client interface method that programatically sets the bind variable in each VO.
Can you specify your use case? This one tends to come up when discussing effective from/to dated queries.
CM.

How to define and work with bind-variables without the dialog-box ?

I want to select different tables with the same bind_variables,
but do want not fill the bind-variables-dialogbox
everytime I use the select statements
because I could simple edit and bind this bind-variables once
at the first select.
select col1, col2 into :bind1, :bind2 from mybasictable_10 where col3 = 'ABCD':
select * from mytable_b where b1 = :bind1 and b2 = :bind2 ;
select * from mytable_c where c1 = :bind1 and c2 = :bind2 ;
select * from mytable_d where d1 = :bind1 and d2 = :bind2 ;
select * from mytable_e where e1 = :bind1 and e2 = :bind2 ;
it doesn't work and I didn't find that in help,
how does it work in sql-developer ?
regards

david,
back to the root of my question:
I do use an 10 years old low-end sql / plsql-tool where I can simple and fast do sql-things like that:
select col1, col2 into :bind1, :bind2 from mybasictable_10 where col3 = 'for_example_ABCD':
select * from mytable_b where b1 = :bind1 and b2 = :bind2 ;
select * from mytable_c where c1 = :bind1 and c2 = :bind2 ;
select * from mytable_d where d1 = :bind1 and d2 = :bind2 ;
select * from mytable_e where e1 = :bind1 and e2 = :bind2 ;
I would like to use oracles SQL-Developer instead of this 'old' tool,
and want to use my 'old' sql / plsql scripts
but the SQL-Developer in this matter seems is to much complicate to use,
I can do complex and big things with sql-dev,
but not simple using bind-variables ;-)( .

Bind variables improve the performence of query??

Similar Messages

Maybe you are looking for