APPS.BEN_AVR_SHD dependencies on BEN_ACTY_VRBL_RT_F

Line 104: from ben_acty_vrbl_rt_f

100: avr_attribute28,
101: avr_attribute29,
102: avr_attribute30,
103: object_version_number
104: from ben_acty_vrbl_rt_f
105: where acty_vrbl_rt_id = p_acty_vrbl_rt_id
106: and p_effective_date
107: between effective_start_date and effective_end_date;
108: --

Line 180: from ben_acty_vrbl_rt_f t

176: --
177: Cursor C_Sel1 Is
178: select t.acty_base_rt_id,
179: t.vrbl_rt_prfl_id
180: from ben_acty_vrbl_rt_f t
181: where t.acty_vrbl_rt_id = p_base_key_value
182: and p_effective_date
183: between t.effective_start_date and t.effective_end_date;
184: --

Line 203: p_base_table_name => 'ben_acty_vrbl_rt_f',

199: -- Call the corresponding datetrack api
200: --
201: dt_api.find_dt_del_modes
202: (p_effective_date => p_effective_date,
203: p_base_table_name => 'ben_acty_vrbl_rt_f',
204: p_base_key_column => 'acty_vrbl_rt_id',
205: p_base_key_value => p_base_key_value,
206: p_parent_table_name1 => 'ben_acty_base_rt_f',
207: p_parent_key_column1 => 'acty_base_rt_id',

Line 240: p_base_table_name => 'ben_acty_vrbl_rt_f',

236: -- Call the corresponding datetrack api
237: --
238: dt_api.find_dt_upd_modes
239: (p_effective_date => p_effective_date,
240: p_base_table_name => 'ben_acty_vrbl_rt_f',
241: p_base_key_column => 'acty_vrbl_rt_id',
242: p_base_key_value => p_base_key_value,
243: p_correction => p_correction,
244: p_update => p_update,

Line 273: (p_base_table_name => 'ben_acty_vrbl_rt_f',

269: -- version number.
270: --
271: l_object_version_number :=
272: dt_api.get_object_version_number
273: (p_base_table_name => 'ben_acty_vrbl_rt_f',
274: p_base_key_column => 'acty_vrbl_rt_id',
275: p_base_key_value => p_base_key_value);
276: --
277: hr_utility.set_location(l_proc, 10);

Line 283: update ben_acty_vrbl_rt_f t

279: --
280: -- Update the specified datetrack row setting the effective
281: -- end date to the specified new effective end date.
282: --
283: update ben_acty_vrbl_rt_f t
284: set t.effective_end_date = p_new_effective_end_date,
285: t.object_version_number = l_object_version_number
286: where t.acty_vrbl_rt_id = p_base_key_value
287: and p_effective_date

Line 361: from ben_acty_vrbl_rt_f

357: avr_attribute28,
358: avr_attribute29,
359: avr_attribute30,
360: object_version_number
361: from ben_acty_vrbl_rt_f
362: where acty_vrbl_rt_id = p_acty_vrbl_rt_id
363: and p_effective_date
364: between effective_start_date and effective_end_date
365: for update nowait;

Line 420: p_base_table_name => 'ben_acty_vrbl_rt_f',

416: --
417: dt_api.validate_dt_mode
418: (p_effective_date => p_effective_date,
419: p_datetrack_mode => p_datetrack_mode,
420: p_base_table_name => 'ben_acty_vrbl_rt_f',
421: p_base_key_column => 'acty_vrbl_rt_id',
422: p_base_key_value => p_acty_vrbl_rt_id,
423: p_parent_table_name1 => 'ben_acty_base_rt_f',
424: p_parent_key_column1 => 'acty_base_rt_id',

Line 460: fnd_message.set_token('TABLE_NAME', 'ben_acty_vrbl_rt_f');

456: -- The object is locked therefore we need to supply a meaningful
457: -- error message.
458: --
459: fnd_message.set_name('PAY', 'HR_7165_OBJECT_LOCKED');
460: fnd_message.set_token('TABLE_NAME', 'ben_acty_vrbl_rt_f');
461: fnd_message.raise_error;
462: When l_object_invalid then
463: --
464: -- The object doesn't exist or is invalid

Line 467: fnd_message.set_token('TABLE_NAME', 'ben_acty_vrbl_rt_f');

463: --
464: -- The object doesn't exist or is invalid
465: --
466: fnd_message.set_name('PAY', 'HR_7155_OBJECT_INVALID');
467: fnd_message.set_token('TABLE_NAME', 'ben_acty_vrbl_rt_f');
468: fnd_message.raise_error;
469: End lck;
470: --
471: -- ----------------------------------------------------------------------------