[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: 115.72 16-MAR-2009 sgundoju 8214333 added the Logical NOT condition to fix the bug
337: in cancel_termination procedure
1444: p_validation_start_date => p_term_date);
1445: --
1446: -- Bugfix 4308892
1447: -- Replace DELETE statements with equivalent calls to
1448: -- pay_element_entry_api.delete_element_entry
1449: --
1450: if rec_entry.effective_start_date > p_term_date then
1451: --
1452: hr_utility.set_location(l_proc,21);
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
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
1477: from pay_element_entries_f
1478: where element_entry_id = rec_entry.element_entry_Id
1479: and effective_start_date = rec_entry.effective_start_date;
1480: --
1481: pay_element_entry_api.delete_element_entry(
1482: p_validate => false,
1483: p_datetrack_delete_mode => 'ZAP',
1484: p_effective_date => rec_entry.effective_start_date,
1485: p_element_entry_id => rec_entry.element_entry_id,
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.
1503: **
1504: --
1505: UPDATE pay_element_entry_values_f eev
1506: SET eev.effective_end_date = p_term_date
1524: and effective_start_date = rec_entry.effective_start_date;
1525: --
1526: l_ee_effective_end_date := rec_entry.effective_end_date;
1527: --
1528: pay_element_entry_api.delete_element_entry(
1529: p_validate => false,
1530: p_datetrack_delete_mode => 'DELETE',
1531: p_effective_date => p_term_date,
1532: p_element_entry_id => rec_entry.element_entry_id,
1618: --
1619: hr_utility.set_location(l_proc,60);
1620: -- Bugfix 4308892
1621: -- Replace DELETE statements with equivalent calls to
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
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: --
1645: from pay_element_entries_f
1646: where element_entry_id = nonrec_entry.element_entry_Id
1647: and effective_start_date = nonrec_entry.effective_start_date;
1648: --
1649: pay_element_entry_api.delete_element_entry(
1650: p_validate => false,
1651: p_datetrack_delete_mode => 'ZAP',
1652: p_effective_date => nonrec_entry.effective_start_date,
1653: p_element_entry_id => nonrec_entry.element_entry_id,
1749:
1750: --
1751: -- Bugfix 4308892
1752: -- Replace DELETE statements with equivalent calls to
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
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.
1762: **
1763: UPDATE pay_element_entries_f ee
1764: SET ee.effective_end_date = p_final_process_date
1765: , ee.last_update_date = l_last_update_date
1777: from pay_element_entries_f
1778: where element_entry_id = nonrec_entry.element_entry_Id
1779: and effective_start_date = nonrec_entry.effective_start_date;
1780: --
1781: pay_element_entry_api.delete_element_entry(
1782: p_validate => false,
1783: p_datetrack_delete_mode => 'DELETE',
1784: p_effective_date => p_final_process_date,
1785: p_element_entry_id => nonrec_entry.element_entry_id,