[Home] [Help]
316: 115.62 09-May-2006 ghshanka 5152164 modified the procedure CANCEL_TERMINATION
317: 115.63 19-May-2006 ggnanagu Added the call to adjust_salary_proposals
318: in per_saladmin_utility to fix bug 5200269
319: 115.65 14-JUN-2006 avarri 4371218 Modified cancel_termination to fix 4371218
320: 115.66 17-JUL-2006 agolechh 4308892 This version of hrempter calls pay_element_entry_api
321: instead of performing direct DML statements on
322: pay_element_entries_f.
323: 115.67 26-Jul-2006 thabara 5368246 Modified terminate_entries_and_alus and
324: delete_alus to end date ALUs with final
329: Leaving reason 'Retirement' type ex-employee.
330: 115.69 10-AUG-2007 pchowdav 6313195 Reverted back the changes done for
331: bug 4371218.
332: 115.71 07-FEB-2008 ckesanap 6801103 Modified cursor rec_entries in delete_entries(). Also
333: added a condition - to call pay_element_entry_api in
334: DELETE mode only if p_term_date is not equal to
335: max_effective_end_date for the record.
336: ================================================================= */
337: g_package varchar2(33) := ' hrempter.'; -- Global package name
1426: p_validation_start_date => p_term_date);
1427: --
1428: -- Bugfix 4308892
1429: -- Replace DELETE statements with equivalent calls to
1430: -- pay_element_entry_api.delete_element_entry
1431: --
1432: if rec_entry.effective_start_date > p_term_date then
1433: --
1434: hr_utility.set_location(l_proc,21);
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
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
1459: from pay_element_entries_f
1460: where element_entry_id = rec_entry.element_entry_Id
1461: and effective_start_date = rec_entry.effective_start_date;
1462: --
1463: pay_element_entry_api.delete_element_entry(
1464: p_validate => false,
1465: p_datetrack_delete_mode => 'ZAP',
1466: p_effective_date => rec_entry.effective_start_date,
1467: p_element_entry_id => rec_entry.element_entry_id,
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.
1485: **
1486: --
1487: UPDATE pay_element_entry_values_f eev
1488: SET eev.effective_end_date = p_term_date
1506: and effective_start_date = rec_entry.effective_start_date;
1507: --
1508: l_ee_effective_end_date := rec_entry.effective_end_date;
1509: --
1510: pay_element_entry_api.delete_element_entry(
1511: p_validate => false,
1512: p_datetrack_delete_mode => 'DELETE',
1513: p_effective_date => p_term_date,
1514: p_element_entry_id => rec_entry.element_entry_id,
1600: --
1601: hr_utility.set_location(l_proc,60);
1602: -- Bugfix 4308892
1603: -- Replace DELETE statements with equivalent calls to
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
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: --
1627: from pay_element_entries_f
1628: where element_entry_id = nonrec_entry.element_entry_Id
1629: and effective_start_date = nonrec_entry.effective_start_date;
1630: --
1631: pay_element_entry_api.delete_element_entry(
1632: p_validate => false,
1633: p_datetrack_delete_mode => 'ZAP',
1634: p_effective_date => nonrec_entry.effective_start_date,
1635: p_element_entry_id => nonrec_entry.element_entry_id,
1731:
1732: --
1733: -- Bugfix 4308892
1734: -- Replace DELETE statements with equivalent calls to
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
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.
1744: **
1745: UPDATE pay_element_entries_f ee
1746: SET ee.effective_end_date = p_final_process_date
1747: , ee.last_update_date = l_last_update_date
1759: from pay_element_entries_f
1760: where element_entry_id = nonrec_entry.element_entry_Id
1761: and effective_start_date = nonrec_entry.effective_start_date;
1762: --
1763: pay_element_entry_api.delete_element_entry(
1764: p_validate => false,
1765: p_datetrack_delete_mode => 'DELETE',
1766: p_effective_date => p_final_process_date,
1767: p_element_entry_id => nonrec_entry.element_entry_id,