[Home] [Help]
1995: -- p_adj_start_date is the earliest overlap_start_date for the assignment in this retropay run
1996: hr_utility.trace('p_adj_start_date : '|| p_adj_start_date);
1997:
1998: -- Get the recorded_date for 'RETRO_OVERLAP' attribute for the assignment
1999: pay_recorded_requests_pkg.get_recorded_date_no_ins( p_process,
2000: l_rec_date,
2001: p_assignment_id);
2002: --
2003: hr_utility.trace('l_rec_date : '|| l_rec_date);
2016: hr_utility.set_location('process_recorded_date', 20);
2017:
2018: v_recorded_date := p_adj_start_date;
2019: --
2020: pay_recorded_requests_pkg.set_recorded_date(
2021: p_process => p_process,
2022: p_recorded_date => p_adj_start_date,
2023: p_recorded_date_o => l_date,
2024: p_attribute1 => p_assignment_id);
2102: Case : Label_identifier in pay_assignment_actions was populated in process_recorded_date only when we are changing the recorded_date
2103: and recorded_date is not equal to start of time (hr_api.g_sot) .
2104: If the Overlap date comes after recorded_date label_identifier was not populated .
2105:
2106: After enabling retro_overlap ,Whenever retropay is rolled back , row from pay_recorded_requests for Retro_Overlap
2107: was getting deleted .This was because label_identifier in pay_assignment_actions was populated as null for Retro assignment action.
2108:
2109: This issue causes retro to run payrolls from overlap start date as there is no record in pay_recorded_requests for RETRO_OVERLAP.
2110:
2105:
2106: After enabling retro_overlap ,Whenever retropay is rolled back , row from pay_recorded_requests for Retro_Overlap
2107: was getting deleted .This was because label_identifier in pay_assignment_actions was populated as null for Retro assignment action.
2108:
2109: This issue causes retro to run payrolls from overlap start date as there is no record in pay_recorded_requests for RETRO_OVERLAP.
2110:
2111: Fix : Modified pay_recorded_requests and removed the check "if (l_date <> hr_api.g_sot)" before updating label_identifier
2112: Start of time will get populated the first time reropay is run after Retro_Overlap feature is enabled
2113:
2107: was getting deleted .This was because label_identifier in pay_assignment_actions was populated as null for Retro assignment action.
2108:
2109: This issue causes retro to run payrolls from overlap start date as there is no record in pay_recorded_requests for RETRO_OVERLAP.
2110:
2111: Fix : Modified pay_recorded_requests and removed the check "if (l_date <> hr_api.g_sot)" before updating label_identifier
2112: Start of time will get populated the first time reropay is run after Retro_Overlap feature is enabled
2113:
2114: Modified reset_recorded_request ,delete the 'RETRO_OVERLAP' row from pay_recorded_requests only when
2115: label_identifier is equal to start of time .
2110:
2111: Fix : Modified pay_recorded_requests and removed the check "if (l_date <> hr_api.g_sot)" before updating label_identifier
2112: Start of time will get populated the first time reropay is run after Retro_Overlap feature is enabled
2113:
2114: Modified reset_recorded_request ,delete the 'RETRO_OVERLAP' row from pay_recorded_requests only when
2115: label_identifier is equal to start of time .
2116: If above is not the case update recorded_date only when label_identifier is not null .
2117: */
2118:
2117: */
2118:
2119: if (l_prev_rec_date = hr_api.g_sot)
2120: then
2121: delete from pay_recorded_requests
2122: where ATTRIBUTE_CATEGORY = 'RETRO_OVERLAP'
2123: and ATTRIBUTE1 =to_char(l_assign_id);
2124: elsif l_prev_rec_date is not null then
2125: update pay_recorded_requests
2121: delete from pay_recorded_requests
2122: where ATTRIBUTE_CATEGORY = 'RETRO_OVERLAP'
2123: and ATTRIBUTE1 =to_char(l_assign_id);
2124: elsif l_prev_rec_date is not null then
2125: update pay_recorded_requests
2126: set RECORDED_DATE = l_prev_rec_date
2127: where ATTRIBUTE_CATEGORY = 'RETRO_OVERLAP'
2128: and ATTRIBUTE1 = to_char(l_assign_id);
2129: --