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.BEN_CWB_BACK_OUT_CONC dependencies on BEN_CWB_PERSON_RATES

Line 33: 27-Apr-04 rpgupta 115.13 bug 3517726 - elete records in ben_cwb_person_rates

29: BEN_CWB_SUMMARY,
30: ben_cwb_pl_dsgn
31: 26-Mar-04 pbodla 115.9 l_ocrd_date need to be passed to
32: BEN_CWB_PL_DSGN_PKG.delete_pl_dsgn
33: 27-Apr-04 rpgupta 115.13 bug 3517726 - elete records in ben_cwb_person_rates
34: with the given group_pl_id, ler_id and life event
35: ocrd date. Sometimes when one thread of benmngle
36: fails, theres a possibility that a few records in
37: person_rates exist with group_per_in_ler_id as -1

Line 70: then while backing out BEN_CWB_PERSON_RATES rows

66: person, the person rates are also
67: deleted and the element entries are
68: not backed out.
69: 06-Apr-2006 abparekh 115.25 Bug 5130397 : When CWB plan has options attached,
70: then while backing out BEN_CWB_PERSON_RATES rows
71: delete pay proposal only once
72: 25-May-2006 ikasired 115.26 Bug 5240208 fix for heirarchy issue for
73: reassign, backout and reprocess issue
74: 26-May-2006 maagrawa 115.27 Always run summary refresh at end

Line 379: -- ben_cwb_person_rates.ELEMENT_ENTRY_VALUE_ID will be passed this routine.

375: -- Ignore proration etc., YES
376: -- Element entry is shared by mutliple cwb entries ? NO
377: --
378: -- Assumptions.
379: -- ben_cwb_person_rates.ELEMENT_ENTRY_VALUE_ID will be passed this routine.
380: -- Element type from ben_cwb_plan_design overrides from abr.
381: -- Abr information have to be fetched similar to cwb post process.
382: --
383: --

Line 911: delete from ben_cwb_person_rates

907:
908: /* bug 3517726
909: */
910:
911: delete from ben_cwb_person_rates
912: where group_pl_id = p_group_pl_id
913: and lf_evt_ocrd_dt = l_ocrd_date
914: and group_per_in_ler_id = -1 -- Bug 5060080
915: and person_id = l_person_id;

Line 1653: from ben_cwb_person_rates

1649: where group_per_in_ler_id = p_per_in_ler_id;
1650: --
1651: cursor c_cwb_person_rates is
1652: select distinct pl_id, oipl_id, pay_proposal_id
1653: from ben_cwb_person_rates
1654: where group_per_in_ler_id = p_per_in_ler_id
1655: order by pay_proposal_id;
1656: --
1657: l_pl_id number;

Line 1665: from ben_cwb_person_rates

1661: select ELEMENT_ENTRY_VALUE_ID,
1662: COMP_POSTING_DATE,
1663: person_id,
1664: object_version_number
1665: from ben_cwb_person_rates
1666: where group_per_in_ler_id = p_per_in_ler_id
1667: and pl_id = l_pl_id
1668: and oipl_id = l_oipl_id ;
1669: --

Line 1748: elsif p_routine = 'BEN_CWB_PERSON_RATES' then

1744:
1745: end loop;
1746: close c_cwb_person_group;
1747: --
1748: elsif p_routine = 'BEN_CWB_PERSON_RATES' then
1749: --
1750: l_pay_proposal_id_prev := -1;
1751: --
1752: open c_cwb_person_rates;

Line 1802: ben_cwb_person_rates_api.delete_person_rate

1798:
1799: end if;
1800: --
1801: if l_object_version_number is not null then
1802: ben_cwb_person_rates_api.delete_person_rate
1803: (p_validate => false
1804: ,p_group_per_in_ler_id => p_per_in_ler_id
1805: ,p_pl_id => l_pl_id
1806: ,p_oipl_id => l_oipl_id

Line 1811: -- Bug 5130397 : When CWB plan has options attached, then all corresponding rows in BEN_CWB_PERSON_RATES

1807: ,p_object_version_number => l_object_version_number
1808: ,p_update_summary => p_update_summary) ;
1809: end if;
1810: --
1811: -- Bug 5130397 : When CWB plan has options attached, then all corresponding rows in BEN_CWB_PERSON_RATES
1812: -- has pay_proposal_id populated and this being same ID, we should not call delete API
1813: -- more than once. Hence added following check : l_pay_proposal_id <> l_pay_proposal_id_prev
1814: --
1815: if l_pay_proposal_id is not null AND

Line 1911: --2. BEN_CWB_PERSON_RATES

1907: ,p_per_in_ler_id => p_per_in_ler_id
1908: ,p_update_summary => p_update_summary
1909: );
1910:
1911: --2. BEN_CWB_PERSON_RATES
1912: hr_utility.set_location( 'Calling delete for BEN_CWB_PERSON_RATES', 15);
1913: fnd_message.set_name('BEN','BEN_91333_CALLING_PROC');
1914: fnd_message.set_token('PROC','delete_person_rates');
1915: cwb_delete_routine

Line 1912: hr_utility.set_location( 'Calling delete for BEN_CWB_PERSON_RATES', 15);

1908: ,p_update_summary => p_update_summary
1909: );
1910:
1911: --2. BEN_CWB_PERSON_RATES
1912: hr_utility.set_location( 'Calling delete for BEN_CWB_PERSON_RATES', 15);
1913: fnd_message.set_name('BEN','BEN_91333_CALLING_PROC');
1914: fnd_message.set_token('PROC','delete_person_rates');
1915: cwb_delete_routine
1916: (p_routine => 'BEN_CWB_PERSON_RATES'

Line 1916: (p_routine => 'BEN_CWB_PERSON_RATES'

1912: hr_utility.set_location( 'Calling delete for BEN_CWB_PERSON_RATES', 15);
1913: fnd_message.set_name('BEN','BEN_91333_CALLING_PROC');
1914: fnd_message.set_token('PROC','delete_person_rates');
1915: cwb_delete_routine
1916: (p_routine => 'BEN_CWB_PERSON_RATES'
1917: ,p_per_in_ler_id => p_per_in_ler_id
1918: ,p_update_summary => p_update_summary
1919: );
1920:

Line 2068: delete from ben_cwb_person_rates

2064: --
2065: backout_heirarchy_data
2066: (p_per_in_ler_id => l_pil_rec.per_in_ler_id);
2067: --
2068: delete from ben_cwb_person_rates
2069: where group_pl_id = p_group_pl_id
2070: and lf_evt_ocrd_dt = l_pil_rec.lf_evt_ocrd_dt
2071: and group_per_in_ler_id = -1 -- Bug 5060080
2072: and person_id = p_person_id;