[Home] [Help]
37: hr_utility.set_message(801, 'HR_6153_ALL_PROCEDURE_FAIL');
38: hr_utility.set_message_token('PROCEDURE', l_proc);
39: hr_utility.set_message_token('STEP','5');
40: hr_utility.raise_error;
41: ElsIf (p_constraint_name = 'BEN_MTCHG_RT_FK1') Then
42: hr_utility.set_message(801, 'HR_6153_ALL_PROCEDURE_FAIL');
43: hr_utility.set_message_token('PROCEDURE', l_proc);
44: hr_utility.set_message_token('STEP','10');
45: hr_utility.raise_error;
122: mtr_attribute28,
123: mtr_attribute29,
124: mtr_attribute30,
125: object_version_number
126: from ben_mtchg_rt_f
127: where mtchg_rt_id = p_mtchg_rt_id
128: and p_effective_date
129: between effective_start_date and effective_end_date;
130: --
195: l_parent_key_value1 number;
196: --
197: Cursor C_Sel1 Is
198: select t.acty_base_rt_id
199: from ben_mtchg_rt_f t
200: where t.mtchg_rt_id = p_base_key_value
201: and p_effective_date
202: between t.effective_start_date and t.effective_end_date;
203: --
217: -- Call the corresponding datetrack api
218: --
219: dt_api.find_dt_del_modes
220: (p_effective_date => p_effective_date,
221: p_base_table_name => 'ben_mtchg_rt_f',
222: p_base_key_column => 'mtchg_rt_id',
223: p_base_key_value => p_base_key_value,
224: p_parent_table_name1 => 'ben_acty_base_rt_f',
225: p_parent_key_column1 => 'acty_base_rt_id',
251: -- Call the corresponding datetrack api
252: --
253: dt_api.find_dt_upd_modes
254: (p_effective_date => p_effective_date,
255: p_base_table_name => 'ben_mtchg_rt_f',
256: p_base_key_column => 'mtchg_rt_id',
257: p_base_key_value => p_base_key_value,
258: p_correction => p_correction,
259: p_update => p_update,
284: -- version number.
285: --
286: l_object_version_number :=
287: dt_api.get_object_version_number
288: (p_base_table_name => 'ben_mtchg_rt_f',
289: p_base_key_column => 'mtchg_rt_id',
290: p_base_key_value => p_base_key_value);
291: --
292: hr_utility.set_location(l_proc, 10);
294: --
295: -- Update the specified datetrack row setting the effective
296: -- end date to the specified new effective end date.
297: --
298: update ben_mtchg_rt_f t
299: set t.effective_end_date = p_new_effective_end_date,
300: t.object_version_number = l_object_version_number
301: where t.mtchg_rt_id = p_base_key_value
302: and p_effective_date
384: mtr_attribute28,
385: mtr_attribute29,
386: mtr_attribute30,
387: object_version_number
388: from ben_mtchg_rt_f
389: where mtchg_rt_id = p_mtchg_rt_id
390: and p_effective_date
391: between effective_start_date and effective_end_date
392: for update nowait;
443: --
444: dt_api.validate_dt_mode
445: (p_effective_date => p_effective_date,
446: p_datetrack_mode => p_datetrack_mode,
447: p_base_table_name => 'ben_mtchg_rt_f',
448: p_base_key_column => 'mtchg_rt_id',
449: p_base_key_value => p_mtchg_rt_id,
450: p_parent_table_name1 => 'ben_acty_base_rt_f',
451: p_parent_key_column1 => 'acty_base_rt_id',
480: -- The object is locked therefore we need to supply a meaningful
481: -- error message.
482: --
483: hr_utility.set_message(801, 'HR_7165_OBJECT_LOCKED');
484: hr_utility.set_message_token('TABLE_NAME', 'ben_mtchg_rt_f');
485: hr_utility.raise_error;
486: When l_object_invalid then
487: --
488: -- The object doesn't exist or is invalid
487: --
488: -- The object doesn't exist or is invalid
489: --
490: hr_utility.set_message(801, 'HR_7155_OBJECT_INVALID');
491: hr_utility.set_message_token('TABLE_NAME', 'ben_mtchg_rt_f');
492: hr_utility.raise_error;
493: End lck;
494: --
495: -- ----------------------------------------------------------------------------