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.PAY_US_TAX_INTERNAL dependencies on PAY_ELEMENT_ENTRY_VALUES_F

Line 328: pay_element_entry_values_f peevf,

324: select peef.effective_start_date,
325: peef.effective_end_date,
326: peevf.screen_entry_value
327: from pay_element_entries_f peef,
328: pay_element_entry_values_f peevf,
329: pay_input_values_f pivf,
330: pay_element_types_f petf,
331: pay_element_links_f pelf
332: where peef.assignment_id = p_assignment_id

Line 376: PAY_ELEMENT_ENTRY_VALUES_F pevf

372: p_jurisdiction varchar2,
373: p_assignment_id number) is
374: select peef.element_entry_id
375: from PAY_ELEMENT_ENTRIES_F peef,
376: PAY_ELEMENT_ENTRY_VALUES_F pevf
377: where peef.assignment_id = p_assignment_id
378: and p_effective_date between peef.effective_start_date
379: and peef.effective_end_date
380: and peef.element_link_id = p_element_link

Line 396: PAY_ELEMENT_ENTRY_VALUES_F pevf

392: p_jurisdiction varchar2,
393: p_assignment_id number) is
394: select peef.element_entry_id, peef.effective_start_date
395: from PAY_ELEMENT_ENTRIES_F peef,
396: PAY_ELEMENT_ENTRY_VALUES_F pevf
397: where peef.assignment_id = p_assignment_id
398: and peef.element_link_id = p_element_link
399: and pevf.element_entry_id = peef.element_entry_id
400: and pevf.input_value_id = p_input_val

Line 413: PAY_ELEMENT_ENTRY_VALUES_F pevf

409: p_input_val number)is
410: select peef.element_entry_id, peef.effective_start_date,
411: peef.effective_end_date
412: from PAY_ELEMENT_ENTRIES_F peef,
413: PAY_ELEMENT_ENTRY_VALUES_F pevf
414: where peef.assignment_id = p_assignment_id
415: and peef.element_link_id = p_element_link
416: and pevf.element_entry_id = peef.element_entry_id
417: and p_effective_date between pevf.effective_start_date

Line 430: from PAY_ELEMENT_ENTRY_VALUES_F

426: cursor csr_get_curr_percnt (p_ele_entry_id number,
427: p_input_val number,
428: p_effective_date date)is
429: select screen_entry_value
430: from PAY_ELEMENT_ENTRY_VALUES_F
431: where element_entry_id = p_ele_entry_id
432: and p_effective_date between effective_start_date
433: and effective_end_date
434: and input_value_id = p_input_val

Line 467: from pay_element_entries_f peef, pay_element_entry_values_f peevf,

463: p_jurisdiction varchar2,
464: p_effective_date date
465: ) is
466: select peef.element_entry_id
467: from pay_element_entries_f peef, pay_element_entry_values_f peevf,
468: pay_element_links_f pelf, pay_element_types_f petf
469: where peef.assignment_id= p_assignment_id
470: and petf.element_name='VERTEX'
471: and peevf.screen_entry_value = p_jurisdiction

Line 660: -- pay_element_entry_values_f structure for a 'VERTEX' element in a given

656: -- ----------------------------------------------------------------------------
657: -- |--------------------< set_and_correct_jurisdiction >----------------------|
658: -- ----------------------------------------------------------------------------
659: -- This procedure corrects the actual percentage stored within the
660: -- pay_element_entry_values_f structure for a 'VERTEX' element in a given
661: -- jurisdiction.
662: --
663: procedure set_and_correct_jurisdiction
664: (

Line 769: -- pay_element_entry_values_f structure for a 'VERTEX' element in a given

765: -- ----------------------------------------------------------------------------
766: -- |-----------------------< calculate_db_percentage >------------------------|
767: -- ----------------------------------------------------------------------------
768: -- This procedure determines the actual percentage to be stored within the
769: -- pay_element_entry_values_f structure for a 'VERTEX' element in a given
770: -- jurisdiction.
771: --
772: procedure calculate_db_percentage
773: (

Line 1318: -- date from pay_element_entry_values_f and pay_element_entries_f.

1314: -- hr_entry_api.update_element_entry with a mode of 'UPDATE'.
1315: -- c. else if call hr_entry_api.update_element_entry with a mode
1316: -- of 'UPDATE_INSERT'.
1317: -- d. remove any percentage records which are before the new effective
1318: -- date from pay_element_entry_values_f and pay_element_entries_f.
1319: -- e. if the new effective date is before the old defaulting date then
1320: -- update the effective start date of the first record in
1321: -- pay_element_entries_f and pay_element_entry_values_f.
1322: elsif p_datetrack_mode = 'INSERT_OVERRIDE' then

Line 1321: -- pay_element_entries_f and pay_element_entry_values_f.

1317: -- d. remove any percentage records which are before the new effective
1318: -- date from pay_element_entry_values_f and pay_element_entries_f.
1319: -- e. if the new effective date is before the old defaulting date then
1320: -- update the effective start date of the first record in
1321: -- pay_element_entries_f and pay_element_entry_values_f.
1322: elsif p_datetrack_mode = 'INSERT_OVERRIDE' then
1323: --
1324: hr_utility.set_location(l_proc, 85);
1325: --

Line 1373: Delete from pay_element_entry_values_f

1369: --
1370: --
1371: -- Remove element entry values first
1372: --
1373: Delete from pay_element_entry_values_f
1374: Where element_entry_id = l_element_entry_id
1375: and effective_start_date < p_effective_date;
1376: --
1377: -- Next, remove the parent element entry records.

Line 1395: Update pay_element_entry_values_f

1391: --
1392: hr_utility.set_location(l_proc, 105);
1393: --
1394: Begin
1395: Update pay_element_entry_values_f
1396: Set effective_start_date = p_effective_date
1397: Where element_entry_id = l_element_entry_id
1398: and effective_start_date = t_effective_start_date;
1399: --

Line 2085: from pay_element_entry_values_f pev

2081: /* Cursor to get the current worker's compensation jurisdiction */
2082:
2083: cursor csr_get_curr_jurisd (p_csr_ele_entry_id number, p_csr_inp_val number) is
2084: select pev.screen_entry_value
2085: from pay_element_entry_values_f pev
2086: where pev.element_entry_id = p_csr_ele_entry_id
2087: and l_get_old_value_date between pev.effective_start_date
2088: and pev.effective_end_date
2089: and pev.input_value_id = p_csr_inp_val

Line 2099: ,pay_element_entry_values_f peevf

2095: ,l_csr_effective_date date
2096: ) is
2097: select peef.element_entry_id
2098: from pay_element_entries_f peef
2099: ,pay_element_entry_values_f peevf
2100: ,pay_element_links_f pelf
2101: ,pay_element_types_f petf
2102: where peef.assignment_id= l_csr_assignment_id
2103: and petf.element_name = lc_workers_comp

Line 2346: delete from pay_element_entry_values_f pev

2342: p_num_entry_values => 2,
2343: p_input_value_id_tbl => l_inp_value_id_table,
2344: p_entry_value_tbl => l_scr_value_table);
2345:
2346: delete from pay_element_entry_values_f pev
2347: where pev.element_entry_id = l_element_entry_id
2348: and pev.effective_start_date < l_effective_date;
2349:
2350: delete from pay_element_entries_f pee

Line 2357: update pay_element_entry_values_f pev

2353:
2354: elsif l_effective_date < l_wc_min_start_date then
2355: -- Manually set effective start date of earliest record to l_effective_date
2356:
2357: update pay_element_entry_values_f pev
2358: set pev.effective_start_date = l_effective_date
2359: where pev.element_entry_id = l_element_entry_id
2360: and pev.effective_start_date = l_wc_min_start_date;
2361: