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 1179: (SELECT 'Y' FROM pay_element_entry_values_f eev

1175: p_assignment_id);
1176: BEGIN
1177: l_ret_chng := 'N';
1178: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1179: (SELECT 'Y' FROM pay_element_entry_values_f eev
1180: WHERE eev.element_entry_id = rec_entry.element_entry_id
1181: AND eev.effective_start_date > p_term_date);
1182: EXCEPTION
1183: WHEN NO_DATA_FOUND THEN NULL;

Line 1203: (SELECT 'Y' FROM pay_element_entry_values_f eev

1199: END IF;
1200: BEGIN
1201: l_ret_chng := 'N';
1202: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1203: (SELECT 'Y' FROM pay_element_entry_values_f eev
1204: WHERE eev.element_entry_id = rec_entry.element_entry_id
1205: AND eev.effective_end_date > p_term_date);
1206: EXCEPTION
1207: WHEN NO_DATA_FOUND THEN NULL;

Line 1283: (SELECT 'Y' FROM pay_element_entry_values_f eev

1279: ELSE
1280: BEGIN
1281: l_ret_chng := 'N';
1282: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1283: (SELECT 'Y' FROM pay_element_entry_values_f eev
1284: WHERE eev.element_entry_id = nonrec_entry.element_entry_id);
1285: EXCEPTION
1286: WHEN NO_DATA_FOUND THEN NULL;
1287: END;

Line 1321: (SELECT 'Y' FROM pay_element_entry_values_f eev

1317: IF p_final_process_date IS NULL THEN
1318: BEGIN
1319: l_ret_chng := 'N';
1320: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1321: (SELECT 'Y' FROM pay_element_entry_values_f eev
1322: WHERE eev.element_entry_id = nonrec_entry.element_entry_id
1323: AND eev.effective_end_date = nonrec_entry.effective_end_date);
1324: EXCEPTION
1325: WHEN NO_DATA_FOUND THEN NULL;

Line 1360: (SELECT 'Y' FROM pay_element_entry_values_f eev

1356: END IF;
1357: BEGIN
1358: l_ret_chng := 'N';
1359: SELECT 'Y' INTO l_ret_chng FROM dual WHERE EXISTS
1360: (SELECT 'Y' FROM pay_element_entry_values_f eev
1361: WHERE eev.element_entry_id = nonrec_entry.element_entry_id
1362: AND eev.effective_end_date = nonrec_entry.effective_end_date);
1363: EXCEPTION
1364: WHEN NO_DATA_FOUND THEN NULL;

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

1451: --
1452: hr_utility.set_location(l_proc,21);
1453: /*
1454: ** Original code, below, performs a delete from PAY_ELEMENT_ENTRIES_F
1455: ** and PAY_ELEMENT_ENTRY_VALUES_F where the entry effective start
1456: ** date is greater than the termination date (i.e. the entry starts
1457: ** after the employee is terminated). Therefore the entry, and its
1458: ** values, can be completely removed.
1459: ** The DML statements can be replaced with a single call to

Line 1463: DELETE FROM pay_element_entry_values_f eev

1459: ** The DML statements can be replaced with a single call to
1460: ** pay_element_entry_api.delete_element_entry using the 'ZAP' mode.
1461: **
1462: --
1463: DELETE FROM pay_element_entry_values_f eev
1464: WHERE eev.element_entry_id = rec_entry.element_entry_id
1465: AND eev.effective_start_date > p_term_date;
1466: --
1467: hr_utility.set_location(l_proc,25);

Line 1498: ** PAY_ELEMENT_ENTRY_VALUES_F, setting the effective_end_date

1494: hr_utility.set_location(l_proc,30);
1495: --
1496: /*
1497: ** Original code, below, updates PAY_ELEMENT_ENTRIES_F and
1498: ** PAY_ELEMENT_ENTRY_VALUES_F, setting the effective_end_date
1499: ** of the entry end date to the termination date where the
1500: ** entry end date falls some point after the termination date.
1501: ** The DML statements can be replaced with a single call to
1502: ** pay_element_entry_api.delete_element_entry using the 'DELETE' mode.

Line 1505: UPDATE pay_element_entry_values_f eev

1501: ** The DML statements can be replaced with a single call to
1502: ** pay_element_entry_api.delete_element_entry using the 'DELETE' mode.
1503: **
1504: --
1505: UPDATE pay_element_entry_values_f eev
1506: SET eev.effective_end_date = p_term_date
1507: WHERE eev.element_entry_id = rec_entry.element_entry_id
1508: AND eev.effective_end_date > p_term_date;
1509: --

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

1622: -- pay_element_entry_api.delete_element_entry
1623: --
1624: /*
1625: ** Original code, below, performs a delete from PAY_ELEMENT_ENTRIES_F
1626: ** and PAY_ELEMENT_ENTRY_VALUES_F since the entry effective start
1627: ** date is greater than the termination date (i.e. the entry starts
1628: ** after the employee is terminated). Therefore the entry, and its
1629: ** values, can be completely removed.
1630: ** The DML statements can be replaced with a single call to

Line 1633: DELETE FROM pay_element_entry_values_f eev

1629: ** values, can be completely removed.
1630: ** The DML statements can be replaced with a single call to
1631: ** pay_element_entry_api.delete_element_entry using the 'ZAP' mode.
1632: **
1633: DELETE FROM pay_element_entry_values_f eev
1634: WHERE eev.element_entry_id = nonrec_entry.element_entry_id;
1635: --
1636: hr_utility.set_location(l_proc,65);
1637: --

Line 1700: -- UPDATE pay_element_entry_values_f eev

1696: -- 31-oct-1995 WWBUG 314277 changed update to p_final_process_date
1697: -- to be p_term_date as this agrees with the relevant termination rule.
1698: -- VT #553177 12/10/97
1699: null;
1700: -- UPDATE pay_element_entry_values_f eev
1701: -- SET eev.effective_end_date = p_term_date
1702: -- WHERE eev.element_entry_id = nonrec_entry.element_entry_id
1703: -- AND eev.effective_end_date = nonrec_entry.effective_end_date;
1704: --

Line 1757: ** PAY_ELEMENT_ENTRY_VALUES_F, setting the effective_end_date

1753: -- pay_element_entry_api.delete_element_entry
1754: --
1755: /*
1756: ** Original code, below, updates PAY_ELEMENT_ENTRIES_F and
1757: ** PAY_ELEMENT_ENTRY_VALUES_F, setting the effective_end_date
1758: ** of the entry end date to the termination date where the
1759: ** entry end date falls some point after the termination date.
1760: ** The DML statements can be replaced with a single call to
1761: ** pay_element_entry_api.delete_element_entry using the 'DELETE' mode.

Line 1768: UPDATE pay_element_entry_values_f eev

1764: SET ee.effective_end_date = p_final_process_date
1765: , ee.last_update_date = l_last_update_date
1766: WHERE ee.element_entry_id = nonrec_entry.element_entry_id
1767: AND ee.effective_end_date = nonrec_entry.effective_end_date;
1768: UPDATE pay_element_entry_values_f eev
1769: SET eev.effective_end_date = p_final_process_date
1770: WHERE eev.element_entry_id = nonrec_entry.element_entry_id
1771: AND eev.effective_end_date = nonrec_entry.effective_end_date;
1772: **