eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HR_ENTRY_API dependencies on PAY_ELEMENT_ENTRY_VALUES_F

Line 127: -- the PAY_ELEMENT_ENTRIES_F or PAY_ELEMENT_ENTRY_VALUES_F tables. --

123: -- hr_entry_api.element_entry_changed PRIVATE FUNCTION --
124: -- --
125: -- DESCRIPTION --
126: -- Determines if the entry to be updated will cause a change on either --
127: -- the PAY_ELEMENT_ENTRIES_F or PAY_ELEMENT_ENTRY_VALUES_F tables. --
128: -- If the entry is going to cause an update against either the --
129: -- PAY_ELEMENT_ENTRIES_F or PAY_ELEMENT_ENTRY_VALUES_F attributes then the --
130: -- return code will be true. --
131: ------------------------------------------------------------------------------

Line 129: -- PAY_ELEMENT_ENTRIES_F or PAY_ELEMENT_ENTRY_VALUES_F attributes then the --

125: -- DESCRIPTION --
126: -- Determines if the entry to be updated will cause a change on either --
127: -- the PAY_ELEMENT_ENTRIES_F or PAY_ELEMENT_ENTRY_VALUES_F tables. --
128: -- If the entry is going to cause an update against either the --
129: -- PAY_ELEMENT_ENTRIES_F or PAY_ELEMENT_ENTRY_VALUES_F attributes then the --
130: -- return code will be true. --
131: ------------------------------------------------------------------------------
132: --
133: function element_entry_changed

Line 209: from pay_element_entry_values_f peev

205: --
206: Cursor select_entry_value is
207: select peev.input_value_id,
208: peev.screen_entry_value
209: from pay_element_entry_values_f peev
210: where peev.element_entry_id = p_element_entry_id
211: and p_driving_date
212: between peev.effective_start_date
213: and peev.effective_end_date;

Line 223: l_input_value_id pay_element_entry_values_f.input_value_id%TYPE;

219: l_loop_counter number := 1;
220: --
221: -- Cursor returning variables
222: --
223: l_input_value_id pay_element_entry_values_f.input_value_id%TYPE;
224: l_screen_entry_value pay_element_entry_values_f.screen_entry_value%TYPE;
225: --
226: -- Function error variables
227: --

Line 224: l_screen_entry_value pay_element_entry_values_f.screen_entry_value%TYPE;

220: --
221: -- Cursor returning variables
222: --
223: l_input_value_id pay_element_entry_values_f.input_value_id%TYPE;
224: l_screen_entry_value pay_element_entry_values_f.screen_entry_value%TYPE;
225: --
226: -- Function error variables
227: --
228: l_appid number := 801;

Line 237: -- then need to determine if any PAY_ELEMENT_ENTRY_VALUES_F are

233: --
234: -- Need to determine if the PAY_ELEMENT_ENTRIES_F table is being
235: -- updated with any new values.
236: -- If No change is being made against PAY_ELEMENT_ENTRIES_F we
237: -- then need to determine if any PAY_ELEMENT_ENTRY_VALUES_F are
238: -- being updated.
239: -- However, if a change is going to place against the PAY_ELEMENT_ENTRIES_F
240: -- table then we don't need to check against a change to the
241: -- PAY_ELEMENT_ENTRY_VALUES_F table.

Line 241: -- PAY_ELEMENT_ENTRY_VALUES_F table.

237: -- then need to determine if any PAY_ELEMENT_ENTRY_VALUES_F are
238: -- being updated.
239: -- However, if a change is going to place against the PAY_ELEMENT_ENTRIES_F
240: -- table then we don't need to check against a change to the
241: -- PAY_ELEMENT_ENTRY_VALUES_F table.
242: --
243: if g_debug then
244: hr_utility.set_location(l_proc_func_name, 5);
245: end if;

Line 454: -- see if any of the PAY_ELEMENT_ENTRY_VALUES_F are to be

450: end;
451: --
452: -- If the entry record to be updated is not updating any of
453: -- the PAY_ELEMENT_ENTRIES_F attributes then we must check to
454: -- see if any of the PAY_ELEMENT_ENTRY_VALUES_F are to be
455: -- updated.
456: --
457: if (l_check_entry_values = 'Y') then
458: --

Line 461: -- match the PAY_ELEMENT_ENTRY_VALUES_F.

457: if (l_check_entry_values = 'Y') then
458: --
459: -- for each entry value ensure that the input_value_id and
460: -- screen_entry_value from the respective pl/sql tables
461: -- match the PAY_ELEMENT_ENTRY_VALUES_F.
462: --
463: open select_entry_value;
464: while (NOT l_entry_changed) loop
465: --

Line 495: -- As the screen_entry_value attribute of PAY_ELEMENT_ENTRY_VALUES_F

491: if ((p_input_value_id_tbl(l_loop_counter) = l_input_value_id) and
492: (nvl(p_entry_value_tbl(l_loop_counter),hr_api.g_varchar2) <>
493: nvl(l_screen_entry_value,hr_api.g_varchar2))) then
494: --
495: -- As the screen_entry_value attribute of PAY_ELEMENT_ENTRY_VALUES_F
496: -- is going to be updated set the returning function code to true.
497: --
498: l_entry_changed := true;
499: exit inner_loop;

Line 1384: from pay_element_entry_values_f eev,

1380: p_input_value_id13,'SET',
1381: p_input_value_id14,'SET',
1382: p_input_value_id15,'SET',
1383: 'NOT_SET') entry_specified
1384: from pay_element_entry_values_f eev,
1385: pay_element_entries_f ee,
1386: pay_input_values_f piv,
1387: pay_element_types_f et
1388: where ee.element_entry_id = p_element_entry_id

Line 1780: from pay_element_entry_values_f eev,

1776: et.input_currency_code,
1777: piv.mandatory_flag,
1778: eev.screen_entry_value peev_default_value,
1779: eev.screen_entry_value
1780: from pay_element_entry_values_f eev,
1781: pay_element_entries_f ee,
1782: pay_input_values_f piv,
1783: pay_element_types_f et
1784: where ee.element_entry_id = p_element_entry_id