APPS.PQP_COPY_UDT dependencies on PAY_USER_COLUMN_INSTANCES_PKG

Line 329: -- However, pay_user_column_instances_pkg.insert_row always

325: Loop -- 2
326:
327: -- Bugfix : 2257831
328: -- Don't create a new PUR Id if its a datetrack changed row
329: -- However, pay_user_column_instances_pkg.insert_row always
330: -- creates a new PUCI Id, so we will first insert a new row
331: -- and then update it with the PUCI Id of the previous row.
332: -- Disadvantage of this approach will be the wasting
333: -- of sequence values

Line 345: pay_user_column_instances_pkg.insert_row

341: -- For the current USER_ROW_ID, find the corresponding new USER_ROW_ID
342: l_new_pur_id := get_new_pur_id(p_curr_pur_id => r_user_ci.user_row_id);
343:
344: -- Insert into PAY_USER_COLUMN_INSTANCES_F
345: pay_user_column_instances_pkg.insert_row
346: (p_rowid => l_row_id -- IN OUT
347: ,p_user_column_instance_id => l_new_puci_id -- IN OUT
348: ,p_effective_start_date => r_user_ci.effective_start_date
349: ,p_effective_end_date => r_user_ci.effective_end_date

Line 367: pay_user_column_instances_pkg.update_row

363: ELSE
364:
365: -- Update the newly inserted row with the PUCI Id of previous row
366: -- l_row_id stores the ROWID of the newly inserted row
367: pay_user_column_instances_pkg.update_row
368: (p_rowid => l_row_id -- IN, used to update row
369: ,p_user_column_instance_id => l_prev_new_puci_id
370: ,p_effective_start_date => r_user_ci.effective_start_date
371: ,p_effective_end_date => r_user_ci.effective_end_date