Performence tuning

hi
can any body tell me how it will work for all entries statement in select stmnt

Hi,
You can only use FOR ALL ENTRIES IN ...WHERE ...in a SELECT statement.
SELECT ... FOR ALL ENTRIES IN itab WHERE cond returns the union of the solution sets of all SELECT statements that would result if you wrote a separate statement for each line of the internal table replacing the symbol itab-f with the corresponding value of component f in the WHERE condition.Duplicates are discarded from the result set. If the internal table itab does not contain any entries, the system treats the statement as though there were no WHERE cond condition, and selects all records (in the current client).
For example:
SELECT * FROM sflight INTO wa_sflight
FOR ALL ENTRIES IN ftab
WHERE CARRID = ftab-carrid AND
CONNID = ftab-connid AND
fldate = '20010228'.
This condition, return all entries of the sflight.
When using FOR ALL ENTRIES the number of matching records is restricted to the number of records in the internal table. If the number of records in the database tables is too large then join would cause overheads in performance. Additionally a JOIN bypasses the table buffering.
follow these links for knowing the difference between For all entries and joins.
http://www.erpgenie.com/abap/performance.htm#For%20all%20entries
http://blogs.ittoolbox.com/sap/db2/archives/for-all-entries-vs-db2-join-8912
Regards,
Priyanka.

Similar Messages

Hi gurur's how we do the PERFORMENCE TUNING OF THE REPORT

hi gurur's how we do the PERFORMENCE TUNING OF THE REPORT .plz help me

Hi,
Use tcode SE30 and ST05
Regards,
Prashant

Database Performence tuning Interview question

Hello All,
I had a bad interview yesterday for Oracle Database Administration job and was a developer who ask me a question about performance tuning that I couldn't answer him; the question was like
A developer come to you with a query that he issue to a database and he complain that it is too slow and the system is hang how can you solve the problem?
describe the steps that you have to follow to take care of this issue
Can some one give me an Idea on how to solve these type of problem, the steps
I assume it has to do with AWR, ASM, ADDM, AMM
I am a very new oracle DBA just certify with no experience that is why i found it difficult
Need help
Thanks
Nounou

user9362044 wrote:
Hello All,
I had a bad interview yesterday for Oracle Database Administration job and was a developer who ask me a question about performance tuning that I couldn't answer him; the question was likeThat's OK, I probably couldn't answer to his liking either.
>
A developer come to you with a query that he issue to a database and he complain that it is too slow and the system is hang how can you solve the problem?
describe the steps that you have to follow to take care of this issue
Can some one give me an Idea on how to solve these type of problem, the steps
I assume it has to do with AWR, ASM, ADDM, AMM
I am a very new oracle DBA just certify with no experience that is why i found it difficultWell, of course you would. As the "what to do when your query is slow" thread shows, there are a number of tools you would be expected to know, and yet, does that really answer the question? Someone depending on certification to get a job may be sorely disappointed, as the expectations of people offering the jobs don't often match up with the certification process. In this case, it sounds like they were expecting someone to have been a developer with experience in these issues moving up to a performance analyst.
Look at the performance tuning manual - it has quite a different process than the "what to do thread." That's because the system hang may not be due to the developers query at all, it may just be the trigger for another problem, or even be entirely coincidental. It might not even be a "system hang," it could be just some stupid app locking goof (or design feature), that makes users think the system is hung. I had one of those yesterday, looked just like http://download.oracle.com/docs/cd/E11882_01/server.112/e10822/tdppt_sqlid.htm#BABFJJCJ But the thing is, that is extremely misleading. What actually happened was another user walked away from her terminal with a row locked for update, causing everything else that needed to get to that row to go nuts trying to get to it. So, every methodology was wrong, it was not a performance problem at all, all I needed to do was look at the "all instance locks" screen and tell the complaining user (and have my boss tell the other users complaining to him) to drag the user away from her lunch and castigate her, as everyone is trained not to leave in the middle of an update screen.
So I probably wouldn't pass the interview either, as my view is a DBA is expected to know his system, know the apps, and know the tools available to solve problems, and a company shouldn't expect someone new to know much of that. The developer probably had a very different answer in mind, and who knows if it was the "what to do" thread, the Oracle party line, some other methodology like Method-R, ODM, Performance Firefighting, Silver Bullet, ratio tuning, the idea that he can know how you work from divining your thought processes or some strange ideas that make less sense. Or maybe none of those, he was just evaluating how you would fit in with the group.
An example of the range of expectations: http://www.freelists.org/post/oracle-l/Questions-for-a-Jr-DBA

Database performence tuning

iam not able to get perfect tuning in database connectivity.
iam creating connection object at login page i wanted to use the same connection object in different page. is this the correct way please give some efficient way of usage of connection object.thanks for any regards

Hi,
Buddy no need to open diff. connection. Just one connection will do(provided ur app is small and ur server is pooling).
fundamentally u must have different DAO's for different components(coz diff. components requir different resultsets).
if ur not using Locator pattern to locate objects... then open connection in static block on servlet., put the opbect in context and share the same .
Its a good practice to close and nullify all ur resultset/statement objects immediate after processing.And connection object is closed when no more required thru out the application or when application is shuting down.
@mit

Regarding performence Tuning

I have two table SDTM_EG,SDTM_SP both have same table structure and indexes.toatl count from both table is SDTM_EG=560066,SDTM_SP=821651.
While i run query select count(*) from each table then it will take time As SDTM_EG=9 Sec and SDTM_SP=5esc.
when i saw table size from dba_segments means i run query
select sum(bytes/1024/1024) from dba_segments where OWNER='SDTMREPOSITORY' and SEGMENT_NAME='SDTM_EG';
'SDTM_EG'=1280;'SDTM_SP'=312.
wether this effect on my query for retriving data.Means whenever i run any script on SDTM_EG table it take more time as compare to SDTM_SP.
Please suggest solution for this .

Hi:
Please do an explain plan on your query and see if it is using the right plan. If you are running on CBO please make sure relevant statistics are collected on the tables. There are so many factors that determing why query on that particular table is slow. Missing index , Wrong statistics and wrong join order just to name a few. Doing an explain plan in most cases will help you what might have gone wrong.
Regards,
BMP

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.

Max. No. of infobjects

Hi experts
What is the maximum no. of infoobjects can we accommodate in a cube? and what is the maximum no. of characterestics can have for a dimension?
Thx a lot in advance
Surya

Hi teja,
In cube there will be 16 dimensions and this 3 are predefined by sap.Those are
1.Unit
2.Time.
3.Data package.
So there will be 13 dimensions.According to the Extended star schema fact table will be in centre and surrounded by the dimensions tabels and one dimension is attached to maximum number of 248 sid tabels.and multiply that 248 * 13 = 3224.
And maximum number of key figures will be 233.
Add those two 3224 + 233 = 3457.
So u can add 3457 characterstics and key figures in a cube.
If u add this much of characterstics the volume of the cube will be increased and performence tuning and loading performence will be decreased.
thanks&Regards,
Giri.

Needs suggestion and help regarding my preparation

I am looking for new job from my existing role. Here all the interviews are I am getting are scenario based and I am not able to reply most of them and as a result getting rejecting in every instance. . In my day to day work I am a part of DBA Monitoring team and everyday job is to monitor tablespace, listener, checking important mountpoint space, instance health check and backup monitoring, it is becoming boring day by day, hence I want to switch. But how to prepare for these typical scenarios based queries, I have both and single and Dataguard setup in my own laptop to play with but I am not getting any idea how to stimulate the different scenario's which can help me to crack the interviews.
Any idea/advice and suggestions will be highly appreciated and will be followed diligently. Thanks in advance.

Hi,
i hope ....in real time world ...they expecting more from you than what your doing now....as DBA...
actually as a DBA you have to do practice/play on your laptop or test environments...lots of things are there to do....
how to prepare myself to reply those type problem scenario's and their solutions
practice and ...........practice...practice...practice.......practice...practice...practice......practice...practice...practice......practice...practice...practice...... various scenarious.......on your test machine......
example: 1st thing is you have to learn oracle architecture and gain the sound knowledge on that.... book expert oracle architecture by thomas kyte...
2:backup and recovery ....every interviewer is expecting more info from you ..in this category...i hope..you have to practice various scenorious on your test machine ...
like some of below....take a full backup of your database before proceeding any.R&D....
1:datafile loss...system datafile losss... delete from the disk and try to restore/recover the db....do practice by using offline backup/online bcakup...
2 redo corruption....modifing redo log size....
3)controfile corruption/lost
4)data gaurd archive log missing sequence like gap at standby side..wrt primary.....break the N/W connection try this scenario...practice switch over/fail over scenarious..etc..
5)practice point in time recovery....
6)take hot backup of database practice above ones...like datafile lost/corruption...etc...
7) unconsciously table drop...flashback technology...
8)RMAN..beauty of oracle...lots of thing are there to play on test by using RMAN...
configuration....show all...it will give you the some conf parameter try to read each and every conf parameter do if its configure other than default...if you ..backup..restore...of any file missing...like datafile missing controfile file missing..etc...practice/play RMAN cmds....
now a days every interviewer will ask lots of things about RMAN....
9) do the cloning by using offline backup/online backup/RMAN
http://gavinsoorma.com/2010/06/some-more-rman-recovery-scenarios/
http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmintro.htm
http://docs.oracle.com/cd/B19306_01/backup.102/b14191.pdf
once you got the sound knowldge on above things...then performence tuning.... analyzing statspack report/awr...etc..
my suggestion is make a habit of to fallow oracle forum every day..if possible every Hr..and try to read old posts in the form.....reproduce problem by your self and fallow the.experts solution and document those it will useful for you in future ..things makes good for you...all the very best....
thanks,
DBC,
Sr DBA.
Edited by: dbc001 on Mar 10, 2013 10:36 AM

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

Apps tuning

i want to know certain information regarding performance tuning in oracle apps database.wat kind of paerformance tuning activities will the users normally follows in apps database environment.

Hi,
I believe you can find such guidelines in the documents/threads referenced below.
Note: 69565.1 - A Holistic Approach to Performance Tuning Oracle Applications Systems
EBS, performence issue
Re: EBS, performence issue
Oracle Apps Tuning
Re: Oracle Apps Tuning
Regards,
Hussein

Best General practice for performance and tuning.

Hi ,
Can some body let me know the General Best practice for performance and tuning for Oracle Application 11i and 10g.
that can be implemented and suggest in a new environment.
Regards,

Hi,
Please see the following documents/threads.
Note: 744143.1 - Tuning performance on eBusiness suite
Note: 864226.1 - How Can I Diagnose Poor E-Business Suite Performance?
Note: 362851.1 - Guidelines to setup the JVM in Apps Ebusiness Suite 11i and R12
Note: 216205.1 - Database Initialization Parameters for Oracle Applications Release 11i
EBS, performence issue
Re: EBS, performence issue
Oracle Apps Tuning
Re: Oracle Apps Tuning
Regards,
Hussein

Need help in performence

hi,
i wont to increase the performence becouse this select is take lot of time
how i can do that?
regards
 SELECT vkorg vtweg spart auart augru vbeln audat mandt kvgr1
 kvgr2 kvgr3 kvgr4 kvgr5 kunnr waerk erdat ps_psp_pnr
 netwr knumv vbtyp
 objnr
 FROM vbak
 INTO wa_reptab
 WHERE audat IN r_sel
 WHERE vbtyp IN ('C','G','L')
 AND auart IN so_type
 AND kvgr1 IN so_csgr1
 AND kvgr2 IN so_csgr2
 AND KVGR4 IN CONTRTYP
 AND KVGR5 IN OFFSDEAL
 AND vkorg IN so_vkorg
 AND vtweg IN so_vtweg
 AND spart IN so_spart
 AND kunnr IN sl_kunnr.
 PERFORM status_desc changing wa_stonr.
 if wa_stonr = '06'.
 continue.
 endif.
 IF wa_reptab-vbtyp = 'L' AND wa_reptab-auart <> 'YMC0' .
 CONTINUE .
 ENDIF .
 SELECT SINGLE bzirk INTO tmp_bzirk
 FROM vbkd
 WHERE vbeln = wa_reptab-vbeln
 AND posnr = 0 .
 IF NOT tmp_bzirk IN so_sldst .
 CONTINUE .
 ELSE .
 wa_reptab-sldst = tmp_bzirk .
 ENDIF .
 SELECT SINGLE brsch INTO tmp_brsch
 FROM kna1
 WHERE kunnr = wa_reptab-kunnr .
 IF NOT tmp_brsch IN so_bsar .
 CONTINUE .
 ELSE .
 wa_reptab-bsar = tmp_brsch .
 ENDIF .
 APPEND wa_reptab TO reptab .
 ENDSELECT .
 LOOP AT reptab INTO wa_reptab .
 AUTHORITY-CHECK OBJECT 'V_VBAK_VKO'
 ID 'VKORG' FIELD wa_reptab-vkorg
 ID 'VTWEG' FIELD wa_reptab-vtweg
 ID 'SPART' FIELD wa_reptab-spart
 ID 'ACTVT' FIELD '03'.
 IF sy-subrc NE 0.
 DELETE reptab.
 ENDIF.
 ENDLOOP .
*& Form status_desc
form status_desc changing wa_stonr.
data: "wa_stonr like tj30-stonr ,
 p_stonr like tj30-stonr ,
 wa_stsma like tj30-stsma .
clear wa_stonr.
CALL FUNCTION 'STATUS_READ'
 EXPORTING
 client = sy-mandt
 objnr = wa_reptab-objnr
 only_active = 'X'
 IMPORTING
 stsma = wa_stsma
 stonr = p_stonr "wa_stonr
 EXCEPTIONS
 object_not_found = 1
 OTHERS = 2.
 wa_stonr = p_stonr.
Regards

Hi
Ways of Performance Tuning
1. Selection Criteria
2. Select Statements
 Select Queries
 SQL Interface
 Aggregate Functions
 For all Entries
Select Over more than one Internal table
Selection Criteria
1. Restrict the data to the selection criteria itself, rather than filtering it out using the ABAP code using CHECK statement.
2. Select with selection list.

Points # 1/2
SELECT * FROM SBOOK INTO SBOOK_WA.
CHECK: SBOOK_WA-CARRID = 'LH' AND
 SBOOK_WA-CONNID = '0400'.
ENDSELECT.
The above code can be much more optimized by the code written below which avoids CHECK, selects with selection list
SELECT CARRID CONNID FLDATE BOOKID FROM SBOOK INTO TABLE T_SBOOK
WHERE SBOOK_WA-CARRID = 'LH' AND
 SBOOK_WA-CONNID = '0400'.
Select Statements Select Queries
1. Avoid nested selects
2. Select all the records in a single shot using into table clause of select statement rather than to use Append statements.
3. When a base table has multiple indices, the where clause should be in the order of the index, either a primary or a secondary index.
4. For testing existence , use Select.. Up to 1 rows statement instead of a Select-Endselect-loop with an Exit.
5. Use Select Single if all primary key fields are supplied in the Where condition .
Point # 1
SELECT * FROM EKKO INTO EKKO_WA.
SELECT * FROM EKAN INTO EKAN_WA
 WHERE EBELN = EKKO_WA-EBELN.
ENDSELECT.
ENDSELECT.
The above code can be much more optimized by the code written below.
SELECT PF1 PF2 FF3 FF4 INTO TABLE ITAB
 FROM EKKO AS P INNER JOIN EKAN AS F
 ON PEBELN = FEBELN.
Note: A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. One should therefore use nested SELECT loops only if the selection in the outer loop contains very few lines or the outer loop is a SELECT SINGLE statement.
Point # 2
SELECT * FROM SBOOK INTO SBOOK_WA.
CHECK: SBOOK_WA-CARRID = 'LH' AND
 SBOOK_WA-CONNID = '0400'.
ENDSELECT.
The above code can be much more optimized by the code written below which avoids CHECK, selects with selection list and puts the data in one shot using into table
SELECT CARRID CONNID FLDATE BOOKID FROM SBOOK INTO TABLE T_SBOOK
WHERE SBOOK_WA-CARRID = 'LH' AND
 SBOOK_WA-CONNID = '0400'.
Point # 3
To choose an index, the optimizer checks the field names specified in the where clause and then uses an index that has the same order of the fields . In certain scenarios, it is advisable to check whether a new index can speed up the performance of a program. This will come handy in programs that access data from the finance tables.
Point # 4
SELECT * FROM SBOOK INTO SBOOK_WA
UP TO 1 ROWS
WHERE CARRID = 'LH'.
ENDSELECT.
The above code is more optimized as compared to the code mentioned below for testing existence of a record.
SELECT * FROM SBOOK INTO SBOOK_WA
 WHERE CARRID = 'LH'.
EXIT.
ENDSELECT.
Point # 5
If all primary key fields are supplied in the Where condition you can even use Select Single.
Select Single requires one communication with the database system, whereas Select-Endselect needs two.
Select Statements contd.. SQL Interface
1. Use column updates instead of single-row updates
to update your database tables.
2. For all frequently used Select statements, try to use an index.
3. Using buffered tables improves the performance considerably.
Point # 1
SELECT * FROM SFLIGHT INTO SFLIGHT_WA.
SFLIGHT_WA-SEATSOCC =
 SFLIGHT_WA-SEATSOCC - 1.
UPDATE SFLIGHT FROM SFLIGHT_WA.
ENDSELECT.
The above mentioned code can be more optimized by using the following code
UPDATE SFLIGHT
 SET SEATSOCC = SEATSOCC - 1.
Point # 2
SELECT * FROM SBOOK CLIENT SPECIFIED INTO SBOOK_WA
WHERE CARRID = 'LH'
 AND CONNID = '0400'.
ENDSELECT.
The above mentioned code can be more optimized by using the following code
SELECT * FROM SBOOK CLIENT SPECIFIED INTO SBOOK_WA
WHERE MANDT IN ( SELECT MANDT FROM T000 )
 AND CARRID = 'LH'
 AND CONNID = '0400'.
ENDSELECT.
Point # 3
Bypassing the buffer increases the network considerably
SELECT SINGLE * FROM T100 INTO T100_WA
BYPASSING BUFFER
WHERE SPRSL = 'D'
 AND ARBGB = '00'
 AND MSGNR = '999'.
The above mentioned code can be more optimized by using the following code
SELECT SINGLE * FROM T100 INTO T100_WA
WHERE SPRSL = 'D'
 AND ARBGB = '00'
 AND MSGNR = '999'.

Select Statements contd Aggregate Functions
 If you want to find the maximum, minimum, sum and average value or the count of a database column, use a select list with aggregate functions instead of computing the aggregates yourself.
Some of the Aggregate functions allowed in SAP are MAX, MIN, AVG, SUM, COUNT, COUNT( * )
Consider the following extract.
 Maxno = 0.
 Select * from zflight where airln = LF and cntry = IN.
 Check zflight-fligh > maxno.
 Maxno = zflight-fligh.
 Endselect.
The above mentioned code can be much more optimized by using the following code.
Select max( fligh ) from zflight into maxno where airln = LF and cntry = IN.

Select Statements contdFor All Entries
 The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the length of the WHERE clause.
 The plus
 Large amount of data
 Mixing processing and reading of data
 Fast internal reprocessing of data
 Fast
 The Minus
 Difficult to program/understand
 Memory could be critical (use FREE or PACKAGE size)
Points to be must considered FOR ALL ENTRIES
 Check that data is present in the driver table
 Sorting the driver table
 Removing duplicates from the driver table
Consider the following piece of extract
Loop at int_cntry.
 Select single * from zfligh into int_fligh
where cntry = int_cntry-cntry.
Append int_fligh.
Endloop.
The above mentioned can be more optimized by using the following code.
Sort int_cntry by cntry.
Delete adjacent duplicates from int_cntry.
If NOT int_cntry[] is INITIAL.
 Select * from zfligh appending table int_fligh
 For all entries in int_cntry
 Where cntry = int_cntry-cntry.
Endif.
Select Statements contd Select Over more than one Internal table
1. Its better to use a views instead of nested Select statements.
2. To read data from several logically connected tables use a join instead of nested Select statements. Joins are preferred only if all the primary key are available in WHERE clause for the tables that are joined. If the primary keys are not provided in join the Joining of tables itself takes time.
3. Instead of using nested Select loops it is often better to use subqueries.
Point # 1
SELECT * FROM DD01L INTO DD01L_WA
WHERE DOMNAME LIKE 'CHAR%'
 AND AS4LOCAL = 'A'.
SELECT SINGLE * FROM DD01T INTO DD01T_WA
 WHERE DOMNAME = DD01L_WA-DOMNAME
 AND AS4LOCAL = 'A'
 AND AS4VERS = DD01L_WA-AS4VERS
 AND DDLANGUAGE = SY-LANGU.
ENDSELECT.
The above code can be more optimized by extracting all the data from view DD01V_WA
SELECT * FROM DD01V INTO DD01V_WA
WHERE DOMNAME LIKE 'CHAR%'
 AND DDLANGUAGE = SY-LANGU.
ENDSELECT
Point # 2
SELECT * FROM EKKO INTO EKKO_WA.
SELECT * FROM EKAN INTO EKAN_WA
 WHERE EBELN = EKKO_WA-EBELN.
ENDSELECT.
ENDSELECT.
The above code can be much more optimized by the code written below.
SELECT PF1 PF2 FF3 FF4 INTO TABLE ITAB
 FROM EKKO AS P INNER JOIN EKAN AS F
 ON PEBELN = FEBELN.
Point # 3
SELECT * FROM SPFLI
INTO TABLE T_SPFLI
WHERE CITYFROM = 'FRANKFURT'
 AND CITYTO = 'NEW YORK'.
SELECT * FROM SFLIGHT AS F
 INTO SFLIGHT_WA
 FOR ALL ENTRIES IN T_SPFLI
 WHERE SEATSOCC < F~SEATSMAX
 AND CARRID = T_SPFLI-CARRID
 AND CONNID = T_SPFLI-CONNID
 AND FLDATE BETWEEN '19990101' AND '19990331'.
ENDSELECT.
The above mentioned code can be even more optimized by using subqueries instead of for all entries.
SELECT * FROM SFLIGHT AS F INTO SFLIGHT_WA
 WHERE SEATSOCC < F~SEATSMAX
 AND EXISTS ( SELECT * FROM SPFLI
 WHERE CARRID = F~CARRID
 AND CONNID = F~CONNID
 AND CITYFROM = 'FRANKFURT'
 AND CITYTO = 'NEW YORK' )
 AND FLDATE BETWEEN '19990101' AND '19990331'.
ENDSELECT.
1. Table operations should be done using explicit work areas rather than via header lines.
2. Always try to use binary search instead of linear search. But dont forget to sort your internal table before that.
3. A dynamic key access is slower than a static one, since the key specification must be evaluated at runtime.
4. A binary search using secondary index takes considerably less time.
5. LOOP ... WHERE is faster than LOOP/CHECK because LOOP ... WHERE evaluates the specified condition internally.
6. Modifying selected components using MODIFY itab TRANSPORTING f1 f2.. accelerates the task of updating a line of an internal table.
Point # 2
READ TABLE ITAB INTO WA WITH KEY K = 'X BINARY SEARCH.
IS MUCH FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY K = 'X'.
If TAB has n entries, linear search runs in O( n ) time, whereas binary search takes only O( log2( n ) ).
Point # 3
READ TABLE ITAB INTO WA WITH KEY K = 'X'. IS FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY (NAME) = 'X'.
Point # 5
LOOP AT ITAB INTO WA WHERE K = 'X'.
ENDLOOP.
The above code is much faster than using
LOOP AT ITAB INTO WA.
CHECK WA-K = 'X'.
ENDLOOP.
Point # 6
WA-DATE = SY-DATUM.
MODIFY ITAB FROM WA INDEX 1 TRANSPORTING DATE.
The above code is more optimized as compared to
WA-DATE = SY-DATUM.
MODIFY ITAB FROM WA INDEX 1.
7. Accessing the table entries directly in a "LOOP ... ASSIGNING ..." accelerates the task of updating a set of lines of an internal table considerably
8. If collect semantics is required, it is always better to use to COLLECT rather than READ BINARY and then ADD.
9. "APPEND LINES OF itab1 TO itab2" accelerates the task of appending a table to another table considerably as compared to LOOP-APPEND-ENDLOOP.
10. DELETE ADJACENT DUPLICATES accelerates the task of deleting duplicate entries considerably as compared to READ-LOOP-DELETE-ENDLOOP.
11. "DELETE itab FROM ... TO ..." accelerates the task of deleting a sequence of lines considerably as compared to DO -DELETE-ENDDO.
Point # 7
Modifying selected components only makes the program faster as compared to Modifying all lines completely.
e.g,
LOOP AT ITAB ASSIGNING <WA>.
I = SY-TABIX MOD 2.
IF I = 0.
 <WA>-FLAG = 'X'.
ENDIF.
ENDLOOP.
The above code works faster as compared to
LOOP AT ITAB INTO WA.
I = SY-TABIX MOD 2.
IF I = 0.
 WA-FLAG = 'X'.
 MODIFY ITAB FROM WA.
ENDIF.
ENDLOOP.
Point # 8
LOOP AT ITAB1 INTO WA1.
READ TABLE ITAB2 INTO WA2 WITH KEY K = WA1-K BINARY SEARCH.
IF SY-SUBRC = 0.
 ADD: WA1-VAL1 TO WA2-VAL1,
 WA1-VAL2 TO WA2-VAL2.
 MODIFY ITAB2 FROM WA2 INDEX SY-TABIX TRANSPORTING VAL1 VAL2.
ELSE.
 INSERT WA1 INTO ITAB2 INDEX SY-TABIX.
ENDIF.
ENDLOOP.
The above code uses BINARY SEARCH for collect semantics. READ BINARY runs in O( log2(n) ) time. The above piece of code can be more optimized by
LOOP AT ITAB1 INTO WA.
COLLECT WA INTO ITAB2.
ENDLOOP.
SORT ITAB2 BY K.
COLLECT, however, uses a hash algorithm and is therefore independent
of the number of entries (i.e. O(1)) .
Point # 9
APPEND LINES OF ITAB1 TO ITAB2.
This is more optimized as compared to
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
Point # 10
DELETE ADJACENT DUPLICATES FROM ITAB COMPARING K.
This is much more optimized as compared to
READ TABLE ITAB INDEX 1 INTO PREV_LINE.
LOOP AT ITAB FROM 2 INTO WA.
IF WA = PREV_LINE.
 DELETE ITAB.
ELSE.
 PREV_LINE = WA.
ENDIF.
ENDLOOP.
Point # 11
DELETE ITAB FROM 450 TO 550.
This is much more optimized as compared to
DO 101 TIMES.
DELETE ITAB INDEX 450.
ENDDO.
12. Copying internal tables by using ITAB2[ ] = ITAB1[ ] as compared to LOOP-APPEND-ENDLOOP.
13. Specify the sort key as restrictively as possible to run the program faster.
Point # 12
ITAB2[] = ITAB1[].
This is much more optimized as compared to
REFRESH ITAB2.
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
Point # 13
SORT ITAB BY K. makes the program runs faster as compared to SORT ITAB.
Internal Tables contd
Hashed and Sorted tables
1. For single read access hashed tables are more optimized as compared to sorted tables.
2. For partial sequential access sorted tables are more optimized as compared to hashed tables
Hashed And Sorted Tables
Point # 1
Consider the following example where HTAB is a hashed table and STAB is a sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE HTAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
This runs faster for single read access as compared to the following same code for sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE STAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
Point # 2
Similarly for Partial Sequential access the STAB runs faster as compared to HTAB
LOOP AT STAB INTO WA WHERE K = SUBKEY.
ENDLOOP.
This runs faster as compared to
LOOP AT HTAB INTO WA WHERE K = SUBKEY.
ENDLOOP.

How to improve function & procedure performence

Hi,
How to improve performence of function and procedure .
When i have to use parallel_enable,deterministic features .
thank you
Edited by: 808542 on Dec 22, 2010 2:25 AM
Edited by: 808542 on Dec 22, 2010 2:26 AM

How to improve performence of function and procedure .Start with tracing the session that executes the functions/procedures and tkprof the trc. file (with wait events).
The tkprof output will give you pointers where you could make some improvement.
You can find many examples on http://asktom.oracle.com, do a search on 'tuning'
For example:
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:6904032233295
If you have no clue what all this means then ask your DBA to help you.
See also the Performance Tuning Guide @ http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/toc.htm

Performence Monitoring

Hi,
We have nearly 20 Queries. I need monitor the performence of these. How can i monitor these. How can i come to know that perticular Query performence is low because of aggregates or some thing. How can i improve it. Please guide me.
Thanks in Advance.
Nagesh.

Try searching the BW forums on "query performance", you'll get lots of hits.
Also SDN has a site called the BW Performance Tuning Knowledge Center. It has links to papers and presentations, and sometimes has links to videos from Tech Ed sessions.
The BW Satistics cubes hold the query stats and there are business content queries you cn use as starters.
Also a good overview of query performance on your system can be gotten from transaction ST03N. For query info, you need to be in Expert Mode. I've posted more detailed info recently on ST03N for other threads so if you search the BI Forums on ST03N, you should get a number of hits.

Help for query tuning

hello all
my one of query is returning result in 1-2 mins only for 1 lakh record but i am not sure if it showed me complete rows or not because when I an trying to get count of result ..its taking lot of time .when I am using this query on plsql code ..code is running slow so just wanted to confirm on query tuning point of view if its fine or not ..please look onto it and let me know if query is fine or not by explain plan .my oracle version is 11g
this is my query
SELECT ROWNUM , TRUNC(rownum/5000) + 20000 ,'FOR_UPDATE', sku_org.NAME ,
acct_promo_sku.src_num , acct_promo_sku.sub_type ,
promo_actual.sku_actual_pos
FROM siebel.s_src acct_promo_hdr,
siebel.s_src acct_title_format,
siebel.s_src acct_promo_sku,
siebel.s_src_x acct_promo_hdrx,
siebel.s_src_x acct_promo_skux,
siebel.s_prod_int prod,
siebel.s_bu promo_hdr_org,
siebel.s_bu sku_org,
siebelwb.stg_sbl_acct_promo_actuals2 promo_actual
WHERE acct_promo_hdr.sub_type = 'PLAN_ACCOUNT_PROMOTION'
AND acct_promo_hdr.row_id = acct_title_format.par_src_id
AND acct_title_format.sub_type = 'PLAN_ACCT_PROMOTION_CATEGORY'
AND acct_title_format.row_id = acct_promo_sku.par_src_id
AND acct_promo_sku.sub_type = 'PLAN_ACCOUNT_PROMOTION_PRODUCT'
AND acct_promo_hdr.row_id = acct_promo_hdrx.par_row_id
AND acct_promo_sku.row_id = acct_promo_skux.par_row_id(+)
AND acct_promo_sku.prod_id = prod.row_id
AND acct_promo_hdr.bu_id = promo_hdr_org.row_id
AND acct_promo_sku.bu_id = sku_org.row_id
AND prod.x_prod_material_num = promo_actual.material_number
and prod.X_PROD_SALES_ORG=promo_actual.sales_org
AND acct_promo_hdr.row_id = promo_actual.acct_promo_id
and nvl(acct_promo_hdr.pr_accnt_id,0)=nvl(promo_actual.acct_siebel_rowid,0)
and nvl(acct_promo_hdr.x_indirect_id,0)=nvl(promo_actual.indirect_acct_siebel_rowid,0)
AND promo_actual.load_date >= TRUNC(SYSDATE)
AND promo_actual.load_date < TRUNC(SYSDATE + 1)
explain plan
PLAN_TABLE_OUTPUT
Plan hash value: 3864590768
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 1 | 298 | 2300 (1)| 00:00:28 |
| 1 | COUNT | | | | | |
|* 2 | FILTER | | | | | |
| 3 | NESTED LOOPS | | | | | |
| 4 | NESTED LOOPS | | 1 | 298 | 2300 (1)| 00:00:28 |
| 5 | NESTED LOOPS OUTER | | 1 | 273 | 2298 (1)| 00:00:28 |
| 6 | NESTED LOOPS | | 1 | 263 | 2296 (1)| 00:00:28 |
| 7 | NESTED LOOPS | | 1 | 236 | 2295 (1)| 00:00:28 |
| 8 | NESTED LOOPS | | 1 | 165 | 2292 (1)| 00:00:28 |
| 9 | NESTED LOOPS | | 1 | 117 | 2289 (1)| 00:00:28 |
| 10 | NESTED LOOPS | | 1 | 109 | 2289 (1)| 00:00:28 |
| 11 | NESTED LOOPS | | 1 | 99 | 2287 (1)| 00:00:28 |
|* 12 | TABLE ACCESS FULL | STG_SBL_ACCT_PROMO_ACTUALS2 | 1 | 49 | 2285 (1)| 00:0
|* 13 | TABLE ACCESS BY INDEX ROWID| S_SRC | 1 | 50 | 2 (0)| 00:00:01 |
|* 14 | INDEX UNIQUE SCAN | S_SRC_P1 | 1 | | 1 (0)| 00:00:01 |
|* 15 | INDEX RANGE SCAN | S_SRC_X_U1 | 1 | 10 | 2 (0)| 00:00:01 |
|* 16 | INDEX UNIQUE SCAN | S_BU_P1 | 1 | 8 | 0 (0)| 00:00:01 |
|* 17 | TABLE ACCESS BY INDEX ROWID | S_SRC | 1 | 48 | 3 (0)| 00:00:01 |
|* 18 | INDEX RANGE SCAN | S_SRC_F2 | 2 | | 2 (0)| 00:00:01 |
|* 19 | TABLE ACCESS BY INDEX ROWID | S_SRC | 1 | 71 | 3 (0)| 00:00:01 |
|* 20 | INDEX RANGE SCAN | S_SRC_F2 | 2 | | 2 (0)| 00:00:01 |
| 21 | TABLE ACCESS BY INDEX ROWID | S_BU | 1 | 27 | 1 (0)| 00:00:01 |
|* 22 | INDEX UNIQUE SCAN | S_BU_P1 | 1 | | 0 (0)| 00:00:01 |
|* 23 | INDEX RANGE SCAN | S_SRC_X_U1 | 1 | 10 | 2 (0)| 00:00:01 |
|* 24 | INDEX UNIQUE SCAN | S_PROD_INT_P1 | 1 | | 1 (0)| 00:00:01 |
|* 25 | TABLE ACCESS BY INDEX ROWID | S_PROD_INT | 1 | 25 | 2 (0)| 00:00:
Predicate Information (identified by operation id):
2 - filter(TRUNC(SYSDATE@!)<TRUNC(SYSDATE@!+1))
12 - filter("PROMO_ACTUAL"."LOAD_DATE">=TRUNC(SYSDATE@!) AND "PROMO_ACTUAL"."LOAD_DATE"<TRUNC(SYSD
13 - filter("ACCT_PROMO_HDR"."SUB_TYPE"='PLAN_ACCOUNT_PROMOTION' AND
NVL("ACCT_PROMO_HDR"."PR_ACCNT_ID",'0')=NVL("PROMO_ACTUAL"."ACCT_SIEBEL_ROWID",'0') AND
NVL("ACCT_PROMO_HDR"."X_INDIRECT_ID",'0')=NVL("PROMO_ACTUAL"."INDIRECT_ACCT_SIEBEL_ROWID",'0'
14 - access("ACCT_PROMO_HDR"."ROW_ID"="PROMO_ACTUAL"."ACCT_PROMO_ID")
15 - access("ACCT_PROMO_HDR"."ROW_ID"="ACCT_PROMO_HDRX"."PAR_ROW_ID")
16 - access("ACCT_PROMO_HDR"."BU_ID"="PROMO_HDR_ORG"."ROW_ID")
17 - filter("ACCT_TITLE_FORMAT"."SUB_TYPE"='PLAN_ACCT_PROMOTION_CATEGORY')
18 - access("ACCT_PROMO_HDR"."ROW_ID"="ACCT_TITLE_FORMAT"."PAR_SRC_ID")
19 - filter("ACCT_PROMO_SKU"."PROD_ID" IS NOT NULL AND
"ACCT_PROMO_SKU"."SUB_TYPE"='PLAN_ACCOUNT_PROMOTION_PRODUCT')
20 - access("ACCT_TITLE_FORMAT"."ROW_ID"="ACCT_PROMO_SKU"."PAR_SRC_ID")
22 - access("ACCT_PROMO_SKU"."BU_ID"="SKU_ORG"."ROW_ID")
23 - access("ACCT_PROMO_SKU"."ROW_ID"="ACCT_PROMO_SKUX"."PAR_ROW_ID"(+))
24 - access("ACCT_PROMO_SKU"."PROD_ID"="PROD"."ROW_ID")
25 - filter("PROD"."X_PROD_MATERIAL_NUM" IS NOT NULL AND
"PROD"."X_PROD_MATERIAL_NUM"="PROMO_ACTUAL"."MATERIAL_NUMBER" AND
"PROD"."X_PROD_SALES_ORG"="PROMO_ACTUAL"."SALES_ORG")
55 rows selected.
thanks

Hi,
the plan you posted has the cost of 2300, i.e. 2300 single-block reads or equivalent number f multi-block reads. Even if none of the blocks is found in cache, 2300 reas shouldn't take more than a couple of minutes, beacause for most of the hard drives available today a disk read is typically within 5-10 ms.
This means that if there is a problem, we will never find out about it by looking in the plan. And it's quite likely that there is, in fact, a problem, because the plan contains a bunch of nested joins, and the cost of each nested join is directly proportional to the cardinality of the previous nested loop. I.e. it suffices to make one bad mistake in estimating the number of rows coming fom one of the nested rows to screw up the entire plan and get all remaining estimates (including the total cost of the query) completely wrong.
In order for us to be able to tell more, we need to see the plan with rowsource statistics, and please don't forget to use tags to preserve formatting (use the preview tab to make sure the posted plan is actually readable).
Best regards,
Nikolay

Performence tuning

Similar Messages

Maybe you are looking for