eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PER_UTILITY_FUNCTIONS dependencies on PAY_NET_CALCULATION_RULES

Line 415: 2. Driving the join to pay_net_calculation_rules through the

411: /*
412: Changes done for Bug 3183291
413: ----------------------------
414: 1. Moved pay_element_entries_f pee1 to second last
415: 2. Driving the join to pay_net_calculation_rules through the
416: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
417: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
418: 3. By disabling the Primary Key join to the table the query can be driven off the
419: element entry route which is more selective when driving through subsequent tables.

Line 416: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of

412: Changes done for Bug 3183291
413: ----------------------------
414: 1. Moved pay_element_entries_f pee1 to second last
415: 2. Driving the join to pay_net_calculation_rules through the
416: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
417: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
418: 3. By disabling the Primary Key join to the table the query can be driven off the
419: element entry route which is more selective when driving through subsequent tables.
420: 4. Added this predicate to help in the filtering

Line 417: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective

413: ----------------------------
414: 1. Moved pay_element_entries_f pee1 to second last
415: 2. Driving the join to pay_net_calculation_rules through the
416: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
417: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
418: 3. By disabling the Primary Key join to the table the query can be driven off the
419: element entry route which is more selective when driving through subsequent tables.
420: 4. Added this predicate to help in the filtering
421: 5. Very poor filter so disabled to drive of the source_id which is more selective

Line 430: pay_net_calculation_rules ncr,

426: cursor c_get_date is
427: select nvl(min(pee1.effective_start_date), P_Accrual_Start_Date)
428: from pay_element_links_f pel1,
429: pay_input_values_f piv,
430: pay_net_calculation_rules ncr,
431: pay_accrual_plans pap,
432: pay_element_links_f pel2,
433: pay_element_entries_f pee1, -- Change (1)
434: pay_element_entries_f pee2

Line 468: pay_net_calculation_rules ncr,

464: select /*+ index(pee1 PAY_ELEMENT_ENTRIES_F_N53) use_nl(ncr)*/
465: nvl(min(pee1.effective_start_date), P_Accrual_Start_Date)
466: from
467: pay_input_values_f piv,
468: pay_net_calculation_rules ncr,
469: pay_accrual_plans pap,
470: pay_element_entries_f pee1,
471: pay_element_entries_f pee2
472: where

Line 572: 2. Driving the join to pay_net_calculation_rules through the

568: /*
569: Changes done for Bug 3183291
570: ----------------------------
571: 1. Moved pay_element_entries_f pee1 to second last
572: 2. Driving the join to pay_net_calculation_rules through the
573: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
574: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
575: 3. Very poor filter so disabled to drive of the source_id which is more selective
576: 4. Same as above

Line 573: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of

569: Changes done for Bug 3183291
570: ----------------------------
571: 1. Moved pay_element_entries_f pee1 to second last
572: 2. Driving the join to pay_net_calculation_rules through the
573: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
574: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
575: 3. Very poor filter so disabled to drive of the source_id which is more selective
576: 4. Same as above
577: 5. Bulk collect is used to store the values into PL/SQL tables

Line 574: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective

570: ----------------------------
571: 1. Moved pay_element_entries_f pee1 to second last
572: 2. Driving the join to pay_net_calculation_rules through the
573: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
574: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
575: 3. Very poor filter so disabled to drive of the source_id which is more selective
576: 4. Same as above
577: 5. Bulk collect is used to store the values into PL/SQL tables
578: */

Line 586: pay_net_calculation_rules ncr,

582: p_effective_date date) is
583: select distinct pee1.element_entry_id
584: from pay_element_links_f pel1,
585: pay_input_values_f piv,
586: pay_net_calculation_rules ncr,
587: pay_accrual_plans pap,
588: pay_element_links_f pel2,
589: pay_element_entries_f pee1, -- Change (1)
590: pay_element_entries_f pee2

Line 624: pay_net_calculation_rules ncr,

620: select /*+ index(pee1 PAY_ELEMENT_ENTRIES_F_N53)*/
621: distinct pee1.element_entry_id
622: from
623: pay_input_values_f piv,
624: pay_net_calculation_rules ncr,
625: pay_accrual_plans pap,
626: pay_element_entries_f pee1,
627: pay_element_entries_f pee2
628: where