APPS.PAY_TEMPLATE_IVS dependencies on PAY_RUN_RESULT_VALUES

Line 82: PAY_RUN_RESULT_VALUES

78: The new New_Input_Value API needs to retrofit [date-effective] rows in
79: the following tables:
80: PAY_LINK_INPUT_VALUES_F
81: PAY_ELEMENT_ENTRY_VALUES_F
82: PAY_RUN_RESULT_VALUES
83: NOTE: These are the rows created for and by payroll runs.
84:
85:
86: IV. ALGORITHM

Line 189: 3b. For each run result found in 3a, create PAY_RUN_RESULT_VALUES row...

185: AND prr.element_type_id = p_element_type_id -- ie. ele w/new iv.
186: ORDER BY prr.run_result_id;
187:
188:
189: 3b. For each run result found in 3a, create PAY_RUN_RESULT_VALUES row...
190: INSERT INTO pay_run_result_values (
191: run_result_id,
192: input_value_id,
193: result_value

Line 190: INSERT INTO pay_run_result_values (

186: ORDER BY prr.run_result_id;
187:
188:
189: 3b. For each run result found in 3a, create PAY_RUN_RESULT_VALUES row...
190: INSERT INTO pay_run_result_values (
191: run_result_id,
192: input_value_id,
193: result_value
194: )

Line 443: 3b. For each run result found in 3a, create PAY_RUN_RESULT_VALUES row...

439: OPEN get_results(p_element_type_id);
440: LOOP
441:
442: /*
443: 3b. For each run result found in 3a, create PAY_RUN_RESULT_VALUES row...
444: */
445:
446: FETCH get_results
447: INTO l_run_result_id;

Line 460: INSERT INTO pay_run_result_values (

456: p_input_val_id => p_input_value_id);
457:
458: if already_exists = 0 then
459:
460: INSERT INTO pay_run_result_values (
461: run_result_id,
462: input_value_id,
463: result_value
464: )