DBA Data[Home] [Help]

APPS.PAY_TEMPLATE_IVS dependencies on PAY_LINK_INPUT_VALUES_F

Line 80: PAY_LINK_INPUT_VALUES_F

76: The package pyusuiet.pkb does the same for earnings templates.
77:
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:

Line 112: Create SINGLE date-effective PAY_LINK_INPUT_VALUES_F row...lasting from

108: WHERE pel.element_link_id = l_element_link_id;
109:
110:
111: 1c. Then create appropriately date-effective link input value row...
112: Create SINGLE date-effective PAY_LINK_INPUT_VALUES_F row...lasting from
113: earliest (min) effective_start_date for element link...to latest (max)
114: eff end date of link...is this ideally the end of time? yes.
115: INSERT INTO pay_link_input_values_f (
116: link_input_value_id,

Line 115: INSERT INTO pay_link_input_values_f (

111: 1c. Then create appropriately date-effective link input value row...
112: Create SINGLE date-effective PAY_LINK_INPUT_VALUES_F row...lasting from
113: earliest (min) effective_start_date for element link...to latest (max)
114: eff end date of link...is this ideally the end of time? yes.
115: INSERT INTO pay_link_input_values_f (
116: link_input_value_id,
117: element_link_id,
118: input_value_id,
119: effective_start_date,

Line 286: Create SINGLE date-effective PAY_LINK_INPUT_VALUES_F row...lasting from

282: WHERE pel.element_link_id = l_element_link_id;
283:
284: /*
285: 1c. Then create appropriately date-effective link input value row...
286: Create SINGLE date-effective PAY_LINK_INPUT_VALUES_F row...lasting from
287: earliest (min) effective_start_date for element link...to latest (max)
288: eff end date of link...is this ideally the end of time? yes.
289: */
290:

Line 304: INSERT INTO pay_link_input_values_f (

300: p_input_val_id => p_input_value_id);
301:
302: if already_exists = 0 then
303:
304: INSERT INTO pay_link_input_values_f (
305: link_input_value_id,
306: element_link_id,
307: input_value_id,
308: effective_start_date,