Download Oracle HRMS US Implementation Guide

Some APIs which update DateTrack entities do not have a
p_datetrack_update_mode parameter. These APIs automatically
perform the DateTrack operations for that business operation.
Each dated instance for the same primary key has a different
object_version_number. When calling the API the
p_object_version_number parameter should be set to the value which
applies as of the date for the operation (i.e. p_effective_date).
Example
Assume the following grade rate values already exist in the
pay_grade_rules_f table:
Grade_rule_id
12122
12122
Effective
Start_Date
01–JAN–1996
21–FEB–1996
Effective_
End_Date
20–FEB–1996
20–JUN–1998
Version_
Number Value
2
45
3
50
Also assume that the grade rate value was updated to the wrong value
on the 21–FEB–1996. The update from 45 to 50 should have been 45 to 55
and you want to modify the error.
declare
l_object_version_number number;
l_effective_start_date date;
l_effective_end_date
date;
begin
l_object_version_number := 3;
hr_grade_api.update_grade_rate_value
(p_effective_date
=> to_date(’21–02–1996’,’DD–MM–YYYY’)
,p_datetrack_update_mode => ’CORRECTION’
,p_grade_rule_id
=> 12122
,p_object_version_number => l_object_version_number
,p_value
=> 55
,p_effective_start_date => l_effective_start_date
,p_effective_end_date
=> l_effective_end_date
);
–– l_object_version_number will now be set to the value
–– as on database row, as of 21st February 1996.
end;
Understanding the p_datetrack_delete_mode Control Parameter
Most APIs which delete data for at least one DateTrack entity have a
p_datetrack_delete_mode control parameter. It allows you to define the
type of DateTrack change to be made. This mandatory parameter must
be set to one of the following values:
p_datetrack_delete_mode Value
A – 66
Oracle HRMS US Implementation Guide
Description