Query-Paid Time Off (PTO)

Hi,
I am working on Time Management. I have a query. I need to set the PTO (Paid Time Off) right wherein the Details given as under:-
Scenario:-
1) Length of Service=0-0.99
Accrual hours per pay period=4.01
Yearly Equivalent= 96 Hours
Maximum Hours of Accrual=96
2) Length of Service=1-1.99
Accrual hours per pay period=4.01
Yearly Equivalent= 96 Hours
Maximum Hours of Accrual=144
Here the query is that the Maximum number of Hours to be accrued should be 96+96=192 but the client wants it to be 144 and not 192 but clients wants to add the Scenario 1 and 2 for maximum number of hours but the total should not exceed 144. Same is the case with other scenario’s given wherein I need to add maximum number of hours but there is limit set  for total.
I went to T559L but unable to understand how to incorporate the above stated.
Kindly help.
Regards,
Garima

Hi,
Kindly go give a reply.
I need to solve the query.
It will be suitably rewarded.
Regards,
Garima

Similar Messages

  • Issue with PTO (Paid Time Off) quota generation

    Hi All,
    We have an issue with quota generation of PTO for our employees.
    The issue goes like this:
    We have a Paid time off for employees 5weeks( 200 hrs) for employees who have worked less than 5 years.
    we have  paid time off for employees 6 weeks ( 240 hrs) for employees who have worked more than 5 years.
    we have the following logic that has to go in this config:
    -- Our fiscal year starts on Feb 1st and ends on Jan end or Feb starts which has a full week of working days. ( ex: if 01/31/2012 falls on a Thursday the following Monday which has full 5 day working week would be the end of the fiscal year).
    -- Depending on the working hours of  the employees and the date of joining for the first year ( for new hires)0041 info type the eligibility gets varied and reduced. Ex( employees who joins on start of fiscal year and works 40hrs per week schedules is eligible for 200hrs of PTO. Employees who join in the month of august and works for 35 hrs per week ( i.e mid of fiscal year) would get 91 hrs of PTO.
    I need to put this in the system. I am thinking this could be done with out tweaking PCR.I need help in configuring this in Absence quotas as to what are the things i need change in system config and how do i do it. Please help with some screen shots if possible.  I really need this to get it done ASAP. Looking forward for help.
    Thanks,
    Chowdary.

    We use TM00 schema. Can i call TS15 and TS 12  rules into TM00 acheieve my issue of quota entilements?
    Iam doing this because my businees needs to see if an employee chages his work schedule from 40 to 30 or 20 etc.. the PTO has to vary accordingly.
    As the minimum eligibility is to work for 20 hrs to avail the PTO days. If at any point the employee drops it under 20 he will not be eligible till he work any this >= 20hrs per month so the evaluation has to check periodically to update the quota availability.... I need help plz suggest ...

  • PTO ( Paid Time Off ) Quota Correction

    Hi,
    Can someone tell me how to make quota corrections to PTO for all the EE's to 40 hours beginning on 10/01/2007 .
    Thanks,
    Swarna.

    Hi,
    You can use the Quota Corrections infotype (2013) to influence how these accrual entitlements are generated and transferred from the table:
    ·         You can increase, decrease, or replace an accrual entitlement (set to a fixed value).
    ·        You can make the accrual entitlements available for deduction immediately in the Absence Quotas infotype (2006).
    An employee has joined your company from another company. His or her contract has guaranteed a one-off entitlement of ten days of leave when the employee joins your company. You therefore want to increase the employee’s leave quota by 10 days. You want the entitlement to be immediately available in the Absence Quotas infotype (2006) so that the employee can take the ten days of leave.
    Structure
    You can only use the infotype to change absence quotas that are accrued in time evaluation. The changes are taken into account the next time that time evaluation is run. Time evaluation carries out a recalculation starting on the day for which you have entered the quota correction. You can view the results of the quota correction in the Quota Overview (transaction PT50).
    Transfer time
    The Absence Quotas infotype (2006) does not take account of quota corrections immediately. The infotype is updated at a specific transfer time that is determined in Customizing.
    If you want to make the corrected accrual entitlements available directly in the Absence Quotas infotype (2006), you can also immediately transfer the accrual entitlements accumulated in time evaluation and the quota number specified in the infotype. You do this by setting the Transfer field to Transfer collected entitlement immediately. 
    Replace and increase
    In the case of automatic accrual, time evaluation can either replace or increase the existing accrual entitlements in the Absence Quotas infotype (2006). You will generally want to use the Quota Corrections infotype (2013) to change only accrual entitlements that are increased by time evaluation.
    If the accrual entitlement is replaced by the quota correction, you can only choose the Transfer collected entitlement immediately function for quotas that are to be replaced. If the entitlement were not transferred immediately, time evaluation would overwrite the correction immediately.
    If an accrual entitlement is replaced by the quota correction, you can only enter one record for each day. This is because a second quota correction would overwrite the first one, thereby making it void.
    Customizing
    To check whether a quota is replaced or increased, choose the Customizing step:
    Personnel Time Management --> Time Data Recording and Administration -->Managing Time Accounts Using Attendance/Absence Quotas --> Calculating Absence Entitlements --> Automatic Accrual of Absence Quotas --> Permit Generation of Quotas in Time Evaluation.
    Cheers
    Prasanth

  • Advise on how to remove paid charge off

    Looking for any advice on the best way of handeling this. I have a old paid charge off  on my credit report that is scheduled to drop off in early 2016. I would love to get this removed early, but not sure if it is worth it. Is it really affecting my credit score at this point? I have read in several forums that when older than 48 mos it doesnt factor much into score. Is writting a goodwill letter to the original creditor the best way to go to get it removed? If I do send one to the OC do I have to send one to the collection agency as well to have them remove it also? If I sent a gw letter could there be any negative consequences? If they dont remove it, could they update the most recent activity date, since I contacted them? I know I posted alot of questions- any help is greatly appreciated.

    jeeptrailmaster wrote:
    Looking for any advice on the best way of handeling this. I have a old paid charge off  on my credit report that is scheduled to drop off in early 2016. I would love to get this removed early, but not sure if it is worth it. Is it really affecting my credit score at this point? I have read in several forums that when older than 48 mos it doesnt factor much into score. Is writting a goodwill letter to the original creditor the best way to go to get it removed? If I do send one to the OC do I have to send one to the collection agency as well to have them remove it also? If I sent a gw letter could there be any negative consequences? If they dont remove it, could they update the most recent activity date, since I contacted them? I know I posted alot of questions- any help is greatly appreciated.A CO always affects your Fico the entire time its on file, the ding lessens with age once it stops monthly updating. Sometimes a creditor interprets a GW  letter as a dispute and will update the  TL brining the account status date current and it can affect the Fico score if that happens. One should avoid all references to disputes in a GW. Since this is coming off in early 2016 you may choose just to wait and ask for early exclusion 6 months out on TU and 3 months out on the other 2 CRAs. Your choice, sending PFDs, GWs or any other letter is always a calculated risk. Welcome to My Fico

  • Query execution time estimation....

    Hi All,
    Is it possible to estimate query execution time using explain plan?
    Thanks in advance,
    Santosh.

    The cost estimated by the cost based optimizer is actually representing the time it takes to process the statement expressed in units of the single block read-time. Which means if you know the estimated time a single block read request requires you can translate this into an actual time.
    Starting with Oracle 9i this information (the time to perform single block/multi block read requests) is actually available if you gather system statistics.
    And this is what 10g actually does, as it shows an estimated TIME in the explain plan output based on these assumptions. Note that 10g by default uses system statistics, even if they are not explicitly gathered. In this case Oracle 10g uses the NOWORKLOAD statistics generated on the fly at instance startup.
    Of course the time estimates shown by Oracle 10g may not even be close to the actual execution time as it is only an estimate based on a model and input values (statistics) and therefore might be way off due to several reasons, the same applies in principle to the cost shown.
    Regards,
    Randolf
    Oracle related stuff:
    http://oracle-randolf.blogspot.com/
    SQLTools++ for Oracle:
    http://www.sqltools-plusplus.org:7676/
    http://sourceforge.net/projects/sqlt-pp/

  • Overtime compensation by time off.

    Dear Experts,
    I am using TM00 for time evaluation, I want to compensate the overtime perfomed by employee by time off only (no payment for overtime), I am using PCR YO16 for determining overtime (Copy of TO16 Determine overtime without approval), I have set the compensation type 3 (Compensation time off) using PCR YO16, I have created one absence quotya type 02 called as "comp off" with "INCREASE" mode in customizing, I have kept base entitlement for this quota type as Day Balance 0410 (Time off from overtime), the issue is that the quota type 02 is geting accrued twice if employee works overtime this is because PCR for compensation of Overtime TC10 updates the quota 02 by UPDTQA by overtime hours and QOUTA function also increases the quota type 02 by overtime hours,.
    Since my quota type 02 should only get generated if any employee works overtime I dont want it to get processed by QUOTA function so could you please let me know how to achieve it.
    If there is any other solution for my requirement then also please let me know.
    Thanks,
    Javed

    Hi Okan,
    For accessing the quota in time evaluation should be in increase mode.
    Still I tries as you said be it is also preventing it from getting updated by UPDTQA.
    I am having one workaround...if I remove the UPDTQA statement from TC12 I am getting correct results since the quota is getting updated by QUOTA function only...but I think this would not be the correct way to get the solution since SAP has provided the UPDTQA statement in TC12 means there should be some purpose behind it...right...the correct way would be to avoid the quota getting updated by QUOTA function...I think we are missing something...bevause of which we are not able prevent QUOTA function from updating our quota..please suggest...
    Thanks,
    Javed

  • Trying to use labview to analyse analog data from a jump on a force plate and measure peak force (at two points, initial land and 2nd land from jump). Also need to mark the time of flight (time off plate).

    Attached is a file of 3 trials of a drop vertical jump activity onto a force plate.  the subject stands on a platform off the force plate, jumps onto the force place and immediately jumps up as if going for a rebound.  I am able to run this data and obtain a waveform graph with no problems.  however, I need to be able to find the initial contact with the force palte, the peak of the drop, the intial time off the force plate (prior to the jump), the return from the jump and finally the second peak (landing from the jump). 
    I want to calculate the time of flight ( time off the plate and in the air after the intial drop) to calculate juimp height.
    I had someone write me a mathscript for it and it works well, however, I need to do it without mathscript as I do not understand mathscript (nor Labview!!).
    Please help
    Attachments:
    Jose_Index and shift register6.vi ‏130 KB
    NI post.docx ‏365 KB

    OK, but I'm not understanding what you're asking us to do... Are you asking us to explain what the MathScript code is doing? (It's searching the array for the elements when the values are above or below a threshold.) Are you asking someone to convert the whole MathScript code to LabVIEW (we are not a code-writing service), or you just want to be able to calculate the new stuff you want with LabVIEW?
    In the future, please do not post proprietary file formats. Most people do not have Word, or Word 2007 for that matter. Please post text files or PDFs. Thanks.

  • Unable to find consolidate field in Time off Process application

    Hi All,
    I create an aplllication for Time off process and unable to find "consolidate" field when selecting set up block parameters .I am using portals EP 7.0 Version
    Could you please help me in getting this ...
    Thanks ,
    Nararaju.

    Hi,
       we group parameters so that the output of process actions is automatically entered as input .We can consolidate parameter at Action,block adn process levels
    follow the below steps
    1. Select your Seq Block and click on the tab "Parameters" at the bottom pane
    2. Mark all the parameter (press ctrl for multiple ) and Click on Map
    3. Supply the Name and say create
    at last do a SavaAll
    hope this will solve ur problem
    cheers
    souza

  • Query execution time

    Dear SCN,
    I am new to BOBJ Environment. I have created a webi report on top of bex query by using BISC connection. Bex query is build for Vendor Ageing Analysis. My bex query will take very less time to execute the report (max 1 min). But in case of webi is takeing around 5 min when i click on refresh. I have not used any conditions,filters,restrictions are done at webi level all are done at bex level only.
    Please let me know techniques to optimize the query execution time in webi. Currently we are in BO 4.0.
    Regards,
    PRK

    Hi Praveen
    Go through this document for performance optimization using BICS connection
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0e3c552-e419-3010-1298-b32e6210b58d?QuickLink=index&…

  • Query taking time

    We have this query which is taking a long time to execute. From the explain plan what i found out is there is a full table scan going on W_GL_OTHER_F. Please help in identifying the problem area and solutions.
    The query is,
    select D1.c1 as c1,
         D1.c2 as c2,
         D1.c3 as c3,
         D1.c4 as c4,
         D1.c5 as c5,
         D1.c6 as c6,
         D1.c7 as c7,
         D1.c8 as c8
    from
         (select distinct D1.c2 as c1,
                   D1.c3 as c2,
                   D1.c4 as c3,
                   D1.c5 as c4,
                   D1.c6 as c5,
                   D1.c7 as c6,
                   D1.c8 as c7,
                   D1.c1 as c8,
                   D1.c5 as c9
              from
                   (select sum(case  when T324628.OTHER_DOC_AMT is null then 0 else T324628.OTHER_DOC_AMT end ) as c1,
                             T91397.GL_ACCOUNT_NUM as c2,
                             T149255.SEGMENT_VAL_CODE as c3,
                             T148908.SEGMENT_VAL_DESC as c4,
                             T148543.HIER4_CODE as c5,
                             T148543.HIER4_NAME as c6,
                             T91707.ACCT_DOC_NUM as c7,
                             T91707.X_LINE_DESCRIPTION as c8
                        from
                             W_GL_OTHER_F T91707 /* Fact_W_GL_OTHER_F */ ,
                             W_GL_ACCOUNT_D T91397 /* Dim_W_GL_ACCOUNT_D */ ,
                             W_STATUS_D T96094 /* Dim_W_STATUS_D_Generic */ ,
                             WC_GL_OTHER_F_MV T324628 /* Fact_WC_GL_OTHER_MV */ ,
                             W_GL_SEGMENT_D T149255 /* Dim_W_GL_SEGMENT_D_Segment1 */ ,
                             W_GL_SEGMENT_D T148937 /* Dim_W_GL_SEGMENT_D_Segment3 */ ,
                             W_HIERARCHY_D T148543 /* Dim_W_HIERARCHY_D_Segment3 */ ,
                             W_GL_SEGMENT_D T148908 /* Dim_W_GL_SEGMENT_D_Segment2 */
                        where  ( T91397.ROW_WID = T91707.GL_ACCOUNT_WID and T91707.DOC_STATUS_WID = T96094.ROW_WID and T96094.ROW_WID = T324628.DOC_STATUS_WID and T148543.HIER_CODE = T148937.SEGMENT_LOV_ID and T148543.HIER20_CODE = T148937.SEGMENT_VAL_CODE and T324628.DELETE_FLG = 'N' and T324628.X_CURRENCY_CODE = 'CAD' and T148543.HIER4_CODE <> '00000000000' and T91397.RECON_TYPE_CODE is not null and T91397.ROW_WID = T324628.GL_ACCOUNT_WID and T91397.ACCOUNT_SEG3_CODE = T148937.SEGMENT_VAL_CODE and T91397.ACCOUNT_SEG3_ATTRIB = T148937.SEGMENT_LOV_ID and T91397.ACCOUNT_SEG2_CODE = T148908.SEGMENT_VAL_CODE and T91397.ACCOUNT_SEG2_ATTRIB = T148908.SEGMENT_LOV_ID and T91397.ACCOUNT_SEG1_CODE = T149255.SEGMENT_VAL_CODE and T91397.ACCOUNT_SEG1_ATTRIB = T149255.SEGMENT_LOV_ID and (T96094.W_STATUS_CODE in ('POSTED', 'REVERSED')) and T91397.GL_ACCOUNT_NUM like '%98%' )
                        group by T91397.GL_ACCOUNT_NUM, T91707.ACCT_DOC_NUM, T91707.X_LINE_DESCRIPTION, T148543.HIER4_CODE, T148543.HIER4_NAME, T148908.SEGMENT_VAL_DESC, T149255.SEGMENT_VAL_CODE
                   ) D1
         ) D1
    order by c1, c2, c3, c4, c5, c6, c7The plan is,
    PLAN_TABLE_OUTPUT
    Plan hash value: 3196636288
    | Id  | Operation                             | Name                | Rows  | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Psto
    |   0 | SELECT STATEMENT                      |                     |   810K|   306M|       |   266K  (1)| 01:20:03 |       |       |
    |   1 |  HASH GROUP BY                        |                     |   810K|   306M|   320M|   266K  (1)| 01:20:03 |       |       |
    |*  2 |   HASH JOIN                           |                     |   810K|   306M|    38M|   239K  (1)| 01:11:56 |       |       |
    |*  3 |    MAT_VIEW ACCESS FULL               | WC_GL_OTHER_F_MV    |  1137K|    40M|       |  9771   (2)| 00:0
    |*  4 |    HASH JOIN                          |                     |   531K|   189M|       |   222K  (1)| 01:06:38 |       |       |
    |   5 |     INLIST ITERATOR                   |                     |       |       |       |            |          |       |       |
    |*  6 |      INDEX RANGE SCAN                 | W_STATUS_D_U2       |     4 |    56 |       |     1   (0)| 00:00:01 |   
    |*  7 |     HASH JOIN                         |                     |   607K|   208M|  8704K|   222K  (1)| 01:06:38 |       |       |
    |*  8 |      HASH JOIN                        |                     | 40245 |  8214K|  2464K| 10843   (2)| 00:03:16 |       |       |
    |   9 |       VIEW                            | index$_join$_007    | 35148 |  2025K|       |   122  (32)| 00:00:03 |       |
    |* 10 |        HASH JOIN                      |                     |       |       |       |            |          |       |       |
    |* 11 |         HASH JOIN                     |                     |       |       |       |            |          |       |       |
    |* 12 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
    |  13 |           BITMAP CONVERSION TO ROWIDS |                     | 35148 |  2025K|       |     1   (0)| 00:00:01 |       |   
    |  14 |            BITMAP INDEX FULL SCAN     | W_HIERARCHY_D_M2    |       |       |       |            |          |       |     
    |  15 |           BITMAP CONVERSION TO ROWIDS |                     | 35148 |  2025K|       |    24   (0)| 00:00:01 |       |   
    |  16 |            BITMAP INDEX FULL SCAN     | W_HIERARCHY_D_M4    |       |       |       |            |          |       |     
    |  17 |          BITMAP CONVERSION TO ROWIDS  |                     | 35148 |  2025K|       |    24   (0)| 00:00:01 |       |   
    |* 18 |           BITMAP INDEX FULL SCAN      | X_W_HIERARCHY_D_M11 |       |       |       |            |          |       |     
    |  19 |         BITMAP CONVERSION TO ROWIDS   |                     | 35148 |  2025K|       |    33   (0)| 00:00:01 |       |   
    |  20 |          BITMAP INDEX FULL SCAN       | X_W_HIERARCHY_D_M12 |       |       |       |            |          |       |     
    |* 21 |       HASH JOIN                       |                     | 40246 |  5895K|  4096K| 10430   (2)| 00:03:08 |       |      
    |  22 |        VIEW                           | index$_join$_008    | 65417 |  3321K|       |   197  (14)| 00:00:04 |      
    |* 23 |         HASH JOIN                     |                     |       |       |       |            |          |       |       |
    |* 24 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
    |  25 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 |  3321K|       |     3   (0)| 00:00:01 |       |   
    |  26 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |     
    |  27 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 |  3321K|       |    66   (2)| 00:00:02 |       |   
    |  28 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |     
    |  29 |          BITMAP CONVERSION TO ROWIDS  |                     | 65417 |  3321K|       |   100   (1)| 00:00:02 |       |   
    |  30 |           BITMAP INDEX FULL SCAN      | W_GL_SEGMENT_D_M3   |       |       |       |            |          |       |     
    |* 31 |        HASH JOIN                      |                     | 40246 |  3851K|       |  9953   (1)| 00:03:00 |       |       |
    |  32 |         VIEW                          | index$_join$_006    | 65417 |  1149K|       |    82  (18)| 00:00:02 |       |      
    |* 33 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
    |  34 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 |  1149K|       |     3   (0)| 00:00:01 |       |   
    |  35 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |     
    |  36 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 |  1149K|       |    66   (2)| 00:00:02 |       |   
    |  37 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |     
    |* 38 |         HASH JOIN                     |                     | 40246 |  3144K|       |  9870   (1)| 00:02:58 |       |       |
    |  39 |          VIEW                         | index$_join$_005    | 65417 |  1149K|       |    82  (18)| 00:00:02 |       |     
    |* 40 |           HASH JOIN                   |                     |       |       |       |            |          |       |       |
    |  41 |            BITMAP CONVERSION TO ROWIDS|                     | 65417 |  1149K|       |     3   (0)| 00:00:01 |       |   
    |  42 |             BITMAP INDEX FULL SCAN    | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |     
    |  43 |            BITMAP CONVERSION TO ROWIDS|                     | 65417 |  1149K|       |    66   (2)| 00:00:02 |       |   
    |  44 |             BITMAP INDEX FULL SCAN    | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |     
    |* 45 |          TABLE ACCESS FULL            | W_GL_ACCOUNT_D      | 40246 |  2436K|       |  9788   (1)| 00:02:57
    |  46 |      PARTITION RANGE ALL              |                     |    11M|  4261M|       |   152K  (2)| 00:45:43 |     1 |1048
    |  47 |       TABLE ACCESS FULL               | W_GL_OTHER_F        |    11M|  4261M|       |   152K  (2)| 00:45:43
    Predicate Information (identified by operation id):
       2 - access("T96094"."ROW_WID"="T324628"."DOC_STATUS_WID" AND "T91397"."ROW_WID"="T324628"."GL_ACC
       3 - filter("T324628"."X_CURRENCY_CODE"='CAD' AND "T324628"."DELETE_FLG"='N')
       4 - access("T91707"."DOC_STATUS_WID"="T96094"."ROW_WID")
       6 - access("T96094"."W_STATUS_CODE"='POSTED' OR "T96094"."W_STATUS_CODE"='REVERSED')
       7 - access("T91397"."ROW_WID"="T91707"."GL_ACCOUNT_WID")
       8 - access("T148543"."HIER_CODE"="T148937"."SEGMENT_LOV_ID" AND "T148543"."HIER20_CODE"="T148937"
      10 - access(ROWID=ROWID)
      11 - access(ROWID=ROWID)
      12 - access(ROWID=ROWID)
      18 - filter("T148543"."HIER4_CODE"<>'00000000000')
      21 - access("T91397"."ACCOUNT_SEG2_CODE"="T148908"."SEGMENT_VAL_CODE" AND
                  "T91397"."ACCOUNT_SEG2_ATTRIB"="T148908"."SEGMENT_LOV_ID")
      23 - access(ROWID=ROWID)
      24 - access(ROWID=ROWID)
      31 - access("T91397"."ACCOUNT_SEG3_CODE"="T148937"."SEGMENT_VAL_CODE" AND
                  "T91397"."ACCOUNT_SEG3_ATTRIB"="T148937"."SEGMENT_LOV_ID")
      33 - access(ROWID=ROWID)
      38 - access("T91397"."ACCOUNT_SEG1_CODE"="T149255"."SEGMENT_VAL_CODE" AND
                  "T91397"."ACCOUNT_SEG1_ATTRIB"="T149255"."SEGMENT_LOV_ID")
      40 - access(ROWID=ROWID)
      45 - filter("T91397"."GL_ACCOUNT_NUM" LIKE '%98%' AND "T91397"."RECON_TYPE_CODE" IS NOT NULL)
    79 rows selected.

    user605926 wrote:
    We have this query which is taking a long time to execute. From the explain plan what i found out is there is a full table scan going on W_GL_OTHER_F. Please help in identifying the problem area and solutions.
    The plan is,
    PLAN_TABLE_OUTPUT
    Plan hash value: 3196636288
    | Id  | Operation                             | Name                | Rows  | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Psto
    |   0 | SELECT STATEMENT                      |                     |   810K|   306M|       |   266K  (1)| 01:20:03 |       |       |
    |   1 |  HASH GROUP BY                        |                     |   810K|   306M|   320M|   266K  (1)| 01:20:03 |       |       |
    |*  2 |   HASH JOIN                           |                     |   810K|   306M|    38M|   239K  (1)| 01:11:56 |       |       |
    |*  3 |    MAT_VIEW ACCESS FULL               | WC_GL_OTHER_F_MV    |  1137K|    40M|       |  9771   (2)| 00:0
    |*  4 |    HASH JOIN                          |                     |   531K|   189M|       |   222K  (1)| 01:06:38 |       |       |
    |   5 |     INLIST ITERATOR                   |                     |       |       |       |            |          |       |       |
    |*  6 |      INDEX RANGE SCAN                 | W_STATUS_D_U2       |     4 |    56 |       |     1   (0)| 00:00:01 |   
    |*  7 |     HASH JOIN                         |                     |   607K|   208M|  8704K|   222K  (1)| 01:06:38 |       |       |
    |*  8 |      HASH JOIN                        |                     | 40245 |  8214K|  2464K| 10843   (2)| 00:03:16 |       |       |
    |   9 |       VIEW                            | index$_join$_007    | 35148 |  2025K|       |   122  (32)| 00:00:03 |       |
    |* 10 |        HASH JOIN                      |                     |       |       |       |            |          |       |       |
    |* 11 |         HASH JOIN                     |                     |       |       |       |            |          |       |       |
    |* 12 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
    |  13 |           BITMAP CONVERSION TO ROWIDS |                     | 35148 |  2025K|       |     1   (0)| 00:00:01 |       |   
    |  14 |            BITMAP INDEX FULL SCAN     | W_HIERARCHY_D_M2    |       |       |       |            |          |       |     
    |  15 |           BITMAP CONVERSION TO ROWIDS |                     | 35148 |  2025K|       |    24   (0)| 00:00:01 |       |   
    |  16 |            BITMAP INDEX FULL SCAN     | W_HIERARCHY_D_M4    |       |       |       |            |          |       |     
    |  17 |          BITMAP CONVERSION TO ROWIDS  |                     | 35148 |  2025K|       |    24   (0)| 00:00:01 |       |   
    |* 18 |           BITMAP INDEX FULL SCAN      | X_W_HIERARCHY_D_M11 |       |       |       |            |          |       |     
    |  19 |         BITMAP CONVERSION TO ROWIDS   |                     | 35148 |  2025K|       |    33   (0)| 00:00:01 |       |   
    |  20 |          BITMAP INDEX FULL SCAN       | X_W_HIERARCHY_D_M12 |       |       |       |            |          |       |     
    |* 21 |       HASH JOIN                       |                     | 40246 |  5895K|  4096K| 10430   (2)| 00:03:08 |       |      
    |  22 |        VIEW                           | index$_join$_008    | 65417 |  3321K|       |   197  (14)| 00:00:04 |      
    |* 23 |         HASH JOIN                     |                     |       |       |       |            |          |       |       |
    |* 24 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
    |  25 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 |  3321K|       |     3   (0)| 00:00:01 |       |   
    |  26 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |     
    |  27 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 |  3321K|       |    66   (2)| 00:00:02 |       |   
    |  28 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |     
    |  29 |          BITMAP CONVERSION TO ROWIDS  |                     | 65417 |  3321K|       |   100   (1)| 00:00:02 |       |   
    |  30 |           BITMAP INDEX FULL SCAN      | W_GL_SEGMENT_D_M3   |       |       |       |            |          |       |     
    |* 31 |        HASH JOIN                      |                     | 40246 |  3851K|       |  9953   (1)| 00:03:00 |       |       |
    |  32 |         VIEW                          | index$_join$_006    | 65417 |  1149K|       |    82  (18)| 00:00:02 |       |      
    |* 33 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
    |  34 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 |  1149K|       |     3   (0)| 00:00:01 |       |   
    |  35 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |     
    |  36 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 |  1149K|       |    66   (2)| 00:00:02 |       |   
    |  37 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |     
    |* 38 |         HASH JOIN                     |                     | 40246 |  3144K|       |  9870   (1)| 00:02:58 |       |       |
    |  39 |          VIEW                         | index$_join$_005    | 65417 |  1149K|       |    82  (18)| 00:00:02 |       |     
    |* 40 |           HASH JOIN                   |                     |       |       |       |            |          |       |       |
    |  41 |            BITMAP CONVERSION TO ROWIDS|                     | 65417 |  1149K|       |     3   (0)| 00:00:01 |       |   
    |  42 |             BITMAP INDEX FULL SCAN    | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |     
    |  43 |            BITMAP CONVERSION TO ROWIDS|                     | 65417 |  1149K|       |    66   (2)| 00:00:02 |       |   
    |  44 |             BITMAP INDEX FULL SCAN    | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |     
    |* 45 |          TABLE ACCESS FULL            | W_GL_ACCOUNT_D      | 40246 |  2436K|       |  9788   (1)| 00:02:57
    |  46 |      PARTITION RANGE ALL              |                     |    11M|  4261M|       |   152K  (2)| 00:45:43 |     1 |1048
    |  47 |       TABLE ACCESS FULL               | W_GL_OTHER_F        |    11M|  4261M|       |   152K  (2)| 00:45:43
    Predicate Information (identified by operation id):
    2 - access("T96094"."ROW_WID"="T324628"."DOC_STATUS_WID" AND "T91397"."ROW_WID"="T324628"."GL_ACC
    3 - filter("T324628"."X_CURRENCY_CODE"='CAD' AND "T324628"."DELETE_FLG"='N')
    4 - access("T91707"."DOC_STATUS_WID"="T96094"."ROW_WID")
    6 - access("T96094"."W_STATUS_CODE"='POSTED' OR "T96094"."W_STATUS_CODE"='REVERSED')
    7 - access("T91397"."ROW_WID"="T91707"."GL_ACCOUNT_WID")
    8 - access("T148543"."HIER_CODE"="T148937"."SEGMENT_LOV_ID" AND "T148543"."HIER20_CODE"="T148937"
    10 - access(ROWID=ROWID)
    11 - access(ROWID=ROWID)
    12 - access(ROWID=ROWID)
    18 - filter("T148543"."HIER4_CODE"<>'00000000000')
    21 - access("T91397"."ACCOUNT_SEG2_CODE"="T148908"."SEGMENT_VAL_CODE" AND
    "T91397"."ACCOUNT_SEG2_ATTRIB"="T148908"."SEGMENT_LOV_ID")
    23 - access(ROWID=ROWID)
    24 - access(ROWID=ROWID)
    31 - access("T91397"."ACCOUNT_SEG3_CODE"="T148937"."SEGMENT_VAL_CODE" AND
    "T91397"."ACCOUNT_SEG3_ATTRIB"="T148937"."SEGMENT_LOV_ID")
    33 - access(ROWID=ROWID)
    38 - access("T91397"."ACCOUNT_SEG1_CODE"="T149255"."SEGMENT_VAL_CODE" AND
    "T91397"."ACCOUNT_SEG1_ATTRIB"="T149255"."SEGMENT_LOV_ID")
    40 - access(ROWID=ROWID)
    45 - filter("T91397"."GL_ACCOUNT_NUM" LIKE '%98%' AND "T91397"."RECON_TYPE_CODE" IS NOT NULL)
    79 rows selected.
    You may want to have a look at <a href="HOW TO: Post a SQL statement tuning request - template posting">HOW TO: Post a SQL statement tuning request - template posting</a> to see what more details are needed in order for somebody to provide better answer.
    Based on what you have posted so far, you may want to share details of following questions (in addition to details in above link)
    1) How much time does the query currently take to execute? How much time do you expect it to take? Also, how are you measuring query execution time?
    2) Your plan suggests that the query is expected to return 810K rows. Is this figure close to actual number of records? What are you doing with this huge amount of data?

  • Help required in optimizing the query response time

    Hi,
    I am working on a application which uses a jdbc thin client. My requirement is to select all the table rows in one table and use the column values to select data in another table in another database.
    The first table can have maximum of 6 million rows but the second table rows will be around 9000.
    My first query is returning within 30-40 milliseconds when the table is having 200000 rows. But when I am iterating the result set and query the second table the query is taking around 4 millisecond for each query.
    the second query selection criteria is to find the value in the range .
    for example my_table ( varchar2 column1, varchar2 start_range, varchar2 end_range);
    My first query returns a result which then will be used to select using the following query
    select column1 from my_table where start_range < my_value and end_range> my_value;
    I have created an index on start_range and end_range. this query is taking around 4 millisseconds which I think is too much.
    I am using a preparedStatement for the second query loop.
    Can some one suggest me how I can improve the query response time?
    Regards,
    Shyam

    Try the code below.
    Pre-requistee: you should know how to pass ARRAY objects to oracle and receive resultsets from java. There are 1000s of samples available on net.
    I have written a sample db code for the same interraction.
    Procedure get_list takes a array input from java and returns the record set back to java. You can change the tablenames and the creteria.
    Good luck.
    DROP TYPE idlist;
    CREATE OR REPLACE TYPE idlist AS TABLE OF NUMBER;
    CREATE OR REPLACE PACKAGE mypkg1
    AS
       PROCEDURE get_list (myval_list idlist, orefcur OUT sys_refcursor);
    END mypkg1;
    CREATE OR REPLACE PACKAGE BODY mypkg1
    AS
       PROCEDURE get_list (myval_list idlist, orefcur OUT sys_refcursor)
       AS
          ctr   NUMBER;
       BEGIN
          DBMS_OUTPUT.put_line (myval_list.COUNT);
          FOR x IN (SELECT object_name, object_id, myvalue
                      FROM user_objects a,
                           (SELECT myval_list (ROWNUM + 1) myvalue
                              FROM TABLE (myval_list)) b
                     WHERE a.object_id < b.myvalue)
          LOOP
             DBMS_OUTPUT.put_line (   x.object_name
                                   || ' - '
                                   || x.object_id
                                   || ' - '
                                   || x.myvalue
          END LOOP;
       END;
    END mypkg1;
    [pre]
    Testing the code above. Make sure dbms output is ON.
    [pre]
    DECLARE
       a      idlist;
       refc   sys_refcursor;
       c number;
    BEGIN
       SELECT x.nu
       BULK COLLECT INTO a
         FROM (SELECT 5000 nu
                 FROM DUAL) x;
       mypkg1.get_list (a, refc);
    END;
    [pre]
    Vishal V.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Turning on the backlight with backlight timer off

    With the backlight timer set on off, there is a feature to turn on the backlight by holding the menu button. I remember doing that a while ago, but my ipod no longer does that anymore. Now with the backlight timer off, and i hold the menu button it no longer does that (it just goes to the main screen). I've tried reseting the ipod, but the feature does not come back.

    The only way I can think of to get the feature back is to "update" using an older updater, such as the one that came with your CD.
    Reinstall the updater from the CD that came with your iPod would give you an older update that would contain the feature your looking for. Also using the "previous updaters" feature in the iPod folder on your computer would have the same effect. Update the iPod with one of these. However, bear in mind that newer features such as the volume limiter that are on the new 1.1.1 update would not be available.

  • My facetime starts connecting then fails to make the call ? ive tried the swtiching face time off switching macbook off then switching it back on the logging back in to facetime but still no joys. any help ?

    my facetime starts connecting then fails to make the call ? ive tried the swtiching face time off switching macbook off then switching it back on the logging back in to facetime but still no joys. any help ?

    my facetime starts connecting then fails to make the call ? ive tried the swtiching face time off switching macbook off then switching it back on the logging back in to facetime but still no joys. any help ?

  • How to run a query several times?

    Hi all,
    Anyone has a clue for the following situation:
    We have made a query (on the web) with several characteristics and key-figures. One of the characteristics has unique values that occurs only once (something like numbers for documents in R/3). The query was build with only one user-input variable based on this characteristic. The query was build especially for printing and fits exactly on a A4-paper.
    We would like to give the end-user a tool in which he/she can store several values for the characteristic. On the basis of these stored values the system has to run the query several times.
    Something for the Reporting Agent or is there an other solution?
    Thanks in advance,
    Henk.

    hi Henk,
    'control query' in few words is to filter data with combination of characteristic value.
    http://help.sap.com/saphelp_nw04s/helpdata/en/6e/b5663a5fb46752e10000000a11402f/frameset.htm
    Control Query for Pre-calculating Web Templates
    Definition
    A control query is a help query that you execute before you execute the queries in the Web template, and use the result to parameterize the Web template.
    Use
    You can specify a control query as significant information in the Reporting Agent settings for a Web template. When you specify a control query, the system does not pre-calculate the Web template itself, but a number of filtered views from the Web template.
    We particularly recommend this procedure when wanting to calculate several Web templates only distinguished by their filter values in one swoop.
    Using a control query in particular allows you to formulate complex selection criteria for the data to be pre-calculated.
    Pre-calculate only the TOP50 customers, whose data is frequently requested, for example.
    Structure
    A very simple query, which contains exactly those characteristics in the drilldown in the rows according to which the Web template will be filtered, is particularly suitable as a control query. Every row in the table that a control query delivers, subsequently serves as a dynamic filter for the Web template views.
    The respective combination of characteristic values is used as a filter for the Web template Data Provider for each table row. The background run produces pre-calculated data records, in actual fact one data record for each table row that delivers a control query.
    If a characteristic does not appear in a view, the filter value is ignored.
    In addition, you automatically get only those filter value combinations, for which data exists in the InfoCube used to define the control query.
    Example
    A typical application of this approach for pre-calculating a Web template is with cockpit applications, since they are controlled mainly through selection lists and no real OLAP navigation is necessary.
    You can also use a control query for filtering when pre-calculating Crystal reports queries. You can find additional information under Defining Crystal Reports Queries Settings.

  • How to obtain the Query Response Time of a query?

    Given the Average Length of Row of tables and the number of rows in each table,
    is there a way we get the query response time of a query involving
    those tables. Query includes joins as well.
    For example, suppose there 3 tables t1, t2, t3. I wish to obtain the
    time it takes for the following query:
    Query
    SELECT t1.col1, t2.col2
    FROM t1, t2, t3
    WHERE t1.col1 = t2.col2
    AND t1.col2 IN ('a', 'c', 'd')
    AND t2.col1 = t3.col2
    AND t2.col1 = t1.col1 (+)
    ORDER BY t1.col1
    Given are:
    Average Row Length of t1 = 200 bytes
    Average Row Length of t2 = 100 bytes
    Average Row Length of t3 = 500 bytes
    No of rows in t1 = 100
    No of rows in t2 = 1000
    No of rows in t3 = 500
    What is required is the 'query response time' for the said query.

    I do not know how to do it myself. But if you are running Oracle 10g, I believe that there is a new tool called: SQL Tuning Advisor which might be able to help.
    Here are some links I found doing a google search, and it looks like it might meet your needs and even give you more information on how to improve your code.
    http://www.databasejournal.com/features/oracle/article.php/3492521
    http://www.databasejournal.com/features/oracle/article.php/3387011
    http://www.oracle.com/technology/obe/obe10gdb/manage/perflab/perflab.htm
    http://www.oracle.com/technology/pub/articles/10gdba/week18_10gdba.html
    http://www.oracle-base.com/articles/10g/AutomaticSQLTuning10g.php
    Have fun reading:
    You can get help from teachers, but you are going to have to learn a lot by yourself, sitting alone in a room ....Dr. Seuss
    Regards
    Tim

Maybe you are looking for