APPS.BEN_PTP_SHD dependencies on DT_API

Line 206: dt_api.find_dt_del_modes

202: --
203: --
204: -- Call the corresponding datetrack api
205: --
206: dt_api.find_dt_del_modes
207: (p_effective_date => p_effective_date,
208: p_base_table_name => 'ben_pl_typ_f',
209: p_base_key_column => 'pl_typ_id',
210: p_base_key_value => p_base_key_value,

Line 237: dt_api.find_dt_upd_modes

233: hr_utility.set_location('Entering:'||l_proc, 5);
234: --
235: -- Call the corresponding datetrack api
236: --
237: dt_api.find_dt_upd_modes
238: (p_effective_date => p_effective_date,
239: p_base_table_name => 'ben_pl_typ_f',
240: p_base_key_column => 'pl_typ_id',
241: p_base_key_value => p_base_key_value,

Line 271: dt_api.get_object_version_number

267: -- Because we are updating a row we must get the next object
268: -- version number.
269: --
270: l_object_version_number :=
271: dt_api.get_object_version_number
272: (p_base_table_name => 'ben_pl_typ_f',
273: p_base_key_column => 'pl_typ_id',
274: p_base_key_value => p_base_key_value);
275: --

Line 427: dt_api.validate_dt_mode

423: --
424: -- Validate the datetrack mode mode getting the validation start
425: -- and end dates for the specified datetrack operation.
426: --
427: dt_api.validate_dt_mode
428: (p_effective_date => p_effective_date,
429: p_datetrack_mode => p_datetrack_mode,
430: p_base_table_name => 'ben_pl_typ_f',
431: p_base_key_column => 'pl_typ_id',