APPS.GHR_HISTORY_API dependencies on PAY_ELEMENT_ENTRIES_F

Line 617: l_element_entry_data pay_element_entries_f%rowtype;

613: l_asgei_data per_assignment_extra_info%rowtype;
614: l_asgn_data per_all_assignments_f%rowtype;
615: l_peopleei_data per_people_extra_info%rowtype;
616: l_element_entry_value_data pay_element_entry_values_f%rowtype;
617: l_element_entry_data pay_element_entries_f%rowtype;
618: l_posnei_data per_position_extra_info%rowtype;
619: l_peranalyses_data per_person_analyses%rowtype;
620: l_address_data per_addresses%rowtype;
621: l_position_data hr_all_positions_f%rowtype;

Line 924: from pay_element_entries_f

920:
921: cursor c3 (c_element_entry_id number) is
922: select
923: assignment_id
924: from pay_element_entries_f
925: where element_entry_id = c_element_entry_id;
926:
927: l_session_var g_session_var_type;
928: l_proc varchar2(30):='get_asgn_peop';

Line 1384: -- PAY_ELEMENT_ENTRIES_F, PER_PERSON_ANALYSES (ghr_history_api.g_eleent_table and g_perana_table)

1380: -- there were intervening records on the same date. So, re-apply the date-effective row from history.
1381: ghr_corr_canc_sf52.update_eleentval( p_hist_pre => l_eleevl_hist_data);
1382: end if;
1383: else
1384: -- PAY_ELEMENT_ENTRIES_F, PER_PERSON_ANALYSES (ghr_history_api.g_eleent_table and g_perana_table)
1385: -- need not be cascaded or updated with
1386: -- most recent values because they will only ever be inserted by non-correction sf52's. They
1387: -- will never be updated by non-correction sf52's. Correction's that update these tables
1388: -- are already handled correctly.