Partition key modification effect the performence of the table ?

we have a partitioned table with more than 15 partitions(Range partition 9i version).
now we want to modify the partition key using row movement option,
but i found in forums and google that partition key modification may effetcs the database performence.
i want to know it will effects the db performence or not,if yes, what extent it effects the db performence and what are the issues may rise ?
Edited by: Nagendra T on Sep 19, 2011 9:32 PM
Edited by: Nagendra T on Sep 19, 2011 9:34 PM

>
i want to know it will effects the db performence or not,if yes, what extent it effects the db performence and what are the issues may rise ?
One thing I can think of is partition pruning.
If the new partition key is not being used in the predicates then partition pruning may not occur.
You should choose partition key wisely to ensure that pruning happens almost for all DMLs.
>
i want to know it will effects the db performence or not,if yes, what extent it effects the db performence and what are the issues may rise ?
Well, due to lack of pruning, you may even see table full scan instead of single partition scan which will drastically hamper the performance

Similar Messages

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

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

Increase the performence of the query how

SELECT * from load_log
where
filetype = 'O/C'
AND EXISTS (SELECT '1' FROM view_orders
WHERE O_ftype = ftype
AND o_loadno = loadno -- << this line
AND o_cocode = 1)
HOW TO INCREASE THIS QUERY PERFORMENCE.
THE view_orders IS THE VIEW THAT CREATED FROM 4 TABLES WHICH HAVE SAME COLUMSN EXCEPT FTYPE
if i remove this line the query execute very fast
AND o_loadno = loadno --<<
PLEASE GIVE ME SOME IDEAS/SUGGESTIONS.
THANKS
HARDSTONE

hard_stone wrote:
hello,
any budy there..plzzz
its urgentIf you mark your question as answered it's quite likely that you won't get any attention any longer.
As already mentioned in the thread, start with an EXPLAIN PLAN to get the execution plan of your statement. Fiddling around with indexes without proper information at hand is like trial-and-error, therefore try to use a systematic approach.
The optimizer might estimate that all your indexes are not selective enough and/or the clustering factor is too high so that the cost accessing the corresponding tables by random access is too high and therefore decides to use a full table scan.
But this can only be checked if you post a proper explain plan output.
Generic instructions how to do so and post the results in proper mono-space formatting here follow:
Could you please post an properly formatted explain plan output using DBMS_XPLAN.DISPLAY including the "Predicate Information" section below the plan to provide more details regarding your statement. Please use the {noformat}[{noformat}code{noformat}]{noformat} tag before and {noformat}[{noformat}/code{noformat}]{noformat} tag after or the {noformat}{{noformat}code{noformat}}{noformat} tag before and after to enhance readability of the output provided:
In SQL*Plus:
SET LINESIZE 130
EXPLAIN PLAN FOR <your statement>;
SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);Note that the package DBMS_XPLAN.DISPLAY is only available from 9i on.
In 9i and above, if the "Predicate Information" section is missing from the DBMS_XPLAN.DISPLAY output but you get instead the message "Plan table is old version" then you need to re-create your plan table using the server side script "$ORACLE_HOME/rdbms/admin/utlxplan.sql".
In previous versions you could run the following in SQL*Plus (on the server) instead:
@?/rdbms/admin/utlxplsA different approach in SQL*Plus:
SET AUTOTRACE ON EXPLAIN
<run your statement>;will also show the execution plan.
In order to get a better understanding where your statement spends the time you might want to turn on SQL trace as described here:
When your query takes too long ...
and post the "tkprof" output here, too.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Does one key recovery effect drives other than the one where windows is installed?

I'm a noob and want to reinstall windows due to some hardware issue. I want to know that if I restore my system partition to its initial state, will the data saved in other drives be affected?

yosam26 wrote:
I'm a noob and want to reinstall windows due to some hardware issue. I want to know that if I restore my system partition to its initial state, will the data saved in other drives be affected?
I'm referring to what I know about OKR based on my unit. There are two drives (C: and D). This is what is explained in the manual (pay particular attention to the Note):

Very much Worried about the performence of my project

Hi All,
We have developed a site. Initially the site was with less no of features and so we have choosen JSP to develop the project. Now we have implemented so many features and the system became complex. I have nearly 1000 Pages most of them containing nearly 2000 lines of code. Now it seems the performence of the sever getting dropping. I fear that is due to the no of Pages and their no of lines of code. Currently i dont have many number of users. If i got the system into full swing i may be having nearly 2000 users. So i wonder the system speed will drop severally. (Currently we are using JRun as the Application Server. Both my database sever and Application sever existing on the same server.)
Can anybody confirm me whether the dropping of the performence of the server is due to the no of pages which existing on the server. Is there any way to solve this problem. I mean to make them a package and keep the package only in the server instead of keeping all the 1000 pages.
I would be very thankfull if anybody help me in this regard.
Thanks and Best Regards,

The number of pages in the application shouldn't really have an impact on the speed of the application. Sure, they consume disk space. Sure, they'll consume memory since each JSP/Servlet gets loaded into memory when it's requested. 1000 pages aren't really that many, I've seen web applications with several thousand JSPs.
I recommend doing some load tests using an application like LoadRunner. And also using some code/JVM analyzers like JProbe to see if you have any problematic areas in your code with respect to memory consumption and CPU utilization.
If you haven't really thought about performance when you were writing your code, chances are there are lots of places you can optimize. Try caching values that don't change often in the VM so you don't have to query the DB ea. time for them. And for goodness sake, put the DB on a different machine than the app server. Are you using DB connection pooling? You should be...

Help on Partition Key .

Team ,
I'm tasked to gather some stats to decide on Partition Key for our Orders table .
It has about 54288107 rows and i need to justify between Order_ID and Insert_Date for ideal partition key .
CREATE TABLE [dbo].[WEb_Order](
[order_id] [int] NOT NULL,
[merchant] [varchar](20) NOT NULL,
[vendor] [varchar](20) NOT NULL,
[Status] [varchar](30) NOT NULL,
[Substatus] [varchar](30) NOT NULL,
[PONumber] [varchar](50) NOT NULL,
[Insert_Date] [datetime] NOT NULL,
[Order_Date] [datetime] NOT NULL,
[line_count] [int] NOT NULL,
[download_date] [datetime] NOT NULL,
CONSTRAINT [PK_WEB_order] PRIMARY KEY CLUSTERED
[order_id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
ON [PRIMARY]
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
GO
Note : I've removed some redundant columns which are of no use on pasted table structure above .
So , What steps do i need to perform so as to decide between order_id or Insert_date such that my partitions are uniform and effective .
Thanks for your pointers in advance !
Rajkumar Yelugu

Partitioning will not always yield to a better performance.
Answer to your question,
You have to use both Order_ID and Insert_Date and define the partition key based on date column.
CREATE TABLE [dbo].[WEb_Order](
[order_id] [int] NOT NULL,
[merchant] [varchar](20) NOT NULL,
[vendor] [varchar](20) NOT NULL,
[Status] [varchar](30) NOT NULL,
[Substatus] [varchar](30) NOT NULL,
[PONumber] [varchar](50) NOT NULL,
[Insert_Date] [datetime] NOT NULL,
[Order_Date] [datetime] NOT NULL,
[line_count] [int] NOT NULL,
[download_date] [datetime] NOT NULL,
CONSTRAINT [PK_WEB_order] PRIMARY KEY CLUSTERED
[order_id] ASC,[Insert_Date]
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
ON [PRIMARY]
) ON [PRIMARY]
OR
ALTER TABLE Web_Orders ADD CONSTRAINT pk_Orders PRIMARY KEY (Order_ID, Insert_Date);
You can refer the below links
https://www.simple-talk.com/sql/database-administration/gail-shaws-sql-server-howlers/
http://www.toadworld.com/platforms/sql-server/w/wiki/9655.partitioned-table-rules-and-gotchas.aspx
--Prashanth

How to improve the performance of the application

Hi,
We have customized the standard SRM BSP application and integrated to portal.
Now it has got some performence issues. It is taking time to load the page and also while navigating between the views.
We have done the performence tuning for the application to the maximum extent. But the problem is while loading the application, its taking time.
Can anyone suggest how to improve the performence of the Application.
Thanks & Regards
Warun

The system configuration is more than enough to run java applications.
You are probalbly doing time-consuming operations in the event thread. Which blocks the event thread and the gui seems not to be responding. If you you have a very bad design.
Use a thread for time consuming operations.

Since upgrading to Firefox 10.0.2 my AVG extension has had to be disabled, as after typing in any web address in the address bar, the enter key had no effect and I could not go to the site without pressing the Reload arrow on right.

I have recently upgraded Firefox to the latest version 10.0.2. After that I could not enter any website address and press the enter key and get to the website, nor could I select a website from the dropdown list of previously visited websites. The only way I could get there was by pressing the arrow on the right side of the address box (Reload current page). Once I disabled the AVG extension, everything worked normally. As soon as I enabled the AVG extension, it stopped working again.

Follow these steps for the controls to work:
# Start > Programs > Mozilla Firefox > Mozilla Firefox
# Find the “Tools” menu at the top of the browser window and select “Add-ons”.
# Click on the “Extensions” icon to make sure you’re in the correct option menu.
# Locate “AVG Safe Search” and click on the containing line to highlight and select the add-on.
# Click the “Disable” button and close the Add-ons window.
# Close down any Firefox windows you may have open.
# That’s It – You’re Done!

Want to know table which stores the Partition key details

Hi Experts,
Could you please tell me if there is way to find out the columns which are part of range partitions of the table. There is a table 'user_tab_partitions' it stores the name of the table and it's partition name. I need to know if there is a similar table/view which stores the partition fields name too.
Thanks and regards,
Ashish Soni

Have you tried..
DBA_PART_KEY_COLUMNS or
ALL_PART_KEY_COLUMNS or
USER_PART_KEY_COLUMNS Views ?
Message was edited by:
biswabijay

I've created a key frame effect in FCP but it dissapears along with the moving object in my layer after rendering, how do I fix this?

I'm creating a titles sequence with Final Cut Pro. In two instances I've put an object in the time line and moved it using keyframes and motion. Before I render the file is still on the layer and visible while scanning the footage with the playhead. However as soon as I render the file dissapears while playing. The object is still listed on the timeline, but is basically invisible when I play the rendered footage. This has happened twice on my timeline. I wish I could explain this any better, but to be honest I've never seen this before and I have no better way to describe it. Other than my object just simply disappears after I render it. Hope you can help. Thank you.

You want your scratch disk to be set externally to a drive with a minimum of a FW800 connection. Is that what you have? (I understand you moved it during the troubleshooting process)
You haven't turned off Clip Enable have you? Right click the text file and make sure Clip Enable is checked. Or have you disabled the track with the green button to the left on the track?
I can't say I've seen this behavior from FCP. Maybe someone else has and they can shed some light on the situation.
I wouldn't use HQ even for a Canon 5D. I use ProRes(LT) RED or Arri Alexa now we talking big sensors that would take advantage of HQ. Assuming that the project will be exhibited on a system that would show you the differences.

Do Outer Joins as well as Self Joins Affect the Performence of a Query ??

4 Tables A,B,C,D.
1 View V Based
Each of the tables having 1 and only one primary key and a few NOT NULL columns.
Now my Query selects from A,B,C,D,V with mapping Table A columns with all other Table(B,C,D,V) Primary Key Columns using Left Outer Join.
Select A.a1,A.a2,A.a3,A.a4,B1.ba,B2.bb,B3.bc,B4.bd,C.c1,D.d1 from (((((((A left outer join B B1 on A.ba=B1.ba) left outer join B B2 on A.bb=B2.bb) left outer join B B3 on A.bc=B3.bc)left outer join B B4 on A.bd=B4.bd)left outer join C on A.c1=C.c1)left outer join D on A.d1=D.d1) left outer join V on A.v1 = V.v1) order by 1;
In this case will the query design effect the Performence???... As this query is taking a long time. As for as Indexes are there on these tables only default Indexes due to Primary, Unique as well as Foreign key only.... Hence table structure is very simple and straight. I need a suggession in such a manner that without making changes to the Table (I am not even allowed to include a single Index to them) ...can the query be modified to optimise the performence??

Each change to a query can effect the performance.
Your query looks straight and simple. Maybe you could increase the performance by simply removeing the order by criteria.
This requires a sort and a sort can be slow, especially when the resulting dataset is very large.
If there are indexes on all foreign keys and you join using those FKs then there should be no problem with the index structure.
I can't say whether it would be better to use an index or not. but you can look at the execution plan and check what the CBO wants to do.
Make sure that all statistics are up to date. You could consider to run an additional dbms_stats.gather_table_stats with compute in the test environment, just to see if the execution plan changes after this.
For further ideas search this forum for the thread "When your query takes too long".

Tiger Classic-ified the OS9 on the other partition.

Hi,
I recently bought this G4 QS and a 5-license DVD of Tiger (black disk with a silver 'X'), both second-hand.
Being a newbie to OS X I also bought about 9 bookshelf inches of Tiger books.
I fitted the G4 with a new 140 Gb hard drive and partitioned it roughly 100/40, taking care to put the OS9 drivers on both partitions.
I then installed OS9.2.2 from a gray G4 installation CD onto both partitions (no apparent problems there) and then put Tiger onto the larger partition.
I opted for this configuration because I have several older applications and files on my various older Macs and one of the books advised choosing a dual-boot system because not all older apps will run under Classic mode. I want to be able to be able to access my legacy files in the transition period until I have got more familiar with Tiger.
Here are my questions:
Tiger has modified the OS9 on the larger partition (which I expected it to do) but it has also modified (Classic-ified) the copy of OS9 on the smaller partition as well, is this normal?
Will the machine behave properly as a dual-boot system?
Did I make some mistake with my installation procedure and, if so, should I try to correct it?
All helpful advice and suggestions will be gratefully received.
Best regards,
Pete.
Message was edited by: Limey Pete
Message was edited by: Limey Pete
Message was edited by: Limey Pete

OS X makes modifications to OS 9 to help classic mode. These modifications do not cause problems when you boot OS 9. There is normally no need for a separate partition for OS 9. OS 9 in an OS X partition can be used with OSX as Classic, or can be booted directly. There are a couple of reasons, though, why you might want separate partitions:
1) You need to run some OS 9 applications that require modifications to OS 9 that make it not work as Classic in OSX.
2) You want to be able to select OS 9 or Classic at boot time using the Option key. If they are in the same partition and boot is set to OS 9, you can get OSX by holding X while booting, but if it is set to OSX, you have to boot OSX, then choose OS 9 in the "Startup Disk" system preference.

When waking from "sleep" screen turns grey under the pointer and the computer is effectively dead. Have to hold power 'off' for five seconds to regain computer.

When waking from "sleep" the screen appears normal but, the pointer leaves a trail of grey as it moves and the whole screen will turn grey if I keep moving the pointer. The computer is effectively dead. Have to shut down by using power off for six seconds and then re-starting. I know little about computers!

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem(s)?
After testing, reboot as usual (i.e., not in safe mode.)

Hi, i am having an issue with a basic motion scroll effect. I already watched and read every tutorial out there regarding this topic and even tried the adobe chat support, but the guy on the other end of the line disconnected me-, probably he didn't unde

Hi, i am having an issue with a basic motion scroll effect.
I already watched and read every tutorial out there regarding this topic and even tried the adobe chat support, but the guy on the other end of the line disconnected me…, probably he didn't understand what i wanted from him because english is not my native language, so a will try to be very, very clear about this one..
please note, that i am new to muse, this is my first project ever.
my idea is as following:
when the customer comes to our companies site, he just sees our logo on a white Background. the logo consists of, say, four elements. when the customer scrolls down, the logo starts to disassamble: first the first part of the logo flies out the left side of the site, then the second part of the logo vanishes down, then the third part of the logo flies to the right, then the fourth part of the logo flies to the top and out of the customers view. given what i have seen, it is possible to do that….
so…..
now i have the four parts of my logo imported as png files into muse and assembled them in design view to build our companies logo. I select every one of the four parts and go into the scroll effects tab left beside the layers tab. first i enter the same values for every one of the four parts: initial motion: 0x and 0x again for the left and right motion; key position ( t-handle) : 0px; final motion: 0x and 0x again for the left and right value.
now i hit "preview".: the logo is "pinned" at the correct position, i can scroll but the logo stays where it is. so far so good….
now i select all the four elements again and go to the scroll effecs tab. at "final motion", i click the down arrows and enter 1x. I hit Preview…
when i am scrolling down the WHOLE logo goes down…. so far so good.
NOW i want the first part of the logo to go down, THEN the second part to go left, THEN the third part to go up, THEN the fourth part to go right.
so i select ONLY the first part, go to the scroll motion tab, at "final motion" i click the left arrows, then i enter 1x.( the up-down value, i set to 0 again).. i hit Preview…
the first part of the logo goes left as soon as i start scrolling, the other three parts still go down at the same time…
NOW i want the second part of the logo to start moving, when the first part has left the scene, not at the same time as the first part.
SO I SELECT THE SECOND PART AND DRAG ITS T-HANDLE (KEY POSITION) DOWN TO, LETS SAY, 200PX. SO IT STARTS MOVING ONLY AFTER THE CUSTOMER HAS REACHED THAT POINT, RIGHT?
BUT WHEN I PREVIEW THAT ****, THE LOGO IS NOT TOGETHER ANYMORE, THE SECOND PART IS FLOATING ANYWHERE ELSE BUT WHERE IT SHOULD BE…..WTFF????
short: when i move the t handle, the initial position of the object changes. thats what i said to the adobe employee, but he said, that thats the expected behavior….
but if thats so, how can i have my four parts correctly together, so they form my logo, but with different t handles, so that they all start to move at different times??
Pleeease help me, i am dying of frustration here…..:( that behavior cant be right, right?
Thanks so much to everyone who actually reads this post and tries to help…….
All the best,
Niki Lapan

Thank you so much for helping,
But i really wonder how you did that. did you always switch between design view and preview view, then change the key position for 2px then switch back, to align the four letters? because i imagine that can get really frustrating, if you have a logo consisting of 58 parts instead of 4!:)
Anyway thank you very much for your time and effort!!!!

Partition key modification effect the performence of the table ?

Similar Messages

Maybe you are looking for