[Home] [Help]
161: changed due to Fidelity issue. Now
162: the cursor does not check for Multi
163: ple wage plan codes across the
164: assignments of a person. It just
165: checks that each individual assgn-
166: ment should not be having more than
167: one wage plan code. It takes care
168: of only paid assignments.
169: 19-JUL-2000 ashgupta 40.14 1354144 Changed the SQL statement of
375: p_jurisdiction_context - Should the JURISDICTION_CODE context be set up
376: for the testing of the balance.
377:
378: Notes : This routine provides a way of coding explicit rules for
379: individual reports where they are different from the
380: standard selection criteria for the report type ie. in
381: NY state the selection of people in the 4th quarter is
382: different from the first 3.
383: */
539:
540: BEGIN
541: SELECT '1'
542: INTO l_resides_true
543: FROM dual
544: WHERE EXISTS (
545: SELECT '1'
546: FROM per_assignments_f paf,
547: per_addresses pad
1466: -- combination.
1467: --
1468: select pay_assignment_actions_s.nextval
1469: into lockingactid
1470: from dual;
1471: --
1472: -- insert into pay_assignment_actions.
1473: hr_nonrun_asact.insact(lockingactid,l_assignment_id,
1474: pactid,chunk,l_tax_unit_id);
1803: l_flag varchar2(1);
1804:
1805: cursor c_chk_payroll_action is
1806: select 'Y'
1807: from dual
1808: where exists (select null
1809: from ff_archive_items fai
1810: where fai.context1 = p_payroll_action_id
1811: and archive_type = 'PPA'); /* Bug:2965887 */