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 386: fnd_date.canonical_to_date(val_start_date)));

382: pay_payroll_actions pa
383: where pp.assignment_action_id = aa.assignment_action_id
384: and aa.payroll_action_id = pa.payroll_action_id
385: and pa.effective_date >=
386: fnd_date.canonical_to_date(val_start_date)));
387: --
388: -- A row returned means no pre-payments after the validation date...OK
389: --
390: return(true);

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

432: where not exists(
433: select 1
434: from pay_personal_payment_methods_f ppm
435: where ppm.org_payment_method_id = opm_id
436: and ppm.effective_end_date > fnd_date.canonical_to_date(val_start_date));
437: --
438: if dummy = 1 then
439: --
440: return(true);

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

478: where not exists(
479: select 1
480: from pay_payrolls_f pp
481: where pp.default_payment_method_id = opm_id
482: and pp.effective_end_date > fnd_date.canonical_to_date(val_start_date));
483: --
484: if valid_del = 'Y' then
485: --
486: return(true);

Line 593: and fnd_date.canonical_to_date(val_start_date) between

589: from pay_payment_types ppt,
590: pay_org_payment_methods_f opm
591: where opm.org_payment_method_id = opm_id
592: and opm.payment_type_id = ppt.payment_type_id
593: and fnd_date.canonical_to_date(val_start_date) between
594: opm.effective_start_date and opm.effective_end_date;
595: --
596: -- Check the category. If it is 'MT' do the checks...
597: --

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

652: select 1
653: from pay_personal_payment_methods_f ppm
654: where ppm.assignment_id = assignment
655: and ppm.priority = in_priority
656: and fnd_date.canonical_to_date(val_start_date) < ppm.effective_end_date
657: and fnd_date.canonical_to_date(val_end_date) > ppm.effective_start_date);
658: --
659: -- See how we did
660: --

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

653: from pay_personal_payment_methods_f ppm
654: where ppm.assignment_id = assignment
655: and ppm.priority = in_priority
656: and fnd_date.canonical_to_date(val_start_date) < ppm.effective_end_date
657: and fnd_date.canonical_to_date(val_end_date) > ppm.effective_start_date);
658: --
659: -- See how we did
660: --
661: if duplicate = 'N' then

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

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