[Home] [Help]
925: pay_tab(1) := 'PAY_US_CITY_TAX_INFO_F';
926: pay_tab(2) := 'PAY_US_COUNTY_TAX_INFO_F';
927: pay_tab(3) := 'PAY_US_STATE_TAX_INFO_F';
928: pay_tab(4) := 'PAY_US_FEDERAL_TAX_INFO_F';
929: pay_tab(5) := 'PAY_US_GARN_EXEMPTION_RULES_F';
930: pay_tab(6) := 'PAY_US_GARN_FEE_RULES_F';
931: pay_tab(7) := 'PAY_US_GARN_LIMIT_RULES_F';
932: pay_tab(8) := 'HR_REPORT_LOOKUPS';
933:
968: end loop;
969:
970: for ger_rec in ger loop
971: savepoint new_primary_key;
972: insert into PAY_US_GARN_EXEMPTION_RULES_F
973: (
974: MIN_WAGE_FACTOR,
975: PRORATION_RULE,
976: LAST_UPDATE_DATE,
1006: ger_rec.CREATED_BY,
1007: ger_rec.CREATION_DATE,
1008: ger_rec.EXEMPTION_RULE_ID,
1009: /* Since we have already deleted all rows from
1010: pay_us_garn_exemption_rules_f, there cannot be any conflict of ids. It is
1011: therefore safe to use the ids from the hr_s table. This will help in
1012: maintainig the correct ids for date-tracked rows. After inserting
1013: all the rows we will set the sequence to start at a value higher than the
1014: max value of the id in pay_us_garn_exemption_rules_f.
1010: pay_us_garn_exemption_rules_f, there cannot be any conflict of ids. It is
1011: therefore safe to use the ids from the hr_s table. This will help in
1012: maintainig the correct ids for date-tracked rows. After inserting
1013: all the rows we will set the sequence to start at a value higher than the
1014: max value of the id in pay_us_garn_exemption_rules_f.
1015: PAY_US_GARN_EXEMPTION_RULES_S.nextval, -- changes for nextval */
1016: ger_rec.EFFECTIVE_START_DATE,
1017: ger_rec.EFFECTIVE_END_DATE,
1018: ger_rec.GARN_CATEGORY,
1035: end loop;
1036:
1037: select max(exemption_rule_id)
1038: into l_max_val
1039: from pay_us_garn_exemption_rules_f;
1040:
1041: l_next_val := 0;
1042:
1043: /* consume sequence till there is no conflict */