APPS.PER_REI_SHD dependencies on DT_API

Line 205: dt_api.find_dt_upd_modes

201: hr_utility.set_location('Entering:'||l_proc, 5);
202: --
203: -- Call the corresponding datetrack api
204: --
205: dt_api.find_dt_upd_modes
206: (p_effective_date => p_effective_date
207: ,p_base_table_name => 'per_contact_extra_info_f'
208: ,p_base_key_column => 'contact_extra_info_id'
209: ,p_base_key_value => p_base_key_value

Line 239: dt_api.find_dt_del_modes

235: hr_utility.set_location('Entering:'||l_proc, 5);
236: --
237: -- Call the corresponding datetrack api
238: --
239: dt_api.find_dt_del_modes
240: (p_effective_date => p_effective_date
241: ,p_base_table_name => 'per_contact_extra_info_f'
242: ,p_base_key_column => 'contact_extra_info_id'
243: ,p_base_key_value => p_base_key_value

Line 275: dt_api.get_object_version_number

271: -- Because we are updating a row we must get the next object
272: -- version number.
273: --
274: l_object_version_number :=
275: dt_api.get_object_version_number
276: (p_base_table_name => 'per_contact_extra_info_f'
277: ,p_base_key_column => 'contact_extra_info_id'
278: ,p_base_key_value => p_base_key_value
279: );

Line 459: dt_api.validate_dt_mode

455: --
456: -- Validate the datetrack mode mode getting the validation start
457: -- and end dates for the specified datetrack operation.
458: --
459: dt_api.validate_dt_mode
460: (p_effective_date => p_effective_date
461: ,p_datetrack_mode => p_datetrack_mode
462: ,p_base_table_name => 'per_contact_extra_info_f'
463: ,p_base_key_column => 'contact_extra_info_id'