APPS.PAY_LIV_BUS dependencies on DT_API

Line 303: NOT (dt_api.check_min_max_dates

299: ,p_argument_value => p_validation_end_date
300: );
301: --
302: If ((nvl(p_input_value_id, hr_api.g_number) <> hr_api.g_number) and
303: NOT (dt_api.check_min_max_dates
304: (p_base_table_name => 'pay_input_values_f'
305: ,p_base_key_column => 'INPUT_VALUE_ID'
306: ,p_base_key_value => p_input_value_id
307: ,p_from_date => p_validation_start_date

Line 315: NOT (dt_api.check_min_max_dates

311: hr_multi_message.add
312: (p_associated_column1 => pay_liv_shd.g_tab_nam || '.INPUT_VALUE_ID');
313: End If;
314: If ((nvl(p_element_link_id, hr_api.g_number) <> hr_api.g_number) and
315: NOT (dt_api.check_min_max_dates
316: (p_base_table_name => 'pay_element_links_f'
317: ,p_base_key_column => 'ELEMENT_LINK_ID'
318: ,p_base_key_value => p_element_link_id
319: ,p_from_date => p_validation_start_date

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

358: -- Processing continues.
359: --
360: -- Post Failure:
361: -- If a row exists by determining the returning Boolean value from the
362: -- generic dt_api.rows_exist function then we must supply an error via
363: -- the use of the local exception handler l_rows_exist.
364: --
365: -- Developer Implementation Notes:
366: -- This procedure should not need maintenance unless the HR Schema model