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 pevf.effective_start_date = peef.effective_start_date

Line 432: from PAY_ELEMENT_ENTRY_VALUES_F

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

Line 469: from pay_element_entries_f peef, pay_element_entry_values_f peevf,

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

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

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

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

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

Line 1320: -- date from pay_element_entry_values_f and pay_element_entries_f.

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

Line 1323: -- pay_element_entries_f and pay_element_entry_values_f.

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

Line 1375: Delete from pay_element_entry_values_f

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

Line 1397: Update pay_element_entry_values_f

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

Line 2087: from pay_element_entry_values_f pev

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

Line 2101: ,pay_element_entry_values_f peevf

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

Line 2348: delete from pay_element_entry_values_f pev

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

Line 2359: update pay_element_entry_values_f pev

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