Help required for improving performance of the Query

Hello SAP Techies,
I have MRP Query which shows Inventory projection by Calendar Year/Month wise.
There are 2 variables Plant and Material in free charateristics where it has been restricted by replacement of Query result .
Another query is Control M Query which is based on multiprovider. Multiprovider is created on 5 cubes.
The Query is taking 20 -15 Mins to get the result.
Due to replacement path by query result for the 2 variables first the control M Query is excuted. Business wanted to see all those materials in MRP query which are allocated to base plant hence they designed the query to use replacement Path by Query result. So it will get all the materials and plants from the control M query and will find the Invetory projection for the same selection in MRP query.
Is there any way I can improve the performance of the Query.
Query performance has been discussed innumerable times in the forums and there is a lot of information on the blogs and the WIKI - please search the forums before posting and if the existing posts do no answer your question satisfactorily then please raise a new post - else almost all the answers you get will be rehashed versions of previous posts ( and in most cases without attribution to the original author )
Edited by: Arun Varadarajan on Apr 19, 2011 9:23 PM

Hi ,
Please see if you can make these changes currently to the report . It will help in improving the performance of the query
1. Select the right read mode.
    Reading data during navigation minimizes the impact on
     the application server resources because only data that
    the user requires will be retrieved.
2. Leverage filters as much as possible. Using filters contributes to
   reducing the number of database reads and the size of the result set,
    hereby significantly improving query runtimes.
   Filters are especially valuable when associated with u201Cbig
    dimensionsu201D where there is a large number of characteristics such as
    customers and document numbers.
3. Reduce RKFs in the query to as few as possible. Also, define
calculated & RKFs on the Infoprovider level instead of locally within the query.
Regards
Garima

Similar Messages

I have a MAC Pro from 2011 currently running MAC OS 10.9.5. This weekend I cloned the MAC HD drive to a new SSD drive for improved performance. The clone was completed successfully with no errors. After the clone completed I successfull restarted my sy

I have a MAC Pro from 2011 currently running MAC OS 10.9.5. This weekend I cloned the MAC HD drive to a new SSD drive for improved performance. The clone was completed successfully with no errors. After the clone completed I successfully restarted my system using the SSD as the boot device. I then successfully tested all of my products, including Photoshop CS6 and all of its plug-ins. I successfully tested the key features that I frequently use. Today while attempting to launch Photoshop CS6 a message is being displayed indicating that a scratch disk cannot be found. All drives are available on the system via the Finder and Disk Utility. I can access all drives including the old MAC HD which is no longer the boot device. I've even attempted to launch Photoshop from the old device yet the same error persist. Is there a way to review/edit/change Photoshop preferences if Photoshop doesn't launch? I've even restarted my system several times to see if that would resolve the issues. Does anyone have any recommendations for this issue? Have you previously address this issue?
Thank you Gregg Williams

Boilerplate text:
Reset Preferences
http://forums.adobe.com/thread/375776
1) Close the program and press Ctrl+Alt+Shift/Cmd+Option+Shift during startup (not reversible)
or
2) Move the Folder. See:
http://www.bugge.com/Family-and-friends/Illy/illy.html
--OB

What Indexes should be created for improve performance of the sql query

Hello Admins
One of my user is facing slow performance issue while running the below query. Can someone, please guide me for the same. I want to know, what indexes should be created to improve the performance of this query. Also what else can be done to achieve the same.
SQL Query:-
SELECT UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_NUMBER))),
CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_NUMBER,
CGSBI_SHIP_DIST_S_EXTRACT.PO_SHIPMENT_NUMBER,
CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_SHIP_DIST_NUMBER,
CGSBI_SHIP_DIST_S_EXTRACT.DISTRIBUTION_DATE,
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_SHIP_DIST_LINE_ID))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PROJECT_ID))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.ACCOUNT_DISTRIBUTION_CODE))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.ORACLE_ACCOUNT_NUMBER))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.COMPONENT_CODE))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.TRANSACTION_CURRENCY_CODE))),
CGSBI_SHIP_DIST_S_EXTRACT.ORDER_QUANTITY, UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.ORDER_UOM))),
CGSBI_SHIP_DIST_S_EXTRACT.UNIT_PRICE_TRX_CURRENCY,
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.EXPENSE_TYPE_INDICATOR))),
CGSBI_SHIP_DIST_S_EXTRACT.SOR_ID,
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_ITEM_CODE))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_ITEM_DESC))),
CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_ITEM_LEAD_TIME,
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.UNSPSC_CODE))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.BUYER_ID))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.REQUESTOR_ID))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.APPROVER_ID))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.SUPPLIER_SITE_ID))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.SUPPLIER_GSL_NUMBER))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.SHIP_TO_LOCATION_CODE))),
UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.TASK_ID))),
(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_RELEASE_ID)))
FROM
CGSBI_SHIP_DIST_S_EXTRACT
WHERE PO_NUMBER IS NOT NULL;
I generated the explain plan for this query and found the following:-
Explain Plan:-
SQL> explain plan for SELECT UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_NUMBER))),
2 CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_NUMBER,
3 CGSBI_SHIP_DIST_S_EXTRACT.PO_SHIPMENT_NUMBER,
4 CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_SHIP_DIST_NUMBER,
5 CGSBI_SHIP_DIST_S_EXTRACT.DISTRIBUTION_DATE,
6 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_SHIP_DIST_LINE_ID))),
7 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PROJECT_ID))),
8 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.ACCOUNT_DISTRIBUTION_CODE))),
9 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.ORACLE_ACCOUNT_NUMBER))),
10 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.COMPONENT_CODE))),
11 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.TRANSACTION_CURRENCY_CODE))),
12 CGSBI_SHIP_DIST_S_EXTRACT.ORDER_QUANTITY, UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.ORDER_UOM))),
13 CGSBI_SHIP_DIST_S_EXTRACT.UNIT_PRICE_TRX_CURRENCY,
14 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.EXPENSE_TYPE_INDICATOR))),
15 CGSBI_SHIP_DIST_S_EXTRACT.SOR_ID,
16 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_ITEM_CODE))),
17 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_ITEM_DESC))),
18 CGSBI_SHIP_DIST_S_EXTRACT.PO_LINE_ITEM_LEAD_TIME,
19 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.UNSPSC_CODE))),
20 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.BUYER_ID))),
21 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.REQUESTOR_ID))),
22 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.APPROVER_ID))),
23 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.SUPPLIER_SITE_ID))),
24 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.SUPPLIER_GSL_NUMBER))),
25 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.SHIP_TO_LOCATION_CODE))),
26 UPPER(LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.TASK_ID))),
27 (LTRIM(RTRIM(CGSBI_SHIP_DIST_S_EXTRACT.PO_RELEASE_ID)))
28 FROM
29 CGSBI_SHIP_DIST_S_EXTRACT
30 WHERE PO_NUMBER IS NOT NULL;
Explained.
SQL>
SQL>
SQL> SELECT * FROM TABLE(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 3891180274
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 77647 | 39M| 2006 (1)| 00:00:25 |
|* 1 | TABLE ACCESS FULL| CGSBI_SHIP_DIST_S_EXTRACT | 77647 | 39M| 2006 (1)| 00:00:25 |
Predicate Information (identified by operation id):
1 - filter("PO_NUMBER" IS NOT NULL)
13 rows selected.
SQL>
SQL>
Kindly suggest on this...
Thanks & Regards
-Naveen Gangil
Oracle DBA

Rafi is correct. Since po_number is the filter column, the only chance you have for using an index to access the table is on that column. However, if there are few (or none) rows with null po_number, you will always have FTS. Does the table have a PK ( which probably consists of at least po_number, line_number )? If that is the case po_number could never be null and in which case you are dumping the whole table and no indexing scheme is going to improve the queri's performance. You might, repeat might, see performance improvement if you cleanse the data in the table ( to eliminate the need for UPPER(LTRIM)RTRIM())) ) before querying it so the the data does not have to be massaged before returning it.

Please help me to increase the performance of the query

Hello
I am not an oracle expert or developer and i have a problem to resolve.
Below is the query and explaiation plan and seeking the help to improve the performance of the query.
Our Analysis,
The query runs good,takes less one minute and fetches the results but during peak time it takes 8 minutes
Require anyone suggestion's to improve the query.
The query is generated from the Microsft dll so we dont have SQL code and require some help on tuning the tables.
If tuning the query improves then also fine please suggest for that also.
Enviroment: Solaris 8
DB : oracle 9i
(SELECT vw.dispapptobjid, vw.custsiteobjid, vw.emplastname, vw.empfirstname,
vw.scheduledonsite AS starttime, vw.appttype, vw.latestart,
vw.endtime, vw.typetitle, vw.empobjid, vw.latitude, vw.longitude,
vw.workduration AS DURATION, vw.dispatchtype, vw.availability
FROM ora_appt_disp_view vw
WHERE ( ( vw.starttime >=
TO_DATE ('2/12/2007 4:59 PM', 'MM/DD/YYYY HH12:MI AM')
AND vw.starttime <
TO_DATE ('2/21/2007 3:59 PM', 'MM/DD/YYYY HH12:MI AM')
OR vw.endtime >
TO_DATE ('2/12/2007 4:59 PM', 'MM/DD/YYYY HH12:MI AM')
AND vw.endtime <=
TO_DATE ('2/21/2007 3:59 PM', 'MM/DD/YYYY HH12:MI AM')
OR ( vw.starttime <=
TO_DATE ('2/12/2007 4:59 PM', 'MM/DD/YYYY HH12:MI AM')
AND vw.endtime >=
TO_DATE ('2/21/2007 3:59 PM', 'MM/DD/YYYY HH12:MI AM')
UNION
(SELECT 0 AS dispapptobjid, emp.emp_physical_site2site AS custsiteobjid,
emp.last_name AS emplastname, emp.first_name AS empfirstname,
TO_DATE ('1/1/3000', 'MM/DD/YYYY') AS starttime, 'E' AS appttype,
NULL AS latestart, NULL AS endtime, '' AS typetitle,
emp.objid AS empobjid, 0 AS latitude, 0 AS longitude, 0 AS DURATION,
'' AS dispatchtype, 0 AS availability
FROM table_employee emp, table_user usr
WHERE emp.employee2user = usr.objid AND emp.field_eng = 1 AND usr.status = 1)
ORDER BY empobjid, starttime, endtime DESC
Operation     Object Name     Rows     Bytes     Cost     Object Node     In/Out     PStart     PStop
SELECT STATEMENT Optimizer Mode=HINT: ALL_ROWS          23 K          11312
SORT UNIQUE          23 K     3 M     11140
UNION-ALL
VIEW     ORA_APPT_DISP_VIEW     17 K     3 M     10485
UNION-ALL
CONCATENATION
NESTED LOOPS OUTER          68      24 K     437
NESTED LOOPS          68      23 K     369
NESTED LOOPS OUTER          68      25 K     505
NESTED LOOPS OUTER          68      24 K     505
NESTED LOOPS          68      23 K     369
NESTED LOOPS          68      22 K     369
NESTED LOOPS OUTER          68      22 K     369
NESTED LOOPS          19      6 K     312
NESTED LOOPS          19      5 K     312
HASH JOIN          19      5 K     293
NESTED LOOPS          19      5 K     274
NESTED LOOPS          19      4 K     236
NESTED LOOPS          19      4 K     198
NESTED LOOPS OUTER          19      3 K     160
NESTED LOOPS OUTER          19      3 K     160
NESTED LOOPS OUTER          19      4 K     160
NESTED LOOPS OUTER          19      1 K     103
NESTED LOOPS OUTER          19      2 K     103
NESTED LOOPS OUTER          19      2 K     103
TABLE ACCESS BY INDEX ROWID     TABLE_DISPTCHFE     19      1 K     46
INDEX RANGE SCAN     GSA_SCHED_REPAIR     44           3
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22      3
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28      3
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_CASE     1      30      2
INDEX UNIQUE SCAN     CASE_OBJINDEX     1           1
TABLE ACCESS BY INDEX ROWID     TABLE_SITE     1      12      2
INDEX UNIQUE SCAN     SITE_OBJINDEX     1           1
TABLE ACCESS BY INDEX ROWID     TABLE_ADDRESS     1      12      2
INDEX UNIQUE SCAN     ADDRESS_OBJINDEX     1           1
TABLE ACCESS FULL     TABLE_EMPLOYEE     1      34      1
INDEX UNIQUE SCAN     SITE_OBJINDEX     1      6      1
INDEX UNIQUE SCAN     USER_OBJINDEX     1      6
TABLE ACCESS BY INDEX ROWID     TABLE_X_GSA_TIME_STAMPS     4      48      3
INDEX RANGE SCAN     GSAIDX_TS2DISP     1           2
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
TABLE ACCESS BY INDEX ROWID     TABLE_MOD_LEVEL     1      12      1
INDEX UNIQUE SCAN     MOD_LEVEL_OBJINDEX     1
INDEX UNIQUE SCAN     PART_NUM_OBJINDEX     1      6
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
INDEX UNIQUE SCAN     SUBCASE_OBJINDX     1      6      1
NESTED LOOPS OUTER          68      25 K     505
NESTED LOOPS OUTER          68      24 K     505
NESTED LOOPS OUTER          68      24 K     437
NESTED LOOPS          68      23 K     369
NESTED LOOPS          68      23 K     369
NESTED LOOPS          68      22 K     369
NESTED LOOPS OUTER          68      22 K     369
NESTED LOOPS          19      6 K     312
NESTED LOOPS          19      5 K     312
NESTED LOOPS          19      5 K     293
NESTED LOOPS          19      5 K     274
NESTED LOOPS          19      4 K     236
NESTED LOOPS          19      4 K     198
NESTED LOOPS OUTER          19      4 K     160
NESTED LOOPS OUTER          19      3 K     160
NESTED LOOPS OUTER          19      3 K     160
NESTED LOOPS OUTER          19      2 K     103
NESTED LOOPS OUTER          19      2 K     103
NESTED LOOPS OUTER          19      1 K     103
TABLE ACCESS BY INDEX ROWID     TABLE_DISPTCHFE     19      1 K     46
INDEX RANGE SCAN     GSA_SCHED_REPAIR     44           3
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22      3
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28      3
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_CASE     1      30      2
INDEX UNIQUE SCAN     CASE_OBJINDEX     1           1
TABLE ACCESS BY INDEX ROWID     TABLE_SITE     1      12      2
INDEX UNIQUE SCAN     SITE_OBJINDEX     1           1
TABLE ACCESS BY INDEX ROWID     TABLE_ADDRESS     1      12      2
INDEX UNIQUE SCAN     ADDRESS_OBJINDEX     1           1
TABLE ACCESS BY INDEX ROWID     TABLE_EMPLOYEE     1      34      1
INDEX UNIQUE SCAN     EMPLOYEE_OBJINDEX     1
INDEX UNIQUE SCAN     SITE_OBJINDEX     1      6      1
INDEX UNIQUE SCAN     USER_OBJINDEX     1      6
TABLE ACCESS BY INDEX ROWID     TABLE_X_GSA_TIME_STAMPS     4      48      3
INDEX RANGE SCAN     GSAIDX_TS2DISP     1           2
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
INDEX UNIQUE SCAN     SUBCASE_OBJINDX     1      6      1
TABLE ACCESS BY INDEX ROWID     TABLE_MOD_LEVEL     1      12      1
INDEX UNIQUE SCAN     MOD_LEVEL_OBJINDEX     1
INDEX UNIQUE SCAN     PART_NUM_OBJINDEX     1      6
NESTED LOOPS OUTER          68      25 K     505
NESTED LOOPS OUTER          68      24 K     505
NESTED LOOPS OUTER          68      24 K     437
NESTED LOOPS          68      23 K     369
NESTED LOOPS          68      23 K     369
NESTED LOOPS          68      22 K     369
NESTED LOOPS OUTER          68      22 K     369
NESTED LOOPS          19      6 K     312
NESTED LOOPS          19      5 K     312
NESTED LOOPS          19      5 K     293
NESTED LOOPS          19      5 K     274
NESTED LOOPS          19      4 K     236
NESTED LOOPS          19      4 K     198
NESTED LOOPS OUTER          19      4 K     160
NESTED LOOPS OUTER          19      3 K     160
NESTED LOOPS OUTER          19      3 K     160
NESTED LOOPS OUTER          19      2 K     103
NESTED LOOPS OUTER          19      2 K     103
NESTED LOOPS OUTER          19      1 K     103
TABLE ACCESS BY INDEX ROWID     TABLE_DISPTCHFE     19      1 K     46
INDEX RANGE SCAN     GSA_REQ_ETA     44           3
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22      3
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      22
INDEX RANGE SCAN     GSA_COMDFE     1           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28      3
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_COMMIT_LOG     1      28
INDEX RANGE SCAN     IND_CASE_COMMIT2CASE     2           2
TABLE ACCESS BY INDEX ROWID     TABLE_CASE     1      30      2
INDEX UNIQUE SCAN     CASE_OBJINDEX     1           1
TABLE ACCESS BY INDEX ROWID     TABLE_SITE     1      12      2
INDEX UNIQUE SCAN     SITE_OBJINDEX     1           1
TABLE ACCESS BY INDEX ROWID     TABLE_ADDRESS     1      12      2
INDEX UNIQUE SCAN     ADDRESS_OBJINDEX     1           1
TABLE ACCESS BY INDEX ROWID     TABLE_EMPLOYEE     1      34      1
INDEX UNIQUE SCAN     EMPLOYEE_OBJINDEX     1
INDEX UNIQUE SCAN     SITE_OBJINDEX     1      6      1
INDEX UNIQUE SCAN     USER_OBJINDEX     1      6
TABLE ACCESS BY INDEX ROWID     TABLE_X_GSA_TIME_STAMPS     4      48      3
INDEX RANGE SCAN     GSAIDX_TS2DISP     1           2
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
INDEX UNIQUE SCAN     GBST_ELM_OBJINDEX     1      6
INDEX UNIQUE SCAN     SUBCASE_OBJINDX     1      6      1
TABLE ACCESS BY INDEX ROWID     TABLE_MOD_LEVEL     1      12      1
INDEX UNIQUE SCAN     MOD_LEVEL_OBJINDEX     1
INDEX UNIQUE SCAN     PART_NUM_OBJINDEX     1      6
NESTED LOOPS          16 K     2 M     5812
HASH JOIN          16 K     2 M     5812
HASH JOIN          16 K     2 M     5286
TABLE ACCESS FULL     TABLE_EMPLOYEE     13 K     441 K     28
HASH JOIN          16 K     1 M     5243
TABLE ACCESS FULL     TABLE_SCHEDULE     991      11 K     2
HASH JOIN OUTER          16 K     1 M     5240
HASH JOIN OUTER          16 K     1 M     3866
HASH JOIN OUTER          16 K     1 M     450
HASH JOIN          16 K     1 M     44
TABLE ACCESS FULL     TABLE_GBST_ELM     781      14 K     2
TABLE ACCESS FULL     TABLE_APPOINTMENT     16 K     822 K     41
INDEX FAST FULL SCAN     CASE_OBJINDEX     1 M     6 M     201
TABLE ACCESS FULL     TABLE_SITE     967 K     11 M     3157
TABLE ACCESS FULL     TABLE_ADDRESS     961 K     11 M     1081
INDEX FAST FULL SCAN     SITE_OBJINDEX     967 K     5 M     221
INDEX UNIQUE SCAN     USER_OBJINDEX     1      6
HASH JOIN          6 K     272 K     51
TABLE ACCESS FULL     TABLE_USER     6 K     51 K     21
TABLE ACCESS FULL     TABLE_EMPLOYEE     6 K     220 K     28

Hi,
First-off, it appear that you are querying a view. I would redo the auery against the base table.
Next, look at a function-based index for the DATE column. Here are my notes:
http://www.dba-oracle.com/t_function_based_indexes.htm
http://www.dba-oracle.com/oracle_tips_index_scan_fbi_sql.htm
Also, make sure you are analyzed properly with dbms_stats:
http://www.dba-oracle.com/art_builder_dbms_stats.htm
And histograms, if appropriate:
http://www.dba-oracle.com/art_builder_histo.htm
Lasty, look at increasing hash_area_size or pga_aggregate_tagtet, depending on your table sizes:
http://www.dba-oracle.com/art_so_undocumented_pga_parameters.htm
Hope this helps. . . .
Donald K. Burleson
Oracle Press Author

How to improve the performance of the query

Hi,
Help me by giving tips how to improve the performance of the query. Can I post the query?
Suresh

Below is the formatted query and no wonder it is taking lot of time. Will give you a list of issues soon after analyzing more. Till then understand the pitfalls yourself from this formatted query.
SELECT rt.awb_number,
       ar.activity_id as task_id,
       t.assignee_org_unit_id,
       t.task_type_code,
       ar.request_id
FROM activity_task ar,
     request_task rt,
     task t
WHERE ar.activity_id =t.task_id
AND ar.request_id = rt.request_id
AND ar.complete_status != 'act.stat.closed'
AND t.assignee_org_unit_id in (SELECT org_unit_id
                               FROM org_unit
                               WHERE org_unit_id in (SELECT oo.org_unit_id
                                                     FROM org_unit oo
                                                     WHERE oo.org_unit_id='3'
                                                     OR oo.parent_id ='3'
                               OR parent_id in (SELECT oo.org_unit_id
                                                FROM org_unit oo
                                                WHERE oo.org_unit_id='3'
                                                OR oo.parent_id ='3'
                               AND has_queue=1
AND ar.parent_task_id not in (SELECT tt.task_id
                              FROM task tt
                              WHERE tt.assignee_org_unit_id in (SELECT org_unit_id
                                                                FROM org_unit
                                                                WHERE org_unit_id in (SELECT oo.org_unit_id
                                                                                      FROM org_unit oo
                                                                                      WHERE oo.org_unit_id='3'
                                                                                      OR oo.parent_id ='3'
                                                                 OR parent_id in (SELECT oo.org_unit_id
                                                                                  FROM org_unit oo
                                                                                  WHERE oo.org_unit_id='3'
                                                                                  OR oo.parent_id ='3'
                                                                 AND has_queue=1
AND rt.awb_number is not null
ORDER BY rt.awb_numberCheers
Sarma.

How to improve performance of the attached query

Hi,
How to improve performance of the below query, Please help. also attached explain plan -
SELECT Camp.Id,
rCam.AccountKey,
Camp.Id,
CamBilling.Cpm,
CamBilling.Cpc,
CamBilling.FlatRate,
Camp.CampaignKey,
Camp.AccountKey,
CamBilling.billoncontractedamount,
(SUM(rCam.Impressions) * 0.001 + SUM(rCam.Clickthrus)) AS GR,
rCam.AccountKey as AccountKey
FROM Campaign Camp, rCamSit rCam, CamBilling, Site xSite
WHERE Camp.AccountKey = rCam.AccountKey
AND Camp.AvCampaignKey = rCam.AvCampaignKey
AND Camp.AccountKey = CamBilling.AccountKey
AND Camp.CampaignKey = CamBilling.CampaignKey
AND rCam.AccountKey = xSite.AccountKey
AND rCam.AvSiteKey = xSite.AvSiteKey
AND rCam.RmWhen BETWEEN to_date('01-01-2009', 'DD-MM-YYYY') and
to_date('01-01-2011', 'DD-MM-YYYY')
GROUP By rCam.AccountKey,
Camp.Id,
CamBilling.Cpm,
CamBilling.Cpc,
CamBilling.FlatRate,
Camp.CampaignKey,
Camp.AccountKey,
CamBilling.billoncontractedamount
Explain Plan :-
Description Object_owner Object_name Cost Cardinality Bytes
SELECT STATEMENT, GOAL = ALL_ROWS 14 1 13
SORT AGGREGATE 1 13
VIEW GEMINI_REPORTING 14 1 13
HASH GROUP BY 14 1 103
NESTED LOOPS 13 1 103
HASH JOIN 12 1 85
TABLE ACCESS BY INDEX ROWID GEMINI_REPORTING RCAMSIT 2 4 100
NESTED LOOPS 9 5 325
HASH JOIN 7 1 40
SORT UNIQUE 2 1 18
TABLE ACCESS BY INDEX ROWID GEMINI_PRIMARY SITE 2 1 18
INDEX RANGE SCAN GEMINI_PRIMARY SITE_I0 1 1
TABLE ACCESS FULL GEMINI_PRIMARY SITE 3 27 594
INDEX RANGE SCAN GEMINI_REPORTING RCAMSIT_I 1 1 5
TABLE ACCESS FULL GEMINI_PRIMARY CAMPAIGN 3 127 2540
TABLE ACCESS BY INDEX ROWID GEMINI_PRIMARY CAMBILLING 1 1 18
INDEX UNIQUE SCAN GEMINI_PRIMARY CAMBILLING_U1 0 1

duplicate thread..
How to improve performance of attached query

Performance of the query is poor

Hi All,
This is Prasad. I have a problem with the query it is taking more time to retrieve the data from the Cube. In the query they are using a Variable of type Customer Exit. The Cube is not at compressed. I think the issue with the F fact table is due to the high number of table partitions (requests) that it has to select from. If I compress the cube, the performance of the query is increased r not? Is there any alternative for improving the performance of the query. Somebody suggested Result set query, iam not aware of this technique if u know let me know.
Thanks in advance

Hi Prasad,
Query performance will depend on many factors like
1. Aggregates
2. Compression of requests
3. Query read mode setting
4. Cache memory setting
5. By Creating BI Accelerator Indexes on Infocubes
6. Indexes
Proposing aggregates to improve query performance:
First try to execute the query in RSRT on which u required to build aggregates. Check how much time it is taking to execute.....and whether it is required to build aggregate on this querry?? To get this information, Goto SE11> Give tabl name RSDDSTAT_DM in BI7.0 or RSDDSTAT in BW3.x.> Disply -> Contnts-> Give from date and to date values as today, user name as Ur user name, and give the query name
--> execute.
Now u'll get a list with fields like Object anme(Report anme), Time read, Infoprovider name(Multiprovider), Partprovider name (Cube), Aggregate name... etc. If the time read is less than 100,000,000 (100 sec) is acceptable. If the time read is more than 100 sec then it is recommended to create Aggregates for that query to increase performance. Keep in mind this time read.
Again goto RSRT> Give query name> Execute+Debug-->
A popup will come in that select the check box display aggregates found--> continue. If any aggregates or exist for that
query it will display first if u press on continue button, it will display from which cube which fields are coming it will display...try to copy this list of objects on which aggregate can be created into one text file...
then select that particular cube in RSA1>context>Maintain Aggregates-> Create by own> click on create aggregate button on top left side> Give discription of the aggregate>continue> take first object from list and fclick on find button in aggregates creation screen> give the object name and search... drag and drop that object into aggregate name right side (Drag and drop all the fields like this into aggregate).---->
Activate the aggregate--> it will take some time once the activation finishes --> make sure that aggregate is in switch on mode.
Try to xecute the query from RSRT again and find out the time read and compare this with first time read. If it is less tahn first time read then u can propose this aggregate to incraese the performance of the query.
I hope this will help u... go through the below links to know about aggregates more clear.
http://help.sap.com/saphelp_nw04s/helpdata/en/10/244538780fc80de10000009b38f842/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
Follow this thread for creation of BIA Indexes:
Re: BIA Creation
Hopr this helps...
Regards,
Ramki.

How to improve performance of attached query

Hi,
How to improve performance of the below query, Please help. also attached explain plan -
SELECT Camp.Id,
rCam.AccountKey,
Camp.Id,
CamBilling.Cpm,
CamBilling.Cpc,
CamBilling.FlatRate,
Camp.CampaignKey,
Camp.AccountKey,
CamBilling.billoncontractedamount,
(SUM(rCam.Impressions) * 0.001 + SUM(rCam.Clickthrus)) AS GR,
rCam.AccountKey as AccountKey
FROM Campaign Camp, rCamSit rCam, CamBilling, Site xSite
WHERE Camp.AccountKey = rCam.AccountKey
AND Camp.AvCampaignKey = rCam.AvCampaignKey
AND Camp.AccountKey = CamBilling.AccountKey
AND Camp.CampaignKey = CamBilling.CampaignKey
AND rCam.AccountKey = xSite.AccountKey
AND rCam.AvSiteKey = xSite.AvSiteKey
AND rCam.RmWhen BETWEEN to_date('01-01-2009', 'DD-MM-YYYY') and
to_date('01-01-2011', 'DD-MM-YYYY')
GROUP By rCam.AccountKey,
Camp.Id,
CamBilling.Cpm,
CamBilling.Cpc,
CamBilling.FlatRate,
Camp.CampaignKey,
Camp.AccountKey,
CamBilling.billoncontractedamount
Explain Plan :-
Description Object_owner Object_name Cost Cardinality Bytes
SELECT STATEMENT, GOAL = ALL_ROWS 14 1 13
SORT AGGREGATE 1 13
VIEW GEMINI_REPORTING 14 1 13
HASH GROUP BY 14 1 103
NESTED LOOPS 13 1 103
HASH JOIN 12 1 85
TABLE ACCESS BY INDEX ROWID GEMINI_REPORTING RCAMSIT 2 4 100
NESTED LOOPS 9 5 325
HASH JOIN 7 1 40
SORT UNIQUE 2 1 18
TABLE ACCESS BY INDEX ROWID GEMINI_PRIMARY SITE 2 1 18
INDEX RANGE SCAN GEMINI_PRIMARY SITE_I0 1 1
TABLE ACCESS FULL GEMINI_PRIMARY SITE 3 27 594
INDEX RANGE SCAN GEMINI_REPORTING RCAMSIT_I 1 1 5
TABLE ACCESS FULL GEMINI_PRIMARY CAMPAIGN 3 127 2540
TABLE ACCESS BY INDEX ROWID GEMINI_PRIMARY CAMBILLING 1 1 18
INDEX UNIQUE SCAN GEMINI_PRIMARY CAMBILLING_U1 0 1

duplicate thread..
How to improve performance of attached query

Performance of the query incresed to 1 hour 15 mins....

the view is working, but the performance of the query is horrible.
Our pull time has increased from 25 minutes to 1 hour and 15 minutes.

Can you please advice me the same solution pplies for prodction box also...
Production database details::::
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The query in production database::::
SELECT                                                      /*+ALL_ROWS*/
2             a .lcl_id AS Ora_Order,                            --Order_Number,
3                a.closed_date AS Closed_Date,
4                a.modified_date AS Modified_Date,
5                a.received_date AS Received_Date,
6                a.status AS Status,
7                b.seq AS Ora_Line,                                 --Line_Number
8                b.sub_seq AS Ora_sub_line,
9                c.seq AS Unit_Number,
10                SUBSTR (c.olig_group_id, INSTR (c.olig_group_id,
11                                                '.',
12                                                -1,
13                                                1)
14                                         + 1)
15                   AS shipment_number,
16                c.tag AS Tag,
17                c.special_tag AS Customer_Tag,
18                h.fmly_serial_id AS Serial_Number,
19                d.allocation_timestamp AS Alloc_Date,
20                MIN (f.closed_timestamp) AS First_Event_On_Floor,
21                -- CALIBRATION
22                MAX (DECODE (f.uutt_mstr_id, 1, f.closed_timestamp, NULL))
23                   AS Calibration_Date,
24                -- PACKAGING
25                MAX (DECODE (f.uutt_mstr_id, 50, f.closed_timestamp, NULL))
26                   AS Package_Date,
27                -- CAPS KITTING
28                MAX(DECODE (
29                       f.uutt_mstr_id,
30                       100,
31                       DECODE (f.stnd_seq, 2024961, f.closed_timestamp, NULL)
32                    ))
33                   AS Caps_Kitting_Date,
34                lastprodsn.pm_mstr_id AS Tagged_Model,
35                b.CEP AS ETO_Number,
36                j.VALUE AS Product_Options,
37                a.PO AS PO_Number,
38                --       lastprodsn.uut_glbl_id                                     as LastProdSN_UUT_Glbl_ID -- replaced on 3/31/2011 BJACK
39                MAX (DECODE (f.uutt_mstr_id, 2, f.glbl_id, NULL))
40                   AS LastProdSN_UUT_Glbl_ID
41          FROM   ssc.ordr_hdrs a,                 -- glbl_id = sales order number
42                ssc.ordr_lns b,          -- oh_glbl_id = SO #, SEQ = line number
43                ssc.ordr_ln_itms c, -- ol_oh_glbl_id = SO #, ol_seq = line #, seq = unit #, olig_group_id = shipment #
44                ssc.omar_track_maps d, -- for tracking id, holds the allocation timestamp
45                (SELECT   x.uut_glbl_id,
46                          x.oli_ol_oh_glbl_id,
47                          x.oli_ol_seq,
48                          x.oli_ol_sub_seq,
49                          x.oli_seq,
50                          x.sm_glbl_id,
51                          x.pm_mstr_id
52                   FROM      ssc.serial_prod_uut_maps x
53                          JOIN
54                             ( SELECT   oli_ol_oh_glbl_id,
55                                         oli_ol_seq,
56                                         oli_ol_sub_seq,
57                                         oli_seq,
58                                         MAX (uut_glbl_id) Max_oli_uut_glbl_id
59                                  FROM   ssc.serial_prod_uut_maps
60                              GROUP BY   oli_ol_oh_glbl_id,
61                                         oli_ol_seq,
62                                         oli_ol_sub_seq,
63                                         oli_seq) MAXOLIUUT
64                          ON MAXOLIUUT.Max_oli_uut_glbl_id = x.uut_glbl_id
65                             AND MAXOLIUUT.oli_ol_oh_glbl_id =
66                                   x.oli_ol_oh_glbl_id
67                             AND MAXOLIUUT.oli_ol_seq = x.oli_ol_seq
68                             AND MAXOLIUUT.oli_ol_sub_seq = x.oli_ol_sub_seq
69                             AND MAXOLIUUT.oli_seq = x.oli_seq) lastprodsn, -- find latest uut for OLI (assumes UUT ids are in sequence so max is latest; needed to deal with SN or product chgs for OLI)
70                ssc.serial_prod_uut_maps e, -- go get all UUT IDs for the OLI's latest product number and serial number
71                ssc.uuts f, -- go get UUT details for all of the good OLI-product-SNs
72                ssc.uut_params g, -- go get the package void parameter (so can exclude them)
73                ssc.serial_mstrs h,        -- go get serial number for the SN id
74                ssc.ORDR_LN_PARAMS j        -- go get options for product number
75        WHERE                   -- join a to b sales orders to sales order lines
76             a      .glbl_id = b.oh_glbl_id
77                AND -- join b to c to get sales order line items (units for a line item)
78                   b.oh_glbl_id = c.ol_oh_glbl_id
79                AND b.seq = c.ol_seq
80                AND b.sub_seq = c.ol_sub_seq
81                AND -- join c to d to get allocation date if available (outer join)
82                   c.otm_track_id = d.track_id(+)
83                AND                                      -- join c to lastprodsn
84                   c.ol_oh_glbl_id = lastprodsn.oli_ol_oh_glbl_id(+)
85                AND c.ol_seq = lastprodsn.oli_ol_seq(+)
86                AND c.ol_sub_seq = lastprodsn.oli_ol_sub_seq(+)
87                AND c.seq = lastprodsn.oli_seq(+)
88                AND -- join lastprodsn to k to get serial number for last product/serial number processed
89                   lastprodsn.sm_glbl_id = h.glbl_id(+)
90                AND -- join lastprodsn to e to go get all the UUT ids for this OLI + Product # + Serial #
91                   lastprodsn.oli_ol_oh_glbl_id = e.oli_ol_oh_glbl_id(+)
92                AND lastprodsn.oli_ol_seq = e.oli_ol_seq(+)
93                AND lastprodsn.oli_ol_sub_seq = e.oli_ol_sub_seq(+)
94                AND lastprodsn.oli_seq = e.oli_seq(+)
95                AND lastprodsn.pm_mstr_id = e.pm_mstr_id(+)
96                AND lastprodsn.sm_glbl_id = e.sm_glbl_id(+)
97                AND --join e to f to get UUT details for the good OLI-Product-SN combos
98                   e.uut_glbl_id = f.glbl_id(+)
99                AND                   -- join f to g to get the voided parameter
100                   f.glbl_id = g.uut_glbl_id(+)
101                AND -- join c to j to get the option codes for the product number (parameter 2070)
102                   c.ol_oh_glbl_id = j.ol_oh_glbl_id(+)
103                AND c.ol_seq = j.ol_seq(+)
104                AND c.ol_sub_seq = j.ol_sub_seq(+)
105                AND c.seq = j.seq(+)
106                AND j.par_mstr_id(+) = 2070
107                AND j.VALUE(+) IS NOT NULL
108                AND                                   -- un-voided packages only
109                   g.par_mstr_id(+) = 1003
110                AND (g.uut_glbl_id IS NULL OR g.VALUE = 'N')
111   /*             AND                      -- 1003 = package void status parameter
112                   g.VALUE(+) = 'N' */
113     GROUP BY   a.lcl_id,
114                b.seq,
115                b.sub_seq,
116                c.seq,
117                c.olig_group_id,
118                a.closed_date,
119                a.modified_date,
120                a.received_date,
121                a.status,
122                c.tag,
123                c.special_tag,
124                h.fmly_serial_id,
125                d.allocation_timestamp,
126                lastprodsn.pm_mstr_id,
127                b.CEP,
128                j.VALUE,
129                a.PO
130             /
SQL>=================
explain plan:::
| Id | Operation                        | Name                 | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                 |                      | 82182 |    29M|       |   160K (2)| 00:32:09 |
|   1 | HASH GROUP BY                   |                      | 82182 |    29M|    30M|   160K (2)| 00:32:09 |
|   2 |   NESTED LOOPS OUTER             |                      | 82182 |    29M|       |   154K (2)| 00:30:51 |
|   3 |    NESTED LOOPS OUTER            |                      | 82182 |    26M|       |   145K (2)| 00:29:12 |
|* 4 |     HASH JOIN                    |                      | 82182 |    23M|    10M|   137K (2)| 00:27:33 |
|   5 |      TABLE ACCESS FULL           | ORDR_HDRS            |   159K| 8716K|       |   397   (4)| 00:00:05 |
|* 6 |      HASH JOIN                   |                      | 89664 |    20M|    15M|   135K (2)| 00:27:09 |
|   7 |       TABLE ACCESS FULL          | ORDR_LNS             |   506K| 9882K|       |   688   (5)| 00:00:09 |
|* 8 |       HASH JOIN RIGHT OUTER      |                      | 89424 |    19M|    17M|   133K (2)| 00:26:39 |
|   9 |        TABLE ACCESS FULL         | OMAR_TRACK_MAPS      |   567K|    10M|       |   725   (5)| 00:00:09 |
|* 10 |        FILTER                    |                      |       |       |       |            |          |
|* 11 |         HASH JOIN RIGHT OUTER    |                      | 89424 |    17M| 4440K|   130K (2)| 00:26:09 |
|* 12 |          TABLE ACCESS FULL       | UUT_PARAMS           |   133K| 2869K|       | 3608   (7)| 00:00:44 |
|* 13 |          HASH JOIN RIGHT OUTER   |                      | 3244K|   563M|    85M| 96934   (3)| 00:19:24 |
| 14 |           TABLE ACCESS FULL      | UUTS                 | 2247K|    60M|       | 4893   (4)| 00:00:59 |
|* 15 |           HASH JOIN RIGHT OUTER |                      | 3244K|   476M|   239M| 62078   (3)| 00:12:25 |
| 16 |            TABLE ACCESS FULL     | SERIAL_PROD_UUT_MAPS | 3639K|   197M|       | 6481   (4)| 00:01:18 |
|* 17 |            HASH JOIN RIGHT OUTER |                      | 3244K|   300M|       | 26716   (4)| 00:05:21 |
| 18 |             VIEW                 |                      |     1 |    48 |       | 18639   (4)| 00:03:44 |
|* 19 |              FILTER              |                      |       |       |       |            |          |
| 20 |               HASH GROUP BY      |                      |     1 |    85 |       | 18639   (4)| 00:03:44 |
|* 21 |                HASH JOIN         |                      |   308K|    25M|    40M| 18587   (4)| 00:03:44 |
|* 22 |                 TABLE ACCESS FULL| SERIAL_PROD_UUT_MAPS | 1060K|    28M|       | 6520   (5)| 00:01:19 |
|* 23 |                 TABLE ACCESS FULL| SERIAL_PROD_UUT_MAPS | 1060K|    57M|       | 6520   (5)| 00:01:19 |
| 24 |             TABLE ACCESS FULL    | ORDR_LN_ITMS         | 3244K|   151M|       | 8011   (4)| 00:01:37 |
|* 25 |     TABLE ACCESS BY INDEX ROWID | ORDR_LN_PARAMS       |     1 |    35 |       |     1   (0)| 00:00:01 |
|* 26 |      INDEX RANGE SCAN            | OLP_OL_FK_I          |     1 |       |       |     1   (0)| 00:00:01 |
| 27 |    TABLE ACCESS BY INDEX ROWID   | SERIAL_MSTRS         |     1 |    37 |       |     1   (0)| 00:00:01 |
|* 28 |     INDEX RANGE SCAN             | SM_PK                |     1 |       |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   4 - access("A"."GLBL_ID"="B"."OH_GLBL_ID")
   6 - access("B"."OH_GLBL_ID"="C"."OL_OH_GLBL_ID" AND "B"."SEQ"="C"."OL_SEQ" AND
              "B"."SUB_SEQ"="C"."OL_SUB_SEQ")
   8 - access("C"."OTM_TRACK_ID"="D"."TRACK_ID"(+))
10 - filter("G"."UUT_GLBL_ID" IS NULL OR "G"."VALUE"='N')
11 - access("F"."GLBL_ID"="G"."UUT_GLBL_ID"(+))
12 - filter("G"."PAR_MSTR_ID"(+)=1003)
13 - access("E"."UUT_GLBL_ID"="F"."GLBL_ID"(+))
15 - access("LASTPRODSN"."OLI_OL_OH_GLBL_ID"="E"."OLI_OL_OH_GLBL_ID"(+) AND
              "LASTPRODSN"."OLI_OL_SEQ"="E"."OLI_OL_SEQ"(+) AND "LASTPRODSN"."OLI_OL_SUB_SEQ"="E"."OLI_OL_SUB_SEQ"(+)
              AND "LASTPRODSN"."OLI_SEQ"="E"."OLI_SEQ"(+) AND "LASTPRODSN"."PM_MSTR_ID"="E"."PM_MSTR_ID"(+) AND
              "LASTPRODSN"."SM_GLBL_ID"="E"."SM_GLBL_ID"(+))
17 - access("C"."OL_OH_GLBL_ID"="LASTPRODSN"."OLI_OL_OH_GLBL_ID"(+) AND
              "C"."OL_SEQ"="LASTPRODSN"."OLI_OL_SEQ"(+) AND "C"."OL_SUB_SEQ"="LASTPRODSN"."OLI_OL_SUB_SEQ"(+) AND
              "C"."SEQ"="LASTPRODSN"."OLI_SEQ"(+))
19 - filter("X"."UUT_GLBL_ID"=MAX("UUT_GLBL_ID"))
21 - access("OLI_OL_OH_GLBL_ID"="X"."OLI_OL_OH_GLBL_ID" AND "OLI_OL_SEQ"="X"."OLI_OL_SEQ" AND
              "OLI_OL_SUB_SEQ"="X"."OLI_OL_SUB_SEQ" AND "OLI_SEQ"="X"."OLI_SEQ")
22 - filter("OLI_OL_OH_GLBL_ID" IS NOT NULL AND "OLI_OL_SEQ" IS NOT NULL AND "OLI_SEQ" IS NOT NULL AND
              "OLI_OL_SUB_SEQ" IS NOT NULL)
23 - filter("X"."OLI_OL_OH_GLBL_ID" IS NOT NULL AND "X"."OLI_OL_SEQ" IS NOT NULL AND "X"."OLI_SEQ" IS
              NOT NULL AND "X"."OLI_OL_SUB_SEQ" IS NOT NULL)
25 - filter("J"."PAR_MSTR_ID"(+)=2070 AND "J"."VALUE"(+) IS NOT NULL AND "C"."SEQ"="J"."SEQ"(+))
26 - access("C"."OL_OH_GLBL_ID"="J"."OL_OH_GLBL_ID"(+) AND "C"."OL_SEQ"="J"."OL_SEQ"(+) AND
              "C"."OL_SUB_SEQ"="J"."OL_SUB_SEQ"(+))
28 - access("LASTPRODSN"."SM_GLBL_ID"="H"."GLBL_ID"(+))
SQL>mod. action : adding tags , is that so difficult ?

How to display header title for 0MATERIAL texts in the query output?

Dear Bwers,
I have a requirement where i need to display headers titles for 0MATERIAL texts in the query output. (example "Material description"). Any ideas on how to do this?
Thanks
Raj

Kamal,
Its is as below:
<b>Vendor</b>    <b>Vendor Name</b>
1001 ---            Bright Industries
1002 ---            Glow Industries
I want to display the header title "Vendor Name" as the title in the column instead of displaying the text without any header title.
Thanks
Raj
Message was edited by:
        Raj Singh
Message was edited by:
        Raj Singh

Help Required :Unable to auto generate the layout in BIP

Hi All,
This is Ronny, I am really having a tough time using OBIEEE. I am trying to create a simple report in which when i try to auto genreate a rtf template then it says *" failed to load the layout"* and gives me connection timed out error ( unable to autoload). I edited it and tried a simple select statement but still no luck.
Has somebody else faced the same problem, I request you to please give me your inputs on the same.
Thanks in advance
Ronny.

Hi Sree,
Thanks a alot for replying, i use the query builder to build the initial query but even after that it fails to auto load the template. I tried building the simplest of queries through the query builder but got the same error even when the query runs fine in TOAD . However, upon trying again i got some luck and it generated the template. But still for me, its a hook and crook means i am not sure that that it would generate the template again for me or not.
Thanks alot for replying ..however, i am working on this and will get back to you once i get the error again.
Thanks
Ronny

What is setting required for Price Contol do the optional entery in master.

Hi SAP EXPERT,
What is setting required for Price Contol do the optional entery in Material master ?
Regards
Mahendra
Edited by: MAHENDRA NAVALE on Aug 27, 2011 2:23 PM

HI
In general in the material master record you can, hide display or optional for a field, but there are certain feilds should be mandatory for material creation,like base unit of measure,material description,and price contro,l valuation price,valuation class,without this you cannot create a purchase order.
If you dont want to the price control means go for mateial type non valuated material NLAG. because the price control is mainly linked with the material valuation. based on the the price control the price difference will post either sock account or price difference account.
Goto>MM>LOGISTICS GENERAL>MATERIAL MASTER>FEILD SELECTION >ASSIGN FEILD SELECTION TO FEILD SELECTIN GROUPS(OMSR) >CHECK YOUR FEILD REFERENCE FOR PRICE CONTROL (MBEW-VPRSV) FEILD REFERNCE GROUP IS 32* > AND GOTO MAINTAIN FEILD REFERENCE FOR DATA SCREENS (OMS9) >ENTER YOUR FEILD SELECTIN GROUP 32 (PRICE CONTROL )AND CHOOSE MM01 MAKE IT FROM REQUIRED TO OPTIONAL.
Thanks
Edited by: Nijamudeen**MM on Aug 29, 2011 10:19 AM

Curerency conversion for a Formula in the query designer

Hi
I have a ' Financial Loss Formula' in the report. I want to convert this 'Financial Loss' into USD Currency at query designer level.
Source Currency = SAR
Target Currency = USD
So how can i do the curerency conversion for a Formula in the query designer.
pls let me kow
kumar

Hi,
If you define your query conversion in BW then it is easy to do currency conversion through Bex.What you need to do is use calculated key figure instead formula and do a right click select properties there at the currency translation area you ca select defined currency conversion in BW and your target currency.
/people/rasim.manavoglu/blog/2007/04/30/currency-currency-currency
Regards.

Help required for the query

sir
below query runs fine
but the probblem is...i am not able to display the figures in the format '999999.99'
Also please guide me as to make the query short... can i use cursors here?
i am using 10g
select
LBRCODE branch,
trim(substr(PRDACCTID,1,8)) product,
sum(case when totsanclimit between 0 and 200000 then
     (Case when hrk in (13,14) THEN
          (CASE WHEN bal4 !=0 THEN 1 else 0 END )
          ELSE
          (CASE WHEN BAL1-(BAL4-BAL5)!=0 THEN 1 ELSE 0 END)
               END )
else 0 end )as "bktCount-1",
SUM( CASE WHEN TOTSANCLIMIT between 0 and 200000 then
     (Case when hrk in (13,14) THEN
          to_number(to_char(bal4,'99999999999.99'))
     else
          to_char(BAL1,'99999999999.99')-(to_char(BAL4,'99999999999.99')-to_char(BAL5,'99999999999.99'))
     END )
ELSE
0 end) AS"Bkt_1",
sum(case when totsanclimit between 200001 and 1000000 then
(Case when hrk in (13,14) THEN
          (CASE WHEN bal4 !=0 THEN 1 else 0 END )
          ELSE
          (CASE WHEN BAL1-(BAL4-BAL5)!=0 THEN 1 ELSE 0 END)
               END )
else 0 end )as "bktCount-2",
SUM(
CASE WHEN TOTSANCLIMIT between 200001 and 1000000
then
     (Case when hrk in (13,14) THEN
          to_number(to_char(bal4,'99999999999.99'))
     else
          to_char(BAL1,'99999999999.99')-(to_char(BAL4,'99999999999.99')-to_char(BAL5,'99999999999.99'))
     END )
ELSE 0 end) AS"Bkt_2",
sum(case when totsanclimit between 1000001 and 5000000 then
(Case when hrk in (13,14) THEN
          (CASE WHEN bal4 !=0 THEN 1 else 0 END )
          ELSE
          (CASE WHEN BAL1-(BAL4-BAL5)!=0 THEN 1 ELSE 0 END)
               END )
else 0 end )as "bktCount-3",
SUM(
CASE WHEN TOTSANCLIMIT between 1000001 and 5000000
then
     (Case when hrk in (13,14) THEN
          to_number(to_char(bal4,'99999999999.99'))
     else
          to_char(BAL1,'99999999999.99')-(to_char(BAL4,'99999999999.99')-to_char(BAL5,'99999999999.99'))
     END )
ELSE 0 end) AS"Bkt_3",
sum(case when totsanclimit between 5000001 and 10000000 then
(Case when hrk in (13,14) THEN
          (CASE WHEN bal4 !=0 THEN 1 else 0 END )
          ELSE
          (CASE WHEN BAL1-(BAL4-BAL5)!=0 THEN 1 ELSE 0 END)
               END )
else 0 end )as "bktCount-4",
SUM(
CASE WHEN TOTSANCLIMIT between 5000001 and 10000000
then
      (Case when hrk in (13,14) THEN
          to_number(to_char(bal4,'99999999999.99'))
     else
          to_char(BAL1,'99999999999.99')-(to_char(BAL4,'99999999999.99')-to_char(BAL5,'99999999999.99'))
     END )
ELSE 0 end) AS"Bkt_4",
sum(case when totsanclimit BETWEEN 10000001 AND 200000000 then
(Case when hrk in (13,14) THEN
          (CASE WHEN bal4 !=0 THEN 1 else 0 END )
          ELSE
          (CASE WHEN BAL1-(BAL4-BAL5)!=0 THEN 1 ELSE 0 END)
               END )
else 0 end )as "bktCount-5",
SUM(
CASE WHEN TOTSANCLIMIT BETWEEN 10000001 AND 200000000
then
     (Case when hrk in (13,14) THEN
          to_number(to_char(bal4,'99999999999.99'))
     else
          to_char(BAL1,'99999999999.99')-(to_char(BAL4,'99999999999.99')-to_char(BAL5,'99999999999.99'))
     END )
ELSE 0 end) AS"Bkt_5",
sum(case when totsanclimit > 200000000 then
(Case when hrk in (13,14) THEN
          (CASE WHEN bal4 !=0 THEN 1 else 0 END )
          ELSE
          (CASE WHEN BAL1-(BAL4-BAL5)!=0 THEN 1 ELSE 0 END)
               END )
else 0 end )as "bktCount-6",
SUM(
CASE WHEN TOTSANCLIMIT > 200000000
then
(Case when hrk in (13,14) THEN
          to_number(to_char(bal4,'99999999999.99'))
     else
          to_char(BAL1,'99999999999.99')-(to_char(BAL4,'99999999999.99')-to_char(BAL5,'99999999999.99'))
     END )
ELSE 0 end) AS"Bkt_6",
--total
sum(
     (Case when hrk in (13,14) THEN
                 (CASE WHEN bal4 !=0 THEN 1 else 0 END )
              ELSE
                 (CASE WHEN BAL1-(BAL4-BAL5)!=0 THEN 1 ELSE 0 END)
     end)
)as "TotCount-7",
SUM((Case when hrk in (13,14) THEN
          to_number(to_char(bal4,'99999999999.99'))
     else
          to_char(BAL1,'99999999999.99')-(to_char(BAL4,'99999999999.99')-to_char(BAL5,'99999999999.99'))
     END )
) AS"Total"
from
select
q1.lbrcode,q1.prdacctid,q1.totsanclimit,q2.balance1,balance3,balance4,balance5,balance6,balance7,q3.hrk
FROM
SELECT LBRCODE,PRDACCTID,SANCDATE,TOTSANCLIMIT,RNK FROM
           SELECT
           LBRCODE,
           PRDACCTID,
           EFFFROMDATE,
           CURCD,
           PLRLINKYN,
           SANCAUTHORITY,
           SANCDATE,
           TOTSANCLIMIT,
           RANK() OVER (PARTITION BY LBRCODE,PRDACCTID ORDER BY EFFFROMDATE DESC) AS RNK
           FROM LIMIT_MAST
           WHERE LBRCODE IN (3)
--    AND PRDACCTID LIKE 'PLLN %'
WHERE RNK=1
)Q1,
(SELECT LBRCODE,PRDACCTID,CBLDATE,BALANCE1,BALANCE2,BALANCE3,BALANCE4,BALANCE5,BALANCE6,BALANCE7 FROM
( SELECT TRN_MAST.*,
RANK() OVER(PARTITION BY LBRCODE,PRDACCTID ORDER BY CBLDATE DESC) AS HRK
FROM TRN_MAST
WHERE CBLDATE <= TO_DATE('31-MAR-2008','DD-MON-RR')
AND (LBRCODE,TRIM(SUBSTR(PRDACCTID,1,8))) IN (SELECT LBRCODE,TRIM(PRDCD) FROM PRD_MAST
        WHERE MODULETYPE IN (13,14,30))
)WHERE HRK=1
)Q2,
( SELECT LBRCODE,TRIM(PRDCD) prd,MODULETYPE hrk FROM PRD_MAST
WHERE (LBRCODE,TRIM(PRDCD)) IN
(SELECT LBRCODE,TRIM(SUBSTR(PRDACCTID,1,8)) FROM LIMIT_MAST)
)q3
WHERE Q1.LBRCODE=Q2.LBRCODE
AND Q1.PRDACCTID=Q2.PRDACCTID
AND TRIM(SUBSTR(Q2.PRDACCTID,1,8))=q3.PRD
AND Q1.LBRCODE=q3.LBRCODE
group by lbrcode,trim(substr(prdacctid,1,8))
order by lbrcode
/

Like this?
SQL> select 123456 my_num from dual;
    MY_NUM
    123456
SQL>
SQL> column my_num format 999999.99
SQL>
SQL> select 123456 my_num from dual;
    MY_NUM
123456.00
SQL>Asif Momen
http://momendba.blogspot.com

Improve performance of the below query

Hi Gurus,
I have following query with the plan described. I need to improve the the performance of this query as it is using full table scans.
How could achieve this.
SELECT csf.*,
       NULL subject_flag,
       NULL next_exp_rewards_date,
       0 next_exp_rewards,
       (csf.rewards_cf - csf.rewards_bf - csf.total_rewards) * -1 reward_spent
FROM crm_statement_fulfilled csf, crm_accounts ca
WHERE csf.account_id = ca.account_id
   AND csf.procg_date = '01-jul-2012'
   AND ca.cycle_id = '01'
   AND ca.date_closed IS NULL
   AND ca.account_type IN ('LTT', 'LTY', 'LYI')
ORDER BY csf.account_id
Connected to Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
Connected as crm
SQL> desc crm_statement_fulfilled
Name                  Type         Nullable Default Comments
ACCOUNT_ID            NUMBER(19)
CAMPAIGN_ID           NUMBER(10)
CYCLE_ID              VARCHAR2(2)
CUSTOMER_ID           NUMBER(14)   Y
PROCG_DATE            DATE
GE_FULFILLED          VARCHAR2(1) Y
POINTS_DISPLAYED      VARCHAR2(1) Y
REASON_ID             VARCHAR2(10) Y
POINTS_BF             NUMBER(10,2) Y
PROMO_POINTS          NUMBER(10,2) Y
GW_ADJ_POINTS         NUMBER(10,2) Y
TOTAL_REWARDS         NUMBER(10,2) Y
GW_FUL_POINTS         NUMBER(10,2) Y
REC_POINTS            NUMBER(10,2) Y
REC_FC_POINTS         NUMBER(10,2) Y
POINTS_CONVERTED      NUMBER(10,2) Y
POINTS_CF             NUMBER(10,2) Y
TOTAL_POINTS          NUMBER(10,2) Y
TOTAL_AIR_MILES_VALUE NUMBER(10)   Y
POINTS_EXPIRED        NUMBER(10,2) Y
CDT_IN_STR_POINTS     NUMBER(10,2) Y
CDT_OUT_STR_POINTS    NUMBER(10,2) Y
ANNIVERSARY_POINTS    NUMBER(10,2) Y
LOYALTY_POINTS        NUMBER(10,2) Y
NEXT_EXP_POINTS       NUMBER(10,2) Y
NEXT_EXP_POINTS_DATE DATE         Y
REWARDS_BF            NUMBER(10,2) Y
REWARDS_CF            NUMBER(10,2) Y
SQL> desc crm_accounts
Name               Type         Nullable Default Comments
ACCOUNT_ID         NUMBER(19)
CYCLE_ID           VARCHAR2(2)
ACCOUNT_TYPE       VARCHAR2(3)
SECURITY_PASSWORD VARCHAR2(80) Y
ACCESS_PASSWORD    VARCHAR2(80) Y
AIRMILES_ID        VARCHAR2(16) Y
DATE_OPENED        DATE
SEED               VARCHAR2(1) Y
AUTO_AIRMILES      VARCHAR2(1) Y
CURRENCY           VARCHAR2(3) Y
DATE_CLOSED        DATE         Y
STORE_OPENED       VARCHAR2(4) Y
DATE_ACTIVATED     DATE         Y
OLD_ACCOUNT_ID     NUMBER(19)   Y
CARDPAC_ACCOUNT_ID NUMBER(19)   Y
ORG_ID             VARCHAR2(10) Y
LOGO_ID            VARCHAR2(10) Y
PTS_TO_ACCOUNT_ID NUMBER(19)   Y
DMW_ACCOUNT_ID     VARCHAR2(19) Y
SQL>

Hi,
Sid_ Z. wrote:
Hi Gurus,
I have following query with the plan described. I need to improve the the performance of this query as it is using full table scans...For all tuning requests, see the forum FAQ {message:id=9360003}
AND csf.procg_date = '01-jul-2012'Don't try to compare a DATE (such as procg_date) with as VARCHAR2 (such as '01-jul-2012'.
Use TO_DATE or a DATE literal instead.

Help required for improving performance of the Query

Similar Messages

Maybe you are looking for