eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HR_PAYMENTS dependencies on FND_DATE

Line 391: fnd_date.canonical_to_date(val_start_date)));

387: pay_payroll_actions pa
388: where pp.assignment_action_id = aa.assignment_action_id
389: and aa.payroll_action_id = pa.payroll_action_id
390: and pa.effective_date >=
391: fnd_date.canonical_to_date(val_start_date)));
392: --
393: -- A row returned means no pre-payments after the validation date...OK
394: --
395: return(true);

Line 441: and ppm.effective_end_date > fnd_date.canonical_to_date(val_start_date));

437: where not exists(
438: select 1
439: from pay_personal_payment_methods_f ppm
440: where ppm.org_payment_method_id = opm_id
441: and ppm.effective_end_date > fnd_date.canonical_to_date(val_start_date));
442: --
443: if dummy = 1 then
444: --
445: return(true);

Line 487: and pp.effective_end_date > fnd_date.canonical_to_date(val_start_date));

483: where not exists(
484: select 1
485: from pay_payrolls_f pp
486: where pp.default_payment_method_id = opm_id
487: and pp.effective_end_date > fnd_date.canonical_to_date(val_start_date));
488: --
489: if valid_del = 'Y' then
490: --
491: return(true);

Line 598: and fnd_date.canonical_to_date(val_start_date) between

594: from pay_payment_types ppt,
595: pay_org_payment_methods_f opm
596: where opm.org_payment_method_id = opm_id
597: and opm.payment_type_id = ppt.payment_type_id
598: and fnd_date.canonical_to_date(val_start_date) between
599: opm.effective_start_date and opm.effective_end_date;
600: --
601: -- Check the category. If it is 'MT' do the checks...
602: --

Line 661: and fnd_date.canonical_to_date(val_start_date) < ppm.effective_end_date

657: select 1
658: from pay_personal_payment_methods_f ppm
659: where ppm.assignment_id = assignment
660: and ppm.priority = in_priority
661: and fnd_date.canonical_to_date(val_start_date) < ppm.effective_end_date
662: and fnd_date.canonical_to_date(val_end_date) > ppm.effective_start_date);
663: --
664: -- See how we did
665: --

Line 662: and fnd_date.canonical_to_date(val_end_date) > ppm.effective_start_date);

658: from pay_personal_payment_methods_f ppm
659: where ppm.assignment_id = assignment
660: and ppm.priority = in_priority
661: and fnd_date.canonical_to_date(val_start_date) < ppm.effective_end_date
662: and fnd_date.canonical_to_date(val_end_date) > ppm.effective_start_date);
663: --
664: -- See how we did
665: --
666: if duplicate = 'N' then

Line 715: and pa.effective_date > fnd_date.canonical_to_date(val_start_date));

711: pay_pre_payments pp
712: where pp.personal_payment_method_id = ppm_id
713: and pp.assignment_action_id = aa.assignment_action_id
714: and aa.payroll_action_id = pa.payroll_action_id
715: and pa.effective_date > fnd_date.canonical_to_date(val_start_date));
716: --
717: -- If there is a row, then all is cool, but check anyhow to be defensive.
718: --
719: hr_utility.set_location('HR_PAYMENTS.CHECK_PP',2);