[Home] [Help]
28: l_proc varchar2(72) := g_package||'constraint_error';
29: --
30: Begin
31: --
32: If (p_constraint_name = 'PER_CONTACT_EXTRA_INFO_FK1') Then
33: fnd_message.set_name('PAY', 'HR_6153_ALL_PROCEDURE_FAIL');
34: fnd_message.set_token('PROCEDURE', l_proc);
35: fnd_message.set_token('STEP','5');
36: fnd_message.raise_error;
33: fnd_message.set_name('PAY', 'HR_6153_ALL_PROCEDURE_FAIL');
34: fnd_message.set_token('PROCEDURE', l_proc);
35: fnd_message.set_token('STEP','5');
36: fnd_message.raise_error;
37: ElsIf (p_constraint_name = 'PER_CONTACT_EXTRA_INFO_FK2') Then
38: fnd_message.set_name('PAY', 'HR_6153_ALL_PROCEDURE_FAIL');
39: fnd_message.set_token('PROCEDURE', l_proc);
40: fnd_message.set_token('STEP','10');
41: fnd_message.raise_error;
127: ,request_id
128: ,program_application_id
129: ,program_id
130: ,program_update_date
131: from per_contact_extra_info_f
132: where contact_extra_info_id = p_contact_extra_info_id
133: and p_effective_date
134: between effective_start_date and effective_end_date;
135: --
203: -- Call the corresponding datetrack api
204: --
205: dt_api.find_dt_upd_modes
206: (p_effective_date => p_effective_date
207: ,p_base_table_name => 'per_contact_extra_info_f'
208: ,p_base_key_column => 'contact_extra_info_id'
209: ,p_base_key_value => p_base_key_value
210: ,p_correction => p_correction
211: ,p_update => p_update
237: -- Call the corresponding datetrack api
238: --
239: dt_api.find_dt_del_modes
240: (p_effective_date => p_effective_date
241: ,p_base_table_name => 'per_contact_extra_info_f'
242: ,p_base_key_column => 'contact_extra_info_id'
243: ,p_base_key_value => p_base_key_value
244: ,p_zap => p_zap
245: ,p_delete => p_delete
272: -- version number.
273: --
274: l_object_version_number :=
275: dt_api.get_object_version_number
276: (p_base_table_name => 'per_contact_extra_info_f'
277: ,p_base_key_column => 'contact_extra_info_id'
278: ,p_base_key_value => p_base_key_value
279: );
280: --
283: --
284: -- Update the specified datetrack row setting the effective
285: -- end date to the specified new effective end date.
286: --
287: update per_contact_extra_info_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.contact_extra_info_id = p_base_key_value
291: and p_effective_date
386: ,request_id
387: ,program_application_id
388: ,program_id
389: ,program_update_date
390: from per_contact_extra_info_f
391: where contact_extra_info_id = p_contact_extra_info_id
392: and p_effective_date
393: between effective_start_date and effective_end_date
394: for update nowait;
442: fnd_message.set_name('PAY', 'HR_7155_OBJECT_INVALID');
443: fnd_message.raise_error;
444: End If;
445: --
446: -- PER_CONTACT_EXTRA_INFO_F is a little bit different from the other datetrack tables.
447: -- The parent of this table is PER_ALL_PEOPLE_F, but does not have column "PERSON_ID".
448: -- So we need to derive PERSON_ID from PER_CONTACT_RELATIONSHIPS table to pass
449: -- it to validate_dt_mode.
450: --
458: --
459: dt_api.validate_dt_mode
460: (p_effective_date => p_effective_date
461: ,p_datetrack_mode => p_datetrack_mode
462: ,p_base_table_name => 'per_contact_extra_info_f'
463: ,p_base_key_column => 'contact_extra_info_id'
464: ,p_base_key_value => p_contact_extra_info_id
465: ,p_parent_table_name1 => 'per_all_people_f'
466: ,p_parent_key_column1 => 'person_id'
496: -- The object is locked therefore we need to supply a meaningful
497: -- error message.
498: --
499: fnd_message.set_name('PAY', 'HR_7165_OBJECT_LOCKED');
500: fnd_message.set_token('TABLE_NAME', 'per_contact_extra_info_f');
501: fnd_message.raise_error;
502: End lck;
503: --
504: -- ----------------------------------------------------------------------------