[Home] [Help]
304: p_argument_value => p_datetrack_mode);
305: --
306: -- Only perform the validation if the datetrack update mode is valid
307: --
308: If (dt_api.validate_dt_upd_mode(p_datetrack_mode => p_datetrack_mode)) then
309: --
310: --
311: -- Ensure the arguments are not null
312: --
320: p_argument => 'validation_end_date',
321: p_argument_value => p_validation_end_date);
322: --
323: If ((nvl(p_pl_id, hr_api.g_number) <> hr_api.g_number) and
324: NOT (dt_api.check_min_max_dates
325: (p_base_table_name => 'ben_pl_f',
326: p_base_key_column => 'pl_id',
327: p_base_key_value => p_pl_id,
328: p_from_date => p_validation_start_date,
330: l_table_name := 'ben_pl_f';
331: Raise l_integrity_error;
332: End If;
333: If ((nvl(p_plip_id, hr_api.g_number) <> hr_api.g_number) and
334: NOT (dt_api.check_min_max_dates
335: (p_base_table_name => 'ben_plip_f',
336: p_base_key_column => 'plip_id',
337: p_base_key_value => p_plip_id,
338: p_from_date => p_validation_start_date,
340: l_table_name := 'ben_plip_f';
341: Raise l_integrity_error;
342: End If;
343: If ((nvl(p_oipl_id, hr_api.g_number) <> hr_api.g_number) and
344: NOT (dt_api.check_min_max_dates
345: (p_base_table_name => 'ben_oipl_f',
346: p_base_key_column => 'oipl_id',
347: p_base_key_value => p_oipl_id,
348: p_from_date => p_validation_start_date,
395: -- Processing continues.
396: --
397: -- Post Failure:
398: -- If a row exists by determining the returning Boolean value from the
399: -- generic dt_api.rows_exist function then we must supply an error via
400: -- the use of the local exception handler l_rows_exist.
401: --
402: -- Developer Implementation Notes:
403: -- This procedure should not need maintenance unless the HR Schema model