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

Line 1161: (SELECT 'Y' FROM pay_element_entry_values_f eev

1157: p_assignment_id);
1158: BEGIN
1159: l_ret_chng := 'N';
1160: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1161: (SELECT 'Y' FROM pay_element_entry_values_f eev
1162: WHERE eev.element_entry_id = rec_entry.element_entry_id
1163: AND eev.effective_start_date > p_term_date);
1164: EXCEPTION
1165: WHEN NO_DATA_FOUND THEN NULL;

Line 1185: (SELECT 'Y' FROM pay_element_entry_values_f eev

1181: END IF;
1182: BEGIN
1183: l_ret_chng := 'N';
1184: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1185: (SELECT 'Y' FROM pay_element_entry_values_f eev
1186: WHERE eev.element_entry_id = rec_entry.element_entry_id
1187: AND eev.effective_end_date > p_term_date);
1188: EXCEPTION
1189: WHEN NO_DATA_FOUND THEN NULL;

Line 1265: (SELECT 'Y' FROM pay_element_entry_values_f eev

1261: ELSE
1262: BEGIN
1263: l_ret_chng := 'N';
1264: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1265: (SELECT 'Y' FROM pay_element_entry_values_f eev
1266: WHERE eev.element_entry_id = nonrec_entry.element_entry_id);
1267: EXCEPTION
1268: WHEN NO_DATA_FOUND THEN NULL;
1269: END;

Line 1303: (SELECT 'Y' FROM pay_element_entry_values_f eev

1299: IF p_final_process_date IS NULL THEN
1300: BEGIN
1301: l_ret_chng := 'N';
1302: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1303: (SELECT 'Y' FROM pay_element_entry_values_f eev
1304: WHERE eev.element_entry_id = nonrec_entry.element_entry_id
1305: AND eev.effective_end_date = nonrec_entry.effective_end_date);
1306: EXCEPTION
1307: WHEN NO_DATA_FOUND THEN NULL;

Line 1342: (SELECT 'Y' FROM pay_element_entry_values_f eev

1338: END IF;
1339: BEGIN
1340: l_ret_chng := 'N';
1341: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1342: (SELECT 'Y' FROM pay_element_entry_values_f eev
1343: WHERE eev.element_entry_id = nonrec_entry.element_entry_id
1344: AND eev.effective_end_date = nonrec_entry.effective_end_date);
1345: EXCEPTION
1346: WHEN NO_DATA_FOUND THEN NULL;

Line 1437: ** and PAY_ELEMENT_ENTRY_VALUES_F where the entry effective start

1433: --
1434: hr_utility.set_location(l_proc,21);
1435: /*
1436: ** Original code, below, performs a delete from PAY_ELEMENT_ENTRIES_F
1437: ** and PAY_ELEMENT_ENTRY_VALUES_F where the entry effective start
1438: ** date is greater than the termination date (i.e. the entry starts
1439: ** after the employee is terminated). Therefore the entry, and its
1440: ** values, can be completely removed.
1441: ** The DML statements can be replaced with a single call to

Line 1445: DELETE FROM pay_element_entry_values_f eev

1441: ** The DML statements can be replaced with a single call to
1442: ** pay_element_entry_api.delete_element_entry using the 'ZAP' mode.
1443: **
1444: --
1445: DELETE FROM pay_element_entry_values_f eev
1446: WHERE eev.element_entry_id = rec_entry.element_entry_id
1447: AND eev.effective_start_date > p_term_date;
1448: --
1449: hr_utility.set_location(l_proc,25);

Line 1480: ** PAY_ELEMENT_ENTRY_VALUES_F, setting the effective_end_date

1476: hr_utility.set_location(l_proc,30);
1477: --
1478: /*
1479: ** Original code, below, updates PAY_ELEMENT_ENTRIES_F and
1480: ** PAY_ELEMENT_ENTRY_VALUES_F, setting the effective_end_date
1481: ** of the entry end date to the termination date where the
1482: ** entry end date falls some point after the termination date.
1483: ** The DML statements can be replaced with a single call to
1484: ** pay_element_entry_api.delete_element_entry using the 'DELETE' mode.

Line 1487: UPDATE pay_element_entry_values_f eev

1483: ** The DML statements can be replaced with a single call to
1484: ** pay_element_entry_api.delete_element_entry using the 'DELETE' mode.
1485: **
1486: --
1487: UPDATE pay_element_entry_values_f eev
1488: SET eev.effective_end_date = p_term_date
1489: WHERE eev.element_entry_id = rec_entry.element_entry_id
1490: AND eev.effective_end_date > p_term_date;
1491: --

Line 1608: ** and PAY_ELEMENT_ENTRY_VALUES_F since the entry effective start

1604: -- pay_element_entry_api.delete_element_entry
1605: --
1606: /*
1607: ** Original code, below, performs a delete from PAY_ELEMENT_ENTRIES_F
1608: ** and PAY_ELEMENT_ENTRY_VALUES_F since the entry effective start
1609: ** date is greater than the termination date (i.e. the entry starts
1610: ** after the employee is terminated). Therefore the entry, and its
1611: ** values, can be completely removed.
1612: ** The DML statements can be replaced with a single call to

Line 1615: DELETE FROM pay_element_entry_values_f eev

1611: ** values, can be completely removed.
1612: ** The DML statements can be replaced with a single call to
1613: ** pay_element_entry_api.delete_element_entry using the 'ZAP' mode.
1614: **
1615: DELETE FROM pay_element_entry_values_f eev
1616: WHERE eev.element_entry_id = nonrec_entry.element_entry_id;
1617: --
1618: hr_utility.set_location(l_proc,65);
1619: --

Line 1682: -- UPDATE pay_element_entry_values_f eev

1678: -- 31-oct-1995 WWBUG 314277 changed update to p_final_process_date
1679: -- to be p_term_date as this agrees with the relevant termination rule.
1680: -- VT #553177 12/10/97
1681: null;
1682: -- UPDATE pay_element_entry_values_f eev
1683: -- SET eev.effective_end_date = p_term_date
1684: -- WHERE eev.element_entry_id = nonrec_entry.element_entry_id
1685: -- AND eev.effective_end_date = nonrec_entry.effective_end_date;
1686: --

Line 1739: ** PAY_ELEMENT_ENTRY_VALUES_F, setting the effective_end_date

1735: -- pay_element_entry_api.delete_element_entry
1736: --
1737: /*
1738: ** Original code, below, updates PAY_ELEMENT_ENTRIES_F and
1739: ** PAY_ELEMENT_ENTRY_VALUES_F, setting the effective_end_date
1740: ** of the entry end date to the termination date where the
1741: ** entry end date falls some point after the termination date.
1742: ** The DML statements can be replaced with a single call to
1743: ** pay_element_entry_api.delete_element_entry using the 'DELETE' mode.

Line 1750: UPDATE pay_element_entry_values_f eev

1746: SET ee.effective_end_date = p_final_process_date
1747: , ee.last_update_date = l_last_update_date
1748: WHERE ee.element_entry_id = nonrec_entry.element_entry_id
1749: AND ee.effective_end_date = nonrec_entry.effective_end_date;
1750: UPDATE pay_element_entry_values_f eev
1751: SET eev.effective_end_date = p_final_process_date
1752: WHERE eev.element_entry_id = nonrec_entry.element_entry_id
1753: AND eev.effective_end_date = nonrec_entry.effective_end_date;
1754: **