[Home] [Help]
17: l_proc varchar2(72) := g_package||'constraint_error';
18: --
19: Begin
20: --
21: If (p_constraint_name = 'AME_RULES_PK') Then
22: fnd_message.set_name('PAY', 'HR_6153_ALL_PROCEDURE_FAIL');
23: fnd_message.set_token('PROCEDURE', l_proc);
24: fnd_message.set_token('STEP','5');
25: fnd_message.raise_error;
54: ,security_group_id
55: ,rule_key
56: ,item_class_id
57: ,object_version_number
58: from ame_rules
59: where rule_id = p_rule_id
60: and ( p_effective_date
61: between start_date and nvl(end_date - ame_util.oneSecond,p_effective_date)
62: or
145: -- Update the specified datetrack row setting the effective
146: -- end date to the specified new effective end date. This query is modified to
147: -- account for rules with future rule dates
148: --
149: update ame_rules t
150: set t.end_date = p_new_end_date
151: ,t.last_updated_by = l_current_user_id
152: ,t.last_update_date = p_new_end_date
153: ,t.last_update_login = l_current_user_id
197: ,security_group_id
198: ,rule_key
199: ,item_class_id
200: ,object_version_number
201: from ame_rules
202: where rule_id = p_rule_id
203: and ( p_effective_date
204: between start_date and nvl(end_date - ame_util.oneSecond,p_effective_date)
205: or
291: -- The object is locked therefore we need to supply a meaningful
292: -- error message.
293: --
294: fnd_message.set_name('PAY', 'HR_7165_OBJECT_LOCKED');
295: fnd_message.set_token('TABLE_NAME', 'ame_rules');
296: fnd_message.raise_error;
297: End lck;
298: --
299: -- ----------------------------------------------------------------------------
351: -- get the next ovn
352: --
353: select nvl(max(t.object_version_number),0) + 1
354: into l_ovn
355: from ame_rules t
356: where t.rule_id = p_rule_id;
357: --
358: -- Return the new object_version_number.
359: --