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.PAY_PPM_BUS dependencies on PAY_PRE_PAYMENTS

Line 1367: -- and rows exist in PAY_PRE_PAYMENTS for PAY_PAYROLL_ACTION

1363: -- If any of the following cases are true then
1364: -- an application error will be raised and processing is terminated
1365: --
1366: -- a) If delete mode is DELETE (ie: set end date)
1367: -- and rows exist in PAY_PRE_PAYMENTS for PAY_PAYROLL_ACTION
1368: -- effective dates that are effective beyond the session date
1369: --
1370: -- b) If delete mode is ZAP (ie: remove all records)
1371: -- and rows exist in PAY_PRE_PAYMENTS

Line 1371: -- and rows exist in PAY_PRE_PAYMENTS

1367: -- and rows exist in PAY_PRE_PAYMENTS for PAY_PAYROLL_ACTION
1368: -- effective dates that are effective beyond the session date
1369: --
1370: -- b) If delete mode is ZAP (ie: remove all records)
1371: -- and rows exist in PAY_PRE_PAYMENTS
1372: --
1373: -- c) If delete mode is DELETE, the personal payment method is to a
1374: -- third party payee and the new end date is earlier than any element
1375: -- entry that references it.

Line 1394: -- check if rows exist in PAY_PRE_PAYMENTS for PAY_PAYROLL_ACTION

1390: --
1391: l_exists varchar2(1);
1392: l_proc varchar2(72) := g_package||'chk_delete';
1393: --
1394: -- check if rows exist in PAY_PRE_PAYMENTS for PAY_PAYROLL_ACTION
1395: -- effective dates that are effective beyond the session date
1396: cursor csr_date_eff is
1397: select null
1398: from pay_pre_payments ppy

Line 1398: from pay_pre_payments ppy

1394: -- check if rows exist in PAY_PRE_PAYMENTS for PAY_PAYROLL_ACTION
1395: -- effective dates that are effective beyond the session date
1396: cursor csr_date_eff is
1397: select null
1398: from pay_pre_payments ppy
1399: , pay_assignment_actions asa
1400: , pay_payroll_actions pra
1401: where p_personal_payment_method_id = ppy.personal_payment_method_id
1402: and ppy.assignment_action_id = asa.assignment_action_id

Line 1406: -- check if rows exist in PAY_PRE_PAYMENTS

1402: and ppy.assignment_action_id = asa.assignment_action_id
1403: and asa.payroll_action_id = pra.payroll_action_id
1404: and pra.effective_date > p_effective_date;
1405: --
1406: -- check if rows exist in PAY_PRE_PAYMENTS
1407: --
1408: cursor csr_del is
1409: select null
1410: from pay_pre_payments ppy

Line 1410: from pay_pre_payments ppy

1406: -- check if rows exist in PAY_PRE_PAYMENTS
1407: --
1408: cursor csr_del is
1409: select null
1410: from pay_pre_payments ppy
1411: where p_personal_payment_method_id = ppy.personal_payment_method_id;
1412: --
1413: procedure check_garnishment_delete is
1414: l_proc varchar2(72) := g_package||'check_garnishment_delete';

Line 1469: -- check if rows exist in PAY_PRE_PAYMENTS for PAY_PAYROLL_ACTION

1465: --
1466: hr_utility.set_location(l_proc, 2);
1467: --
1468: -- If delete mode is DELETE (ie: set end date) then
1469: -- check if rows exist in PAY_PRE_PAYMENTS for PAY_PAYROLL_ACTION
1470: -- effective dates that are effective beyond the session date
1471: --
1472: if p_datetrack_mode = 'DELETE' then
1473: open csr_date_eff;

Line 1489: -- check if rows exist in PAY_PRE_PAYMENTS

1485: --
1486: hr_utility.set_location(l_proc, 3);
1487: --
1488: -- If delete mode is ZAP (ie: remove all records) then
1489: -- check if rows exist in PAY_PRE_PAYMENTS
1490: --
1491: if p_datetrack_mode = 'ZAP' then
1492: open csr_del;
1493: fetch csr_del into l_exists;