APPS.PAY_CAL_SHD dependencies on DT_API

Line 155: dt_api.find_dt_upd_modes

151: hr_utility.set_location('Entering:'||l_proc, 5);
152: --
153: -- Call the corresponding datetrack api
154: --
155: dt_api.find_dt_upd_modes
156: (p_effective_date => p_effective_date
157: ,p_base_table_name => 'pay_cost_allocations_f'
158: ,p_base_key_column => 'cost_allocation_id'
159: ,p_base_key_value => p_base_key_value

Line 189: dt_api.find_dt_del_modes

185: hr_utility.set_location('Entering:'||l_proc, 5);
186: --
187: -- Call the corresponding datetrack api
188: --
189: dt_api.find_dt_del_modes
190: (p_effective_date => p_effective_date
191: ,p_base_table_name => 'pay_cost_allocations_f'
192: ,p_base_key_column => 'cost_allocation_id'
193: ,p_base_key_value => p_base_key_value

Line 225: dt_api.get_object_version_number

221: -- Because we are updating a row we must get the next object
222: -- version number.
223: --
224: l_object_version_number :=
225: dt_api.get_object_version_number
226: (p_base_table_name => 'pay_cost_allocations_f'
227: ,p_base_key_column => 'cost_allocation_id'
228: ,p_base_key_value => p_base_key_value
229: );

Line 361: dt_api.validate_dt_mode

357: --
358: -- Validate the datetrack mode mode getting the validation start
359: -- and end dates for the specified datetrack operation.
360: --
361: dt_api.validate_dt_mode
362: (p_effective_date => p_effective_date
363: ,p_datetrack_mode => p_datetrack_mode
364: ,p_base_table_name => 'pay_cost_allocations_f'
365: ,p_base_key_column => 'cost_allocation_id'