APPS.PAY_US_RETRO_OVERLAP dependencies on PAY_RETRO_ASSIGNMENTS

Line 28: to check pay_retro_assignments table

24: c_check_retro_pay_element to change
25: the table name to
26: hr_all_organization_units
27: 17-03-2011 nkjaladi 115.5 10428204 Modified procedure enable_retro_overlap
28: to check pay_retro_assignments table
29: rather than action_type 'L' to verfiy
30: if retropay(enhanced) is used by
31: customer or not
32:

Line 114: pay_retro_assignments pra,

110: CURSOR c_chk_adv_retro_pay_enabled(p_business_group_id IN NUMBER)
111: IS
112: SELECT 'Y'
113: FROM pay_assignment_actions paa ,
114: pay_retro_assignments pra,
115: pay_payroll_actions ppa
116: WHERE ppa.action_type = 'L'
117: AND ppa.business_group_id = p_business_group_id
118: AND paa.payroll_action_id = ppa.payroll_action_id

Line 254: So To differentiate the process we need to check the pay retro assignments table

250: l_enro_flag := 'N';
251: END IF;
252: CLOSE c_check_retro_pay_element; */
253: /* Retro Enhanced and Retro Pay by element share same action type 'L'
254: So To differentiate the process we need to check the pay retro assignments table
255: this is used only for advanced retro pay. Once advanced retro pay is used
256: ct. wouldn't be able to move back to retro pay by element process*/
257: l_bg_count := 0;
258: l_adv_ret_bg_count := 0;