APPS.PAY_RETRO_PKG dependencies on HR_API

Line 908: , p_system_reprocess_date IN DATE default hr_api.g_eot)

904: , p_reprocess_date IN DATE
905: , p_eff_date IN DATE
906: , p_retro_component_id IN NUMBER
907: , p_owner_type IN VARCHAR2 default 'S' --System
908: , p_system_reprocess_date IN DATE default hr_api.g_eot)
909: is
910: l_min_reprocess_date date;
911: l_min_effective_date date;
912: l_min_sys_reprocess_date date;

Line 926: nvl(system_reprocess_date, hr_api.g_eot),

922: --
923: select reprocess_date,
924: effective_date,
925: owner_type,
926: nvl(system_reprocess_date, hr_api.g_eot),
927: retro_component_id
928: into l_min_reprocess_date,
929: l_min_effective_date,
930: l_owner_type,

Line 1873: if (l_rec_date = hr_api.g_sot OR

1869: Otherwise, Balance Adjustments will be used till the reprocess_date and recalculations can be done from the reprocess_date.
1870: v_recorded_date is the date from which full recalculations are done. This is stored in serial_number column of
1871: pay_assignment_actions and can be queried after the retropay run to verify the recalculation_date used by the process.
1872: */
1873: if (l_rec_date = hr_api.g_sot OR
1874: p_adj_start_date < l_rec_date) THEN
1875: --
1876: hr_utility.set_location('process_recorded_date', 20);
1877: