APPS.BEN_SHR_SHD dependencies on BEN_SCHEDD_HRS_RT_F

Line 112: from ben_schedd_hrs_rt_f

108: shr_attribute28,
109: shr_attribute29,
110: shr_attribute30,
111: object_version_number
112: from ben_schedd_hrs_rt_f
113: where schedd_hrs_rt_id = p_schedd_hrs_rt_id
114: and p_effective_date
115: between effective_start_date and effective_end_date;
116: --

Line 185: from ben_schedd_hrs_rt_f t

181: l_parent_key_value1 number;
182: --
183: Cursor C_Sel1 Is
184: select t.vrbl_rt_prfl_id
185: from ben_schedd_hrs_rt_f t
186: where t.schedd_hrs_rt_id = p_base_key_value
187: and p_effective_date
188: between t.effective_start_date and t.effective_end_date;
189: --

Line 207: p_base_table_name => 'ben_schedd_hrs_rt_f',

203: -- Call the corresponding datetrack api
204: --
205: dt_api.find_dt_del_modes
206: (p_effective_date => p_effective_date,
207: p_base_table_name => 'ben_schedd_hrs_rt_f',
208: p_base_key_column => 'schedd_hrs_rt_id',
209: p_base_key_value => p_base_key_value,
210: p_parent_table_name1 => 'ben_vrbl_rt_prfl_f',
211: p_parent_key_column1 => 'vrbl_rt_prfl_id',

Line 241: p_base_table_name => 'ben_schedd_hrs_rt_f',

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

Line 274: (p_base_table_name => 'ben_schedd_hrs_rt_f',

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

Line 284: update ben_schedd_hrs_rt_f t

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

Line 370: from ben_schedd_hrs_rt_f

366: shr_attribute28,
367: shr_attribute29,
368: shr_attribute30,
369: object_version_number
370: from ben_schedd_hrs_rt_f
371: where schedd_hrs_rt_id = p_schedd_hrs_rt_id
372: and p_effective_date
373: between effective_start_date and effective_end_date
374: for update nowait;

Line 429: p_base_table_name => 'ben_schedd_hrs_rt_f',

425: --
426: dt_api.validate_dt_mode
427: (p_effective_date => p_effective_date,
428: p_datetrack_mode => p_datetrack_mode,
429: p_base_table_name => 'ben_schedd_hrs_rt_f',
430: p_base_key_column => 'schedd_hrs_rt_id',
431: p_base_key_value => p_schedd_hrs_rt_id,
432: p_parent_table_name1 => 'ben_vrbl_rt_prfl_f',
433: p_parent_key_column1 => 'vrbl_rt_prfl_id',

Line 466: hr_utility.set_message_token('TABLE_NAME', 'ben_schedd_hrs_rt_f');

462: -- The object is locked therefore we need to supply a meaningful
463: -- error message.
464: --
465: hr_utility.set_message(801, 'HR_7165_OBJECT_LOCKED');
466: hr_utility.set_message_token('TABLE_NAME', 'ben_schedd_hrs_rt_f');
467: hr_utility.raise_error;
468: When l_object_invalid then
469: --
470: -- The object doesn't exist or is invalid

Line 473: hr_utility.set_message_token('TABLE_NAME', 'ben_schedd_hrs_rt_f');

469: --
470: -- The object doesn't exist or is invalid
471: --
472: hr_utility.set_message(801, 'HR_7155_OBJECT_INVALID');
473: hr_utility.set_message_token('TABLE_NAME', 'ben_schedd_hrs_rt_f');
474: hr_utility.raise_error;
475: End lck;
476: --
477: -- ----------------------------------------------------------------------------