APPS.BEN_ESP_BUS dependencies on DT_API

Line 254: If (dt_api.validate_dt_upd_mode(p_datetrack_mode => p_datetrack_mode)) then

250: p_argument_value => p_datetrack_mode);
251: --
252: -- Only perform the validation if the datetrack update mode is valid
253: --
254: If (dt_api.validate_dt_upd_mode(p_datetrack_mode => p_datetrack_mode)) then
255: --
256: --
257: -- Ensure the arguments are not null
258: --

Line 270: NOT (dt_api.check_min_max_dates

266: p_argument => 'validation_end_date',
267: p_argument_value => p_validation_end_date);
268: --
269: If ((nvl(p_eligy_prfl_id, hr_api.g_number) <> hr_api.g_number) and
270: NOT (dt_api.check_min_max_dates
271: (p_base_table_name => 'ben_eligy_prfl_f',
272: p_base_key_column => 'eligy_prfl_id',
273: p_base_key_value => p_eligy_prfl_id,
274: p_from_date => p_validation_start_date,

Line 280: NOT (dt_api.check_min_max_dates

276: l_table_name := 'ben_eligy_prfl_f';
277: Raise l_integrity_error;
278: End If;
279: If ((nvl(p_special_ceiling_step_id, hr_api.g_number) <> hr_api.g_number) and
280: NOT (dt_api.check_min_max_dates
281: (p_base_table_name => 'per_spinal_point_steps_f',
282: p_base_key_column => 'step_id',
283: p_base_key_value => p_special_ceiling_step_id,
284: p_from_date => p_validation_start_date,

Line 334: -- generic dt_api.rows_exist function then we must supply an error via

330: -- Processing continues.
331: --
332: -- Post Failure:
333: -- If a row exists by determining the returning Boolean value from the
334: -- generic dt_api.rows_exist function then we must supply an error via
335: -- the use of the local exception handler l_rows_exist.
336: --
337: -- Developer Implementation Notes:
338: -- This procedure should not need maintenance unless the HR Schema model