[Home] [Help]
136: ppm_information27,
137: ppm_information28,
138: ppm_information29,
139: ppm_information30
140: from pay_personal_payment_methods_f
141: where personal_payment_method_id = p_personal_payment_method_id
142: and p_effective_date
143: between effective_start_date and effective_end_date;
144: --
211: --
212: Cursor C_Sel1 Is
213: select t.org_payment_method_id,
214: t.assignment_id
215: from pay_personal_payment_methods_f t
216: where t.personal_payment_method_id = p_base_key_value
217: and p_effective_date
218: between t.effective_start_date and t.effective_end_date;
219: --
234: -- Call the corresponding datetrack api
235: --
236: dt_api.find_dt_del_modes
237: (p_effective_date => p_effective_date,
238: p_base_table_name => 'pay_personal_payment_methods_f',
239: p_base_key_column => 'personal_payment_method_id',
240: p_base_key_value => p_base_key_value,
241: p_parent_table_name1 => 'pay_org_payment_methods_f',
242: p_parent_key_column1 => 'org_payment_method_id',
273: -- Call the corresponding datetrack api
274: --
275: dt_api.find_dt_upd_modes
276: (p_effective_date => p_effective_date,
277: p_base_table_name => 'pay_personal_payment_methods_f',
278: p_base_key_column => 'personal_payment_method_id',
279: p_base_key_value => p_base_key_value,
280: p_correction => p_correction,
281: p_update => p_update,
306: -- version number.
307: --
308: l_object_version_number :=
309: dt_api.get_object_version_number
310: (p_base_table_name => 'pay_personal_payment_methods_f',
311: p_base_key_column => 'personal_payment_method_id',
312: p_base_key_value => p_base_key_value);
313: --
314: hr_utility.set_location(l_proc, 10);
316: --
317: -- Update the specified datetrack row setting the effective
318: -- end date to the specified new effective end date.
319: --
320: update pay_personal_payment_methods_f t
321: set t.effective_end_date = p_new_effective_end_date,
322: t.object_version_number = l_object_version_number
323: where t.personal_payment_method_id = p_base_key_value
324: and p_effective_date
424: ppm_information27,
425: ppm_information28,
426: ppm_information29,
427: ppm_information30
428: from pay_personal_payment_methods_f
429: where personal_payment_method_id = p_personal_payment_method_id
430: and p_effective_date
431: between effective_start_date and effective_end_date
432: for update nowait;
465: --
466: -- It is necessary to lock PAY_ORG_PAY_METHOD_USAGES_F for datetrack modes
467: -- that extend a PPM because return_effective_end_date needs to be ensure that
468: -- the usages are still valid when the record is valid. PAY_ORG_PAY_METHOD_USAGES_F
469: -- comes before PAY_PERSONAL_PAYMENT_METHODS_F in the HRMS lock ladder.
470: --
471: --
472: if p_datetrack_mode = 'DELETE_NEXT_CHANGE' or p_datetrack_mode = 'FUTURE_CHANGE'
473: then
476: end if;
477: --
478: -- We must select and lock the current row.
479: --
480: l_lock_table := 'pay_personal_payment_methods_f';
481: Open C_Sel1;
482: Fetch C_Sel1 Into g_old_rec;
483: If C_Sel1%notfound then
484: Close C_Sel1;
522: --
523: dt_api.validate_dt_mode
524: (p_effective_date => p_effective_date,
525: p_datetrack_mode => p_datetrack_mode,
526: p_base_table_name => 'pay_personal_payment_methods_f',
527: p_base_key_column => 'personal_payment_method_id',
528: p_base_key_value => p_personal_payment_method_id,
529: p_parent_table_name1 => 'pay_org_payment_methods_f',
530: p_parent_key_column1 => 'org_payment_method_id',
572: --
573: -- The object doesn't exist or is invalid
574: --
575: hr_utility.set_message(801, 'HR_7155_OBJECT_INVALID');
576: hr_utility.set_message_token('TABLE_NAME', 'pay_personal_payment_methods_f')
577: ;
578: hr_utility.raise_error;
579: End lck;
580: --