[Home] [Help]
215: changed due to Fidelity issue. Now
216: the cursor does not check for Multi
217: ple wage plan codes across the
218: assignments of a person. It just
219: checks that each individual assgn-
220: ment should not be having more than
221: one wage plan code. It takes care
222: of only paid assignments.
223: 19-JUL-2000 ashgupta 40.14 1354144 Changed the SQL statement of
435: p_jurisdiction_context - Should the JURISDICTION_CODE context be set up
436: for the testing of the balance.
437:
438: Notes : This routine provides a way of coding explicit rules for
439: individual reports where they are different from the
440: standard selection criteria for the report type ie. in
441: NY state the selection of people in the 4th quarter is
442: different from the first 3.
443: */
603:
604: BEGIN
605: SELECT '1'
606: INTO l_resides_true
607: FROM dual
608: WHERE EXISTS (
609: SELECT '1'
610: FROM per_assignments_f paf,
611: per_addresses pad
1547: -- combination.
1548: --
1549: select pay_assignment_actions_s.nextval
1550: into lockingactid
1551: from dual;
1552: --
1553:
1554: SELECT pay_us_payroll_utils.get_parameter('TRANSFER_GRE',legislative_parameters)
1555: INTO l_transfer_gre_id
1902: l_flag varchar2(1);
1903:
1904: cursor c_chk_payroll_action is
1905: select 'Y'
1906: from dual
1907: where exists (select null
1908: from ff_archive_items fai
1909: where fai.context1 = p_payroll_action_id
1910: and archive_type = 'PPA'); /* Bug:2965887 */