APPS.PAY_PUR_SHD dependencies on DT_API

Line 157: dt_api.find_dt_upd_modes

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

Line 191: dt_api.find_dt_del_modes

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

Line 227: dt_api.get_object_version_number

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

Line 349: dt_api.validate_dt_mode

345: --
346: -- Validate the datetrack mode mode getting the validation start
347: -- and end dates for the specified datetrack operation.
348: --
349: dt_api.validate_dt_mode
350: (p_effective_date => p_effective_date
351: ,p_datetrack_mode => p_datetrack_mode
352: ,p_base_table_name => 'pay_user_rows_f'
353: ,p_base_key_column => 'user_row_id'