Download Oracle HRMS US Implementation Guide

Example 1
This example creates a new grade rate which starts from today.
hr_grade_api.create_grade_rate_value
(...
,p_effective_date => trunc(sysdate)
...);
Example 2
This example creates a new employee who will join the company at the
start of March 1997.
hr_employee_api.create_employee
(...
,p_hire_date => to_date(’01–03–1997’,’DD–MM–YYYY’)
...);
Some APIs which do not modify data in DateTrack entities still have a
p_effective_date parameter. The date value is not used to affect when
the changes take affect. It is used to validate QuickCode values. Each
QuickCodes value can have be specified with a valid date range. The
start date indicates when the value can first be used. The end date
shows the last date the value can be used on new records and set when
updating records. Existing records, which are not changed, can continue
to use the QuickCode after the end date.
Understanding the p_datetrack_update_mode Control Parameter
Most APIs which update data for at least one DateTrack entity have a
p_datetrack_update_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:
Value
Description
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
UPDATE
Keep history of existing information
CORRECTION
Correct existing information
UPDATE_OVERRIDE
Replace all scheduled changes
UPDATE_CHANGE_INSERT
Insert this change before next
scheduled change
It may not be possible to use every mode in every case. For example, if
there are no existing future changes for the record you are changing, the
DateTrack modes UPDATE_OVERRIDE and
UPDATE_CHANGE_INSERT cannot be used.
Technical Essays
A – 65