APPS.PER_PER_SHD dependencies on DT_API

Line 332: dt_api.find_dt_del_modes

328: --
329: --
330: -- Call the corresponding datetrack api
331: --
332: dt_api.find_dt_del_modes
333: (p_effective_date => p_effective_date,
334: p_base_table_name => 'per_all_people_f',
335: p_base_key_column => 'person_id',
336: p_base_key_value => p_base_key_value,

Line 363: dt_api.find_dt_upd_modes

359: hr_utility.set_location('Entering:'||l_proc, 5);
360: --
361: -- Call the corresponding datetrack api
362: --
363: dt_api.find_dt_upd_modes
364: (p_effective_date => p_effective_date,
365: p_base_table_name => 'per_all_people_f',
366: p_base_key_column => 'person_id',
367: p_base_key_value => p_base_key_value,

Line 397: dt_api.get_object_version_number

393: -- Because we are updating a row we must get the next object
394: -- version number.
395: --
396: l_object_version_number :=
397: dt_api.get_object_version_number
398: (p_base_table_name => 'per_all_people_f',
399: p_base_key_column => 'person_id',
400: p_base_key_value => p_base_key_value);
401: --

Line 680: dt_api.validate_dt_mode

676: -- Validate the datetrack mode mode getting the validation start
677: -- and end dates for the specified datetrack operation.
678: --
679:
680: dt_api.validate_dt_mode
681: (p_effective_date => p_effective_date,
682: p_datetrack_mode => p_datetrack_mode,
683: p_base_table_name => 'per_all_people_f', -- for bug 7518991
684: p_base_key_column => 'person_id',