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 511: 2. Driving the join to pay_net_calculation_rules through the

507: /*
508: Changes done for Bug 3183291
509: ----------------------------
510: 1. Moved pay_element_entries_f pee1 to second last
511: 2. Driving the join to pay_net_calculation_rules through the
512: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
513: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
514: 3. By disabling the Primary Key join to the table the query can be driven off the
515: element entry route which is more selective when driving through subsequent tables.

Line 512: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of

508: Changes done for Bug 3183291
509: ----------------------------
510: 1. Moved pay_element_entries_f pee1 to second last
511: 2. Driving the join to pay_net_calculation_rules through the
512: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
513: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
514: 3. By disabling the Primary Key join to the table the query can be driven off the
515: element entry route which is more selective when driving through subsequent tables.
516: 4. Added this predicate to help in the filtering

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

509: ----------------------------
510: 1. Moved pay_element_entries_f pee1 to second last
511: 2. Driving the join to pay_net_calculation_rules through the
512: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
513: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
514: 3. By disabling the Primary Key join to the table the query can be driven off the
515: element entry route which is more selective when driving through subsequent tables.
516: 4. Added this predicate to help in the filtering
517: 5. Very poor filter so disabled to drive of the source_id which is more selective

Line 526: pay_net_calculation_rules ncr,

522: cursor c_get_date is
523: select nvl(min(pee1.effective_start_date), P_Accrual_Start_Date)
524: from pay_element_links_f pel1,
525: pay_input_values_f piv,
526: pay_net_calculation_rules ncr,
527: pay_accrual_plans pap,
528: pay_element_links_f pel2,
529: pay_element_entries_f pee1, -- Change (1)
530: pay_element_entries_f pee2

Line 564: pay_net_calculation_rules ncr,

560: select /*+ index(pee1 PAY_ELEMENT_ENTRIES_F_N53) use_nl(ncr)*/
561: nvl(min(pee1.effective_start_date), P_Accrual_Start_Date)
562: from
563: pay_input_values_f piv,
564: pay_net_calculation_rules ncr,
565: pay_accrual_plans pap,
566: pay_element_entries_f pee1,
567: pay_element_entries_f pee2
568: where

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

664: /*
665: Changes done for Bug 3183291
666: ----------------------------
667: 1. Moved pay_element_entries_f pee1 to second last
668: 2. Driving the join to pay_net_calculation_rules through the
669: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
670: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
671: 3. Very poor filter so disabled to drive of the source_id which is more selective
672: 4. Same as above

Line 669: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of

665: Changes done for Bug 3183291
666: ----------------------------
667: 1. Moved pay_element_entries_f pee1 to second last
668: 2. Driving the join to pay_net_calculation_rules through the
669: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
670: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
671: 3. Very poor filter so disabled to drive of the source_id which is more selective
672: 4. Same as above
673: 5. Bulk collect is used to store the values into PL/SQL tables

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

666: ----------------------------
667: 1. Moved pay_element_entries_f pee1 to second last
668: 2. Driving the join to pay_net_calculation_rules through the
669: input_value_id (PAY_NET_CALCULATION_RULES_N3) instead of
670: ncr.accrual_plan_id (PAY_NET_CALCULATION_RULES_FK1) which is more selective
671: 3. Very poor filter so disabled to drive of the source_id which is more selective
672: 4. Same as above
673: 5. Bulk collect is used to store the values into PL/SQL tables
674: */

Line 682: pay_net_calculation_rules ncr,

678: p_effective_date date) is
679: select distinct pee1.element_entry_id
680: from pay_element_links_f pel1,
681: pay_input_values_f piv,
682: pay_net_calculation_rules ncr,
683: pay_accrual_plans pap,
684: pay_element_links_f pel2,
685: pay_element_entries_f pee1, -- Change (1)
686: pay_element_entries_f pee2

Line 720: pay_net_calculation_rules ncr,

716: select /*+ index(pee1 PAY_ELEMENT_ENTRIES_F_N53)*/
717: distinct pee1.element_entry_id
718: from
719: pay_input_values_f piv,
720: pay_net_calculation_rules ncr,
721: pay_accrual_plans pap,
722: pay_element_entries_f pee1,
723: pay_element_entries_f pee2
724: where