APPS.BEN_VMR_SHD dependencies on BEN_VRBL_MTCHG_RT_F

Line 115: from ben_vrbl_mtchg_rt_f

111: vmr_attribute28,
112: vmr_attribute29,
113: vmr_attribute30,
114: object_version_number
115: from ben_vrbl_mtchg_rt_f
116: where vrbl_mtchg_rt_id = p_vrbl_mtchg_rt_id
117: and p_effective_date
118: between effective_start_date and effective_end_date;
119: --

Line 188: from ben_vrbl_mtchg_rt_f t

184: l_parent_key_value1 number;
185: --
186: Cursor C_Sel1 Is
187: select t.vrbl_rt_prfl_id
188: from ben_vrbl_mtchg_rt_f t
189: where t.vrbl_mtchg_rt_id = p_base_key_value
190: and p_effective_date
191: between t.effective_start_date and t.effective_end_date;
192: --

Line 210: p_base_table_name => 'ben_vrbl_mtchg_rt_f',

206: -- Call the corresponding datetrack api
207: --
208: dt_api.find_dt_del_modes
209: (p_effective_date => p_effective_date,
210: p_base_table_name => 'ben_vrbl_mtchg_rt_f',
211: p_base_key_column => 'vrbl_mtchg_rt_id',
212: p_base_key_value => p_base_key_value,
213: p_parent_table_name1 => 'ben_vrbl_rt_prfl_f',
214: p_parent_key_column1 => 'vrbl_rt_prfl_id',

Line 244: p_base_table_name => 'ben_vrbl_mtchg_rt_f',

240: -- Call the corresponding datetrack api
241: --
242: dt_api.find_dt_upd_modes
243: (p_effective_date => p_effective_date,
244: p_base_table_name => 'ben_vrbl_mtchg_rt_f',
245: p_base_key_column => 'vrbl_mtchg_rt_id',
246: p_base_key_value => p_base_key_value,
247: p_correction => p_correction,
248: p_update => p_update,

Line 277: (p_base_table_name => 'ben_vrbl_mtchg_rt_f',

273: -- version number.
274: --
275: l_object_version_number :=
276: dt_api.get_object_version_number
277: (p_base_table_name => 'ben_vrbl_mtchg_rt_f',
278: p_base_key_column => 'vrbl_mtchg_rt_id',
279: p_base_key_value => p_base_key_value);
280: --
281: hr_utility.set_location(l_proc, 10);

Line 287: update ben_vrbl_mtchg_rt_f t

283: --
284: -- Update the specified datetrack row setting the effective
285: -- end date to the specified new effective end date.
286: --
287: update ben_vrbl_mtchg_rt_f t
288: set t.effective_end_date = p_new_effective_end_date,
289: t.object_version_number = l_object_version_number
290: where t.vrbl_mtchg_rt_id = p_base_key_value
291: and p_effective_date

Line 376: from ben_vrbl_mtchg_rt_f

372: vmr_attribute28,
373: vmr_attribute29,
374: vmr_attribute30,
375: object_version_number
376: from ben_vrbl_mtchg_rt_f
377: where vrbl_mtchg_rt_id = p_vrbl_mtchg_rt_id
378: and p_effective_date
379: between effective_start_date and effective_end_date
380: for update nowait;

Line 435: p_base_table_name => 'ben_vrbl_mtchg_rt_f',

431: --
432: dt_api.validate_dt_mode
433: (p_effective_date => p_effective_date,
434: p_datetrack_mode => p_datetrack_mode,
435: p_base_table_name => 'ben_vrbl_mtchg_rt_f',
436: p_base_key_column => 'vrbl_mtchg_rt_id',
437: p_base_key_value => p_vrbl_mtchg_rt_id,
438: p_parent_table_name1 => 'ben_vrbl_rt_prfl_f',
439: p_parent_key_column1 => 'vrbl_rt_prfl_id',

Line 472: hr_utility.set_message_token('TABLE_NAME', 'ben_vrbl_mtchg_rt_f');

468: -- The object is locked therefore we need to supply a meaningful
469: -- error message.
470: --
471: hr_utility.set_message(801, 'HR_7165_OBJECT_LOCKED');
472: hr_utility.set_message_token('TABLE_NAME', 'ben_vrbl_mtchg_rt_f');
473: hr_utility.raise_error;
474: When l_object_invalid then
475: --
476: -- The object doesn't exist or is invalid

Line 479: hr_utility.set_message_token('TABLE_NAME', 'ben_vrbl_mtchg_rt_f');

475: --
476: -- The object doesn't exist or is invalid
477: --
478: hr_utility.set_message(801, 'HR_7155_OBJECT_INVALID');
479: hr_utility.set_message_token('TABLE_NAME', 'ben_vrbl_mtchg_rt_f');
480: hr_utility.raise_error;
481: End lck;
482: --
483: -- ----------------------------------------------------------------------------